[AIXM-608] Add availability association to GuidanceLine

Description

An association between GuidanceLine and ManoeuvringAreaAvailability is added, including an association class that replaces the usageDirection attribute. The maxSpeed attribute of the GuidanceLine is deleted.

Rationale for change

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

On complex airports and in particular on complex Taxiway intersections, guidance lines have usage limitations, sometimes separately for each direction based on the wingspan, type of aircraft, or even the ICAO code of the aircraft. The Taxiway/TaxiwayElement availability does not fully cover this issue because multiple GuidanceLines may be located on a single TaxiwayElement with different limitations.

The GuidanceLine already has two attributes that can provide usage limitation (direction and maximum speed). Instead of adding supplementary attributes for aircraft wingspan, weight, type etc. in the GuidanceLine, it is proposed to apply the same approach as for the other airport movement area usage limitations, which is an association with the general ManoeuvringAreaAvailability.

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.

Change Proposal details

In the UML model, in the GuidanceLine feature:

• delete the maxSpeed attribute
• delete the usageDirection attribute
• add composition relationship GuidanceLine isOperationalBy ManoeuvringAreaAvailability with the following characteristics:
  • ManoeuvringAreaAvailability multiplicity 0..*,. role name “availability”, role definition = “Information about usage permissions and/or constraints that apply to the GuidanceLine”
  • association class GuidanceLineDirection, <<object>> stereotype, definition = “An association class that identifies the GuidanceLine direction concerned by the ManoeuvringAreaAvailability”
    • attributes:
      • direction, CodeDirectionType, definition = “Indicates the direction concerned by the availability information with reference to the start and end points of the associated ElevatedCurve.”
      • cardinalDirection, CodeCardinalDirectionType, definition = “Indicates the direction concerned by the availability information with reference to the conventional compass directions (N, S, NE, Etc.)”
    • GuidanceLineDirection hasAnnotations Note with
      • Note role “annotation” (definition = “A free text remark concerning the guidance line direction or one of its properties.”), multiplicity 0…*

The following UML class diagram shows the deleted attributes and the new association:

Mapping AIXM 5.1.1 to AIXM 5.2 (forward)

[MAPC-00] For each GuidanceLine that has maxSpeed and/or usageDirection child element:

• add a child availabilityGuidanceLineDirection element with:
  • direction value copied from usageDirection value
  • ManoeuvringAreaAvailability with:
    • operationalStatus = FORBID
    • ManoeuvringAreaUsage having:
      • selection.ConditionCombination.aircraft.AircraftCharracteristic with speed copied from the maxSpeed and speedInterpretation=”ABOVE”

Mapping AIXM 5.2 to AIXM 5.1.1 (backward)

[MAPC-99] For each GuidanceLine that has availability child elements, the new association provides the possibility to code complex usage restrictions for the GuidanceLine, which are not mappable into the old model. Delete the availability elements.

Mapping example

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

AIXM Input	AIXM Output