My proposal for the EMLID team is to take into account the creation of a partition in the Reach RTK module memory with user access for introducing an optimal geoid model for the area of interest. This would avoid impractical ellipsoidal heights. The EMLID firmware could then be used in RTK measurements with m.s.l. heights (orto- or normal), so not only in the postprocessed option.
An example is Professional website - Geoids
(we deal with geoids as public domain, not corporate).
What are the suggestions of other users and the EMLID team?
PS.Similarly, one could solve the problem of reference systems and cartographic projections.
.
1 Like
This topic was automatically closed 100 days after the last reply. New replies are no longer allowed.