Troubleshooting the Import AIXM to AIS tool

This topic applies to ArcInfo only.

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?

  1. Make sure you have the appropriate licensing: ArcGIS ArcInfo, ArcGIS Data Interoperability, and Aeronautical Solution.
  2. The Aeronautical Tools toolbox is only available with the Aeronautical Solution, but you also need ArcGIS Data Interoperability.
  3. Check that your parameters and versions are correct.
  4. Ensure that your data is AIXM 4.5 (check Header information on the XML file).
  5. 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?

When there are errors and warnings, it is usually a data issue:

  • A related ORGAUTH is required for most feature classes.
  • Runways must have GeoLat and GeoLong attributes or they will not be imported correctly.

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.

Learn more about finding missing features

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.

Learn more about 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.

Learn more about the AIXM 4.5 features that are supported in the AIS database

How do I check the new AIXM file before writing to the database?

You can set the output to run to the visualizer rather than committing everything to your database.

How do I improve performance on large datasets?

Increase the Translation priority in the workbench, under Tools > Options > Runtime on the Spatial ETL window.

Where can I find the log file?

The default location for log files is C:\Documents and Settings\<user login>\Application Data\Safe Software\Interoperability\logs. However, you should note the location of the log file to access it after you close the tool dialog box in case it is a different location.

What are other helpful tips to diagnose importing problems?

  • Using a direct connection in ArcCatalog when available will improve performance.
  • Ensure Airspace and GeoBorder are m-enabled measures in the data model.
  • Search the Aeronautical Solution Forum for relevant case studies or examples of similar issues.