Aerodrome Mapping Data Bases

Document Sample
Aerodrome Mapping Data Bases Powered By Docstoc
					                                                                                   AIS-AIMSG/1-SN No. 9

                                            FIRST MEETING

                                     Montréal, 2 to 4 December 2008

Agenda Item 7:   Annex amendment proposals
            7.1: Terrain and obstacle data

                               AERODROME MAPPING DATA BASES

                             (Presented by Paul Bosman and Stephane Dubet)


              This study note recommends the inclusion of AMDB provisions into ICAO
              SARPS. The study note provides an initial high level draft proposition. It is
              further proposed to delegate the elaboration of detailed propositions to the
              EUROCAE/RTCA - WG44/SC217.


1.1           This study note presents an initial proposition for the inclusion of Aerodrome Mapping
Databases (AMDB) into ICAO SARPS. The information in this paper was prepared in coordination with
Sam Van-der-Stricht from EUROCONTROL.

1.2            Consistent AMDB for multiple applications requires common industry standards, which
have been developed by the joint EUROCAE / RTCA Committee WG44 / SC193 (currently SC217),
involving both national and international organizations, including ICAO, and the concerned industry

1.3             The AMDB supports the current industry requirements for improved situational
awareness during the taxiing phase, such as the Electronic Flight Bag (EFB) with AMDB and “own-ship-
position” data overlay.

1.4          Furthermore, the need for Aerodrome Mapping information has been identified by both
the SESAR and NextGen concepts which are aligned with the ICAO concept of operations. The AMDB
(5 pages)
AIS-AIMSG/1-SN No. 9                              -2-

constitutes a basis which may be enriched to support future Aerodrome Mapping requirements and, if
made available as an AMDB Geospatial Information Service, will enable a service oriented approach in
alignment with the SESAR / NextGen future network centric operations.

1.5            The activities of the EUROCAE / RTCA - WG44 / SC217 are engaging into further
developments to include new industry requirements mainly in alignment with SESAR and NextGen. The
AMDB is the common reference for shared aerodrome mapping information, on which collaborative
guidance and runway safety applications should be built. For example, future AMDBs will support
EUROCAE / RTCA - WG78 / SC214 D-Taxi Graphical Data Link requirements.


2.1             Improved common situational awareness and applications such as the Airbus On-board
Airport Navigation System (OANS), certified on A380 and the equivalent Boeing integrated forward-
facing aerodrome mapping moving map, taxi situational awareness displays, Runway Incursion
Prevention Systems (RIPS), aerodrome D-Taxi Graphical guidance, are being developed in order to
enhance the safety and efficiency of aircraft operations on the aerodrome surface. These applications are
dependent on accurate, reliable, and up-to-date AMDB data. Fig.1 shows how the AMDB is the
foundation for additional information overlays and related collaborative applications.

                            Fig 1: The AMDB as the foundation of CDM

The AMDB design, as developed by the EUROCAE / RTCA - WG44 / SC193, is based on the
application of GIS principles and the use of ISO19100 standards for geographic information.
Consequently the AMDB defines Aerodrome Mapping geographic features such as Taxiway_Element,
StandGuidanceLine, etc…, and its associated attributes, including provisions for ISO19115 Metadata
elements and ISO19131 Data Product Specification elements. Fig. 2 provides an overview of the
EUROCAE / RTCA AMDB feature layers.
                                                  -3-                           AIS-AIMSG/1-SN No. 9

                                     Fig 2: AMDB Feature layers

The AMDB features are frequently based on ortho-rectified aerial imagery restitution, and digitized as
spatial elements following defined geometrical constraints, and GIS best practice. AMDB feature layers
may be combined with other layers, within other usage contexts. This GIS layered approach enables
further information overlays such as with traffic, taxi path for guidance, Digital Notam and
Meteorological information. (See Fig. 1)

2.2             The EUROCAE / RTCA and ARINC AMDB standards are based on the global
ISO19100 standards. This approach provides open and interoperable standardisation of AMDB data
exchange, and enables interoperable application developments which will replace the so called “stove-
pipe” applications. Furthermore, in the context of State information provision services, it is possible to
quickly and efficiently ensure the networked availability of AMDB data as a new type of AIM Digital
Information Service. As a result the AMDB services appear to the end-users as distributed, homogenous,
seamless and secured well defined data services applicable in a wide array of activities.

