Supporting material for ICAO Aerodrome Mapping Data Sets
Page History
| Excerpt |
|---|
This section provides ‘TaxiwayHoldingPosition’ feature data encoding guidance. |
Table of Contents
General
AMD data encoding can start when the necessary geographic information, aeronautical information and basic knowledge regarding the structure of the created feature is available.
From the geographical point of view, the TaxiwayHoldingPosition is a line where taxiing aircraft and vehicles shall stop and hold until further cleared by ground control. For TaxiwayHoldingPosition two points shall be measured to capture the line. The key attributes are the longitude, latitude and the elevation in reference with WGS-84. In In the next part the process of converting the geographical information into the GML form, thus into geometry information, is described.
Based on Aeronautical Data Catalogue the required type of geometry for the TaxiwayHoldingPosition the TaxiwayHoldingPosition is the line. The definition of point line can be found in the the Table A1-9 Data types of the Aeronautical Data Catalogue.
AMD encoding
AIXM 5.1
TaxiwayHoldingPosition is mapped to the AIXM 5.1 as feature TaxiHoldingPositionMarking.
In AIXM 5.1 the TaxiHoldingPosition is a general operational concept which allows for the encoding of a point whereas in the AMD a line is used. This is the reason why the AIXM 5.1 TaxiHoldingPositionMarking is used to encode the line geometry (1 or more). The AIXM 5.1 TaxiHoldingPositionMarking also encodes a relation to the AIXM 5.1 TaxiHoldingPosition. The line that is captured can represent the real world feature. Careful consideration is needed when not all marking elements that constitute a single TaxiHoldingPositionMarking are captured. If a single line element is provided the operationally significant geometry shall be captured for safety reasons. Further details on these digitizing considerations are out of scope of this supporting material.
Geometry
In the AIXM 5.1 the geometry of the TaxiHoldingPositionMarking 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 : TaxiwayHoldingPosition
Time
Feature Runway TaxiwayHoldingPosition shall be established in accordance with coding rules and requirements listed in AIXM 5.1 Temporality Model.
AIXM 5.1 features
TaxiwayHoldingPosition is encoded to the AIXM 5.1 as feature TaxiHoldingPositionMarking.
All associations are shown in the UML Diagram (see below).
TaxiHoldingPositionMarking feature
https://aixm.aero/sites/aixm.aero/files/imce/AIXM51HTML/AIXM/Class_TaxiHoldingPositionMarking.html
UML Diagram (Markings/Surface Marking)
https://aixm.aero/sites/aixm.aero/files/imce/AIXM51HTML/AIXM/Diagram_SurfaceMarking.html
| Info | ||
|---|---|---|
| ||
The following AMD properties are not covered in the AIXM 5.1. coding example: vres, hres, integr, holddir, marktype, rwelight, aippub, lvo. These are covered by an AIXM 5.1. extension. |
Coding example - Structure of message
| Code Block | ||
|---|---|---|
| ||
<AIXMBasicMessage ...>
<aixm:messageMetadata>
</aixm:messageMetadata>
<hasMember>
<aixm:AirportHeliport gml:id="uuid.0b7a2688-ab95-47e6-82c2-23fe321c4a48">
</hasMember>
<hasMember>
<aixm:Taxiway gml:id="uuid.3ae48a00-5f20-42c4-bb60-032252a56aa6">
</hasMember>
<hasMember>
<aixm:GuidanceLine gml:id="uuid.3f3a4933-8dfd-4629-8ac3-b1564cca31aa">
</hasMember>
<hasMember>
<aixm:TaxiHoldingPosition gml:id="uuid.a00c0684-9929-4b82-8692-01f9c2acc3f2">
</hasMember>
<hasMember>
<aixm:TaxiHoldingPositionMarking gml:id="uuid.61e12571-79db-4fae-be23-8c483c40ac7f">
</hasMember>
</AIXMBasicMessage> |
Coding example - AIXM 5.1
| Code Block | ||
|---|---|---|
| ||
<hasMember>
<aixm:TaxiHoldingPositionMarking gml:id="uuid.61e12571-79db-4fae-be23-8c483c40ac7f">
<gml:identifier codeSpace="urn:uuid:">61e12571-79db-4fae-be23-8c483c40ac7f</gml:identifier>
<aixm:timeSlice>
<aixm:TaxiHoldingPositionMarkingTimeSlice gml:id="uuid.d20cce42-05c5-4664-bc0e-8d5c0df6aa18">
<gml:validTime>
<gml:TimePeriod gml:id="uuid.b4998943-ab8f-4ea4-92a7-7009473b5b44">
<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.431a691f-bd8a-4214-b4d2-ec73f181afcd">
<gml:beginPosition>2020-09-01T00:00:00Z</gml:beginPosition>
<gml:endPosition indeterminatePosition="unknown" />
</gml:TimePeriod>
</aixm:featureLifetime>
<aixm:element>
<aixm:MarkingElement gml:id="uuid.3591ec2c-7921-4445-98eb-c24ab6d11d0b">
<aixm:extent_curveExtent>
<aixm:ElevatedCurve gml:id="uuid.90b97e03-e595-47bb-9ad1-6edfc19680d0" srsName="urn:ogc:def:crs:EPSG::4326">
<gml:segments>
<gml:GeodesicString interpolation="geodesic">
<gml:posList>50.11536156 14.27503495 50.11557195 14.27511634</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:markedTaxiHold xlink:href="#a00c0684-9929-4b82-8692-01f9c2acc3f2" />
</aixm:TaxiHoldingPositionMarkingTimeSlice>
</aixm:timeSlice>
</aixm:TaxiHoldingPositionMarking>
</hasMember> |
Download feature TaxiwayHoldingPosition:
Overview
Content Tools