Versions Compared

Version Old Version 10 New Version Current
Changes made by

WILSON Scott

WILSON Scott

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

    This section provides supporting material for the encoding of AMD features.

    This includes the list of ED-99()/DO-272() AMDB features and how they map into the corresponding 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).
    • Info
    titleBefore 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

    AMD features.

    The encoding of features in AIXM 5.1.1 is further documented per feature.

    Excerpt
    Note

    The correspondences between the AMDB features and the AIXM AMD 5.1.1. features provide guidance on how to translate the content of one model to another based on the structures of the models.

    However, care must be taken to ensure that:

    • the content is translated according to the specific business rules and data encoding requirements for the intended applications; and
    • the result is operationally correct and that the data is coherent and consistent.

    The quality of the result can be checked by validating the data and ensuring that it supports the intended applications.

    An example of where care is needed is the translation of wingspan data (see https://ext.eurocontrol.int/aixm_confluence/display/ACGAMD/TaxiwayGuidanceLine+correspondence).



    Content

    Child pages (Children Display)