Skip to main content

Import AIXM 5.1 Message (Aviation Tools)

Summary

Imports Aeronautical Information Exchange Model (AIXM) version 5.1 data into an aviation geodatabase.

Note:

The AIXM format is commonly referred to by its acronym in the aviation industry rather than the full name of Aeronautical Information Exchange Model. Consequently, the tool name reflects the common usage of the acronym.

AIXM is a well-established information exchange format in the aviation domain, and importing data in this format may be needed to populate an AIS Charting or Esri Airports geodatabase.

Usage

  • An AIXM 5.1 file is commonly referred to as a message.

  • AIXM message properties that are missing or that contain a value of true for the xsi:nil attribute will be copied as Null values in the corresponding AIS schema fields in the target database. Any AIXM message properties containing an xsi:nil value of true and a nilReason value will be written to a related record in the nilReason table in the target database.

  • The optional Input Tables parameter will be populated by a list of either AIS or Esri Airports tables and feature classes in the selected workspace for which an AIXM feature type exists. Selecting any of these will import only the selected feature types. Leaving all of them unselected will import the full message.

  • To update a database with existing data, check the Update Existing Features parameter.

    By default, importing AIXM data is an append-only operation. When the Update Existing Features parameter is checked, the tool will update the attributes and geometry of features in the target geodatabase where values in the AIS Clientkey_Id or Esri Airports IDNUMBER fields match the gml:identifier values in the input AIXM message, while unmatched AIXM features are appended as new features in the target database. Missing AIXM fields will not update any existing values to Null in the target database, but any AIXM message properties containing an xsi:nil value of true and a nilReason value will populate the nilReason table.

  • The Set Fields To Null On Update parameter can be used to update fields to Null in the target database if the corresponding fields in the imported AIXM message are missing or contain xsi:nil="true" attributes. The nilReason table is populated for any nilReason values in the AIXM message. This option is only available if Update Existing Features is checked.

  • No datum transformation is performed by the tool. Input AIXM 5.1 geometry is expected to be expressed in either the EPSG:9057 or the OGC:CRS84 coordinate reference system.

  • The spatial reference of the Target AIS geodatabase should be geographic coordinate system WGS_1984 (G1762) WKID: 9057 Authority: EPSG.

    Note:

    If your data uses a different coordinate system, it is recommended that you project your data to WGS 1984 (G1762) WKID: 9057.

  • SQL Server Geography spatial type is not supported.

Parameters

Label Explanation Data type

Input AIXM 5.1 Message File

The input AIXM 5.1 message.

File

Target Geodatabase

The ArcGIS Aviation Charting or Esri Airports schema workspace where the AIXM message will be imported.

Workspace

Input Tables

(Optional)

The names of the tables used to restrict the feature types that will be imported.

String

Update Existing Features

(Optional)

Specifies whether existing features will be updated or new features will be inserted.

  • Checked—Existing features will be updated. Unmatched features are appended as new features.

  • Unchecked—Existing features will not be updated; all features are appended as new features. This is the default.

Boolean

Set Fields To Null On Update

(Optional)

Set fields to Null when updating existing features so the feature exactly reflects the contents of the update file instead of preserving existing data.

  • Checked—The tool updates existing fields to Null, preserving only the records from the input update file.

  • Unchecked—The tool will not update existing records to Null. This is the default.

Boolean

Custom Configuration File

(Optional)

A custom writer configuration file that can be used to extend the AIXM mappings to use custom mappings without having to overwrite the default configuration file. Custom mappings will be used in addition to the default mappings, with precedence given to the custom configuration file in any case of duplicate mappings.

File

Derived output

Label Explanation Data type

Updated Geodatabase

The updated workspace.

Workspace

Environments

This tool does not use any geoprocessing environments.

Licensing information

  • Basic: No
  • Standard: Requires Airports or ArcGIS Aviation Charting
  • Advanced: Requires Airports or ArcGIS Aviation Charting