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

SAREF4AGRI & SAREF4AUTO Join Smart Data Models: 58 Candidate Models for Precision Agriculture and Connected Vehicles

Smart Data Models’ Candidates repository now includes two more ETSI SAREF extensions: saref4agri and saref4auto, together contributing 58 candidate models. Both ship
the full Candidates artifact set — a JSON Schema, an NGSI-LD @context, and all four example serializations — validated against its own schema.

SAREF4AGRI — 21 models

SAREF4AGRI (ETSI TS 103 410-6) extends SAREF into precision agriculture and livestock monitoring, stitching together W3C SSN/SOSA (systems, platforms, deployments), GeoSPARQL (farm and parcel topology), the TIME ontology (deployment periods), OBO TAXRANK (species classification), and FOAF (farmers and farm holdings as organizations). It’s grounded in two worked examples in the standard: a livestock farm with milking and eating-activity sensors, and a smart-irrigation deployment with soil tensiometers and pluviometers reporting through a platform/system/deployment chain.

Category Models
Features of interest / topology Animal, AnimalGroup, Crop, Soil, Parcel, Farm
People / organizations Farmer, FarmHolding
Infrastructure Platform, Deployment
Smart-irrigation sensors/actuators Pluviometer, SoilTensiometer, WeatherStation, WateringGun, WateringSystem, WateringValve, Thermometer
Livestock-farming sensors MovementActivitySensor, EatingActivitySensor, MilkingSensor, WeightSensor

https://github.com/smart-data-models/Candidates/tree/master/standards/saref4agri

SAREF4AUTO — 37 models

SAREF4AUTO (ETSI TS 103 410-7) is SAREF’s extension for connected and automated vehicles and the roadside infrastructure (C-ITS) that supports them — vehicles, trailers, dangerous-goods cargo, vehicle platoons, pedestrians/cyclists and their clusters, parking spots, roadside units/sensors/actuators/traffic lights, traffic management centres, and a wide catalogue of sensor types (lidar, radar, UWB, stereovision…).

Category Models
Core automotive entities AutomotiveEntity, TrafficParticipant, Vehicle, Trailer, DangerousGoods
Platooning Platoon, PlatoonJoin, PlatoonBreakup, PlatoonLeave
Vulnerable road users VulnerableRoadUser, VRUCluster, ClusterJoin, ClusterBreakup, ClusterLeave
Roadside infrastructure AutomotiveDevice, RoadSideEquipment, RoadSideUnit, RoadSideActuator, TrafficLightController, RoadSideSensor, TrafficManagementCentre
Traffic events & parking TrafficEventObservation, TrafficEventCause, ParkingSpot
Sensors 13 types, e.g. LidarSensor, RadarSensor, StereovisionSensor, UwbSensor

https://github.com/smart-data-models/Candidates/tree/master/standards/saref4auto

Translation notes

  • Large named-individual vocabularies, kept open rather than exploded. SAREF4AUTO’s 161-member TrafficEventCause vocabulary (drawn from ETSI’s ITS Common Data Dictionary) became one entity with an open causeCode and a closed category enum of the 20 top-level causes — not ~160 separate models. Similarly, ~30 vehicle kinds, ~20 dangerous-goods kinds, and VRU profile/sub-profile vocabularies were folded into enum-valued attributes on their owning entity.
  • Generic value-wrapper classes excluded. Eight SAREF4AUTO OWL “typing” classes with no domain content of their own (BooleanProperty, DecimalProperty, ConfidenceValue…) aren’t modeled as entities — every property using them is instead a plain typed attribute on its owning entity. Net effect: ~46 raw primary classes in scope → 37 genuinely distinct models.
  • Road topology deliberately excluded. SAREF4AUTO’s own Road/ RoadSegment/Lane classes were left out of this translation, since they would duplicate rather than extend the official dataModel.Transportation subject’s existing coverage.
  • Two naming collisions found, kept verbatim. SAREF4AUTO’s own Vehicle (C-ITS/kinematics-oriented: heading, speed, automation level) and ParkingSpot (thinner, C-ITS-oriented) share a name with existing official Smart Data Models that cover complementary but non-identical ground (fleet/telematics Vehicle; richer occupancy-model ParkingSpot). SAREF4AGRI’s Animal likewise shares a name with the official dataModel.Agrifood‘s own Animal. Per the translation policy, names were kept exactly as the source ontologies define them rather than renamed to dodge the collision — flagged in each standard’s standard-metadata.yaml for the Candidates review process to resolve.

Try it, and tell us what’s missing

These are Candidates — first, carefully-sourced translations, not yet
promoted to official Smart Data Models subjects. The naming collisions
above are the main open item for both standards before promotion.

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

Converted Global Data dictionary codes

What is Global Data Dictionary

The GS1 Global Data Dictionary (GDD) is a repository of the data elements defined across all GS1 Standards.

What is the scope of the Global Data Dictionary?

GS1 Business Message Standards (BMS) and their components with definitions for GDSN 3.1, 3.1.2 , 3.1.3 and 3.1.4, GS1 XML for EDI 3.0, 3.1, 3.2 and 3.3, TSD and EPCIS 1.0.1. Higher versions will be added upon ratification.

  • Business Messages
  • Business Information Entities – message components and the relationship between them
  • Business Data Types
  • Code Lists used in Business Messages

The Business Messages are composed of Business Information Entities that comprise classes of information and their attributes. The attributes, in turn, have data types that may contain code list

The Full Set of GDSN & Shared Code Lists, and the Full Set of EDI, EPCIS, CPV & Shared Code Lists is now in a structured format in json much easier to integrate with NGSI platform.

Soon there will be part of them integrated into the smart data models.

Updates on data models

There are 4 new data models under review at incubated folder

DeviceOperation
FleetVehicleOperation
FleetVehicleStatus

They will have to be adapted to the guidelines and to the manual of single data code

Additionally, there are new contributions to water Network management

It also has been submitted a new data model for water observation. Soon to be assessed and shared.

 

 

Subscribe to the data models you are interested

If you are not a developer (But if you are you can also use it) we have created a page for being updated about the last news of your domain of interest

Check the 10 mail lists available, one per domain. Click in the image to access it.

It is also available in the main menu in the option Subscribe