[AIXM-414] Add name property to AirspaceVolume

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

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

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

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

AIXM 5.2	AIXM 5.1(.1)