Better Accuracy in Field Maps with Trimble DA2

SeanNagy1

My company recently acquired the Trimble DA2 GNSS receiver to use with Field Maps and Survey123 for data collection. We did a test of accuracy by comparing points collected with Field Maps to actual surveyed points and in general the points were off by about 6" all in the east south east direction. I know our survey crews use PA83-SF with US Survey Foot units as their coordinate system. I believe the standard for ArcGIS online with basemaps uses the Web Mercator with meters as their unit. Is there a way to set Field Maps up to collect in PA83-SF so we don't need to worry about projections that might skew data? I would also prefer obtaining elevation information in feet instead of meters and currently have to use arcade to obtain the elevation at the MSL and then do a calculation into feet which doesn't auto populate the elevation field when bringing into CAD. I included the current Trimble Mobile Manager and Field Maps profile settings for reference.

Trimble Mobile Manager Settings.jpg

Field Maps Profile Settings.jpg

TracyGarrison

I am not familiar with PA83-SF but if that is NAD 83 Pennsylvania State Plane South Zone (2011 adjustment) and you have GNSS setup as GCS NAD 1983 2011 then there would not be any datum transformation because they are both based on the same datum "NAD 1983 2011 adjustment".

But, in order for this to work you need to have an ArcGIS Portal so that you can create your own basemap.  The basemap would have to be in the NAD 83 2011 Pennsylvania South Zone coordinate system andin survey feet.   Then when you collect the data with the DA2 the point saved will have the X,Y for that state plane zone in us ft.  The Z will be in Meters (sorry) and be from the Geoid18 CONUS that you set in your Trimble Mobile Manager.   

Use arcade to display the data in the portal var xpoint = geomertry($feature).z*3.28083333333 for z.

If you go into ArcGIS Pro you can add the Feature Service and add three fields N, E, Zmeter and use calculate Geometry using the appropriate  property for each field:  For the Field "Zmeter" the property would be point z coordinate but, this will be in meters.  Then create new field "Z" and calculate that field to be equal to Zmeter*3.280833333.   The N, and E fields would not need further calculations.