v1.0.6

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

This section includes the correspondences between different models that cover the needs of aerodrome mappings.


Introduction

This chapter elaborates on the data encoding of AMD features and properties. 

The content constitutes supporting material for the provision of aerodrome mapping data sets in accordance with revised ICAO Annex 15 and new PANS-AIM (ICAO Doc 10066), applicable European regulations and industry standards e.g. EUROCAE ER-009

---

It includes a series of tables that:

  • list the information items from the “User Requirements for Aerodrome Mapping Information” (EUROCAE ED-99 / RTCA DO-272).
  • detail which elements (classes, attributes and associations) to use in AIXM 5.1.1. to meet the requirements of the EUROCAE ED-99 / RTCA DO-272 standard.
  • give the semantic correspondences of the information items to the ATM Information Reference Model (AIRM).


Before you begin...

Before you begin you should know:

  • Documents
    • EUROCAE ED99 and RTCA DO-272 are equivalent specifications. This is also true of ED-119 and DO-291.
    • The latest version of the “User Requirements for Aerodrome Mapping Information” is ED-99D/DO-272D.
    • ED-119C/DO-291C "Interchange Standards for Terrain, Obstacle, and Aerodrome Mapping Data" is also used on this page to provide e.g. enumeration. It contains the encoding to be used when realising ED-99/DO-272.
  • Models
    • The latest version of AIXM is AIXM 5.1.1.
    • AMXM is a schema that can be used to exchange aerodrome mapping data. The latest version is AMXM 2.0.0.
    • The AIRM is a vocabulary that is used for semantic interoperability.
  • Correspondences
    • The correspondence tables follow a given structure. See: How to read the correspondence tables.
    • Not everything has a correspondence so extensions are required. See AIXM 5.1.1 extensions.

    • The correspondences alone will not guarantee that an ED-99 compliant Aerodrome Mapping Database is created. This can only be done by applying the data product specification rules and the complete functional and geometrical constraints within ED-99 and ED-119. See Limitations to the correspondences.

Content


  • No labels

Status: Published