v1.0.6

RunwayMarking encoding

Owned by WILSON Scott
Last updated: 2021 Mar 31

This section provides ‘RunwayMarking’ 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, several points of the outer border of the RunwayMarking 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 RunwayMarking is 'Polygon'. The definition of Polygon can be found in the Table A1-9 Data types of the Aeronautical Data Catalogue.

AMD encoding

AIXM 5.1

ED-99 feature RunwayMarking is mapped to the AIXM 5.1 as feature RunwayMarking.

Geometry

In the AIXM 5.1 the geometry of the RunwayMarking is polygon encoded as object ElevatedSurface.

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 PolygonPatch.


Figure 1 : RunwayMarking

Time

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

AIXM 5.1 features

RunwayMarking is encoded to the AIXM 5.1 as RunwayMarking features.

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

RunwayMarking 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

The following AMD properties are not covered in the AIXM 5.1. coding example: vres, hres, integr. 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.0525a3fa-3b07-41ff-b260-e09feab801f7">
  </hasMember>
</AIXMBasicMessage>

Coding example - RunwayMarking

  <hasMember>
    <aixm:RunwayMarking gml:id="uuid.0525a3fa-3b07-41ff-b260-e09feab801f7">
      <gml:identifier codeSpace="urn:uuid:">0525a3fa-3b07-41ff-b260-e09feab801f7</gml:identifier>
      <aixm:timeSlice>
        <aixm:RunwayMarkingTimeSlice gml:id="uuid.2de051ff-21b6-49c8-a80c-8e76717c9395">
          <gml:validTime>
            <gml:TimePeriod gml:id="uuid.1b275d03-e0ea-458b-8cff-38abfa6717e1">
              <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.7449ae96-bee2-45af-99dd-3faecc4b2d90">
              <gml:beginPosition>2020-09-01T00:00:00Z</gml:beginPosition>
              <gml:endPosition indeterminatePosition="unknown" />
            </gml:TimePeriod>
          </aixm:featureLifetime>
          <aixm:element>
            <aixm:MarkingElement gml:id="uuid.895e3d15-003e-4f6d-90d9-ac43b59e3db1">
              <aixm:extent_surfaceExtent>
                <aixm:ElevatedSurface gml:id="uuid.49256bd7-ee07-427e-a9b8-964fbabb6308" srsName="urn:ogc:def:crs:EPSG::4326">
                  <gml:patches>
                    <gml:PolygonPatch>
                      <gml:exterior>
                        <gml:Ring>
                          <gml:curveMember>
                            <gml:Curve gml:id="uuid.ae5af9f9-7577-419b-99c0-f44b4dc1b3e2">
                              <gml:segments>
                                <gml:GeodesicString interpolation="geodesic">
                                  <gml:posList>50.11435525 14.26834844 50.11430628 14.26838364 50.11413542 14.26781356 50.11418436 14.26777822 50.11435525 14.26834844</gml:posList>
                                </gml:GeodesicString>
                              </gml:segments>
                            </gml:Curve>
                          </gml:curveMember>
                        </gml:Ring>
                      </gml:exterior>
                    </gml:PolygonPatch>
                  </gml:patches>
                  <aixm:horizontalAccuracy uom="M">1</aixm:horizontalAccuracy>
                  <aixm:elevation uom="M">376</aixm:elevation>
                  <aixm:verticalAccuracy uom="M">1</aixm:verticalAccuracy>
                </aixm:ElevatedSurface>
              </aixm:extent_surfaceExtent>
            </aixm:MarkingElement>
          </aixm:element>
          <aixm:markingLocation>AIM</aixm:markingLocation>
          <aixm:markedRunway xlink:href="#3f4952ee-a237-47d9-ab33-23f46a6332b1" xlink:title="06/24" />
        </aixm:RunwayMarkingTimeSlice>
      </aixm:timeSlice>
    </aixm:RunwayMarking>
  </hasMember>


Download feature RunwayMarking:

BL_RunwayMarking.xml

 



Status: Published