v1.0.6

LandAndHoldShortOperationLocation encoding

Owned by WILSON Scott
Last updated: 2021 Mar 31

This section provides ‘LandAndHoldShortOperationLocation’ feature data encoding guidance.


General

AMD data encoding can start when the necessary geographic information, aeronautical information and basic knowledge regarding the structure of created feature is available. 

From the geographical point of view, two or more points of the LandAndHoldShortOperationLocation need to be captured. The key attributes are the longitude, latitude in reference with WGS-84 and the elevation of each captured point. In the next part the process of converting the geographical information into the GML form, thus into geometry information is described.

Based on Aeronatical Data Catalogue the required type of geometry for feature LandAndHoldShortOperationLocation is 'Line'. The definition of Curve/Line can be found in the Table A1-9 Data types of the Aeronautical Data Catalogue.

AMD encoding

AIXM 5.1

ED-99 feature LandAndHoldShortOperationLocation is mapped in the AIXM 5.1 as feature Runway Marking with property Type set to "OTHER:LAHSO". The option "LAHSO" within the type of the Runway Marking is not in the scope of the AIXM 5.1 and is part of the extension.

Geometry

In the AIXM 5.1 the geometry of the Runway Marking can be point, curve or polygon, but in case of this feature the correct geometry is curve encoded as object ElevatedCurve.

For more information regarding AIXM 5.1 Geometry encoding follow 'AIXM data coding'.

GML considerations:

AIXM 5.1 is based on GML. Hence, obtained geographical locations shall be transferred into a GML geometry object GeodesicString.


Figure 1 : LandAndHoldShortOperationLocation

Time

Feature LandAndHoldShortOperationLocation shall be established in accordance with coding rules and requirements listed in AIXM 5.1 Temporality Model.

AIXM 5.1 features

LandAndHoldShortOperationLocation is encoded to the AIXM 5.1 as Runway Marking features.

All associations are shown in the UML Diagram (see below).

Runway Element feature

http://aixm.aero/sites/aixm.aero/files/imce/AIXM51HTML/AIXM/Class_RunwayMarking.html

UML Diagram (Surface Marking)

http://aixm.aero/sites/aixm.aero/files/imce/AIXM51HTML/AIXM/Diagram_SurfaceMarking.html

Content of example

This is a ficticious example. No feature was present at the aerodrome used.

The following AMD properties are not covered in the AIXM 5.1. coding example: vres, hres, integr, idthr, idp, lahsotyp, holddir. These are covered by an AIXM 5.1. extension.

Coding example - Structure of message

<AIXMBasicMessage  ...>
  <aixm:messageMetadata>
  </aixm:messageMetadata>
  <hasMember>
    <aixm:AirportHeliport gml:id="uuid.0b7a2688-ab95-47e6-82c2-23fe321c4a48">
  </hasMember>
  <hasMember>
    <aixm:Runway gml:id="uuid.3f4952ee-a237-47d9-ab33-23f46a6332b1">
  </hasMember>
  <hasMember>
    <aixm:RunwayMarking gml:id="uuid.5c578d87-8ad7-4052-9ffe-6f4bb813bddb">
  </hasMember>
</AIXMBasicMessage>

Coding example - AIXM 5.1

  <hasMember>
    <aixm:RunwayMarking gml:id="uuid.5c578d87-8ad7-4052-9ffe-6f4bb813bddb">
      <gml:identifier codeSpace="urn:uuid:">5c578d87-8ad7-4052-9ffe-6f4bb813bddb</gml:identifier>
      <aixm:timeSlice>
        <aixm:RunwayMarkingTimeSlice gml:id="uuid.90ad4f6f-2565-4b47-869b-21e31d3d1f64">
          <gml:validTime>
            <gml:TimePeriod gml:id="uuid.98c8ff5d-4985-45f8-b146-87aed9960271">
              <gml:beginPosition>2020-09-01T00:00:00Z</gml:beginPosition>
              <gml:endPosition indeterminatePosition="unknown" />
            </gml:TimePeriod>
          </gml:validTime>
          <aixm:interpretation>BASELINE</aixm:interpretation>
          <aixm:sequenceNumber>1</aixm:sequenceNumber>
          <aixm:correctionNumber>0</aixm:correctionNumber>
          <aixm:featureLifetime>
            <gml:TimePeriod gml:id="uuid.4291a53b-f13e-4bf9-9b21-10593160c922">
              <gml:beginPosition>2020-09-01T00:00:00Z</gml:beginPosition>
              <gml:endPosition indeterminatePosition="unknown" />
            </gml:TimePeriod>
          </aixm:featureLifetime>
          <aixm:element>
            <aixm:MarkingElement gml:id="uuid.af5cb2b6-7cd0-49d9-8166-4a85c905cdb9">
              <aixm:extent_curveExtent>
                <aixm:ElevatedCurve gml:id="uuid.ee9c828f-970f-4c9d-9f5a-4e787b6baaea" srsName="urn:ogc:def:crs:EPSG::4326">
                  <gml:segments>
                    <gml:GeodesicString interpolation="geodesic">
                      <gml:posList>50.10855452 14.24945265 50.10873449 14.24929766 50.10890974 14.24914822</gml:posList>
                    </gml:GeodesicString>
                  </gml:segments>
                  <aixm:horizontalAccuracy uom="M">0.5</aixm:horizontalAccuracy>
                  <aixm:elevation uom="M">376</aixm:elevation>
                  <aixm:verticalAccuracy uom="M">0.5</aixm:verticalAccuracy>
                </aixm:ElevatedCurve>
              </aixm:extent_curveExtent>
            </aixm:MarkingElement>
          </aixm:element>
          <aixm:markingLocation>OTHER:LAHSO</aixm:markingLocation>
          <aixm:markedRunway xlink:href="#3f4952ee-a237-47d9-ab33-23f46a6332b1" xlink:title="06/24" />
        </aixm:RunwayMarkingTimeSlice>
      </aixm:timeSlice>
    </aixm:RunwayMarking>
  </hasMember>


Download feature LandAndHoldShortOperationLocation:

BL_LAHSO.xml

 



Status: Published