v1.0.6

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

This section provides ‘RunwayCenterlinePoint’ feature data encoding guidance.

Vocabulary

 

ED-99

ED-119/AMXM

AIXM 5.1

AIRM

Name

RunwayCenterlinePointAM_RunwayCenterlinePoint

RunwayCenterlinePoint

RunwayCenterlinePoint

 

Information concept:

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

Data concept:

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


Information concepts indicate the reference vocabulary and relations of an RunwayCenterlinePoint with other concepts. 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, the RunwayCenterlinePoint represents an operationally significant position on the centre line of a runway direction. This position is represented by one point and only this point shall be measured. 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 RunwayCenterlinePoint 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 RunwayCenterlinePoint is mapped to the AIXM 5.1 as feature RunwayCentrelinePoint.

Geometry

In the AIXM 5.1 the geometry of the RunwayCentrelinePoint is point encoded 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 : RunwayCentrelinePoint

Time

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

AIXM 5.1 features

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

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

RunwayCentrelinePoint

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

Content of example

This is a ficticious example. No feature was present at the aerodrome used.

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

<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:RunwayCentrelinePoint gml:id="uuid.71228bfe-4b2a-4c04-94ef-b76aba948cc9">
  </hasMember>
  <hasMember>
    <aixm:RunwayDirection gml:id="uuid.62dd41c8-fa4e-4017-9d58-6c8432c35a03">
  </hasMember>
</AIXMBasicMessage>

Coding example - RunwayCenterlinePoint

  <hasMember>
    <aixm:RunwayCentrelinePoint gml:id="uuid.71228bfe-4b2a-4c04-94ef-b76aba948cc9">
      <gml:identifier codeSpace="urn:uuid:">71228bfe-4b2a-4c04-94ef-b76aba948cc9</gml:identifier>
      <aixm:timeSlice>
        <aixm:RunwayCentrelinePointTimeSlice gml:id="uuid.0bf931af-77d4-4d30-9a0e-99b3265960cd">
          <gml:validTime>
            <gml:TimePeriod gml:id="uuid.7db20d96-21ed-4472-80b5-02560d344ea0">
              <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.1387bc19-ed6c-42fd-909f-1a2e0527fa24">
              <gml:beginPosition>2020-09-01T00:00:00Z</gml:beginPosition>
              <gml:endPosition indeterminatePosition="unknown" />
            </gml:TimePeriod>
          </aixm:featureLifetime>
          <aixm:location>
            <aixm:ElevatedPoint gml:id="uuid.10c1fb09-4837-4755-9bb5-06a1208bb464" srsName="urn:ogc:def:crs:EPSG::4326">
              <gml:pos>50.1036375 14.2544378</gml:pos>
              <aixm:horizontalAccuracy uom="M">0.5</aixm:horizontalAccuracy>
              <aixm:elevation uom="M">352</aixm:elevation>
              <aixm:geoidUndulation uom="M">45.7</aixm:geoidUndulation>
              <aixm:verticalAccuracy uom="M">0.25</aixm:verticalAccuracy>
            </aixm:ElevatedPoint>
          </aixm:location>
          <aixm:onRunway xlink:href="#62dd41c8-fa4e-4017-9d58-6c8432c35a03" xlink:title="30" />
        </aixm:RunwayCentrelinePointTimeSlice>
      </aixm:timeSlice>
    </aixm:RunwayCentrelinePoint>
  </hasMember>

Table of properties of RunwayCenterlinePoint


ED-99/DO-272AIXM 5.1Contained within example

RunwayCenterlinePoint

RunwayCentrelinePoint

-

1stfeatfeatureLifetime.gml:TimePeriod.gml:beginPositionyes
2endfeatfeatureLifetime.gml:TimePeriod.gml:endPositionyes
3stvalidvalidTime.gml:TimePeriod.gml:beginPosition

yes

4endvalidvalidTime.gml:TimePeriod.gml:endPositionyes
5interpinterpretationyes
6

feattype

Note: Can be implied

-
7idnumberidentifieryes
8

idarpt

onRunway.RunwayDirection.usedRunway.Runway.associatedAirportHeliport.AirportHeliport.locationIndicatorICAO

yes
9idrwy

onRunway.RunwayDirection.usedRunway.Runway.designator

yes
10

vacc

location.ElevatedPoint.verticalAccuracy

yes
11

hacc

location.ElevatedPoint.horizontalAccuracy

yes
12

vres

location.ElevatedPoint.verticalResolution

no (part of AIXM extension)
13

hres

location.ElevatedPoint.horizontalResolution

no (part of AIXM extension)
14

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".

yes
15

integr

integrity

no (part of AIXM extension)
16

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"

yes
17ellipseNote: Can be calculated.

-

18geound

location.ElevatedPoint.geoidUndulation

yes
19elev

location.ElevatedPoint.elevation

yes
20geopnt

location.ElevatedPoint

yes

Download feature RunwayCenterlinePoint:

BL_RunwayCenterlinePoint.xml

AMXM

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

TBD

 

 

  • No labels