/
[AIXM-318] Runway side additional value

[AIXM-318] Runway side additional value

ID:

AIXM-318

target version:

AIXM 5.2

version:

1.0

last updated:

17 AUG 2018

status:

APPROVED


Description

Add the new code CENTRE to the codelist for CodeSideBaseType.

Rationale for change

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

The rationale for this change was discovered when describing an obstacle location in relation to a runway. An obstacle can also be situated directly on an extension of the runway’s centerline. The current list of values (LEFT, RIGHT, BOTH, OTHER) does not include a value to describe this situation, so when using the current version of AIXM this must be coded using the OTHER value. Beyond just the obstacle placement, there are other attributes which use the same codelist and would have this new value available for use, as appropriate.

Further, this change would align the AIXM codelist values with those currently used by the FAA to describe obstacle placement in relation to a runway, as described in the FAA Airport Master Record standard (see FAA Advisory Circular 150/5200-35a).

Impact assessment

[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 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.

Change Proposal details

In the UML model, add the following code to CodeSideBaseType:

  • CENTRE (definition: On the axis)

The new coded value is shown in the UML class diagram at the right.

Mapping AIXM 5.1.1 to AIXM 5.2 (forward)

 The following algorithm shall be applied:

  • For each ObstaclePlacement.obstaclePlacement that has the value ”OTHER:CENTRE“ or “OTHER:CENTER”: 
    • replace the value with “CENTRE”;
  • For each Ridge.side that has the value ”OTHER:CENTRE“ or “OTHER:CENTER”: 
    • replace the value with “CENTRE”;
  • For each RunwayContamination.clearedSide that has the value ”OTHER:CENTRE“ or “OTHER:CENTER”: 
    • replace the value with “CENTRE”.

Mapping AIXM 5.2 to AIXM 5.1.1 (backward)

The following algorithm shall be applied: 

  • For each ObstaclePlacement.obstaclePlacement that has the value ”CENTRE“:
    • replace the value with “OTHER:CENTRE”;
  • For each Ridge.side that has the value ”CENTRE“: 
    • replace the value with “OTHER:CENTRE”;
  • For each RunwayContamination.clearedSide that has the value ”CENTRE“: 
    • replace the value with “OTHER:CENTRE”;
  • For each FinalLeg.courseOffsetSide that has the value ”CENTRE“: 
    • replace the value with “OTHER:CENTRE”;
    • add an annotation.Note
      • purpose=”WARNING”
      • property=”courseOffsetSide”
      • translatedNote.LinguisticNote.note=“This values is mapped back from a future AIXM version, but it does not seem to be appropriate for this attribute!”
  • For each VisualGlideSlopeIndicator.position that has the value ”CENTRE“: 
    • replace the value with “OTHER:CENTRE”;
    • add an annotation.Note
      • purpose=”WARNING”
      • property=”position”
      • translatedNote.LinguisticNote.note=“This values is mapped back from a future AIXM version, but it does not seem to be appropriate for this attribute!”


Mapping example

(Note: for mapping test data see: https://github.com/aixm/mapping_52_511/tree/master/AIXM-318) 

AIXM 5.2AIXM 5.1(.1)