ID: | AIXM-539 |
target version: | AIXM 5.2 |
version: | 1.0 |
last updated: | 08 AUG 2022 |
status: | APPROVED |
Description
Association roles from RunwayCentrelinePoint and LandingTakeOffAreaCollection to RunwayDirection are renamed to “onRunwayDirection” and “runwayDirection” respectively.
Rationale for change
See https://aixmccb.atlassian.net/browse/AIXM-266
In order to avoid any misunderstanding and to align with other classes referencing RunwayDirection, the role name needs to explicitly indicate “runway direction”, not just “runway”.
Note: A similar change was already made with the CP AIXM-515 for the association between ObstacleAreaOrigin and RunwayDirection.
Impact assessment
When receiving data from AIXM 5.2 implementations, current AIXM 5.1(.1) systems will have to be able to map data back, as described in the mapping rules further in this document.
When receiving data from AIXM 5.1(.1) implementations, current AIXM 5.2 systems will have to be able to map data forward, as described in the mapping rules further in this document.
Mapping AIXM 5.1.1 to AIXM 5.2 (forward)
[MAPC-00] The following algorithm shall be applied:
- For each RunwayCentrelinePoint that has a onRunway element:
- change the element name into “onRunwayDirection”
- For each ApproachCondition, InstrumentApproachProcedure, StandardInstrumentArrival, StandardInstrumentDeparture, ProcedureTransition that have a runway element:
- change the element name into “runwayDirection”
Mapping AIXM 5.2 to AIXM 5.1.1 (backward)
[MAPC-00] The following algorithm shall be applied:
- For each RunwayCentrelinePoint that has a onRunwayDirection element:
- change the element name into “onRunway”
- For each ApproachCondition, InstrumentApproachProcedure, StandardInstrumentArrival, StandardInstrumentDeparture, ProcedureTransition that have a runwayDirection element:
- change the element name into “runway”
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) |
---|---|