[AIXM-561] Adjust TouchDownLiftOff performance class

Description

The helicopterPerformanceClass attribute is added to AircraftCharacteristics and the association between TouchDownLiftOff and AircraftCharacteristic is established.

Rationale for change

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

It was identified that for certain TLOF multiple helicopter performance classes may be designated (depending on e.g. sectors). Current TouchDownLiftOff class does not support that.

It is therefore proposed to remove the helicopterClass attribute from TouchDownLiftOff, add the helicopterPerformanceClass to AircraftCharacteristics and establish the association between the two classes with 0..* multiplicity. Several other editorial clarifications are proposed to the definitions, data type names to highlight that the attribute in question refers to the helicopter performance classes and not other classifications of an aircraft.

Impact assessment

[FWD_MAP_1:1] Data mapping is possible 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.

Mapping AIXM 5.1.1 to AIXM 5.2 (forward)

[MAPC-00] For each TouchDownLiftOff that has a helicopterClass value:

• Add aircraft.AircraftCharacteristic element and copy the helicopterClass value into the helicopterPerformanceClass as follows:
  • “OTHER:2WE” into “2WE”
  • otherwise, identical copy
• Remove the TouchDownLiftOff.helicopterClass element

If there exist TouchDownLiftOff.annotation.Note elements with propertyName=”helicopterClass”: (e.g. referring to the sectors to which specific performance class applies)

• change the propertyName into “aircraft”.

Mapping AIXM 5.2 to AIXM 5.1.1 (backward)

The following algorithm shall be applied:

• [MAPC-04] For each AircraftCharacteristic.helicopterPerformanceClass elements
  • Select the most restrictive value (‘1’ - CP1 etc.) from the AircraftCharacteristic.helicopterPerformanceClass and copy the value to helicopterClass
  • Add an annotation.Note associated with the owner class having
    • purpose=“OTHER:BACKWARD_MAPPING”;
    • LinguisticNote.note=”aircraft[1].AircraftCharacteristic.helicopterPerformanceClass1: <.helicopterPerformanceClass1> ;
      • where“[1]” indicates that this needs to be repeated as many times as necessary to cover all the remaining (e.g. less restrictive ‘2’ - CP2 etc.) occurrences of the AircraftCharacteristic
    • propertyName=’helicopterClass’.

• • If there exist AircraftCharacteristics.annotation.Note elements with propertyName=”helicopterPerformanceClass”:

• • • move those annotation.Note into the TouchDownLiftOff element and change their propertyName into “helicopterClass”.

• • Remove the aircraft.AircraftCharacteristics class

• [MAPC-99] In case the TouchDownLiftOff.aircraft.AircraftCharacteristics has other elements than helicopterPerformanceClass that have a value, no mapping is possible.

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)