[AIXM-526] Addition of RF Leg radius

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

[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 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] For each SegmentLeg class and it’s specialised subclasses: ArrivalFeederLeg, FinalLeg, InitialLeg , IntermediateLeg, MissedApproachLeg, ArrivalLeg, DepartureLeg that 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 Input	AIXM Output