ID: | AIXM-524 |
target version: | AIXM 5.2 |
version: | 1.0 |
last updated: | 08 AUG 2022 |
status: | APPROVED |
|
|---|
Description
Additional values supporting conditional altitude termination of a SegmentLeg are added and the clarification of an INTERCEPT definition is introduced.
Rationale for change
See https://aixmccb.atlassian.net/browse/AIXM-477
In the current model it is not possible to indicate that the leg has a conditional altitude termination, meaning the leg ends as specified in the ARINC Path Terminator or at the altitude specified, under the condition indicated which might be "whichever is later" or is "whichever is earlier".
In general the condition relates to a distance/DME distance and an altitude.
Having the ICAO PANS-OPS provisions in mind, the clarification for the endConditionDesignator = “INTERCEPT” definition is also introduced.
Impact assessment
There is no impact on existing implementations as the current 
[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) data remains fully valid against 1 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, current for input.
[BWD_MAP_1:1] Data mapping is possible and no data loss occurs 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 into OTHER:... values, as described in the mapping rules further in this document.1 for input.
Change Proposal details
In the UML model:
- In the data type CodeSegmentTerminationBaseType
add the following values:
- ALTITUDE_AND_DISTANCE, type = string, definition = “Used to indicate that the leg has a conditional altitude termination, meaning the SegmentLeg ends as specified by the distance or at or above the altitude specified, under the condition indicated. Condition is whichever is later (altitude and reaching DME distance/flight distance).”.
- ALTITUDE_OR_DISTANCE,type = string, definition = “Used to indicate that the leg has a conditional altitude termination, meaning the SegmentLeg ends as specified by the distance or at or above the altitude specified, under the condition indicated. Condition is whichever is earlier (altitude or reaching DME distance/flight distance).”.
- DME_DISTANCE,type = string, definition = ”Leg is terminated when reaching the limiting distance indication defined by a DME associated with the leg.”
change the definition for INTERCEPT to read:
- ”Leg is terminated when reaching the limiting angle indication.”
The following UML class diagram shows the modified list of values, with the new values highlighted.
Mapping AIXM 5.1.1 to AIXM 5.2 (forward)
[MAPC-01] The following data conversion algorithm is proposed for (and incl. specialised subclasses) SegmentLeg.endConditionDesignator values:
- ”OTHER:ALTITUDE_AND_DISTANCE”
- Replace the value with “ALTITUDE_AND_DISTANCE”
- ”OTHER:ALTITUDE_OR_DISTANCE”
- Replace the value with “ALTITUDE_OR_DISTANCE”
- ”OTHER:DME_DISTANCE”
- Replace the value with “DME_DISTANCE”
Mapping AIXM 5.2 to AIXM 5.1.1 (backward)
[MAPC-01] The following data conversion algorithm is proposed for (and incl. specialised subclasses) SegmentLeg.endConditionDesignator values:
- ”ALTITUDE_AND_DISTANCE”
- Replace the value with “OTHER:ALTITUDE_AND_DISTANCE”
- ”ALTITUDE_OR_DISTANCE”
- Replace the value with “OTHER:ALTITUDE_OR_DISTANCE”
- ”DME_DISTANCE”
- Replace the value with “OTHER:DME_DISTANCE”
Mapping example
(Note: for mapping test data see: https://github.com/aixm/mapping_52_511/tree/master/AIXM-xxx)
| AIXM 5.2Input | AIXM 5.1(.1)Output |
|---|---|