Available with Advanced license.
These suggestions are to help you diagnose issues you may have with the exporter. Any changes made to the workbench are your responsibility.
- What are the initial checks to diagnose problems when exporting?
- Which schema mapper file do I use while exporting?
- How do I know which features are not exporting?
- How do I check the new AIXM file before writing to the database?
- Where can I find the log file?
- What other helpful tips are there to diagnose problems with exporting?
What are the initial checks to diagnose problems when exporting?
- Make sure you have the appropriate licensing: ArcGIS for Desktop Advanced, ArcGIS Data Interoperability, and ArcGIS for Aviation: Charting.
- The Aviation Data Management Tools toolbox is only available with Aviation Charting, but you also need ArcGIS Data Interoperability extension for Desktop .
- Check that your parameters and versions are correct.
- Look for ERRORS or WARNINGS in the log file and try to identify them to resolve them for export.
Which schema mapper file do I use while exporting?
If you are exporting using a geodatabase in SQL Server, use the ESRItoAIXM_SQLServer_Attribute schema mapper file. If you are using a geodatabase in Oracle, use the ESRItoAIXM_Oracle_Attribute schema mapper file. The schema mappers are found at <Installation location>\Program Files\ArcGIS\AviationCharting\Desktop10.3\DataConversion\AIXM\SchemaMapper.
How do I know which features are not exporting?
Add visualizers within the workbench to help display how features are moving through the workbench and help determine why features are not exporting.
For more information, see Visualizing AIXM data
How do I check the new AIXM file before writing to the database?
Where can I find the log file?
What other helpful tips are there to diagnose problems with exporting?
- Verify that the Airspace and GeoBorder feature classes are m-enabled measures in the data model.
- Search the ArcGIS for Aviation forum for relevant case studies or examples of similar issues.