Supporting material for ICAO Aerodrome Mapping Data Sets
This section provides an overview of the general requirements in relation to AMD. It is important to distinguish the notions that are used in the AMD context:
- AMD is geographic aerodrome information (i.e. features) and is addressed by ICAO requirements
- an AMD set contains AMD and is addressed by ICAO requirements
- an aerodrome mapping database (AMDB) is a specific aerodrome mapping data set defined by industry requirements EUROCAE ED99() / RTCA DO272()
It is therefore important to use the qualifier AMDB with caution.
In general the idea is that (ICAO) AMD can be used as input to create AMDB content.
It should however be clear that the creation of an AMDB implies the satisfaction of the industry requirements when intended to be used for the listed Industry applications.
|Annex 14 (Ed 8)||2.1.1||standard||Determination and reporting of aerodrome-related aeronautical data shall be in accordance with the accuracy and integrity classification required to meet the needs of the end-users of aeronautical data.||AMD quality shall meet the needs of the end-user applications.|
|Annex 14 (Ed 8)||2.1.1||note||Specifications concerning the accuracy and integrity classification related to aerodrome-related aeronautical data are contained in PANS-AIM (Doc 10066), Appendix 1.||Where to find AMD quality requirements.|
|Annex 14 (Ed 8)||2.1.2||recommendation||Aerodrome mapping data should be made available to the aeronautical information services for aerodromes deemed relevant by States where safety and/or performance-based operations suggest possible benefits.||When to make AMD available to AIS.|
|Annex 14 (Ed 8)||2.1.2||note||Aerodrome mapping databases related provisions are contained in Annex 15, Chapter 5 and PANS-AIM|
(Doc 10066), Chapter 5.
|Where to find requirements for AMD sets.|
|Annex 14 (Ed 8)||2.1.2||note||Guidance material concerning the application of aerodrome mapping databases is provided in Attachment A, Section 23.||-|
|Annex 14 (Ed 8)||2.1.3||standard||Where made available in accordance with 2.1.2, the selection of the aerodrome mapping data features to be collected shall be made with consideration of the intended applications.||Various aerodromes can expose various AMD sets in terms of features. The supported applications should drive the content of the AMD set.|
|Annex 14 (Ed 8)||2.1.3||note||It is intended that the selection of the features to be collected match a defined operational need.||The operational need should lead to an information exchange requirement which determines the features to be captured.|
|Annex 14 (Ed 8)||2.1.3||note||Aerodrome mapping databases can be provided at one of two levels of quality — fine or medium. These levels and the corresponding numerical requirements are defined in RTCA Document DO-272B and European Organization for|
Civil Aviation Equipment (EUROCAE) Document ED-99C — User Requirements for Aerodrome Mapping Information.
|Accuracy is determined in PANS-AIM Appendix 1 which mostly maps to fine quality. If AMDBs are provided they can be provided according fine or medium quality.|
|Annex 14 (Ed 8)||2.1.4||standard||Digital data error detection techniques shall be used during the transmission and/or storage of aeronautical data and digital data sets.||-|
|Annex 14 (Ed 8)||2.1.4||note||Detailed specifications concerning digital data error detection techniques are contained in PANS-AIM (Doc 10066).||-|
|Annex 14 (Ed 8)||2.2 - 2.13||N/A||N/A||Data collection requirements.|
|Annex 14 (Ed 8)||Attachment A||N/A||N/A||AMD applications and determination of airports for data collection.|
|Annex 15 (Ed 16)||184.108.40.206||standard||Digital data shall be in the form of the following data sets:|
a) AIP data set;
b) terrain data sets;
c) obstacle data sets;
d) aerodrome mapping data sets; and
e) instrument flight procedure data sets.
|AMD is provided as a data set hence the requirements on data set provision are applicable.|
|Annex 15 (Ed 16)||220.127.116.11||note||Detailed specifications concerning the content of the digital data sets are contained in the PANS-AIM (Doc 10066).||-|
|Annex 15 (Ed 16)||18.104.22.168||standard||Each data set shall be provided to the next intended user together with at least the minimum set of metadata that|
|Applicable to AMD set.|
|Annex 15 (Ed 16)||22.214.171.124||note||Detailed specifications concerning metadata are contained in the PANS-AIM (Doc 10066).||Applicable to AMD set.|
|Annex 15 (Ed 16)||126.96.36.199||standard||Aerodrome mapping data sets shall contain the digital representation of aerodrome features.||Realised through the use of an appropriate data exchange language (e.g. AIXM 5.1 XML Schema).|
|Annex 15 (Ed 16)||188.8.131.52||note||Aerodrome features consist of attributes and geometries, which are characterized as points, lines or polygons. Examples include runway thresholds, taxiway guidance lines and parking stand areas.||-|
|Annex 15 (Ed 16)||184.108.40.206||recommendation||Aerodrome mapping data sets should be made available for aerodromes regularly used by international civil aviation.||When to make AMD sets available.|
|PANS AIM (Doc 10066)||220.127.116.11||note||Aerodrome mapping data includes aerodrome geographic information that supports applications which improve the user’s situational awareness or supplements surface navigation, thereby increasing safety margins and|
operational efficiency. Aerodrome mapping data sets with appropriate data element accuracy support requirements for collaborative decision making, common situational awareness and aerodrome guidance applications are intended to be used, among others, in the following air navigation applications:
a) position and route awareness including moving maps with own ship position, surface guidance and navigation
b) traffic awareness including surveillance and runway incursion detection and alerting;
c) facilitation of aerodrome-related aeronautical information, including NOTAM;
d) resource and aerodrome facility management; and
e) aeronautical chart production.
The data may also be used in other applications such as training/flight simulator and synthetic vision systems.
|PANS AIM (Doc 10066)||18.104.22.168||note||Aerodrome mapping data is organized and arranged in aerodrome mapping databases (AMDBs) for ease of electronic storage and usage by appropriate applications.||Establishes a relation between AMD and AMDB.|
|PANS AIM (Doc 10066)||22.214.171.124||note||The content of the aerodrome mapping data sets is defined in Radio Technical Commission for Aeronautics (RTCA) Document DO 272D/European Organization for Civil Aviation Equipment (EUROCAE) Document ED 99 — User Requirements for Aerodrome Mapping Information.||Indicates the use of industry standards to define AMD set content.|
|PANS AIM (Doc 10066)||126.96.36.199||note||Metadata elements applicable to aerodrome mapping data are contained in RTCA DO-291B/EUROCAE ED-119B — Interchange Standards for Terrain, Obstacle, and Aerodrome Mapping Data.||Indicates the use of industry standards to define metadata.|
|PANS AIM (Doc 10066)||188.8.131.52.1||recommendation||Aerodrome mapping data should be supported by electronic terrain and obstacle data for Area 3 in order to ensure consistency and quality of all geographical data related to the aerodrome.||-|
|PANS AIM (Doc 10066)||184.108.40.206.1||note||Accuracy and integrity requirements for aerodrome mapping data are contained in Appendix 1.||-|
|PANS AIM (Doc 10066)||220.127.116.11.1||note||Electronic terrain and obstacle data pertaining to Area 3 and aerodrome mapping data may be originated using common acquisition techniques and managed within a single geographic information system (GIS).||-|
|PANS AIM (Doc 10066)||18.104.22.168.1||note||The content of the aerodrome mapping data sets is defined in RTCA DO 272D/EUROCAE ED-99D.||-|
The Aeronautical Data Catalogue presents the scope of the data that should be collected and maintained by an AIS organization and includes data quality requirements. For more information please refer to PANS AIM Doc 10066 Appendix 1.
Not all data required by the Data Catalogue are available in the Aeronautical Information Publication. For specific information the data originator should obtain data from other source of information, e.g. aerodrome operator.
Data update requirements
Specific requirements for how data sets should be updated are contained in ICAO Annex 15, section 6.3:
22.214.171.124 Data sets shall be amended or reissued at such regular intervals as may be necessary to keep them up to date.
126.96.36.199 Permanent changes and temporary changes of long duration (three months or longer) made available as digital data shall be issued in the form of a complete data set or a sub-set that includes only the differences from the previously issued complete data set.
188.8.131.52 Recommendation.— When made available as a completely re-issued data set, the differences from the previously issued complete data set should be indicated.”
ICAO Doc 10066 PANS AIM Chapter 6.1 contains section Aeronautical Information Product Updates, where the provision and updates of digital data sets is described.
The AMD follow the same rules and requirements regarding the provision and updates of data sets as AIP data set as described: Baseline data and updates
The industry requirements for AMDB are driven by the applications that are intended to be enabled by AMDBs. These applications are documented in ED-99() and the associated industry requirements for AMDB cover aspects such as:
- content → feature catalogue → ED-99(), ED-119()
- quality → numerical requirements -> ED-99()
- relations between features → functional constraints → ED-99()
- geospatial relations between features→ geometrical constraints → ED-99()
- general constraints → for instance digitizing order etc... → ED-99()
- data format → application schema and information exchange model → ED-119()
Interpretation of ICAO requirements in relation to Industry requirements
ICAO requirements enable the provision of AMD in support of AMDB applications. When translating data between AIXM 5.1 and AMXM 2.0.0 it is important to be aware of any side effects and points of attention.
Some indicative aspects are provided below but these require close inspection when performing such data translation tasks:
|ICAO Requirements for AMD||Industry Requirements for AMDB||AMD->AMDB||AMDB->AMD|
|Content||PANS-AIM ADC||ED119() Feature Catalogue|
use feature mapping (supporting material)
possibly some information losses
use feature mapping (supporting material)
possibly additional data elements needed (e.g. extensions)
resulting AMDB in fine/medium/course possible
resulting AMD in fine if AMDB in fine
resulting AMD may not meet PANS-AIM Appendix 1 accuracy requirements if AMDB below fine
|Business Rules||AIXM 5.1 Business Rules||ED99() Constraints (generic, geometrical, functional)|
ED99() Constraints: possibly to be satisfied
ED99() generic: to be checked
ED99() geometry: to be checked
ED99() functional: to be checked
AIXM 5.1 business rules: possibly to be satisified
ED99() generic: passed through
ED99() geometry: passed through
ED99() functional: possibly lost in translation
|Data product type||data set||data set||no type change||no type change|
|Data product||AMD set||AMDB||data product conversion||data product conversion|
|Data format||AIXM 5.1||AMXM||format conversion||format conversion|
Data Coding GuideLines
The complexities inherent to the encoding of aeronautical information and lack of harmonised approaches may lead to differences in the data. This in turn may lead to barriers to be surmounted when exploiting digital data in a network context.
To promote the harmonisation of digital data there is a need for common data coding guidelines. When supported by precise and interpretable business rules, it is then possible to verify the compliance of digital data (e.g. AIXM data sets) versus the common data coding guidelines.
This will then result in more harmonised digital data to the benefit of the consumers of information.
In the context of this AMD supporting material the breakdown of data coding guidelines is as follows:
- the common data coding guidelines applicable to any AIXM 5.1 encoded data set
- the specific data coding guidelines applicable for:
- AMD sets encoded in AIXM 5.1 (), currently (July 2023) unspecified
- AMDB as specified in ED-99(), ED-119(), also known as the functional and geometrical constraints
Continue to read about this topic in the section about information exchange models.