Versions Compared

Version Old Version 15 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 elements in the different models that cover the needs of aerodrome mappings
  • elaborates on the data encoding of AMD features and properties 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
    • provides examples of

    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 AMD features.

    The encoding of features in AIXM 5.1.1

    . encoding

    Limitations

    The supporting material alone will not guarantee that an ED-99/DO-272 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/DO-272 and its normative encoding found in ED-119/DO-291.

    In addition, where calculations or geometrical mergings are required, visual verification of the result will be required.

    In some cases, additional steps are required by the implementer. For example:

  • AIXM 5.1.1 allows the use of the geometrical curves and geodesics. ED-99/DO-272 only allows line-strings. Therefore the curve will need to be transformed into a line-string. Details on such transformations are out of the scope of this site.
    • The AMDB Default values will need to be added to the AMDB where the AIXM 5.1.1 data is missing elements that are mandatory in AMDB

    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)