/
[AIXM-521] Add lightingTechnology to LightElement

[AIXM-521] Add lightingTechnology to LightElement

Owned by georgiana.andrei04
Last updated: 2024 Aug 19 by ADAM STYLES

ID:

AIXM-521

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 identification of specific lighting technology.

Rationale for change

See https://aixmccb.atlassian.net/browse/AIXM-392

It was identified that specific lighting technologies, such as LED (Light Emitting Diode)-based lighting may affect enhanced flight vision system (EFVS) capabilities. Indicating that information specifically should raise awareness and minimise potential risks when LED lighting is used as a part of ALS or runway lighting.

Together with LED, three other lighting technologies are used regularly such as: HALOGEN,  INCANDESCENT and FLUORESCENT. These values would be added for completeness.

Impact assessment

[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 for output towards a system (B) that uses AIXM 5.2 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 for input.

Change Proposal details

In the UML model, in the LightElement feature:

  • Add a new lightingTechnology attribute defined as “An indication of the lighting technology used to emit light.”, data type CodeLightingTechnologyType.

In the UML model, add the following data types:

  • CodeLightingTechnologyBaseType (stereotype <<codelist>>, definition: “A coded value representing the technology used to emit light”), with the following list of values:
    • FLUORESCENT, type = string, definition = “Fluorescent light.”
    • HALOGEN, type = string, definition = “Halogen light.”
    • INCANDESCENT, type = string, definition = - “Incandescent light.”
    • LED, type = string, definition = “LED light.”
    • OTHER, type = string, definition = ”Other”
  • CodeLightingTechnologyType (specialisation of CodeLightingTechnologyBaseType, stereotype <<datatype>>, definition: “ A complex data type that enables the provision of a NIL reason for any attribute using this type.”), attribute:
    • nilReason (type: NilReasonEnumeration)

The following UML class diagram shows the new attribute and its list of values.


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:

  1. Remove the new attribute lightingTechnology.
  2. Add an annotation.Note associated with the owner class having
  • purpose=“OTHER:BACKWARD_MAPPING”;

translatedNote.LinguisticNote.note=”lightingTechnology:<value of lightingTechnology>”

Mapping example

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

AIXM InputAIXM Output