Page Comparison

Description

Two additional properties are added on AeronauticalGroundLight: designator and intensity.

Rationale for change

See https://aixmccb.atlassian.net/browse/AIXM-444, https://aixmccb.atlassian.net/browse/AIXM-445

ICAO Document 10066 (PANS-AIM) Data Catalogues include a designator and a light intensity attribute for aeronautical ground lights. These attributes don't exist in AIXM 5.1(.1). There is a risk that some datasets use the name attribute to store the designator.

Also, as the ICAO Data Catalogue specifically requests for the light intensity a published resolution of thousands of candela, it is proposed that the intensity property shall use the data type ValLightIntensityType rather than intensity levels used on other lighting systems.

Impact assessment

There is no impact on existing implementations as the current Image Added

[FWD_1:1] No data mapping is necessary and no data loss occurs when data is exchanged from a system (A) that uses AIXM 5.1(.1 ) data remains fully valid against for output towards a system (B) that uses AIXM 5.2 . No values are removed from this list. When receiving data from AIXM 5.2 implementations, current for input.

[BWD_MAP_LOSS] Data mapping is possible, but some data would be lost (or converted into Notes) when data is exchanged from a system (B) that uses AIXM 5.2 for output towards a system (A) that uses AIXM 5.1(.1 ) systems will have to map back the new attributes as described in the mapping rules further in this documentfor input.

Change Proposal details

• In the AeronauticalGroundLight feature:
• Add a new designator attribute defined as “The designator of the AGL.”, data type TextDesignatorType.
• Add a new intensity attribute defined as “The exact value of the intensity of the lights in the AGL.”, data type ValLightIntensityType.

The following UML class diagram indicates the new attributes.

Mapping AIXM 5.1.1 to AIXM 5.2 (forward)

Not applicable.

Mapping AIXM 5.2 to AIXM 5.1.1 (backward)

[MAPC-02] From the three backward mapping options applicable in this case, the first two (discard the value or use an extension) are straightforward and do not need any further details. The 3rd option (backward mapping into a Note) is detailed in order to provide a complete description of this case and its conversion option. The following mapping into Note algorithm is proposed:

For each AeronauticalGroundLight that has designator and/or intensity child elements:

1. Add an annotation.Note associated with the owner class having
   • purpose=“OTHER:BACKWARD_MAPPING”;
   • translatedNote.LinguisticNote.note=”designator:<value of designator>”
2. Add an annotation.Note associated with the owner class having
   • purpose=“OTHER:BACKWARD_MAPPING”;
   • translatedNote.LinguisticNote.note=”intensity:<value of intensity> <value of intensity.uom>”
3. Remove the elements designator and intensity.

Mapping example

(Note: for mapping test data see: https://github.com/aixm/mapping_52_511/tree/master/AIXM-xxx)