ID: | AIXM-519 |
target version: | AIXM 5.2 |
version: | 1.0 |
last updated: | 08 AUG 2022 |
status: | APPROVED |
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
There is no impact on existing implementations as the current AIXM 5.1.(.1) data remains fully valid against AIXM 5.2.
When receiving data from AIXM 5.2 implementations, current AIXM 5.1(.1) systems will have to be able to map back the new values, as described in the mapping rules further in this document.
Change Proposal details
In the UML model:
- In the Route class:
- Add an association “isValidFor” AircraftCharacteristic with role name “aircraftCapability” and multiplicity 0…* on the AircraftCharacteristic <<object>> side, definition = “A combination of aircraft characteristics, equipment and capabilities that ensure Route classification”.
The following UML class diagram shows the new association. For completeness, the changes made in other Change Proposals are also shown.
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) |
|---|---|