2.3             Current trials which demonstrate interoperable and seamless information sharing involve
distributed and interoperable digital AMDB data services in support of decision making and planning.
More specifically, the joint EUROCONTROL/LFV Digital AIM trials (D-AIM) demonstrate information
sharing concepts involving AMDBs. (see The information sharing standards applied
within the context of D-AIM are also used by SIA FRANCE in an experiment to originate and publish
digital AMDB data.


3.1             Use of AMDB in EFB is a fact but it goes well beyond. The aerodrome mapping layout is
a key aspect for collaborative decision making (CDM), common situational awareness in the aerodrome
movement area, aerodrome guidance applications, AIS MET data link, Digital NOTAM, Aerodrome
Capacity planning and runway safety.
AIS-AIMSG/1-SN No. 9                               -4-

3.2             To enable the applications listed above it is required to have common quality reference
AMDB data which are shared between the various involved actors. The more stringent applications, such
as guidance, require even more accurate data which are today not available.

3.3             Furthermore, there is an opportunity with the origination of eTOD Area 3 data to
consider an extension towards the production of AMDBs using common base data and common GIS
technologies. Consequently, the AMDB would increase the number of derived data products and the
overall added value.


4.1             ICAO - Annex 15 defines the concept of a data product as a set or data set series that
conforms to a data product specification compliant to ISO19131 - Data Product Specification.

4.2            EUROCAE/RTCA - ED119/DO291, based on the EUROCAE/RTCA - ED99/DO272
user requirements for AMDB data, provides the AMDB interchange specification as an ISO19131
compliant Data Product Specification.

4.3             The AIXM5 data exchange model supports the publication of ED99/DO272 compliant
data. The AIXM5 is based on the ISO19100 standards for geographic information. It is the subject of
another study note.

4.4            ARINC 816 is the binary encoding standard for embedded AMDBs which are used by
on-board applications such as OANS and Electronic Flight Bags. ARINC 816 is aligned with the
EUROCAE / RTCA standards. The embedded standard is needed due to the additional constraints of
avionics manufacturers.

        ICAO SARPS

5.1        It should be noted that, in principle, the proposals mentioned hereafter, are supported by
the EUROCONTROL AI Team, and the EUROCAE / RTCA - WG44 / SC217 industry committee.

5.2           In terms of execution of a detailed proposal and provision of additional draft material it is
proposed do delegate this activity to the EUROCAE / RTCA - WG44 / SC217, in collaboration with

5.3            It is proposed to tie the recommendations for the generation of AMDB data to provisions
related to eTOD in ICAO Annex 15, especially since area 3 requirements are closely linked to the AMDB

5.4             It is proposed to make AMDB provision non mandatory. However, in cases where the
opportunity exists for States to provide AMDBs, this provision shall then be compliant with the AMDB

5.5          Changes for ICAO Annex 14: insertion of the AMDB specifications (list of features) into
a new paragraph inside Chapter 2 - Aerodrome Data. ED99/DO272 essential requirements and
ED119/DO291 AMDB Application Schema are to be considered in a new Appendix to Annex 14.
                                                   -5-                           AIS-AIMSG/1-SN No. 9

5.6            Changes for ICAO Annex 15: insertion of a new paragraph in Chapter 10 (Electronic
Terrain and Obstacle Data) to explain the objectives, the link to eTOD, and reference the specifications of
Annex 14.

5.7              Changes for ICAO Annex 4: insertion of a reference in Chapter 13 (Aerodrome Chart)
referencing the specifications of Annex 14.

5.8           It is proposed to discuss in the Group the overall schedule for the corresponding
amendments to the various Annexes in close coordination with the ICAO Secretariat and corresponding


6.1              This study note recommends the inclusion of AMDB provisions into ICAO SARPS
following the initial draft propositions provided in item 5.

6.2           This study note recommends the delegation of the elaboration of detailed AMDB ICAO
SARPS propositions to the EUROCAE / RTCA - WG44 / SC217.


7.1             The AIS-AIMSG is invited to:

                a) Note the contents of this study note, notably the current and future applications of
                   AMDB that are central to future ATM concept

                b) Discuss the recommendations outlined under item 6

                c) Agree on a way forward and on a corresponding action plan

                                               — END —

Shared By: