Supporting material for ICAO Aerodrome Mapping Data Sets
v1.0.6
This section provides ‘RunwayIntersection’ 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 theTable A1-9 Data types of the Aeronautical Data Catalogue.
AMD encoding
AIXM 5.1
ED-99 feature RunwayIntersection is mapped to the AIXM 5.1 as feature RunwayElement with property Type set to "INTERSECTION".
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 : RunwayIntersection
Time
Feature RunwayIntersection shall be established in accordance with coding rules and requirements listed in AIXM 5.1 Temporality Model.
AIXM 5.1 features
RunwayIntersection is encoded to the AIXM 5.1 as RunwayElement with property Type set to "INTERSECTION".
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.3f4952ee-a237-47d9-ab33-23f46a6332b1"> </hasMember> <hasMember> <aixm:Runway gml:id="uuid.de77ab7f-6bb1-43b4-817e-ce4465deb3a3"> </hasMember> <hasMember> <aixm:RunwayElement gml:id="uuid.594237b4-3fd6-4343-9665-a85503c26aee"> </hasMember> </AIXMBasicMessage>
Coding example - RunwayIntersection
<hasMember> <aixm:RunwayElement gml:id="uuid.594237b4-3fd6-4343-9665-a85503c26aee"> <gml:identifier codeSpace="urn:uuid:">594237b4-3fd6-4343-9665-a85503c26aee</gml:identifier> <aixm:timeSlice> <aixm:RunwayElementTimeSlice gml:id="uuid.2a3e4355-9edb-4474-8d57-88cd43483dfd"> <gml:validTime> <gml:TimePeriod gml:id="uuid.c48ea55f-31e3-4c2a-9032-34e2fad7eb12"> <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.7351e2e8-55a7-4a7d-bec1-98ce030fd13f"> <gml:beginPosition>2020-09-01T00:00:00Z</gml:beginPosition> <gml:endPosition indeterminatePosition="unknown" /> </gml:TimePeriod> </aixm:featureLifetime> <aixm:type>INTERSECTION</aixm:type> <aixm:surfaceProperties> <aixm:SurfaceCharacteristics gml:id="uuid.23e88c04-3d86-4e75-a492-6c91b6d064ca"> <aixm:composition>CONC</aixm:composition> <aixm:preparation>GROOVED</aixm:preparation> <aixm:classPCN>75</aixm:classPCN> <aixm:pavementTypePCN>RIGID</aixm:pavementTypePCN> <aixm:pavementSubgradePCN>B</aixm:pavementSubgradePCN> <aixm:maxTyrePressurePCN>W</aixm:maxTyrePressurePCN> <aixm:evaluationMethodPCN>TECH</aixm:evaluationMethodPCN> </aixm:SurfaceCharacteristics> </aixm:surfaceProperties> <aixm:associatedRunway xlink:href="#3f4952ee-a237-47d9-ab33-23f46a6332b1" xlink:title="06/24" /> <aixm:associatedRunway xlink:href="#de77ab7f-6bb1-43b4-817e-ce4465deb3a3" xlink:title="12/30" /> <aixm:extent> <aixm:ElevatedSurface gml:id="uuid.97404777-a076-4c81-98f9-b30a74db2fe4" srsName="urn:ogc:def:crs:EPSG::4326"> <gml:patches> <gml:PolygonPatch> <gml:exterior> <gml:Ring> <gml:curveMember> <gml:Curve gml:id="uuid.ea12dbf8-8b03-4821-ae09-6a6946c0c3a4"> <gml:segments> <gml:GeodesicString interpolation="geodesic"> <gml:posList>50.10796399 14.24598385 50.10777016 14.24533757 50.10749326 14.24589716 50.10768771 14.2465474 50.10796399 14.24598385</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.9b70ebc9-a2ea-4e74-a8fc-70b74b441cb5"> <aixm:operationalStatus>NORMAL</aixm:operationalStatus> <aixm:usage> <aixm:ManoeuvringAreaUsage gml:id="uuid.2de2ef73-9a07-442e-bcc0-6bf17990fedb"> <aixm:type>FORBID</aixm:type> <aixm:selection> <aixm:ConditionCombination gml:id="uuid.26d24b45-d02d-417a-9fda-f9779bb5e401"> <aixm:aircraft> <aixm:AircraftCharacteristic gml:id="uuid.01e94834-fd64-447d-85a8-7ad78391e594"> <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 RunwayIntersection: