Bug
| Bug-ID-Nummer | BUG-000125974 |
|---|---|
| Eingereicht | October 14, 2019 |
| Zuletzt geändert | April 2, 2025 |
| Gilt für | ArcGIS Aviation Charting |
| Gefunden in Version | 10.6.1 |
| Betriebssystem | Windows OS |
| Betriebssystemversion | 2016 64 Bit |
| Behoben in Version | 10.8.1 |
| Status | Fixed |
Workaround 1:
Use Create Aviation Geodatabase with the 18B Data Model option and give no optional projection. This loads the 18B as NAD83 Geographic. Follow up by using the Projections and Transformations\Batch Project script tool to set the HCS/VCS desired on the output feature datasets. Set the Output Workspace to the same data connection file as the input feature dataset's. This creates new feature datasets and feature classes with a '_1' appended to them. Once completed, delete the original feature datasets and rename all the '_1' feature data sets and feature classes to remove the '_1'. NOTE: Simply using the Define Projection tool does not reset the XY domain, and this is a problem if going from Degrees to Meters or Feet.
Workaround 2:
This appears to work with no failure if a file geodatabase is used. Use Create Aviation Geodatabase with the 18B Data Model option with a file geodatabase as the input and set the desired HCS/VCS Coordinate System. Once completed, export that schema to an XML workspace document. Then use the catalog window to manually import that XML workspace into the enterprise geodatabase. Follow up by manually setting versioning and archiving on the feature datasets, and the eTODVerticalStructure table. (PROPERTIES, PROPERTYFOLDERS and all 'PD_' tables should not be versioned).
Bug-ID: BUG-000125974
Software:
Unterstützung durch ArcGIS-Experten anfordern
Esri Support App herunterladen