Skip to main content

We are looking into more low cost GNSS rover devices which unfortunately only measure ellipsoidal heights. To use those for mapping applications, we have to post-process those heights to receive orthometric heights (MSL). I have now received an official ascii grid file with the geoid undulation values. The distance between each point feature is between approx. 750 and 900 m:

undulationWould it be a viable approach to correct the height from ellips. heights to MSL by performing a nearest feature search (with the NeighborFinder

transformer) and then subtract the geoid undulation from the ellips. heights? And if this is a viable way to do so in order to get proper MSL heights, would it be smarter to rasterize the grid first in order to increase the performance (ultimately this should end up in a FME Server webhook upon submitted survey from ArcGIS Survey123 or ArcGIS Collector). What would be a suitable raster size if point spacing varies between 750 and 900 m?

You should read this article https://community.safe.com/s/article/creating-vertical-adjustment-grid-files-for-use-wi

You don't convert ellipsoid heights to orthometric by nearest neighbours, you use a spline interpolation to determine the undulations for your specific location using 16 points in your vecinity, so using a grid file and CSMapReprojector is the way to go.

In the article I mentioned you have workspaces to generate grd grid files from ASCII ones.

As for your FME Server implementation of the grid file check the install guide for more information on using them on the server side.


Reply