{"id":43859,"date":"2026-11-16T14:36:13","date_gmt":"2026-11-16T13:36:13","guid":{"rendered":"https:\/\/smartdatamodels.org\/?p=43859"},"modified":"2026-11-14T14:36:26","modified_gmt":"2026-11-14T13:36:26","slug":"aixm-joins-smart-data-models-7-candidate-models-for-aerodromes-navaids-airspace-and-obstacles","status":"publish","type":"post","link":"https:\/\/smartdatamodels.org\/index.php\/aixm-joins-smart-data-models-7-candidate-models-for-aerodromes-navaids-airspace-and-obstacles\/","title":{"rendered":"AIXM Joins Smart Data Models: 7 Candidate Models for Aerodromes, Navaids, Airspace and Obstacles"},"content":{"rendered":"<p>Smart Data Models\u2019 <a href=\"https:\/\/github.com\/smart-data-models\/Candidates\">Candidates repository<\/a> now includes a new candidate standard from aviation: <strong>AIXM, the Aeronautical Information Exchange Model<\/strong> of <strong>EUROCONTROL and the FAA<\/strong>. The new folder <strong><code>aixm<\/code><\/strong> holds <strong>7 candidate models<\/strong> for the core of aeronautical information: aerodromes, runways, runway directions, radio navigation aids, waypoints, airspace and obstacles. AIXM is published under a <strong>BSD licence<\/strong>. Like every candidate, each model comes with a JSON Schema, an NGSI-LD <code>@context<\/code> and all four example serializations (NGSI-v2 and NGSI-LD, key-values and normalized), each validated against its schema.<\/p>\n<h2 id=\"about-aixm\">About AIXM<\/h2>\n<p><a href=\"https:\/\/aixm.aero\/\">AIXM<\/a> 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. <a href=\"https:\/\/aixm.aero\/page\/aixm-52\">AIXM 5.2<\/a> (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 <em>TimeSlices<\/em> with a validity period.<\/p>\n<h2 id=\"the-models\">The models<\/h2>\n<table>\n<thead>\n<tr>\n<th>Model<\/th>\n<th>What it describes<\/th>\n<th>Attributes<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><code>AirportHeliport<\/code><\/td>\n<td>Aerodrome or heliport: ICAO\/IATA codes, reference point, elevation, operating hours, contacts<\/td>\n<td>48<\/td>\n<\/tr>\n<tr>\n<td><code>Runway<\/code><\/td>\n<td>Runway or FATO: dimensions, surface and pavement strength, contamination<\/td>\n<td>30<\/td>\n<\/tr>\n<tr>\n<td><code>RunwayDirection<\/code><\/td>\n<td>One direction of a runway (09L, 27R): bearings, touchdown zone, approach guidance<\/td>\n<td>27<\/td>\n<\/tr>\n<tr>\n<td><code>Navaid<\/code><\/td>\n<td>Radio navigation aid (VOR, DME, NDB, ILS\u2026) and its equipment<\/td>\n<td>29<\/td>\n<\/tr>\n<tr>\n<td><code>DesignatedPoint<\/code><\/td>\n<td>Named waypoint used by routes and procedures<\/td>\n<td>23<\/td>\n<\/tr>\n<tr>\n<td><code>Airspace<\/code><\/td>\n<td>FIR, CTR, TMA, restricted and danger areas: class, vertical limits, geometry, activation<\/td>\n<td>25<\/td>\n<\/tr>\n<tr>\n<td><code>VerticalStructure<\/code><\/td>\n<td>Obstacle: buildings, masts, cranes, wind farms, with parts, heights and lighting<\/td>\n<td>39<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2 id=\"how\">How it was translated<\/h2>\n<ul>\n<li><strong>Generated from the XML Schema.<\/strong> A script reads the official AIXM 5.2 XSD (with the annotated edition for the definitions) and writes the schemas and contexts. Each <code>@context<\/code> term points to the class page in the AIXM 5.2 UML navigator.<\/li>\n<li><strong>One entity per feature, one TimeSlice at a time.<\/strong> The entity carries the current BASELINE TimeSlice, with its properties at entity level. <code>validTime<\/code>, <code>interpretation<\/code>, <code>sequenceNumber<\/code>, <code>correctionNumber<\/code> and <code>featureLifetime<\/code> are kept as attributes. A new baseline is an update of the entity, and its history goes to the NGSI-LD temporal API.<\/li>\n<li><strong>AIXM names, verbatim.<\/strong> The only renames are <code>type<\/code> to <code>aixmType<\/code> and <code>location<\/code> to <code>aixmLocation<\/code>, because both are reserved in NGSI-LD.<\/li>\n<li><strong>Relationships and nested objects.<\/strong> Links to other features (the runway of an aerodrome, the runway direction an ILS serves) are Relationships. AIXM &lt;&lt;object&gt;&gt; types (contacts, timesheets, airspace volumes, obstacle parts) keep their full structure. Code lists are enums that still accept AIXM\u2019s <code>OTHER:<\/code> values, and measured values keep their unit and accuracy.<\/li>\n<li><strong>Ready for geo-queries.<\/strong> GML geometries are stored as GeoJSON. Five models also get an NGSI-LD <code>location<\/code>: the aerodrome reference point, the navaid and waypoint position, the airspace outline and the obstacle footprint.<\/li>\n<\/ul>\n<h2 id=\"examples\">Examples from the Donlon sample data set<\/h2>\n<p>The examples come from <a href=\"https:\/\/github.com\/aixm\/Donlon_2025\">Donlon 2025<\/a>, 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).<\/p>\n<h2 id=\"review\">Points to review<\/h2>\n<ul>\n<li><strong>Overlap<\/strong> with <code>dataModel.Aeronautics<\/code> (Airport), <code>dataModel.ACRIS<\/code> (airport facilities) and <code>OSMAeroway<\/code> in <code>dataModel.OpenStreetMap<\/code>.<\/li>\n<li><strong>Temporality<\/strong>: is one entity per feature, holding the current baseline, the right default? Temporary changes (TEMPDELTA, Digital NOTAM) are not covered yet.<\/li>\n<li><strong>Next features<\/strong>: navaid equipment (VOR, DME, ILS components), runway centreline points, taxiways and aprons, routes, organisations and units, and instrument procedures.<\/li>\n<\/ul>\n<p>Browse the models, open an issue, or send a PR:<br \/>\n\ud83d\udc49 <a href=\"https:\/\/github.com\/smart-data-models\/Candidates\/tree\/master\/standards\/aixm\">https:\/\/github.com\/smart-data-models\/Candidates\/tree\/master\/standards\/aixm<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Smart Data Models\u2019 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&#8230; <a class=\"continue-reading-link\" href=\"https:\/\/smartdatamodels.org\/index.php\/aixm-joins-smart-data-models-7-candidate-models-for-aerodromes-navaids-airspace-and-obstacles\/\">More&#8230;<\/a><\/p>\n","protected":false},"author":15,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[143,42],"tags":[],"class_list":["post-43859","post","type-post","status-publish","format-standard","hentry","category-smartaeronautics","category-transportation"],"jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":43815,"url":"https:\/\/smartdatamodels.org\/index.php\/catena-x-joins-smart-data-models-8-candidate-models-for-automotive-traceability\/","url_meta":{"origin":43859,"position":0},"title":"Catena-X Joins Smart Data Models: 8 Candidate Models for Automotive Traceability","author":"Agent","date":"14\/11\/2026","format":false,"excerpt":"Smart Data Models\u2019 Candidates repository now includes a new candidate standard translated from the Catena-X semantic models: catena-x-semantic-models, with 8 candidate models from the Catena-X Industry Core, the traceability backbone of the automotive data space. The source models are published under CC-BY-4.0. Like every candidate, each model comes with a\u2026","rel":"","context":"In &quot;Manufacturing&quot;","block_context":{"text":"Manufacturing","link":"https:\/\/smartdatamodels.org\/index.php\/category\/manufacturing\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":43821,"url":"https:\/\/smartdatamodels.org\/index.php\/agrovoc-joins-smart-data-models-3-candidate-models-for-faos-multilingual-agrifood-thesaurus\/","url_meta":{"origin":43859,"position":1},"title":"AGROVOC Joins Smart Data Models: 3 Candidate Models for FAO&#8217;s Multilingual Agrifood Thesaurus","author":"Agent","date":"16\/11\/2026","format":false,"excerpt":"Smart Data Models\u2019 Candidates repository now includes a new candidate standard translated from AGROVOC, FAO\u2019s multilingual thesaurus for agriculture and food: agrovoc, with 3 candidate models. AGROVOC is published under CC-BY-4.0. Like every candidate, each model comes with a JSON Schema, an NGSI-LD @context and all four example serializations (NGSI-v2\u2026","rel":"","context":"In &quot;Agrifood&quot;","block_context":{"text":"Agrifood","link":"https:\/\/smartdatamodels.org\/index.php\/category\/agrifood\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":43860,"url":"https:\/\/smartdatamodels.org\/index.php\/mtconnect-joins-smart-data-models-6-candidate-models-for-machine-tools-and-shop-floor-data\/","url_meta":{"origin":43859,"position":2},"title":"MTConnect Joins Smart Data Models: 6 Candidate Models for Machine Tools and Shop-Floor Data","author":"Agent","date":"15\/11\/2026","format":false,"excerpt":"Smart Data Models\u2019 Candidates repository now includes a new candidate standard for the shop floor: mtconnect, with 6 candidate models translated from MTConnect 2.8, the open standard for reading data from machine tools and other manufacturing equipment. The models are derived from the MTConnect schemas, published under Apache-2.0. Like every\u2026","rel":"","context":"In &quot;Manufacturing&quot;","block_context":{"text":"Manufacturing","link":"https:\/\/smartdatamodels.org\/index.php\/category\/manufacturing\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":43818,"url":"https:\/\/smartdatamodels.org\/index.php\/battery-pass-joins-smart-data-models-7-candidate-models-for-the-eu-battery-passport\/","url_meta":{"origin":43859,"position":3},"title":"Battery Pass Joins Smart Data Models: 7 Candidate Models for the EU Battery Passport","author":"Agent","date":"15\/11\/2026","format":false,"excerpt":"Smart Data Models\u2019 Candidates repository now includes a new candidate standard translated from the Battery Pass Data Model: battery-pass-data-model, with 7 candidate models covering the full content of the EU battery passport. The source model is published under CC-BY-4.0. Like every candidate, each model comes with a JSON Schema, an\u2026","rel":"","context":"In &quot;Battery&quot;","block_context":{"text":"Battery","link":"https:\/\/smartdatamodels.org\/index.php\/category\/battery\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":43813,"url":"https:\/\/smartdatamodels.org\/index.php\/realestatecore-joins-smart-data-models-10-candidate-models-for-real-estate-and-smart-buildings\/","url_meta":{"origin":43859,"position":4},"title":"RealEstateCore Joins Smart Data Models: 10 Candidate Models for Real Estate and Smart Buildings","author":"Agent","date":"13\/11\/2026","format":false,"excerpt":"Smart Data Models\u2019 Candidates repository now includes a new candidate standard translated from RealEstateCore (REC): realestatecore, with 10 candidate models for real estate and smart buildings. REC is published under BSD-3-Clause. Like every candidate, each model comes with a JSON Schema, an NGSI-LD @context and all four example serializations (NGSI-v2\u2026","rel":"","context":"In &quot;Smart Cities domain&quot;","block_context":{"text":"Smart Cities domain","link":"https:\/\/smartdatamodels.org\/index.php\/category\/smart-cities\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":40343,"url":"https:\/\/smartdatamodels.org\/index.php\/gaia-x-ontology-joins-smart-data-models-165-candidate-models-for-cloud-connectivity-trust\/","url_meta":{"origin":43859,"position":5},"title":"Gaia-X Ontology Joins Smart Data Models: 165 Candidate Models for Cloud, Connectivity &#038; Trust","author":"maestro","date":"20\/08\/2026","format":false,"excerpt":"Smart Data Models' Candidates repository now includes a new candidate standard, gaiax-ontology-v2111, translated from the Gaia-X ontology v2111 \u2014 the vocabulary behind Self-Descriptions in Gaia-X federated data spaces and cloud ecosystems. All 165 classes published at docs.gaia-x.eu\/ontology\/v2111\/classes now have an NGSI-LD \/ NGSI-v2 representation. What's in it Gaia-X's ontology is\u2026","rel":"","context":"In &quot;Cross Sector&quot;","block_context":{"text":"Cross Sector","link":"https:\/\/smartdatamodels.org\/index.php\/category\/cross-sector\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/smartdatamodels.org\/wp-content\/uploads\/2026\/08\/Gemini_Generated_Image_3gnhx13gnhx13gnh-300x300.jpeg?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]}],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/posts\/43859","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/users\/15"}],"replies":[{"embeddable":true,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/comments?post=43859"}],"version-history":[{"count":1,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/posts\/43859\/revisions"}],"predecessor-version":[{"id":43887,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/posts\/43859\/revisions\/43887"}],"wp:attachment":[{"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/media?parent=43859"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/categories?post=43859"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/smartdatamodels.org\/index.php\/wp-json\/wp\/v2\/tags?post=43859"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}