Frequently Asked Questions
Explain the relation between AIXM5.1, AMXM, ARINC 816 and other GIS formats used in the context of Aerodrome Mapping data exchange.
The Aerodrome Mapping Exchange Schema (AMXM XML Schema) is an exchange format specification for AMDB as standardized by and dedicated to the EUROCAE/RTCA Aeronautical Databases WG44/SC217. It is an XML Schema implementation of the DO-291C/ED-119C AMXM UML model. The AMXM XML Schema uses a flattened feature/attribute representation that is derived from the AMXM UML Model using ISO19100/OGC standards.
ARINC 816, the "Embedded Interchange Format for Airport Mapping Database", is an open encoding format aimed at, but not limited to, AMDBs which are loaded into embedded avionic systems. The format builds on EUROCAE/RTCA AMDB requirements. ARINC 816 has additional data elements such as anchor points in support of map label placement and tessellated polygons. ARINC 816 specifies the use of projected coordinates and a binary encoding. This enables a reduction of the processing steps on-board the aircraft and enables a quick and efficient use of AMDBs.
The Aeronautical Information Exchange Model (AIXM) is an international exchange model for aeronautical data. It is designed to enable the management and distribution of AIM data in digital format. AIXM 5.1 covers both the content of Aeronautical Information Publications (AIP) and of the NOTAM information. AIXM has been extended in version 5.1 to cover ED-99B/DO-272B aerodrome mapping data concepts in a manner compliant with the AIXM 5.1 design principles. AIXM 5.1 is based on ISO19100/OGC standards. The corresponding AIXM 5.1 XML Schema is based on GML (Geography Mark-up Language) version 3.2 and can be used in conjunction with the OpenGIS Web Feature Service 2.0 (WFS2.0) for aeronautical data exchange. It is possible to provide with an AIXM 5.1 Digital NOTAM the data about availability of airport surfaces/facilities that can be then overlaid on top of an AMXM display.
The use of the AMXM UML Model facilitates the creation of a compliant custom GIS database schema. A frequently used format is shapefile (.shp).
The use and application of AIXM 5.1 XML Schema, AMXM XML Schema, ARINC 816, and/or other GIS formats depends on implementation considerations (requirements) and actual context within the overall data chain. In this context SWIM principles and standards are enablers of interoperability.
- aerodrome mapping data (AMD) as "Data collected for the purpose of compiling aerodrome mapping information."
- aerodrome mapping database (AMDB) as "A collection of aerodrome mapping data organized and arranged as a structured data set.", and also further points at the EUROCAE/RTCA requirements for further guidance.
ICAO standardisation context:
- AIXM5.1 can be used to provide AMD and other aeronautical data in accordance with ICAO Annex 14/15 SARPs.
- AMXM XML Schema can be used to provide AMDB in accordance with ICAO Annex 14/15 SARPs.
EUROCAE/RTCA standardisation context:
- AMXM XML Schema can be used to provide AMDB in accordance with DO-291C/ED-119C requirements.
On specific common data items, AMXM XML Schema data can be used as source format for AIXM 5.1 XML Schema data and reversely AIXM5.1 XML Schema data can be used as source format for AMXM XML Schema data. This requires a data transformation.
Which ICAO Annexes contain aerodrome mapping provisions and what is their relation?
ICAO differentiates aerodrome mapping data (AMD) from aerodrome mapping database (AMDB). The AMD & AMDB ICAO requirements are captured in ICAO Annex 14 Vol. 1 Chapter 2 and ICAO Annex 15 Chapter 11. The general approach is that AMD requirements are covered by ICAO Annex 14 and AMDB requirements are covered by ICAO Annex 15. The underlying logic is that the data requirements stem from ICAO Annex 14 whereas the data product requirements in terms of packaging (content and format) stem form ICAO Annex 15.