In "Geometry Properties", it would be nice to collect Z values whiles using cloud services to store elevation for 3D data. Especially in regards to utilities data collection.
The ability to store z-values in Collector would be a HUGE improvement for me and my Public Works Department. If x and y can be stored, why not z? Along with storing z-values it would be great to have the option of loading a custom geoid into Collector to store those z-values. With the improvement to Collector at 10.4 to work with high accuracy receivers, I'm surprised that z-value was not a part of this release.
Has there been a solution to this issue? I'm running into this problem now trying to collect property monuments.
I know the original post was from some time back but wanted to share that the GPS audit fields you mention can now be configured with Collector app. At the 10.4 release of Collector for ArcGIS, we added support for high-accuracy GPS receivers. In addition to collecting high-accuracy geometry for your data, you can also collect GPS metadata as outlined here. To see more detail on how this GPS metadata will add to your existing data's schema, take a look at this link.
But still the GPS meta data is only for point. We do have a situation where we want to force our enumerators to collect plot boundary using GPS (not using on screen digitizing) and I thing enabling the storage of Z value for polygons would help.
The addition of the metadata fields are a nice enhancement. Is Esri planning on doing anything with hosted feature services as they relate to z-enabled feature classes? In other words, currently it doesn't work without a workaround.
Could ESRI Collector team give and update on this? How far away (months? years?) this could happen? Thanks. Collector for ArcGIS
Is it still impossible to collect altitude information within line geometries? Or has this change been implemented? if so, how can we collect altitude information within line geometries? Collector for ArcGIS
This would be a absolute game changer for underground utilities collection. Especially with the integration of high accuracy receivers (such as the Trimble R2) being paired with Collector.
The two biggest shortcomings of using Collector are that it doesn't do elevation or snapping. Considering ancient stuff like arcpad does these just fine, it's a real head-scratcher.
Great article on High Accuracy RTK and Elevations with Collector for ArcGIS
For those using Eos Arrow receivers, Eos has recently introduced support for Geoid Models (Geoid12B for the US and three Canadian geoid models in the first release). You can record orthometric heights directly in the field in Collector and Survey123 (for iOS and Android only for now). The January 2019 issue of Eos Newsletter explains the workflow on how to add the Z-Value in your map. The article is titled: How to Record Orthometric Heights in Collector v18.1.0 (Aurora) with Your Eos Arrow GNSS Receiver
For Android, still on Collector Classic, there is no Z-value support yet, but you can still record the orthometric height in the ESRI_GNSS_ALTITUDE field. As long as your setup is properly made as per this guide, and Eos Tools Pro elevation is configured for "Orthometric", orthometric heights will be recorded in the above field instead of the Ellipsoidal height.
Hope this helps !
Retrieving data ...