Available with Advanced license.
These suggestions are to help you diagnose issues you may have when importing. Any changes made to the workbench are your responsibility.
- What are the initial checks to diagnose problems when importing?
- What do I look for if there are errors and warnings in the log file?
- How do I know when features are not being imported?
- How do I know which features are not importing?
- What does the Unexpected Input dialog box convey?
- How do I check the new AIXM file before writing to the database?
- How do I improve performance on large datasets?
- Where can I find the log file?
- What are other helpful tips to diagnose importing problems?
What are the initial checks to diagnose problems when importing?
- 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.
- Ensure that your data is AIXM 4.5 (check Header information on the XML file).
- Look for ERRORS or WARNINGS in the log file and try to identify them to resolve them for import.
What do I look for if there are errors and warnings in the log file?
How do I know when features are not being imported?
Compare the number of features read to the number of features written in the log file and try to identify when features are not being imported.
For more information, see Workflow: Finding missing AIXM features when importing and visualizing data
How do I know which features are not importing?
Add visualizers within the workbench to help display how features are moving through the workbench and help determine why features are not importing.
For more information, see Visualizing AIXM data
What does the Unexpected Input dialog box convey?
If you receive the Unexpected Input dialog box, the features you are trying to input are valid AIXM features that will not be written into the database because there are no corresponding feature classes in the database for them.
For more information, see AIXM 4.5 features supported by the Import AIXM 4.5 to AIS tool
How do I check the new AIXM file before writing to the database?
How do I improve performance on large datasets?
Where can I find the log file?
What are other helpful tips to diagnose importing problems?
- 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.