AIXM Joins Smart Data Models: 7 Candidate Models for Aerodromes, Navaids, Airspace and Obstacles

Smart Data Models’ Candidates repository now includes a new candidate standard from aviation: AIXM, the Aeronautical Information Exchange Model of EUROCONTROL and the FAA. The new folder aixm holds 7 candidate models for the core of aeronautical information: aerodromes, runways, runway directions, radio navigation aids, waypoints, airspace and obstacles. AIXM is published under a BSD licence. Like every candidate, each model comes with a JSON Schema, an NGSI-LD @context and all four example serializations (NGSI-v2 and NGSI-LD, key-values and normalized), each validated against its schema.

About AIXM

AIXM is the global standard for exchanging aeronautical information in digital form: the content of the national Aeronautical Information Publications, aerodrome data, navaids, airspace, routes, procedures, obstacles and Digital NOTAM. It underpins the ICAO PANS-AIM data sets and is maintained by an international Change Control Board. AIXM 5.2 (January 2025), the version translated here, is a UML model with a GML 3.2 XML Schema of about 170 features. Every feature is temporal: its values live in TimeSlices with a validity period.

The models

Model What it describes Attributes
AirportHeliport Aerodrome or heliport: ICAO/IATA codes, reference point, elevation, operating hours, contacts 48
Runway Runway or FATO: dimensions, surface and pavement strength, contamination 30
RunwayDirection One direction of a runway (09L, 27R): bearings, touchdown zone, approach guidance 27
Navaid Radio navigation aid (VOR, DME, NDB, ILS…) and its equipment 29
DesignatedPoint Named waypoint used by routes and procedures 23
Airspace FIR, CTR, TMA, restricted and danger areas: class, vertical limits, geometry, activation 25
VerticalStructure Obstacle: buildings, masts, cranes, wind farms, with parts, heights and lighting 39

How it was translated

  • Generated from the XML Schema. A script reads the official AIXM 5.2 XSD (with the annotated edition for the definitions) and writes the schemas and contexts. Each @context term points to the class page in the AIXM 5.2 UML navigator.
  • One entity per feature, one TimeSlice at a time. The entity carries the current BASELINE TimeSlice, with its properties at entity level. validTime, interpretation, sequenceNumber, correctionNumber and featureLifetime are kept as attributes. A new baseline is an update of the entity, and its history goes to the NGSI-LD temporal API.
  • AIXM names, verbatim. The only renames are type to aixmType and location to aixmLocation, because both are reserved in NGSI-LD.
  • Relationships and nested objects. Links to other features (the runway of an aerodrome, the runway direction an ILS serves) are Relationships. AIXM <<object>> types (contacts, timesheets, airspace volumes, obstacle parts) keep their full structure. Code lists are enums that still accept AIXM’s OTHER: values, and measured values keep their unit and accuracy.
  • Ready for geo-queries. GML geometries are stored as GeoJSON. Five models also get an NGSI-LD location: the aerodrome reference point, the navaid and waypoint position, the airspace outline and the obstacle footprint.

Examples from the Donlon sample data set

The examples come from Donlon 2025, the official EUROCONTROL sample data set for a fictitious State in the middle of the Atlantic (BSD licence, never for operational use). They form one consistent set: Donlon International airport EADD, its runway 09L/27R and runway direction 09L, the ILS/DME OSL that serves it, the waypoint ABOLA, the DONLON TMA and the mast that hosts the OSL glide path. Donlon is AIXM 5.1.1, so the script converted it to 5.2 (for example, the separate accuracy elements became the accuracy of each value).

Points to review

  • Overlap with dataModel.Aeronautics (Airport), dataModel.ACRIS (airport facilities) and OSMAeroway in dataModel.OpenStreetMap.
  • Temporality: is one entity per feature, holding the current baseline, the right default? Temporary changes (TEMPDELTA, Digital NOTAM) are not covered yet.
  • Next features: navaid equipment (VOR, DME, ILS components), runway centreline points, taxiways and aprons, routes, organisations and units, and instrument procedures.

Browse the models, open an issue, or send a PR:
👉 https://github.com/smart-data-models/Candidates/tree/master/standards/aixm

Bookmark the permalink.

Comments are closed.