ID: | AIXM-339 |
target version: | AIXM 5.2 |
version: | 1.0 |
last updated: | 17 AUG 2018 |
status: | APPROVED |
|
---|
Description
Add the new code BUOY to the codelist for CodeRunwayMarkingBaseType.
Rationale for change
See https://aixmccb.atlassian.net/browse/AIXM-292
Water runways often use buoys as the only element to mark the runway, and the current version of AIXM (v5.1) does not allow any straightforward way to encode this data in a situation where no additional information is available about each floating element and it is not possible to provide the individual buoy data. This additional value is of the same kind as the RUNWAY_NUMBERS value, which is also a global indication of the type of marking
Impact assessment
There is no impact on existing implementations as the current AIXM 5.1(.1) data remains fully valid against AIXM 5.2. No values are removed from this list.
When receiving data from AIXM 5.2 implementations, current AIXM 5.1(.1) systems will have be able to map back the BUOY value into OTHER:BUOY, as described in the mapping rules further in this document.
Change Proposal details
In the UML model, add the following code to CodeRunwayMarkingBaseType:
- BUOY = “Marking buoys (for waterways and seaplane bases)”
Mapping AIXM 5.1.1 to AIXM 5.2 (forward)
The following algorithm shall be applied:
- For each RunwayDirection.approachMarkingType that has the value ”OTHER: BUOY”:
- replace the value with “BUOY”
Mapping AIXM 5.2 to AIXM 5.1.1 (backward)
The following algorithm shall be applied:
- For each RunwayDirection.approachMarkingType that has the value “BUOY”:
- replace the value with “OTHER: BUOY”
Mapping example
(Note: for mapping test data see: https://github.com/aixm/mapping_52_511/tree/master/AIXM-xxx339)
AIXM 5.2 | AIXM 5.1(.1) | ||||
---|---|---|---|---|---|
|
|