We have been told that the ESRI software does not calculate the correction from HAE to MSL. We have also been told that people are, indeed, using this equipment configuration to do so. And it seems like it should be poosible.
Don,
Below are the instructions to convert the HAE to actual elevation transformation from the data obtained from high accuracy GPS using Collector. I have assumed the following:
Now lets get to the actual transformation of the 2D data stored in ArcGIS Online (AGOL) to 3D data with the correct elevation data.
Click on the Current XY box then select:
Geographic coordinate system > North America > USA and territories > NAD 1983 (2011)
Click on the Current Z box and select:
Vertical Coordinate System > Ellipsoidal-based > North America > NAD 1983 2011
Click OK
Geographic coordinate system > North America > USA and territories > NAD 1983
Vertical Coordinate System > North America > NAVD 1988
Select NVAD 1988 even if you want ftUS. It is not possible to directly translate to NAVD88 (height) (ftUS)
If you need to convert the elevation data to US Feet, continue with the following. If you only need elevation in meters skip this step. This step is only converting the NVAD 1988 in meters to NAVD88 (height) (ftUS)
Vertical Coordinate System > North America > NAVD88 (height) (ftUS)
One last step.
I hope this helps you with adding the elevation data to your data. As noted previously, please double check the coordinate system your GPS is running on. This is critical for accurate translation. You can also select a different output coordinate system if I assumed the incorrect system. For example we output to a projected coordinate system rather than a geographic system. So we set our Output Current XY to Projected coordinate system > State Plane > NAD 1983 (2011) (US Feet) > NAD 1983 (2011) StatePlane Ohio North FIPS 3401 (US Feet). This will return Northing, Easting and Elevation, rather than Lat, Long and Elevation.
Lance
I moved my reply to your new question here and will continue our dialog. Below was your last reply:
Don Rodgers @ Lance Cole on Apr 3, 2019 7:47 AMLance, thank you for your quick and thorough response. I can clearly see that your knowledge base and experience far exceeds mine, but I will try to keep up.In response to your follow-up questions:When I say NAD 83 I mean that the Seiler Rep who walked me through the Trimble R2/ArcGIS Collector setup had me enter NAD 83 2011 as the GNSS Coordinate system and as the "to" system in my Datum Transformation box in my Profile. All the data that our organization stores on our in-house databases is NAD_1983_StatePlane_Indiana_East_FIPS_1301_Feet.On the vertical data I ultimately want my data to be in US Feet.With respect to metadata fields what I have done is to add metadata fields to a published Feature Service Layer and then added that new Feature Service layer to my Web Map. I have attempted to Configure a feature service to store GPS metadata. The obstacle that I encountered is that the instructions indicate that I should add field names to my feature attribute table and these field names are longer than that field will accept.
Lance, thank you for your quick and thorough response. I can clearly see that your knowledge base and experience far exceeds mine, but I will try to keep up.
In response to your follow-up questions:
When I say NAD 83 I mean that the Seiler Rep who walked me through the Trimble R2/ArcGIS Collector setup had me enter NAD 83 2011 as the GNSS Coordinate system and as the "to" system in my Datum Transformation box in my Profile. All the data that our organization stores on our in-house databases is NAD_1983_StatePlane_Indiana_East_FIPS_1301_Feet.
On the vertical data I ultimately want my data to be in US Feet.
With respect to metadata fields what I have done is to add metadata fields to a published Feature Service Layer and then added that new Feature Service layer to my Web Map. I have attempted to Configure a feature service to store GPS metadata. The obstacle that I encountered is that the instructions indicate that I should add field names to my feature attribute table and these field names are longer than that field will accept.
I will update my original answer later tonight to reflect the additional information you just provided. The first step you need to complete is getting your Trimble R2 parried with collector and pushing the correct data to ArcGIS Online (AGOL) database that is configured for GNSS data. Please take a look at Record GPS metadata for Classic or Prepare for high-accuracy data collection.
It sounds like your Trimble unit is configured to use a geographic coordinate system of NAD 1983 (2011) and a ellipsoidal-based, vertical coordinate system also of NAD 1983 2011. This is common for this type of system. Once you have the data configured in your database, Collector will store the "Raw" GPS data from the unit in the Latitude, Longitude and Altitude fields for each point collected. What the process described above does is take that raw data in GCS_NAD_1983_2011 / VCS: NAD_1983_2011 and using the tool "ProjectZ" creates new feature class of 3D points in NAD_1983_StatePlane_Indiana_East_FIPS_1301_Feet / NAVD 1988 (meters). You then run a "Project" tool of the data to convert the NAVD 1988 in meters to US Feet and "Add XY Coordinates" to display the Northing, Easting and Elevation data in the attribute table.
Lance, it looks like I may need tab-by-tab navigation help to locate the Current ArcGIS Coordinate System Data on MyESRI.com
Don Rodgers
City of Greenfield
GIS Coordinator
On my.esri.com go to:
My Organizations > Downloads
Select the "View Downloads" button next to either ArcGIS Pro or ArcGIS Desktop
Scroll down to the Data and Content section
Click the Download button next to "ArcGIS Coordinate Systems Data"
Mine is showing the current version being 10.7.167057
Your my.esri.com page may be slightly different depending upon your licensing but this should get you close.
Lance, it appears that I may need a more basic level of instruction.
Beginning with "Open ArcGIS Pro and load the original AGOL data into a map." I started a new project in ArcPro. I added a file geodatabase feature class from another ArcPro project that I confirmed contained several features.
Next I right-clicked the name of the feature class that appeared in the Contents page and clicked Data>Export features. Then I clicked the Run button and received the empty output warning. Since it was a yellow warning and I did not know what else to do I ignored the warning and continued.
When I run the Project Z tool I get to the part where I confirm the X,Y and Z value fields and, as you probably anticipated, I only see the Object ID and Shape field choices. This indicates failure to me and I am now stuck.
I can make web map and collect points. It seems like I do not understand how to get point features into an AGOL file that I can add to my ArcPro project so I can then run the Project Z tool.
The workarounds that other users have posted here to transform from Height Above Ellipsoid to MSL elevations are appreciated, but it would really be nice if ESRI could include these transformations as a native part of Collector for ArcGIS functionality. MSL elevations are the industry standard, and Height Above Ellipsoid is almost useless unless you just need to compare relative elevation differences.
Has ESRI made any progress with this issue (using Collector and a centimeter R2 antenna to collect accurate Z coordinate data)? Without scientific workarounds? When I first asked this question I was told that some progress may be coming soon.
Has anyone had an error message "Unable to locate the attachment table for the input feature class" using the projectZ tool? The tool moves through several steps, but fails while running the maintain attachments script. After having issues with it, I disabled attachments on the AGO feature class but that didn't fix it.
I am adding the feature class to Pro, exporting it to a local GDB, and running the tool on that exported feature class using the guidelines from Lance Cole (thanks, by the way!). The only difference being that my data is in ITRF 2008.
I have also tried exporting it to a shapefile and deleting all but the essential fields to narrow down the issue, but it always fails on the maintain attachment step. I also tried turning off "maintain attachments" in the environments setting for projectZ.
Any help would be appreciated! I attached a screenshot of the error message.
Vertical transformations are still very much in our future plans for Collector. Although I cannot give you a specific date, we hope to have this in some form within the year.
Regards,
Colin
Is this still the case? Will this be part of the launch of Field Maps?
Ross Volkwein This is still on the roadmap, but will not be a part of the initial release of Field Maps later this month.
Hi Lance,
Thank you for the great explanation. I have collected 2 years of data and having the same problem converting the GPS Altitude value to MSL elevation.
I am using Trimble R2 with Collector App and I set the Collector's Location Profile as:
GNSS Coordinate System: GCS NAD 1983 2011
Map Coordinate System: WGS 1984 Web Mercator Auxiliary Sphere.
Datum Transformation: WGS_1984_(ITRF08)_To_NAD_1983_2011
I want my final data to be in NAD 1983 (2011) StatePlane New York East FIPS 3101 (US Feet). Can you please help?
Thank you
Any update from ESRI on if Field Maps has been updated to deal with vertical transformations?
Im using a Trimble DA2 Catalyst with Field Maps to collect survey data, and vertical accuracy is very important for our work. When we collect points in the field we are able to see the Ortho height measurements, but they do not get recorded to the attribute field. I ran through the Project Z process posted in this thread, but I am not able to get the elevations to match what was shown in the pop up in field maps. I have ensured my coordinate systems are all correct and have ran through the process several times but am still unable to get the right numbers. For example, the ortho height (m) shown below is 285.62, but when I run the Project Z tool I get 285.60. Is there any way to get more accurate results?
Signed in members can post, follow updates, and more. New here? Register a free account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.