Page Comparison

Vocabulary

Information concept:

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

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

Data concept:

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

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

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, the HelipadThreshold represents an operationally significant position on the centreline of a runway direction. This position is represented by one point and only this point shall be measured. Parking The key attributes are the longitude, latitude and the elevation in reference with WGS-84. 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 RunwayCentrelinePoint is 'Point'. The definition of geometry type Point can be found in the Table A1-9 Data types of the Aeronautical Data Catalogue.

AMD encoding

AIXM 5.1

ED-99 feature HelipadThreshold is mapped to the AIXM 5.1 as feature RunwayCenterlinePoint with property Role set to "THR" with association with feature Runway with property Type set to "FATO".

Geometry

In the AIXM 5.1 the geometry of the RunwayCentrelinePoint is pointencoded as object ElevatedPoint.

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 location shall be transferred into a GML geometry object Point.

Figure 1 : HelipadThreshold

Time

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

AIXM 5.1 features

HelipadThreshold is encoded to the AIXM 5.1 as single feature RunwayCenterlinePoint.

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

RunwayCenterlinePoint 

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

UML Diagram (RunwayDirection)

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

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.96b243ca-d114-475e-b195-06dd3af51ed9">
  </hasMember>
  <hasMember>
    <aixm:RunwayDirection gml:id="uuid.53aa2710-acff-4fae-9554-b72df918a99b">
  </hasMember>
  <hasMember>
    <aixm:RunwayCentrelinePoint gml:id="uuid.4a2d9ebf-7a93-4f87-b8c6-e62ef7296e9c">
  </hasMember>
</AIXMBasicMessage>

Coding example - HelipadThreshold

  <hasMember>
    <aixm:RunwayCentrelinePoint gml:id="uuid.4a2d9ebf-7a93-4f87-b8c6-e62ef7296e9c">
      <gml:identifier codeSpace="urn:uuid:">4a2d9ebf-7a93-4f87-b8c6-e62ef7296e9c</gml:identifier>
      <aixm:timeSlice>
        <aixm:RunwayCentrelinePointTimeSlice gml:id="uuid.bc53de25-5bf1-4922-a75a-03070f95c32a">
          <gml:validTime>
            <gml:TimePeriod gml:id="uuid.80572856-d39b-44f5-abdb-898e19055c6b">
              <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.51a9dc21-f84e-4eea-9335-47ee40c6c77c">
              <gml:beginPosition>2020-09-01T00:00:00Z</gml:beginPosition>
              <gml:endPosition indeterminatePosition="unknown" />
            </gml:TimePeriod>
          </aixm:featureLifetime>
          <aixm:designator>THR_FATO1</aixm:designator>
          <aixm:location>
            <aixm:ElevatedPoint gml:id="uuid.ddada743-4269-42ad-9b89-bdc82b3f911b" srsName="urn:ogc:def:crs:EPSG::4326">
              <gml:pos>50.09257222 14.28376389</gml:pos>
              <aixm:horizontalAccuracy uom="M">0.5</aixm:horizontalAccuracy>
              <aixm:elevation uom="M">371</aixm:elevation>
              <aixm:geoidUndulation uom="M">46</aixm:geoidUndulation>
              <aixm:verticalAccuracy uom="M">0.25</aixm:verticalAccuracy>
            </aixm:ElevatedPoint>
          </aixm:location>
          <aixm:onRunway xlink:href="#53aa2710-acff-4fae-9554-b72df918a99b" />
        </aixm:RunwayCentrelinePointTimeSlice>
      </aixm:timeSlice>
    </aixm:RunwayCentrelinePoint>
  </hasMember>

Table of properties of HelipadThreshold

HelipadThreshold

-

yes

feattype

Note: Can be implied

idarpt

onRunway.RunwayDirection.usedRunway.Runway.associatedAirportHeliport.AirportHeliportlocationIndicatorICAO

idthr

designator

vacc

location.ElevatedPoint.verticalAccuracy

hacc

location.ElevatedPoint.horizontalAccuracy

vres

location.ElevatedPoint.verticalResolution

hres

location.ElevatedPoint.horizontalResolution

source

source
OR
gmd:MD_Metadata.gmd:dataQualityInfo.gmd:lineage.gmd:LI_Lineage.gmd:processStep.gmd:LI_ProcessStep
Note: Needs processor with a role set to "publisher".

integr

integrity

revdate

revisionDate
OR
gmd:MD_Metadata.gmd:identificationInfo.gmd:MD_DataIdentification.gmd:citation.gmd:CI_Citation.gmd:date.gmd:CI_Date.gmd:date
Note: also needs gmd:CI_Date.gmd:dateType.gmd:CI_DateTypeCode to be set to "revision"

status

onRunway.RunwayDirection.availability.ManoeuvringAreAvailability.operationalStatus

-

location.ElevatedPoint.geoidUndulation

location.ElevatedPoint.elevation

location.ElevatedPoint

Download feature HelipadThreshold:

BL_HelipadThreshold.xml

AMXM

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

TBD