[AIXM-519] Add Route association with AircraftCharacteristic

Description

An association is added to the Route class to allow for classification using AircraftCharacteristic attributes.

Rationale for change

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

It was identified that the current list of attributes of class Route does not allow for easy classification vis-a-vis ICAO Doc 10066 structure: Conventional navigation routes, Area navigation routes and does not facilitate sorting of route tables for AIP and for other publications.

Similar to the solution adopted in the Alignment with PBN concept CP (RouteSegment is associated with Aircraft Characteristics),the proposed solution is to associate the class Route with AircraftCharacteristic.

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.

Mapping AIXM 5.1.1 to AIXM 5.2 (forward)

Not applicable.

Mapping AIXM 5.2 to AIXM 5.1.1 (backward)

The following algorithm shall be applied:

• [MAPC-03] For each Route that has aircraftCapability.AircraftCharacteristics with navigationType, navigationSpecification, navigationAccuracy or category child elements:
  • From the three backward mapping options available 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:
• Add an annotation.Note associated with the RouteSegment having:
  • purpose=“OTHER:BACKWARD_MAPPING”;
  • LinguisticNote.note=“[1] navigationType: <value of navigationType>; navigationSpecification: <value of navigationSpecification> <uom>; navigationAccuracy: <value of navigationAccuracy>, category: <value of category> [2] etc.”, where “[1]” indicates that this needs to be repeated as many times as necessary to cover all occurrences of the AircraftCharacteristic class
  • remove the aircraftCapability element
• [MAPC-99] No mapping possible. For each Route that has aircraftCapability.AircraftCharacteristics with child elements other than navigationType, navigationSpecification, navigationAccuracy or category:
  • No mapping is possible for the remaining AircraftCharacteristic attributes: typeAircraftICAO, aircraftLandingCategory, wingSpan, wingSpanInterpretation, classWingSpan, weight, weightInterpretation, passengers, passengersInterpretation, speed, speedInterpretation, wakeTurbulence, navigationEquipment, verticalSeparationCapability, antiCollisionAndSeparationEquipment, communicationEquipment, surveillanceEquipment.
  • remove the aircraftCapability element

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)