Versions Compared

Version Old Version 1 New Version Current
Changes made by

georgiana.andrei04

ADAM STYLES

Saved on

Key

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

ID:

AIXM-526

target version:

AIXM 5.2

version:

1.0

last updated:

08 AUG 2022

status:

APPROVED


Table of Contents
printablefalse

Description

An attribute for RF leg radius is added to the SegmentLeg class.

Rationale for change

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

Current model is missing a possibility to indicate leg radius in support of SegmentLeg.legTypeARINC=’RF’ (Radius to Fix), for which this element is required in order to align with ARINC 424.

This requires adding a separate attribute “radius'' to the SegmentLeg class.

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 SegmentLeg class add the following attribute:
    • radius, type = ValDistanceType, definition = “Radius of the turning segment.”.

The following UML class diagram indicates the new attribute. Other approved changes in the list of SegmentLeg attributes are also shown in this diagram, for completeness sake:


Mapping AIXM 5.1.1 to AIXM 5.2 (forward)

The following algorithm shall be applied:

Not applicable.

Mapping AIXM 5.2 to AIXM 5.1.1 (backward)

[MAPC-02] For each SegmentLeg class and it’s specialised subclasses: ArrivalFeederLeg, FinalLeg, InitialLeg , IntermediateLeg, MissedApproachLeg, ArrivalLeg, DepartureLegthat have radius 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 radius element
  • Add an annotation.Note associated with the owner class or subclass having
  • purpose=“OTHER:BACKWARD_MAPPING”;
  • LinguisticNote.note=”radius: <value of radius> <uom of radius>

Mapping example

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

AIXM 5.2InputAIXM 5.1(.1)Output