Wondering if there is anyone out there that is using ArcGIS Field Maps via Android with the RS2/RS2+.
I’d be interested to hear how it has worked out and if anyone has figured out a way to obtain the orthometric height directly as Field Maps will only store the ellipsoidal height
Hi Chris,
Hmm, I tried to search for more info about it. But the last updates that I found were saying that ArcGIS Filed Maps currently supports just the ellipsoidal heights. So the only thing I can come up with is using 3rd-party converters.
Why don’t you work in Emlid Flow? Do you lack any features in it?
Yes. Presently I have to post-process the data to get orthometric heights. The main reason we use Field Maps is to be able to access our AGOL datasets and feature layers all in one map. We can also update any one of them as required.
Appreciate your help.
I tried Field Maps with an RS+ and iPhone and it would not get coordinates from the RS+ no matter what. I never figured out how to prevent it from using the onboard GPS
You can only use Field Maps with Emlid products using an Android device not IOS.
Hi @daygeckoart,
I agree with @CRoss13. You can only integrate Reach devices with FieldMaps using an Android device. We’ve written a guide on how to integrate your Reach devices with ArcGIS Field Maps for Android.
Hi @CRoss13,
Yes, unfortunately, FieldMaps only shows height above the ellipsoid. As others have mentioned in the ArcGIS community, one workaround to access the Z value (orthometric height) is to use arcade expressions in ArcGIS Online or Map Viewer.
I’ve used ArcGIS Field Maps (AFM) on Android with an RS2.
The setups (hardware and editable feature service layer) and collection workflow are well documented elsewhere, but there’s no option for spatially referencing the necessary geoid height models for converting ellipsoid heights to orthometric heights.
So, if I really need to use AFM and I really need height, then I will disable the Z option and post-process my point data with ArcGIS Pro to extract values from the GEOID18 grids ( which I downloaded from the NGS at GEOID18 Downloads | GEOID | Data & Imagery | National Geodetic Survey ) and calculate a new height field. Be mindful that if you enable the Z option on your feature service layer before collecting data, your Z collected values (ellipsoid heights) will not change just because you calculated a new height field in your attribute table.
Maybe someone smarter than I can illuminate an Arcade-based workflow that handles the extraction/shift calculation stuff on the fly.
