Versions Compared

Version Old Version 1 New Version 2
Changes made by

POROSNICU Eduard

VLASOV Sergiy (EXT) (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

ID:

AIXM-495

target version:

AIXM 5.2

version:

1.0

last updated:

13 AUG 2020

status:

PROPOSED


Table of Contents
printablefalse

Description

Add an association from VerticalStructure towards ArrestingGear.

Rationale for change

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

Arresting devices are considered as obstacles. When “up”, they can have an impact on the performance calculation. AIXM allows encoding arresting gear devices, but does not include an association between this feature and VerticalStructure.

In general, AIXM allows to indicate that a VerticalStructure is actually another aeronautical feature support/building, such as a Navaid, etc. Adding an explicit between ArrestingGear and VerticalStructure would allow to indicate that the two are the same, when the database contains both.

Impact assessment

There is no impact on existing implementations as the current

Image Added

[FWD_1:1] No data mapping is necessary 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

.When receiving data from systems that use the new association, the backward mapping rules defined further in the document shall be applied

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 a new association as follows

  • VerticalStructure isUsedAs ArrestingGear
    • 0..* on the ArrestingGear side with “arrestingDevice” role name, definition = “The VerticalStructure is an arresting device”;
    • 0..* on the VerticalStructure side.

The change is highlighted (in blue) in the UML class diagram to the right.

Mapping AIXM 5.1.1 to AIXM 5.2 (forward)

Not applicable.

Mapping AIXM 5.2 to AIXM 5.1.1 (backward)

[MAPC-03] From the three options discussed for this mapping case, the first two (drop the association data or use an extension) are straight-forward and are not detailed here. Only the third option (mapping into a note) is detailed here:

  • For each occurrence of VerticalStructure that has an arrestingDevice child element:
    • Add an annotation.Note associated with the <<feature>>VerticalStructure
      • purpose=“OTHER:BACKWARD_MAPPING”;
      • translatedNote.LinguisticNote.note=”arrestingDevice:<value of arrestingDevice@xlink:href>, <value of arrestingDevice@xlink:title>”
    • Remove the arrestingDevice element

Mapping example

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

AIXM 5.2AIXM 5.1(.1)