EUROCONTROL Guidelines for ED-99 airport mapping requirements in AIXM 5.1
Guidelines ED-99 airport mapping requirements in AIXM 5.1
EUROCONTROL Guidelines for ED-99 airport mapping requirements in AIXM 5.1DOCUMENT IDENTIFIER : EUROCONTROL-GUID-
Edition Number : 0.2
Edition Date : 25 APR 2012
Status : Draft
Intended for : General Public
Category : EUROCONTROL Guidelines
DOCUMENT CHARACTERISTICS
TITLEEUROCONTROL Guidelines for ED-99 airport mapping requirements in AIXM 5.1
Publications Reference: / GUID-
ISBN Number:
Document Identifier / Edition Number: / 0.2
EUROCONTROL-GUID- / Edition Date: / 25 APR 2012
Abstract
This document contains the EUROCONTROL Guidelines for the support provided in the Aeronautical Information Exchange Model (AIXM) version 5.1 for the Airport Mapping data requirements stated in Eurocae ED-99, User Requirements for Aerodrome Mapping Information. This supports the standardised encoding and the distribution in digital format of the aeronautical information/data that is in the scope of Aeronautical Data Quality (ADQ) Regulation (EU) 73/2010, developed in accordance with the interoperability Regulation in the framework of the Single European Sky (SES).
Keywords
Airport Mapping / AIXM / Mapping / Interoperability
AIX / SES / AIS / AIM
AMDB
Contact Person(s) / Tel / Unit
Eduard POROSNICU / +32 2 729 3326 / DSR/IM
Scott WILSON / +32 2 729 4792 / DSR/IM
STATUS, AUDIENCE AND ACCESSIBILITY
Status / Intended for / Accessible via
Working Draft / o / General Public / þ / Intranet / o
Draft / þ / EUROCONTROL / o / Extranet / o
Proposed Issue / o / Restricted / o / Internet (www.eurocontrol.int) / o
Released Issue / o
DOCUMENT APPROVAL
The following table identifies all management authorities who have successively approved the present issue of this document.
AUTHORITY / NAME AND SIGNATURE / DATEDSS/REG/SES / Editor / Mr Scott WILSON
Mr Eduard POROSNICU / 25 APR 2012
Activity Manager / Mr Manfred UNTERREINER / 25 APR 2012
Director Single Sky / Mr Luc TYTGAT
On behalf of the Director General by special delegation
Principal Director ATM / Mr. Bo REDEBORN
DOCUMENT CHANGE RECORD
The following table records the complete history of the successive editions of the present document.
EDITIONNUMBER / EDITION
DATE / REASON FOR CHANGE / PAGES AFFECTED
0.1 / 20 JAN 2012 / Initial draft, based on previous work done by Scott Wilson in the frame of the Airport Mapping activities of Eurocontrol / All
0.2 / 25 APR 2012 / Completely reviewed version, using ED 99A and the experience gathered with the writing of the Metadata Requirements documents / All
Publications
EUROCONTROL Headquarters
96 Rue de la Fusée
B-1130 BRUSSELS
Tel: +32 (0)2 729 4715
Fax: +32 (0)2 729 5149
E-mail:
CONTENTS
DOCUMENT CHARACTERISTICS 2
DOCUMENT APPROVAL 3
DOCUMENT CHANGE RECORD 4
CONTENTS 5
LIST OF FIGURES 8
LIST OF TABLES 9
EXECUTIVE SUMMARY 11
1. Introduction 13
1.1 Scope and purpose 13
1.2 ED99 versions 13
1.3 ED119 13
1.4 Abbreviations 13
1.5 Reference material 15
1.6 Document structure 15
2. Mapping methodology 16
2.1 Shared vocabulary 16
2.2 Understanding the mappings 16
2.2.1 Feature level mapping 16
2.2.1.1 Definitions 16
2.2.1.2 Table columns 16
2.2.1.3 General observations 16
2.2.2 Enumerations and codelists mapping 17
2.2.2.1 Table columns 17
2.2.2.2 General observations 17
2.2.3 Datatype mapping 17
2.2.3.1 Table columns 17
3. Mappings 18
3.1 ED-99A Features Mapped to AIXM Features 18
3.1.1 AM_AerodromeReference Point 18
3.1.2 AM_ ApronElement 19
3.1.3 AM_ ArrestingGearLocation 20
3.1.4 AM_ ConstructionArea 20
3.1.5 AM_ DeicingArea 21
3.1.6 AM_ FinalApproachAndTakeOffArea 22
3.1.7 AM_ FrequencyArea 23
3.1.8 AM_ HelipadThreshold 24
3.1.9 AM_ LandAndHoldShortOperationLocation 25
3.1.10 AM_ PaintedCenterline 26
3.1.11 AM_ ParkingStandArea 27
3.1.12 AM_ ParkingStandLocation 28
3.1.13 AM_ RunwayDisplacedArea 29
3.1.14 AM_ RunwayElement 30
3.1.15 AM_ RunwayExitLine 31
3.1.16 AM_ RunwayIntersection 33
3.1.17 AM_ RunwayMarking 34
3.1.18 AM_ RunwayShoulder 34
3.1.19 AM_ RunwayThreshold 35
3.1.20 AM_ ServiceRoad 37
3.1.21 AM_ StandGuidanceLine 38
3.1.22 AM_ Stopway 39
3.1.23 AM_ SurveyControlPoint 40
3.1.24 AM_ TaxiwayElement 41
3.1.25 AM_ TaxiwayGuidanceLine 42
3.1.26 AM_ TaxiwayHoldingPosition 44
3.1.27 AM_ TaxiwayIntersectionMarking 45
3.1.28 AM_ TaxiwayShoulder 46
3.1.29 AM_ TouchDownLiftOffArea 47
3.1.30 AM_ VerticalLineStructure 47
3.1.31 AM_ VerticalPointStructure 49
3.1.32 AM_ VerticalPolygonalStructure 51
3.2 Enumeration and Codelists 52
3.2.1 bridge 52
3.2.2 cat 52
3.2.3 catstop 53
3.2.4 color 53
3.2.5 direc 54
3.2.6 docking 54
3.2.7 feattype 54
3.2.8 fuel 56
3.2.9 gndpower 57
3.2.10 gsurftyp 58
3.2.11 jetway 59
3.2.12 lighting 59
3.2.13 linsttyp 59
3.2.14 marking 61
3.2.15 material 61
3.2.16 papivasi 62
3.2.17 plysttyp 62
3.2.18 pntsttyp 65
3.2.19 station 67
3.2.20 status 67
3.2.21 style 67
3.2.22 surftype 68
3.2.23 thrtype 70
3.2.24 towing 70
3.2.25 vdatum 71
3.3 Data Types 71
ANNEX A – ED-99C Mappings 74
A.1 AM_ AerodromeSurfaceLighting 74
A.2 AM_ Water 74
ANNEX B – Functional and Geometrical Constraints 76
B.1 ED-99A Constraints 76
3.3.1 Functional Constraints 76
3.3.2 Geometrical Constraints 78
LIST OF FIGURES
Error! No table of figures entries found.
LIST OF TABLES
Error! No table of figures entries found.
Edition: 0.2 Draft Page 3
EUROCONTROL Guidelines for ED-99 airport mapping requirements in AIXM 5.1
EXECUTIVE SUMMARY
To de added
Edition: 0.2 Draft Page 3
EUROCONTROL Guidelines for ED-99 airport mapping requirements in AIXM 5.11. Introduction
1.1 Scope and purpose
This document provides evidence for Compliance with [REQ-AMDB-01] of EUROCONTROL’s AIX Guidelines.
It analyses the coverage of the “User Requirements for Aerodrome Mapping Information” (ED99) within AIXM 5.1. A series of tables is provided to map the ED99 information items to classes, attributes and associations in the AIXM UML model, in particular the AirportHeliport package.
This document looks at:
· Features and Attributes
· Enumerations and Codelist
· Relationships and Rules
Note that this document will not provide instructions on how to create an ED-99A compliant Aerodrome Mapping Database. This can only be done by following the complete rules within ED-99A and its sister-document ED-119.
1.2 ED99 versions
This mapping considers ED-99A as specified in [REQ-AMDB-01].
The latest version of the “User Requirements for Aerodrome Mapping Information” is ED-99C. This was published in September 2011. Amongst other things, it introduced new features to capture ArrestingSystemLocations, RunwayCenterlinePoints, AsrnEdges and AsrnNodes. Several new attributes were added to existing features and a new temporality concept was incorporated into the requirements.
ED-99B was published in April, 2009. Amongst other things, it added new features for Blastpad, Water, Hotspot and Aerodrome Surface Lighting.
ED-99A was published in October 2005. This was the version available at the start of the development of AIXM 5.1.
1.3 ED119
In cases where ED-99A is not clear, ED-119 has been used for extra details. ED-119 details an interchange standard for aerodrome mapping data with accompanying UML diagrams. In particular, the details on the geometries of the features have been taken from ED-119. For example, where ED-99A lists a feature as of type “Point”, ED-119 has added an attribute “geopnt”. This additional attribute is included in the mappings.
1.4 Abbreviations
Term / DefinitionADQ / Aeronautical Data Quality
ADQ IR / Commission Regulation (EU) No. 73/2010, of 26 January 2010, laying down requirements on the quality of aeronautical data and aeronautical information for the single European sky OJ L 23/6 (27.1.2010)
AIM / Aeronautical Information Management
AIP / Aeronautical Information Publication
AIRAC / Aeronautical Information Regulation And Control
AIS / Aeronautical Information Service
AIX / Aeronautical Information Exchange
AIXM / Aeronautical Information eXchange Model
AMDB / Aerodrome Mapping Database
ANSP / Air Navigation Service Provider
ATM / Air Traffic Management
DSS / Single Sky Directorate (in EUROCONTROL)
EAD / European AIS Database
EC / European Commission
ECTL / EUROCONTROL
ERAF / EUROCONTROL Regulatory and Advisory Framework (Cadre réglementaire et consultatif d'EUROCONTROL)
EU / European Union
GML / Geographical Markup Language
IAIP / Integrated Aeronautical Information Package
ICAO / International Civil Aviation Organization
IR / Implementing Rule (SES)
ISBN / International Standard Book Number
ISO / International Standards Organization
NOTAM / Notice to Airmen
OJ / Official Journal
PDF / Portable Document Format
SARPS / Standards And Recommended Practices
SES / Single European Sky
UML / Unified Modelling Language
UTC / Coordinated Universal Time
XML / EXtensible Markup Language
XSD / XML Schema
1.5 Reference material
[1] Internal guidelines for the development of EUROCONTROL specifications and EUROCONTROL guidelines. Edition 1.0 dated 16 October 2007. Ref. ECTL_SPEC_GUID_1.0 191007
[2] EUROCONTROL Guidelines – Use of AIXM 5.1 in relation with the AIX Specification. Proposed Issue x.x dated xx XXX xxxx. Ref …
[3] [AIXM_5_1] - AIXM 5.1, version of of 2 February 2010, EUROCONTROL and FAA
[4] [GML] - Geography Markup Language Open Geospatial Consortium, Inc.
[5] [UML] - http://www.uml.org/#UML2.0 Object Management Group - Unified Modeling Language
[6] [XML] - http://www.w3.org/XML/ Extensible Markup Language (XML) World Wide Web Consortium
[7] [ED-99] - http://www.eurocae.net/publications/publications-list.html
[8] [ED-119] - http://www.eurocae.net/publications/publications-list.html
1.6 Document structure
The document starts with a general introduction to the mapping methodology (Chapter 2). Chapter 2 also includes some general observations.
The detailed mapping tables are in Chapter 3. Chapter 3 is divided into three main sections. The first deals with the top-level mapping, from ED-99A features to the equivalent AIXM 5.1 feature. The second section covers the values that are found in the enumerations and codelists. Other data type mappings are in the third section.
Mappings to later version of the ED-99 document can be found in Annex A. Annex B provides detail on how to map ED-99A’s functional and geometrical constraints.
2. Mapping methodology
2.1 Shared vocabulary
AIXM 5.1 and ED99 both make use of the ISO 19100 series of standards. Therefore, the base-types (CharacterString, Boolean, Real) do not need to be mapped. Both specifications use the same series of stereotypes (e.g. <Feature>) in order to mark their elements. Both use ISO 19136 (GML) for geometries and ISO 19115 for their metadata encodings.
2.2 Understanding the mappings
The mappings are listed in a series of tables.
2.2.1 Feature level mapping
2.2.1.1 Definitions
Each entry starts with the ED99A definition of the feature and the AIXM 5.1 definition for the mapped feature.
2.2.1.2 Table columns
The ED-99A to AIXM features mapping tables uses the following columns:
· ED-99A
o The first row gives the feature name from ED-99A
o Subsequent rows give the attributes of that feature.
· AIXM 5.1
o The first row gives the name of the AIXM Feature that should act as the root for the mapping.
o Subsequent rows give the attributes. Where these are from a feature that is related to the root feature, the exact path is given. The syntax used is:
§ <property name>.<feature name>.<property name> e.g. associatedAirportHeliport.AirportHeliport.locationIndicatorICAO.
§ square brackets are used to give conditions on the values of a property e.g. Runway[type=‘FATO’]. This is important as AIXM is often more general that ED-99A.
§ {results of query} is used as shorthand in some mappings. The query should be detailed elsewhere in the table.
o Notes are included where relevent to the mapping.
2.2.1.3 General observations
There are some general remarks on the mappings.
· Some attributes map at metadata level rather than feature level. For example, ED-99A’s ‘vres’ attribute maps to a metadata field and not to an attribute that is directly present in the corresponding AIXM 5.1 feature. Such mappings begin with “gmd:Metadata”.
· ED-99A does not include a temporality model. Therefore, no mapping has been attempted from AIXM 5.1’s temporality model to ED-99A. In effect, everything can be seen as a SNAPSHOT.
· In the case of some features detailing guidance lines and markings (e.g. Land and Hold Short Operations) a choice of mapping approach was possible. The option adopted was to use the marking element as main root of these mappings rather than e.g. the centreline point. This has a practical benefit and is more inline with the philosophy of ED-99A.
· The feattype mapping is noted as ‘can be implied’. A query will need to be performed in order to fill out the correct value.
2.2.2 Enumerations and codelists mapping
2.2.2.1 Table columns
The enumerations and codelists mapping tables use the following columns:
· ED-99A
o The first row gives the codelist/enumeration name from ED-119.
o Subsequent rows list the possible values.
· AIXM 5.1
o The first row gives the name of the AIXM codelist that should act as the root for the mapping.
o Subsequent rows give the mapped value.
2.2.2.2 General observations
There are some general remarks on the mappings.
· ED-99A does not provide values for codelists and enumerations. These are taken from ED-119.
· ED-119 uses a mixture of codelists and enumerations. However, AIXM 5.1 only uses codelists. These are open enumerations which means that if there is not direct mapping from the ED-119 value, it is possible to use the construct “OTHER:UPPER_CASE_VALUE”. This has been used in several mappings.
· In one case, surftyp, more than one AIXM 5.1 codelist is required in order to complete the mapping.
· In once case, status, an ED-99A attribute can map to two AIXM 5.1 codelist.
2.2.3 Datatype mapping
2.2.3.1 Table columns
The datatype mapping table uses a column for the ED-99A datatype and the equivalent AIXM 5.1 datatype.
Edition 0.2 / XXXEUROCONTROL Guidelines for ED-99 airport mapping requirements in AIXM 5.1
3. Mappings
3.1 ED-99A Features Mapped to AIXM Features
3.1.1 AM_AerodromeReference Point
ED-99A Definition: The designated geographical location of an aerodrome.
AIXM 5.1 Definition: A defined area on land or water (including any buildings, installations and equipment) intended to be used either wholly or in part for the arrival, departure and surface movement of aircraft/helicopters.
ED-99A / AIXM 5.1AM_AerodromeReferencePoint / AirportHeliport
idarpt / locationIndicatorICAO
iata / designatorIATA
geopnt / ARP.ElevatedPoint
name / name
feattype / Note: Can be implied
vacc / ARP.ElevatedPoint.verticalAccuracy
vres / gmd:MD_Metadata.gmd:dataQualityInfo.
gmd:DQ_DataQuality
hacc / ARP.ElevatedPoint.horizontalAccuracy
hres / gmd:MD_Metadata.gmd:dataQualityInfo.
gmd:DQ_DataQuality
integr / gmd:MD_Metadata.gmd:dataQualityInfo.
gmd:DQ_DataQuality
source / gmd:MD_Metadata.gmd:dataQualityInfo
revdate / gmd:MD_Metadata.gmd:identificationInfo.
gmd:MD_DataIdentification.gmd:citation.
gmd:CI_Citation.gmd:date.gmd:CI_Date.
gmd:date
3.1.2 AM_ ApronElement
ED-99A Definition: The remaining parts of a defined apron area that are not covered by Parking Stand Area features or Taxiway Element features.