I would like to obtain latitude and longitude, but in RGF93 reference format (trough the SDK) ?
How to do it ?
I searched a bit and realized that RGF93 can be both a datum and/ or projection.
So these are essentially all flavors of RGF93: Spatial Reference List -- Spatial Reference
What we support right now is the geodetic datum RGF93 - so to get into the correct datum. You can find this if you search for EPSG Geodetic Parameter Registry code 6171.
What we do not support is the RGF93 projection - which looks like a UTM projection.
So when you ask for XYZ you ask for grid coordinates I guess - which mean you have an applied projection aka coordinate system. This is something we do not support today - so you would need to calculate the projection on your own/ apply a coordinate system.
best thing is to have a look into the CatalystFacade project available in the sample zip.
If you open the project you'll find two modules - Facade and FacadeDemo.
FacadeDemo shows how to use the Facade; as you are looking for a very specific feature you can directly start with the Facade implementation.
In the CatalystFacade.java class you'll find a
IDatumTransformationTimeDependent createTimeDependentTransformation(ISsiRTKSurvey ssiRtkSurvey, TargetReferenceFrame targetReferenceFrame)
This method currently allows to switch between 4 different reference frames - the most common ones (Facade only exposes the most wanted ones).
But if you look into the options for a
You will find a frame called 'RGF93v2'.
So in your software you need to create a
object and configure it to this:
The enum 'ReferenceFrame' lists all available frames - the list is also documented in the help file.
Note that you need to set the ReferenceFrameEpoch to Reference - which is the 0 epoch of the frame - in other words the creation epoch.
After defining your target system you also must use/ apply it during 'startSurvey'.
Note that - depending on how your clients work - you might also want to configure a source reference frame. A source reference frame is needed in case of RTK or VRS surveys which are not operate by Trimble. In those cases we can't auto-detect the source reference frame - so the frame broadcasted by the base station.
So typically TargetReferenceFrame and SourceReferenceFrame come in pairs - Target defines the output, source the input. Source can be auto detected in case of a Trimble VRS Now network, Trimble Correction Hub or Trimble RTX. In case of a custom NTRIP caster you need to define the source reference frame as well so we know what epoch the received coordinate is in.
Hope this gives a rough guideline. The best point to start is as mentioned the private IDatumTransformationTimeDependent createTimeDependentTransformation(ISsiRTKSurvey ssiRtkSurvey, TargetReferenceFrame targetReferenceFrame) in the CatalystFacade.java class. This method acts as base - but you need to implement the RGF93 frame which the facade does not implement in the default case. Then you need to check where the created object is used (in the startSurvey method) and do the same in your application.
I also changed the target reference frame to RGF93, and values appears to have changed from
to something like
However, I expected something like "6756xxx.xxx, 3274xxx.xxx" , in XYZ map projection.
Maybe I should rather go through "IPositionListener" and observations to get this ?
Okay, it seems to be a picky subject !
So, I will work on projection computing...
Thanks a lot for your support !
So we also have this on our roadmap - to improve the overall a) understanding and b) usability here including a certain toolset...
The more 'precise' a position is supposed to be the more things suddenly pop up that an application needs to configure and handle... Otherwise you have a precise position but in the wrong location
Retrieving data ...