Versions Compared

Version Old Version 1 New Version 2
Changes made by

georgiana.andrei04

VLASOV Sergiy (EXT) (Deactivated)

Saved on

Key

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

ID:

AIXM-530

target version:

AIXM 5.2

version:

1.0

last updated:

08 AUG 2022

status:

APPROVED


Table of Contents
printablefalse

Description

Additional attribute maxWingSpan is added to GuidanceLine.

Rationale for change

https://aixmccb.atlassian.net/browse/AIXM-479

It was identified that GuidanceLine was missing an attribute that could support wingspan limitations for the aircraft maneuvering among different airport movement areas using e.g. various guidance lines connecting the surfaces.

The new maxWingSpan attribute introduced in the GuidanceLine is added to cover these needs.

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

. No values are removed from this list.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 will be able to map back the new values, as described in the mapping rules further in this document

.1 for input.

Change Proposal details

In the UML model, in the GuidanceLine feature:

  • Add a new maxWingSpan attribute defined as “A limitation of aircraft’s wing span. It can be used to indicate the size of an aircraft that can maneuver along a guidance line.”, data type = ValDistanceType.

The following UML class diagram shows the additional attribute:

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:

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

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)