Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

ID:

AIXM-414

target version:

AIXM 5.2

version:

1.0

last updated:

15 MAY 2019

status:

APPROVED


Description

Add new attribute for the name to airspace volume.

Rationale for change

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

In AIXM, the Airspace feature is associated with the AirspaceVolume object that forms the geometry components of the airspace.  In order to facilitate the coding of an airspace volume that has several parts, each with its own name, it is recommended to add an attribute for the AirspaceVolume.name. The current model only allows for the part name to be coded as an annotation or as two separate airspace instances that are aggregated as a final airspace, which is unnecessarily complicated.

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. 

AIXM 5.2 files that use the new attributes would be invalid against the AIXM 5.1.1 schema and will need to be converted, applying one of the options specified in the mapping rules.

Change Proposal details

In the UML model:

  • In the AirspaceVolume object
    • add a name attribute defined as “The free text identifier or name of the the airspace volume”, data type TextNameType

The UML class diagram to the right shows the new element of the new model for Airspace Volume.


Mapping AIXM 5.1.1 to AIXM 5.2 (forward)

Not applicable.

Mapping AIXM 5.2 to AIXM 5.1.1 (backward)

[MAPC-02] From the three backward mapping options applicable in this case, the first two (discard the value or use an extension) are straightforward and do not need any further details. The 3rd option (backward mapping into a Note) is detailed in order to provide a complete description of this case and its conversion option. The following mapping into Note algorithm is proposed:

  • Remove the new element
  • Add an annotation.Note associated with the owner class having
    • purpose=“OTHER:BACKWARD_MAPPING”;
    • translatedNote.LinguisticNote.note=”name:<value of name>

Mapping example

Mapping example to be added...


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

AIXM 5.2AIXM 5.1(.1)







  • No labels