Versions Compared

Version Old Version 6 New Version Current
Changes made by

POROSNICU Eduard

POROSNICU Eduard

Saved on

Key

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

ID:

AIXM-322

target version:

AIXM 5.2

version:

1.0

last updated:

17 AUG 2018

status:

APPROVED


Table of Contents
printablefalse

Description

Add dd a new attribute (“marked”) to VerticalStructure feature to indicate if the structure is marked or not.

Rationale for change

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

For consistency in the AIXM model, marking and lighting for obstacles should be treated in the same way. For lighting, the VerticalStructure feature includes two attributes that describe its lighting:

  • VerticalStructure.lighted – A simple indication that the obstacle is lighted, when no further details are available.
  • VerticalStructure.lightingICAOStandard – An indication that the lighting of a vertical structure used as criteria for the ICAO standard as described in Annex 14.

In AIXM v5.1, the VerticalStructure feature includes one attribute that describes its marking, VerticalStructure.markingICAOStandard, which is similar to the lightingICAOStandard attribute. However, there is no attribute to provide a simple indication that the obstacle is marked when no additional details are available. The new attribute VerticalStructure.marked for marking would be analogous to the VerticalStructure.lighted attribute for lighting.

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 for output towards a system (B) that uses AIXM 5.2 . No attributes are removed from the VerticalStructure feature in AIXM 5.2.When receiving data from AIXM 5.2 implementations, current 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) systems that are interested in the new data will have be able to map back the attribute VerticalStructure.marked to the attribute VerticalStructure.markingICAOStandard, using the workaround approach as described in the mapping rules further in this document.1 for input.

Change Proposal details

In the UML model, add the following attribute to the VerticalStructure feature:

  • marked (data type: CodeYesNoType; definition: A simple indication that the vertical structure is marked, when no further details are available.)

The UML class diagram to the right shows the new attribute.

Mapping AIXM 5.1.1 to AIXM 5.2 (forward)

NIL (Not applicable)

Mapping AIXM 5.2 to AIXM 5.1.1 (backward)

The following algorithm shall be applied:

  • For each VerticalStructure.marked that has the value ”YES”:
    • Remove the marked element
    • add an annotation.Note with 
  • purpose=“REMARK”
  • translatedNote.LinguisticNote.note=”marked=YES”
  • propertyName=markingICAOStandard

Mapping example

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

AIXM 5.2AIXM 5.1(.1)