/
[AIXM-548] Seaplane model improvements

[AIXM-548] Seaplane model improvements

Owned by georgiana.andrei04
Last updated: 2024 Aug 22 by ADAM STYLES

ID:

AIXM-548

target version:

AIXM 5.2

version:

1.0

last updated:

08 AUG 2022

status:

APPROVED


Description

An association is added between SeaplaneLandingArea and AirportHeliport. Additional properties related to the operation of seaplanes are added in Runway and Taxiway together with a new Gangway feature associated with the SeaplaneLandingArea.

Rationale for change

Seaplane landing areas have characteristics that are the same as those of an airport/heliport (i.e. ICAO designator, name). In order to encode these characteristics, an association is required between SeaplaneLandingArea and Airport/Heliport. In the current model, this association is missing and needs to be added in order to support encoding of these data elements.

In addition to adding the missing association to AirportHeliport, three elements were identified in the APAC guidance as minimum specifications for a water aerodrome. Using prior AIRM-AIXM analysis, each element related to seaplanes was examined using FAA OV-7 and AC 150/5300-18B and cross-referenced with the ICAO-APAC Guidance on Seaplanes. From this analysis, three elements were identified as common to both the ICAO and FAA documents: TaxiChannel, TurningBasin, and Gangway. While some elements such as TaxiChannel and TurningBasin may be modeled with existing AirportHeliport classes (i.e. Taxiway), the remaining element Gangway has properties that cannot be coded with existing AIXM features and is added as a new feature with an association to the SeaplaneLandingArea in AIXM.

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 Runway feature:

  • Modify Runway feature to be defined as “A defined rectangular area on a land or a water aerodrome/heliport prepared for the landing and take-off of aircraft. Note: this includes the concept of Final Approach and Take-Off Area (FATO) for helicopters.”
  • Add a new depth attribute defined as “The depth of the water measured at low water level in the water runway should not be less than 1.8 m (6 ft.) or less than 0.3 m below the hull or floats when the seaplane is stationary and loaded to maximum takeoff weight.”, data type ValDistanceType with uom.

In the UML model, in the Taxiway feature:

  • Add a new depth attribute defined as “The depth of the water measured at low water level in the water taxiway should not be less than 1.8 m (6 ft.) or less than 0.3 m below the hull or floats when the seaplane is stationary and loaded to maximum takeoff weight.”, data type ValDistanceType with uom.
  • Add a new diameter attribute defined as “A diameter measured at low water level of not less than twice the specified minimum width of the corresponding water turning basin.”, data type ValDistanceType with uom.

In the UML model:

  • Add association SeaplaneLandingArea isSituatedAt AirportHelport
    • AirportHeliport role name “associatedAirportHeliport” (definition = “The airport/heliport the seaplane landing area is associated with”.”), multiplicity 0..1
    • SeaplaneLandingArea with multiplicity 0..*
  • Add code values to CodeTaxiwayBaseType
    • TURNING_BASIN, type = “string”, definition = “A water area used for the water taxi maneuvering of seaplanes along shoreline facilities and at the ends of a narrow water runway.”
    • CHANNEL, type = “string”, definition = “A defined path on a water aerodrome, intended for the use of taxing seaplanes.”
  • Add code value to CodeRunwayBaseType
    • WATER_RWY, type = “string”, definition = “A defined rectangular area on a water aerodrome, intended for the landing and take-off of seaplanes along its length.” 

The following UML class diagram shows the new attribute and its list of values.


  • Add feature Gangway with the definition “A movable walkway where people board and disembark such as platforms, and piers. Gangways shall be painted red or signage provided indicating seaplane access only.”
    • Add new attribute width defined as “The physical width of the Gangway”, datatype ValDistanceType with uom
    • Add new attribute length defined as ““The physical length of the Gangway”, datatype ValDistanceType with uom
    • Add new attribute type defined as “The type of gangway assigned to a seaplane landing area.”, datatype CodeGangwayType
    • Add new attribute mobility defined as “Defines whether a Gangway is mobile or stationary.”, datatype CodeYesNoType
  • Add complex data type CodeGangwayType which is a specialization of the CodeGangwayBaseType class and enables the use of Nil reason.
  • Add CodeGangwayBaseType which is a code indicating the type of Gangway.
  • Add to CodeGangwayBaseType
    • WATER, definition = “A gangway that exists on water or a floating dock site.”
    • GROUND, definition = “A gangway that exists on the ground”.
    • OTHER = Other
  • Add association SeaplaneLandingArea hasGangway Gangway
    • Gangway role name “assignedGangway” (definition = “The gangway the seaplane landing area is associated with”.”), multiplicity 0..1
    • Gangway with multiplicity 0..*
  • Add association Gangway hasAnnotations Note with
    • Note role “annotation” (definition = “A free text remark concerning the Gangway or one of its properties.”), multiplicity 0..*

The following UML class diagram shows the new attribute and its list of values.



Mapping AIXM 5.1.1 to AIXM 5.2 (forward)

[MAPC-00] The following data conversion algorithm is proposed for Runway.type values:

  • Replace ‘OTHER:WATER_RWY’ with ‘WATER_RWY’ 

[MAPC-00] The following data conversion algorithm is proposed for Taxiway.type values:

  • Replace ‘OTHER:CHANNEL’ with ‘CHANNEL’
  • Replace ‘OTHER:TURNING_BASIN’ with ‘TURNING_BASIN’

Mapping AIXM 5.2 to AIXM 5.1.1 (backward)

  • [MAPC-00] The following data conversion algorithm is proposed for Runway.type values:
    • Replace ‘WATER_RWY’ with ‘OTHER:WATER_RWY’
  • [MAPC-00] The following data conversion algorithm is proposed for Taxiway.type values:
    • Replace ‘CHANNEL’ with ‘OTHER:CHANNEL’
    • Replace ‘TURNING_BASIN’ with ‘OTHER:TURNING_BASIN’


  • [MAPC-02] For each SeaplaneLandingArea that has a child associatedAirportHeliport, 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:
  • For each SeaplaneLandingArea that has an associatedAirportHeliport element:
    • add an annotation.Note to the SeaplaneLandingArea with:
      • purpose=“OTHER:BACKWARD_MAPPING”;
      • LinguisticNote.note=”isSituatedAt AirportHeliport with xlink:href:<associatedAirportHeliport:xlink:href>>;
    • Remove the associatedAirportHeliport element.

 

  • [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 attributedepth.
  • remove the new attributediameter
  • Add an annotation.Note associated with the owner class having
    • purpose=“OTHER:BACKWARD_MAPPING”;
    • LinguisticNote.note=”depth:<value of depth>;diameter:<value-of diameter>.


  • [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 attributedepth.
  • Add an annotation.Note associated with the owner class having
    • purpose=“OTHER:BACKWARD_MAPPING”;
    • LinguisticNote.note=”depth:<value of depth>;


  • [MAPC-99] For Gangway, which is a new feature, no useful mapping is possible. If needed in AIXM 5.1.1, it can be used through an extension.

Mapping example

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

AIXM InputAIXM Output