v1.0.6
RunwayShoulder encoding
This section provides ‘RunwayShoulder’ 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 RunwayShoulder 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 RunwayElement 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 RunwayShoulder is mapped to the AIXM 5.1 as feature RunwayElement with property Type set to "SHOULDER".
Geometry
In the AIXM 5.1 the geometry of the RunwayElement 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 :Â RunwayShoulder
(Note: the dark part of the Runway is only park of background image and is not part of the RunwayShoulder)
Time
Feature RunwayShoulder shall be established in accordance with coding rules and requirements listed in AIXM 5.1 Temporality Model.
AIXM 5.1 features
RunwayShoulder is encoded to the AIXM 5.1 as RunwayElement feature with property type set to 'SHOULDER'.
All associations are shown in the UML Diagram (see below).
RunwayElement feature
http://aixm.aero/sites/aixm.aero/files/imce/AIXM51HTML/AIXM/Class_RunwayElement.html
UML Diagram (Runway)
http://aixm.aero/sites/aixm.aero/files/imce/AIXM51HTML/AIXM/Diagram_Runway.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.de77ab7f-6bb1-43b4-817e-ce4465deb3a3"> </hasMember> <hasMember> <aixm:RunwayElement gml:id="uuid.757f11b7-4130-4b4b-b274-3696bbba411c"> </hasMember> </AIXMBasicMessage>
Coding example -Â RunwayShoulder
<hasMember> <aixm:RunwayElement gml:id="uuid.757f11b7-4130-4b4b-b274-3696bbba411c"> <gml:identifier codeSpace="urn:uuid:">757f11b7-4130-4b4b-b274-3696bbba411c</gml:identifier> <aixm:timeSlice> <aixm:RunwayElementTimeSlice gml:id="uuid.a8a95f82-580d-4413-9c14-a5766fe0a6d2"> <gml:validTime> <gml:TimePeriod gml:id="uuid.bb49b17d-8194-4e6e-bc38-98f11cd15b2d"> <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.cac89765-b3b6-47ed-93df-b40fca124579"> <gml:beginPosition>2020-09-01T00:00:00Z</gml:beginPosition> <gml:endPosition indeterminatePosition="unknown" /> </gml:TimePeriod> </aixm:featureLifetime> <aixm:type>SHOULDER</aixm:type> <aixm:surfaceProperties> <aixm:SurfaceCharacteristics gml:id="uuid.0301c977-6d29-4421-bba1-e526c07f54f6"> <aixm:composition>CONC</aixm:composition> </aixm:SurfaceCharacteristics> </aixm:surfaceProperties> <aixm:associatedRunway xlink:href="#de77ab7f-6bb1-43b4-817e-ce4465deb3a3" xlink:title="12/30" /> <aixm:extent> <aixm:ElevatedSurface gml:id="uuid.a8390e23-2217-4fa1-b087-f9ac22b73792" srsName="urn:ogc:def:crs:EPSG::4326"> <gml:patches> <gml:PolygonPatch> <gml:exterior> <gml:Ring> <gml:curveMember> <gml:Curve gml:id="uuid.c86493ab-c851-4b15-bea3-0489dd2dac47"> <gml:segments> <gml:GeodesicString interpolation="geodesic"> <gml:posList>50.10762335 14.2468655 50.10759152 14.24675955 50.1075094 14.24692953 50.10750328 14.2469413 50.1074606 14.24703092 50.10743878 14.24707491 50.10737404 14.24721097 50.10730789 14.2473455 50.10723792 14.24749004 50.10717354 14.24762404 50.10710827 14.24775824 50.10706452 14.24784907 50.1069905 14.24800211 50.10694961 14.24808837 50.10621937 14.24959991 50.10577376 14.25052266 50.10555623 14.25097297 50.10560858 14.25103769 50.10571991 14.25080399 50.10596111 14.25030431 50.10620392 14.24980456 50.10658826 14.24900806 50.10683158 14.24850183 50.1070504 14.24804822 50.10712071 14.24789938 50.10719229 14.24775265 50.10726383 14.24760538 50.10733316 14.24746183 50.10740595 14.24731131 50.1074946 14.24712826 50.10755487 14.24700306 50.10760956 14.24689347 50.10762335 14.2468655</gml:posList> </gml:GeodesicString> </gml:segments> </gml:Curve> </gml:curveMember> </gml:Ring> </gml:exterior> </gml:PolygonPatch> </gml:patches> <aixm:horizontalAccuracy uom="M">0.5</aixm:horizontalAccuracy> <aixm:elevation uom="M">376</aixm:elevation> <aixm:verticalAccuracy uom="M">0.5</aixm:verticalAccuracy> </aixm:ElevatedSurface> </aixm:extent> <aixm:availability> <aixm:ManoeuvringAreaAvailability gml:id="uuid.3ab2ca02-5bd8-4bed-bf1a-12f4435f44c4"> <aixm:operationalStatus>NORMAL</aixm:operationalStatus> </aixm:ManoeuvringAreaAvailability> </aixm:availability> </aixm:RunwayElementTimeSlice> </aixm:timeSlice> </aixm:RunwayElement> </hasMember>
Download feature RunwayShoulder:
Â
Status: Published