Hello Esri Community,
I'm encountering persistent issues with getting vertical datum transformations (specifically those using Geoid models like Geoid18 or Geoid12B for CONUS) to work correctly in both ArcGIS Pro 3.x (initially 3.4.3, then 3.5) and ArcGIS Pro 2.4. I'm hoping to see if others have experienced similar problems or have insights.
The Core Problem:
Despite installing/reinstalling the "ArcGIS Coordinate Systems Data" multiple times for each respective ArcGIS Pro version, the arcpy.ListTransformations() function consistently returns an empty list when trying to find paths for transformations like NAD_1983_2011_To_NAVD88_CONUS_GEOID18_Height (in Pro 3.x) or NAD_1983_2011_To_NAVD88_CONUS_GEOID12B_Height (in Pro 2.4).
Consequently, when my Python script (or a manual Project tool test) attempts these vertical transformations, it either fails with ERROR 000365: Invalid geographic transformation or, in some cases (like with ArcMap 10.8.1 previously), it runs without error but applies a geoid separation of N=0, leading to incorrect orthometric heights.
Environment Details & What I've Found:
- ArcGIS Pro Versions Tested: Primarily 3.4.3, then upgraded to 3.5. Also tested on a separate ArcGIS Pro 2.4 installation.
- Coordinate Systems Data Installation:
- For Pro 3.x, I confirmed the "ArcGIS Pro Coordinate Systems Data" (version aligning with Pro, e.g., 3.4.x) was installed via the setup/modify options. I was able to locate g2018u0.bin in the per-user path: C:\Users\MyUserName\AppData\Local\Programs\ArcGIS\CoordinateSystemsData\pedata\vertical\north-america\us\geoid\.
- For Pro 2.4, after ensuring its Coordinate Systems Data was installed, I have seen a more populated pedata\vertical folder structure (including north-america, geoid, vertcon subfolders) in its expected installation path (e.g., C:\Program Files\ArcGIS\Pro\Resources\Pedata\vertical or a per-user equivalent if Pro 2.4 was installed that way). I also found a g2012bu0.bin file in a custom documents path, which I tried copying to Pro 2.4's pedata structure.
- Diagnostic Script Results:
- A Python diagnostic script using arcpy.ListTransformations() with appropriate source (NAD83(2011) ellipsoidal height meters) and target (NAVD88 orthometric height meters) coordinate systems for an extent in Tennessee consistently returns an empty list for both the Geoid18 transformation in Pro 3.x and the Geoid12B transformation in Pro 2.4.
Troubleshooting Steps Taken:
- Multiple attempts to install/reinstall/repair "ArcGIS Coordinate Systems Data" for each respective Pro version.
- Ensured I was selecting the North American / Vertical components during data installation.
- Verified the presence of some geoid grid files (e.g., g2018u0.bin for Pro 3.x, and saw a generally populated pedata\vertical for Pro 2.4 after its data install).
- Tested with simplified diagnostic scripts using arcpy.ListTransformations().
- Performed manual Project tool tests (which failed with ERROR 000365 or produced N=0).
- Tried different ArcGIS Pro versions (2.4, 3.4.3, 3.5).
- Attempted ArcGIS Pro profile resets (renaming ESRI folders in AppData).
- Performed a "Repair" on ArcGIS Pro installations.
My Key Questions for the Community:
- Has anyone else experienced arcpy.ListTransformations() failing to find standard vertical transformations (like CONUS Geoid18 or Geoid12B paths) even after confirming the "ArcGIS Coordinate Systems Data" appears to be installed and some geoid grid files (.bin or .gsb) are present in the pedata structure?
- Are there known issues or specific requirements for ArcGIS Pro (versions 2.4 or 3.x) to correctly register/use .bin geoid files (like g2018u0.bin or g2012bu0.bin) for the standard named transformations? Does it strictly require .gsb for these?
- Are there any other common reasons or less obvious configuration steps that might prevent ArcGIS Pro from recognizing or utilizing installed vertical transformation grid files, leading to ERROR 000365 or ListTransformations returning empty?
I'm trying to perform a standard ellipsoidal height to NAVD88 orthometric height conversion for GPS data collected in Tennessee, and I'm currently stuck due to the transformation paths not being found by ArcGIS Pro. Any advice or shared experiences would be greatly appreciated!
Thanks,
Orlando
