Currently the GPS/GNSS standard metadata fields are only those that come from the GGA string. For serious surveyors wanting to collect their GPS positions repeatably and be able to check that the person collecting the data had the correct settings more metadata is needed.
The simplest example of this is recording the antenna height with each observation. The location provider settings allot for an "antenna height" to be entered when using an external receiver. Without the antenna height recorded for each observation as a field just like the rest of the metadata fields it is impossible to check the observation.
Also the location profile should have its three corresponding fields recorded; "GNSS Coordinate System", "Map Coordinate System", and "Datum Transformation". This is important for the vast majority of users as the basemap used for most web maps is in WGS 1984 Web Mercator Auxillary Sphere with the root 1984 datum, while most united state provided RTK gps correction networks are using a more recent version of NAD83 like NAD83 (ITRF 2011) for the basis of their state plane coordinate systems. To correctly collect these positions a datum transformation needs to be used as part of the location profile. In our case in southern Michigan that would mean we need to record fields as follows:
GNSS Coordinate System: GCS NAD 1983 2011 (EPSG 6318)
Map Coordinate System: WGS 1984 Web Mercator Auxillary Sphere (EPSG 3857)
Datum Transformation: ~WGS_1984_(ITRF08)_To_NAD_1983_2011
Because of the shift between the most current ITRF of NAD83 and WGS1984, if these collection settings are not correct, the positions collected on the feature service can be 3 feet off. Without knowing the location profile used during the data collection, there is no way of knowing if the positions were collected correctly or not. These should be simple things to incorporate for ESRI.
If you customize the base map you are using (import one to your GDB, then redefine the projection) you can avoid the headache of doing a transformation directly in your map. That said, your GNSS is already collecting in WGS84 anyway, and performing a local transformation in your data collector (this is how all receivers operate), as your CORS is almost guaranteed to be broadcasting in WGS84.
I've been debating how to handle this, myself, and it seems like the best solution is to maintain field collection in WGS84, then perform a localized transformation for desktop/admin use etc. This, however, then comes with the risks associated to transformation distortion. Not really a good solution however you look at it, unless maps act fully like a data collector and perform a localized transformation immediately.
But yeah, save a local base map copy, define the projection (it matches your map closely anyway), and roll on.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.