Requirements mapping to AIXM 5

Owned by POROSNICU Eduard
Last updated: 2023 Feb 16

Scope

These pages contain the mapping of the Obstacle data set subjects as defined in the ICAO Annex 15, 16th edition and further detailed in the PANS-AIM to the corresponding AIXM 5 features and attributes. For this purpose, three categories of requirements have been identified:

1. Minimal requirements

Annex 15, item 5.3.3 contains general provisions for how obstacles must be organised in data sets specific to either the entire State territory (Area 1) or an aerodrome (such as Area 2, which is subdivided in a/b/c/d, Area 3, etc.) The definition of these areas needs to be mapped into the corresponding AIXM features and properties. In addition, Annex 15 section 5.3.3.4 contains some specific requirements and recommendations for which obstacles shall/should be provided in particular cases. These are not mapped into the AIXM features and properties, but will be taken into consideration as a source of data set verification rules.

The PANS - AIM section 5.3.3.2.2 provides further provisions with regard to Obstacle data sets. Most of these requirements need to be considered in the mapping, in particular item 5.3.3.2.2.2 which requires that each obstacle "shall be described according to the list of mandatory attributes provided in Appendix 6, Table A6-2". The obstacle properties that appear in this table are further detailed in the PANS-AIM Appendix 1 "Aeronautical Data Catalogue", which is also considered for the mapping.

Some requirements refer to data quality requirements, which are considered as a source of data set verification rules.

2. Conditional requirements

According to a Note in PANS - AIM section 5.3.3.2.2, "specific attributes associated with mobile (feature operations) and temporary types of obstacles are annotated in Appendix 6, Table A6-2, as optional attributes. If these types of obstacles are to be provided in the data set, appropriate attributes describing such obstacles are also required". Even if these attributes are considered "conditional", as they depend on the nature of the obstacle (fix versus mobile, permanent versus temporary), they are included in the mapping and in the coding rules.

When the Obstacle data set (as specified in 5.3.3.2.2) is provided, certain sections of the AIP may be left blank and a reference to the data set availability shall be provided. In PANS-AIM these sections are marked with #OBS-DS# in PANS-AIM Appendix 2 "Contents of the Aeronautical Information Publication (AIP)" and they are also explicitly listed in the PANS-AIM section 5.2.1.1.4:

  1. "ENR 5.4 Air navigation obstacles
  2. ***AD 2.10 Aerodrome obstacles
  3. ***AD 3.10 Heliport obstacles"

All data elements that are described in these sections are taken into account for the mapping.

3. Optional elements

Apart from the minimum and conditional properties, the PANS-AIM specifies:

  • in Appendix 6 "height" as optional property
  • in Appendix 1 "material" as additional property in the Data Catalogue.

These are included in the mapping as optional elements.

Additional resources

The ICAO Annex 15 and PANS-AIM provisions also take into consideration the end-user requirements for obstacle data sets. These have been formalised in a joint specification published by RTCA and EUROCAE:

  • EUROCAE ED-98 / RTCA DO-276 / User Requirements for Terrain and Obstacle data, version C, October 2015. Definitions, descriptions and data capturing rules from this standard are sometimes quoted in order to further detail the ICAO provisions.

At regional level, EUROCONTROL provides a manual with the aim to support data originators and data providers in originating and making available terrain and obstacle data sets.

  • EUROCONTROL Terrain and Obstacle Data Manual, edition 2.1, November 2015. Explanations from this manual are sometimes referred to in the coding guidelines for the obstacle data set, in order to detail certain topics.

How to read

Each topic page contains at least:

  • Mapping Diagram(s) - One or more mapping diagrams are provided (depending on the complexity of the AIXM 5.1.1 model).

On the left-hand side of the diagram, the PANS-AIM subject with its attributes (in yellow colour) is shown. The attributes are sorted as they are in PANS-AIM Appendix 1 (Aeronautical Data Catalogue).

The PANS-AIM data type of the property is considered for the mapping. For example, a type that is text in PANS-AIM might require in AIXM two attributes, such as a code and a Note (type Description).

On the right-hand side, you find the AIXM 5.1.1 features and objects the PANS-AIM subject and its properties are mapped to.

  • Mapping Table - Below the mapping diagram the corresponding, detailed mapping of the PANS-AIM properties to AIXM 5.1.(1) is provided in tabular form.

A tabular view of the mapping in form of Excel spreadsheets can be accessed via the corresponding File list: to be developed

Whereas on the Confluence pages AIXM/SBVR notation (see Editorial Conventions) is applied for the AIXM elements, it is planned to use XPath expressions (XML syntax) within the Excel spreadsheets.