Troubleshooting the Export AIS to AIXM tool
このトピックは、ArcInfo にのみ適用されます。
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 ArcInfo, ArcGIS Data Interoperability, and Aeronautical Solution.
- The Aeronautical Tools toolbox is only available with the Aeronautical Solution, but you also need ArcGIS Data Interoperability.
- 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 anArcSDE geodatabase for SQL Server, use the ESRItoAIXM_SQLServer_Attribute schema mapper file. If you are using an ArcSDE geodatabase for Oracle, use the ESRItoAIXM_Oracle_Attribute schema mapper file. The schema mappers are found at <Install location>\ESRIAeronautical\Desktop10.0\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.
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.
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 other helpful tips are there to diagnose problems with exporting?
- 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.