Record GPS position details in Collector: GPS ModePosition CoordinatesElevationNavigation InformationPosition Measure of QualityQuality Parameters Similar to available information in the GPS Position Window in ArcPad.
Thank you for submitting this idea. 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.
Scott - when these fields are added, are they populated automatically upon creating or updating a feature? Thank you.
My experience: If you use the GPS when collecting new points, the fields are populated automatically. If you "collect here" instead of using the GPS location, the fields are not populated. These fields are not updated if you move/update a feature.
Randy - thanks for the feedback. We are using an external GPS so I believe
most of the features will be created using the GPS location
The GPS metadata fields can be set up to display after collection. It is also possible (but probably not recommended) to set the fields up for editing, so you could manually add/edit data for existing features, but this data would not come directly from the GPS.
To build upon what Randy said, when the metadata fields are properly configured, a geometry coming from the GPS unit will populate these fields. I have not tested updating an existing feature, but if the geometry is coming from the GPS unit it should be consistent. If you see issues with the population of metadata fields, please let me know and we can dig into it further.
Scott- OK Thanks . I used this page as a guide for the fields:
Also, do we need to follow these procedures when connecting our external
GPS to an iPad?:
Thanks for the help
The metadata procedures will be necessary on any feature service you will be collecting this data with. All devices editing the service will behave in the same way. The fields listed out in your first link are recognized by Collector, which parses out the information as it comes from the GPS device and populates the fields. Based on this behavior, you are not required to add all of the metadata fields, only ones that you want to collect.
The steps outlined in your second link will be necessary to ensure Collector recognizes the external GPS receiver and uses information coming from it. Are you seeing that the steps outlined are not up to date, or confusing in some way?
Scott- thanks again.
Re. the GPS external receiver - I had not had a chance yet to go through
the steps so was just wondering; but they seem clear enough
Just note, as of last time I checked the Elevation values stored automatically by collector from a high accuracy GPS are ellipsoidal heights in metric, not orthometric heights in feet. Hopefully a future release of collector will include the Geoid vertical datum correction in the app, and the ability to pick units. Right now our elevation values get stored in Metric and are about 116 feet off before running the points through geoid 12B. We have abandoned use of collector until there is support for vertical datum transformation.
Dan- thanks, I was wondering about units for that field. Good to know.
Retrieving data ...