v1.0.6
RunwayElement encoding
This section provides ‘RunwayElement’ 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 RunwayElement 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 RunwayElement is mapped to the AIXM 5.1 as feature RunwayElement with property Type set to "NORMAL".
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'.
One of the reasons to create multiple RunwayElements under one Runway may be the diversity of the surface characteristics of the Runway. One part of the Runway can have different Surface or different friction coefficients than other part of the Runway.
GML considerations:
AIXM 5.1 is based on GML. Hence, obtained geographical locations shall be transferred into a GML geometry object PolygonPatch.
Figure 1 : RunwayElement
Time
Feature RunwayElement shall be established in accordance with coding rules and requirements listed in AIXM 5.1 Temporality Model.
AIXM 5.1 features
RunwayElement is encoded to the AIXM 5.1 as RunwayElement features.
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, lvo. 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.86f614b3-3959-4cfd-b775-27dcc851c21e"> </hasMember> </AIXMBasicMessage>
Coding example -Â RunwayElement
<hasMember> <aixm:RunwayElement gml:id="uuid.86f614b3-3959-4cfd-b775-27dcc851c21e"> <gml:identifier codeSpace="urn:uuid:">86f614b3-3959-4cfd-b775-27dcc851c21e</gml:identifier> <aixm:timeSlice> <aixm:RunwayElementTimeSlice gml:id="uuid.c47f35cc-4700-437a-81c0-6705162df741"> <gml:validTime> <gml:TimePeriod gml:id="uuid.0d173c5d-b6bc-46c5-86d2-cb6b45b38351"> <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.e84c0431-4a34-483c-9a4e-1b69b942de27"> <gml:beginPosition>2020-09-01T00:00:00Z</gml:beginPosition> <gml:endPosition indeterminatePosition="unknown" /> </gml:TimePeriod> </aixm:featureLifetime> <aixm:type>NORMAL</aixm:type> <aixm:surfaceProperties> <aixm:SurfaceCharacteristics gml:id="uuid.1e101571-16c7-469a-9499-81c176b865df"> <aixm:composition>CONC_ASPH</aixm:composition> <aixm:preparation>PAVED</aixm:preparation> <aixm:classPCN>45</aixm:classPCN> <aixm:pavementTypePCN>FLEXIBLE</aixm:pavementTypePCN> <aixm:pavementSubgradePCN>B</aixm:pavementSubgradePCN> <aixm:maxTyrePressurePCN>X</aixm:maxTyrePressurePCN> <aixm:evaluationMethodPCN>TECH</aixm:evaluationMethodPCN> </aixm:SurfaceCharacteristics> </aixm:surfaceProperties> <aixm:associatedRunway xlink:href="#de77ab7f-6bb1-43b4-817e-ce4465deb3a3" xlink:title="12/30" /> <aixm:extent> <aixm:ElevatedSurface gml:id="uuid.f211d4a4-9cee-49c5-8232-bcf12c346dbb" srsName="urn:ogc:def:crs:EPSG::4326"> <gml:patches> <gml:PolygonPatch> <gml:exterior> <gml:Ring> <gml:curveMember> <gml:Curve gml:id="uuid.63ac9bfb-a495-4be2-a925-722cd9a231f7"> <gml:segments> <gml:GeodesicString interpolation="geodesic"> <gml:posList>50.10818836 14.24554382 50.10810686 14.24544709 50.10792576 14.24523156 50.10785808 14.24515087 50.10777016 14.24533757 50.10796399 14.24598385 50.10801161 14.24589457 50.10801953 14.24589793 50.10808946 14.24574987 50.10818564 14.24554965 50.10818836 14.24554382</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.6c61b059-3f5f-4add-9f3e-d0a4454263ca"> <aixm:usage> <aixm:ManoeuvringAreaUsage gml:id="uuid.2a0bc35a-14bd-40ba-8ec1-a12e292318b2"> <aixm:type>FORBID</aixm:type> <aixm:selection> <aixm:ConditionCombination gml:id="uuid.b5675be6-e52c-4f3b-89a4-bc612730e06e"> <aixm:aircraft> <aixm:AircraftCharacteristic gml:id="uuid.7f31b938-bc4a-408b-a625-9dc42c1185da"> <aixm:typeAircraftICAO>B748</aixm:typeAircraftICAO> </aixm:AircraftCharacteristic> </aixm:aircraft> </aixm:ConditionCombination> </aixm:selection> </aixm:ManoeuvringAreaUsage> </aixm:usage> </aixm:ManoeuvringAreaAvailability> </aixm:availability> </aixm:RunwayElementTimeSlice> </aixm:timeSlice> </aixm:RunwayElement> </hasMember>
Download feature RunwayElement:
Â
Status: Published