v1.0.6

This section provides ‘ConstructionArea’ 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 ConstructionArea 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 ConstructionArea 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 ConstructionArea is mapped to the the AIXM 5.1 as feature WorkArea.

Geometry

In the AIXM 5.1 the geometry of the WorkArea 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 : ConstructionArea

Time

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

AIXM 5.1 features

ConstructionArea is encoded to the AIXM 5.1 as one feature WorkArea.

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

WorkArea

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

UML Diagram (Airport Heliport / Airport Heliport Associations)

http://aixm.aero/sites/aixm.aero/files/imce/AIXM51HTML/AIXM/Diagram_AirportHeliportAssociations.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.v

Coding example - Structure of message

<AIXMBasicMessage  ...>
  <aixm:messageMetadata>
  </aixm:messageMetadata>
  <hasMember>
    <aixm:AirportHeliport gml:id="uuid.0b7a2688-ab95-47e6-82c2-23fe321c4a48">
  </hasMember>
  <hasMember>
    <aixm:WorkArea gml:id="uuid.76b8665c-e5d6-48af-8327-7b6e8b913274">
  </hasMember>
</AIXMBasicMessage>

Coding example - WorkArea

  <hasMember>
    <aixm:WorkArea gml:id="uuid.76b8665c-e5d6-48af-8327-7b6e8b913274">
      <gml:identifier codeSpace="urn:uuid:">76b8665c-e5d6-48af-8327-7b6e8b913274</gml:identifier>
      <aixm:timeSlice>
        <aixm:WorkAreaTimeSlice gml:id="uuid.2818f2db-453a-4dba-a984-ec96dc6824c8">
          <gml:validTime>
            <gml:TimePeriod gml:id="uuid.6e3ce5f3-b25d-4752-8051-b429a97e5a6c">
              <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.357b6f20-1844-405a-9862-a57116175586">
              <gml:beginPosition>2020-09-01T00:00:00Z</gml:beginPosition>
              <gml:endPosition>2020-09-02T00:00:00Z</gml:endPosition>
            </gml:TimePeriod>
          </aixm:featureLifetime>
          <aixm:plannedOperational>2020-09-01T00:00:01Z</aixm:plannedOperational>
          <aixm:associatedAirportHeliport xlink:href="#0b7a2688-ab95-47e6-82c2-23fe321c4a48" xlink:title="LKPR" />
          <aixm:extent>
            <aixm:ElevatedSurface gml:id="uuid.53fe299e-1653-47e1-b465-4cc3d1bc5394" srsName="urn:ogc:def:crs:EPSG::4326">
              <gml:patches>
                <gml:PolygonPatch>
                  <gml:exterior>
                    <gml:Ring>
                      <gml:curveMember>
                        <gml:Curve gml:id="uuid.05762cac-bae0-439c-857a-abbcc81fe079">
                          <gml:segments>
                            <gml:GeodesicString interpolation="geodesic">
                              <gml:posList>50.10385833 14.26713934 50.10382098 14.26722381 50.10362405 14.26766915 50.10359613 14.26773224 50.10336375 14.26748404 50.10330875 14.26742457 50.10308098 14.26718215 50.10333734 14.26660407 50.10339995 14.2664623 50.10378192 14.26559771 50.10403445 14.26585119 50.10424344 14.26607454 50.10430061 14.26613683 50.10385833 14.26713934</gml:posList>
                            </gml:GeodesicString>
                          </gml:segments>
                        </gml:Curve>
                      </gml:curveMember>
                    </gml:Ring>
                  </gml:exterior>
                </gml:PolygonPatch>
              </gml:patches>
              <aixm:horizontalAccuracy uom="M">1</aixm:horizontalAccuracy>
              <aixm:elevation uom="M">376</aixm:elevation>
              <aixm:verticalAccuracy uom="M">1</aixm:verticalAccuracy>
            </aixm:ElevatedSurface>
          </aixm:extent>
        </aixm:WorkAreaTimeSlice>
      </aixm:timeSlice>
    </aixm:WorkArea>
  </hasMember>


Download feature ConstructionArea:

BL_ConstructionArea.xml

  • No labels