AIXM Schema Extension#

Required roles: AIS Navigation Data via Cloud — Roles
Base endpoint: https://cdn.ibosoft.net.tr/aviation-data/schema/aixm/5.2/extension/
Reference documents: AIXM 5.2 schema set and "AIXM Application Schema Generation" (aixm.aero) · ICAO Doc 8144 Directives to Regional Air Navigation Meetings and Rules of Procedure for their Conduct · ICAO Doc 7030 Regional Supplementary Procedures
Attribution: show ibonav.aero wherever this data is displayed
Data sources: none — schema definition.
Last updated: 18 OCT 2026

About the reference documents: Related Documents and Resources

AIXM 5.2 has no place for some information that the ibonav.aero Navigation Database needs: where each feature came from, a second distance on change-over points, and the ICAO region of an FIR. This information is carried in an extension schema of our own, built with the standard AIXM extension mechanism. The core AIXM 5.2 content is not changed.

The extension is used in our own data: every AIXM file of the ibonav.aero Navigation Database (ATS Data, Airspace Data) carries it, and the GeoPackage columns described in those pages are filled from it.

Schema#

The namespace is an identifier, not an address: XML tools compare it as text and do not download anything from it. It must be written exactly as above.

The schema imports the AIXM 5.2 namespace without a schema location. To validate a file, compile the AIXM 5.2 schema set and this schema together in your validator.

Versioning: a change that breaks existing files increases the major version; a new optional element increases the minor version.

How it works#

Every AIXM feature TimeSlice may end with any number of aixm:extension elements. Each one holds one element that belongs to the extension group of that feature type (aixm:Abstract<Feature>Extension). Our elements are declared in those groups and derive from aixm:AbstractExtensionType, so each needs its own gml:id.

• One TimeSlice can carry several of our extensions; each purpose has its own aixm:extension.
• The extensions come after all core AIXM properties of the TimeSlice.
• XML Schema 1.0 allows an element in only one substitution group, so the same content has a different element name per feature type (for example RouteDataProvenance, AirspaceDataProvenance). The content type is the same.

A reader that does not know the extension can ignore the aixm:extension elements; the rest of the file is plain AIXM 5.2.

Additions#

Data provenance#

AIXM has no property for the source of a feature. Our data is merged from several sources, so every feature carries its source in a <Feature>DataProvenance element.

Elements by feature type:

In our files every feature has exactly one provenance element, as the last extension of its TimeSlice.

<aixm:DesignatedPointTimeSlice gml:id="DP_1_TS">
  <!-- core AIXM properties -->
  <aixm:extension>
    <ibosoftais:DesignatedPointDataProvenance gml:id="DP_1_PROV">
      <ibosoftais:dataProvider>EUROCONTROL EAD SDO</ibosoftais:dataProvider>
      <ibosoftais:dataOriginator>DHMI TURKIYE</ibosoftais:dataOriginator>
      <ibosoftais:dataEffectivity>01 OCT 2026 (AIRAC 2610)</ibosoftais:dataEffectivity>
    </ibosoftais:DesignatedPointDataProvenance>
  </aixm:extension>
</aixm:DesignatedPointTimeSlice>

Change-over point#

The route tables of AIP ENR 3 can give the position of a change-over point (COP) by its distance from both ends of the route portion — from the navaid at the start and from the navaid at the end. AIXM 5.2 does not support the second value: the core property distance of a ChangeOverPoint is measured from the start of the route portion and has one value only. The distance from the end is therefore carried in this extension.

<aixm:extension>
  <ibosoftais:ChangeOverPointExtension gml:id="COP_1_EXT">
    <ibosoftais:distanceFromEnd uom="NM">42</ibosoftais:distanceFromEnd>
  </ibosoftais:ChangeOverPointExtension>
</aixm:extension>
<aixm:extension>
  <ibosoftais:ChangeOverPointDataProvenance gml:id="COP_1_PROV">
    <!-- provenance -->
  </ibosoftais:ChangeOverPointDataProvenance>
</aixm:extension>

Airspace#

AIXM has no property for the ICAO region of an airspace. It is added for FIR and UIR features.

Values are written as published by the data source. Next to the ICAO region codes, the source may use combined codes such as CARSAM or ASIAPAC.

<aixm:extension>
  <ibosoftais:AirspaceExtension gml:id="FIR_1_EXT">
    <ibosoftais:regionIcao>EUR</ibosoftais:regionIcao>
    <ibosoftais:regionSupProc>EUR</ibosoftais:regionSupProc>
  </ibosoftais:AirspaceExtension>
</aixm:extension>