ID: | AIXM-517 |
target version: | AIXM 5.2 |
version: | 1.0 |
last updated: | 08 AUG 2022 |
status: | APPROVED |
|
---|
Description
Additional attribute is added to LightElement to allow for indicating the direction of the lighting.
Rationale for change
See https://aixmccb.atlassian.net/browse/AIXM-393
It was identified that in the current model it is not possible to indicate direction of the LightElement, such as unidirectional or bidirectional. This is necessary, for example, for runway lighting elements.
Impact assessment
There is no impact on existing implementations as the current[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 against1 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, currentfor 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 be able to map back the new values, as described in the mapping rules further in this document.1 for input.
Mapping AIXM 5.1.1 to AIXM 5.2 (forward)
Not applicable
Mapping AIXM 5.2 to AIXM 5.1.1 (backward)
[MAPC-02] For each LightElement that has a direction value:
The following mapping into Note algorithm is proposed:
- Remove the new attribute direction.
- Add an annotation.Note associated with the owner class having
- purpose=“OTHER:BACKWARD_MAPPING”;
translatedNote.LinguisticNote.note=”direction:<value of direction>”
Mapping example
(Note: for mapping test data see: https://github.com/aixm/mapping_52_511/tree/master/AIXM-xxx)
AIXM 5.2 | AIXM 5.1(.1) |
---|---|