Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Excerpt
This section provides ‘FinalApproachAndTakeOffArea’ feature data encoding guidance.


Table of Contents

Vocabulary

ED-99

ED-119/AMXM

AIXM 5.1

AIRM

Name

FinalApproachAndTakeOffAreaAM_FinalApproachAndTakeOffAreaRunway[type='FATO']Runway[type='FATO']

 

Information concept:

Runway: http://www.airm.aero/viewer/1.0.0/conceptual-model.html#Runway

Data concept:

RunwayElement: http://www.airm.aero/viewer/1.0.0/logical-model.html#RunwayElement

CodeRunwayType: http://www.airm.aero/viewer/1.0.0/logical-model.html#CodeRunwayType

Information concepts indicate the reference vocabulary and relations of an FinalApproachAndTakeOffArea with other concepts for operational experts. Data concepts indicate the reference features and properties for service architects, information/data architects and system implementers.

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 FinalApproachAndTakeOffArea 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 FATO 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 FinalApproachAndTakeOffArea is mapped to the AIXM 5.1 as feature Runway with property Type set to "FATO". Because feature Runway does not contain geometry feature, RunwayElement in association with Runway is necessary.

Geometry

In the AIXM 5.1 the geometry of the RunwayElement is Polygon defined by Elevated Surface.

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 : FinalApproachAndTakeOffArea

Time

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

AIXM 5.1 features

FinalApproachAndTakeOffArea is encoded to the AIXM 5.1 as Runway Element feature.

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

Runway feature

http://aixm.aero/sites/aixm.aero/files/imce/AIXM51HTML/AIXM/Class_Runway.html

Runway Element 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

Info
titleContent 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

Code Block
languagexml
<AIXMBasicMessage  ...>
  <aixm:messageMetadata>
  </aixm:messageMetadata>
  <hasMember>
    <aixm:AirportHeliport gml:id="uuid.0b7a2688-ab95-47e6-82c2-23fe321c4a48">
  </hasMember>
  <hasMember>
    <aixm:Runway gml:id="uuid.96b243ca-d114-475e-b195-06dd3af51ed9">
  </hasMember>
  <hasMember>
    <aixm:RunwayDirection gml:id="uuid.53aa2710-acff-4fae-9554-b72df918a99b">
  </hasMember>
  <hasMember>
    <aixm:RunwayElement gml:id="uuid.b03870d4-2e08-44f2-aa95-7b7387ddda4f">
  </hasMember>
</AIXMBasicMessage>

Coding example - FinalApproachAndTakeOffArea

Code Block
languagexml
  <hasMember>
    <aixm:Runway gml:id="uuid.96b243ca-d114-475e-b195-06dd3af51ed9">
      <gml:identifier codeSpace="urn:uuid:">96b243ca-d114-475e-b195-06dd3af51ed9</gml:identifier>
      <aixm:timeSlice>
        <aixm:RunwayTimeSlice gml:id="uuid.daed4825-c49c-4aa0-ac68-04ff61a97b10">
          <gml:validTime>
            <gml:TimePeriod gml:id="uuid.4da2c5dc-af3e-46ac-ba7a-6b43860af1b3">
              <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.e598d2d3-0135-4d92-8db3-d07886de72ef">
              <gml:beginPosition>2020-09-01T00:00:00Z</gml:beginPosition>
              <gml:endPosition indeterminatePosition="unknown" />
            </gml:TimePeriod>
          </aixm:featureLifetime>
          <aixm:designator>FATO1</aixm:designator>
          <aixm:type>FATO</aixm:type>
          <aixm:surfaceProperties>
            <aixm:SurfaceCharacteristics gml:id="uuid.1b01ef92-bcc0-4c55-b467-927d7111cbf7">
              <aixm:composition>ASPH</aixm:composition>
              <aixm:preparation>COMPACTED</aixm:preparation>
            </aixm:SurfaceCharacteristics>
          </aixm:surfaceProperties>
          <aixm:associatedAirportHeliport xlink:href="#0b7a2688-ab95-47e6-82c2-23fe321c4a48" xlink:title="LKPR" />
        </aixm:RunwayTimeSlice>
      </aixm:timeSlice>
    </aixm:Runway>
  </hasMember>

Download feature FinalApproachAndTakeOffArea:

BL_FATO.xml

AMXM

https://ext.eurocontrol.int/aixm_confluence/display/AMX/FinalApproachAndTakeOffArea

TBD