Hi all,
Wondering if anyone has information about this, or if it is worth suggesting as a possible feature to add.
I have configured an Arrow Gold+ with RTK for field data collection with Field Maps. In the Eos Tools Pro app, I selected the appropriate Geoid correction for my area.
However, when Field Maps logs data, it does not appear to access the orthometric elevation value calculated in Eos Tools Pro. Instead, the Altitude field (esrignss_altitude) appears to continue logging the ellipsoidal elevation (which in my area is usually a negative number, confusing users in the field).
While this page describes some workarounds that I have applied successfully, I am wondering if anyone has found more direct ways to populate the desired ortho elevation in field maps - e.g. to have that be the value sent to the Altitude field. The fact that an ortho height is sent to some part of the Field Maps feature makes me think it shouldn't be too hard to expose that height and send the value straight to an attribute field when collecting data, but I'm not sure how it is working under the hood.
Also - while the field calculation approaches described in that post yield values that generally seem consistent when I check them against ortho height calculations by hand, I noticed some points from a recent data collection effort where the relationship between the Altitude field and the calculated ortho height did not check out (maybe this was because some of the points were collected before the geoid model was applied in ETP?).
Additionally, I am wondering if there is any way to get the true orthometric elevation (the geometry Z value for a point feature) sent to the gnss metadata entries for each vertex in a line or polygon. The _gnss_metadata.json attachment that is automatically collected for each line and polygon feature includes metadata for each vertex in the feature, and esrignss_altitude is one of those pieces of metadata collected - but again, it continues to be ellipsoidal elevation even when a geoid model is applied in Eos Tools Pro. I have a script to make point features from the vertices of lines and polygons because it can be faster to cover a surface as a single feature (only enter attributes once) than as a set of points, and the script extracts metadata values to populate the point feature attributes - it would be ideal to be able to access the ortho heigh in the vertex metadata.
Thanks in advance for any insights, clarifications, or suggestions!
