The following actors are involved in this information exchange:
- The Information Provider is the Aerodrome
- only major airports identified in CP1 are expected to implement this information exchange as defined here
- The Information Consumer is the AISP
Purpose
This exchange address the need for an aerodrome to share aerodrome map data to the AISP .
The information exchanged relates to the geospatial aeronautical mapping information features of an aerodrome.
The specific list of aerodrome features aligns with those in the scope of the Aerodrome Mapping Data set features.
The aerodrome mapping supporting material for "ICAO - Aerodrome Mapping Data Set" is available here.
Interaction
There are no considerations specified with regards to how information is expected to be exchanged between the identified stakeholders.
Non Functional Requirements
There is no non functional requirement identified.
Constraints
This exchange of information may be based on AIXM
EUROCAE WG-44 AMDB industry standards is possible based on existing supporting material (e.g. Features - (ICAO) Aerodrome Mapping Data Sets - AIXM Confluence (eurocontrol.int) ). This .
This information exchange relates to the requirements stated by CP1 and the SDP as described here.
It is not mandated by CP1 or SDP to implement this information exchange as a SWIM Service, however this is beneficial.
There are two aerodrome mapping data exchanges:
- Airport provision of data to AISP (covered in this section)
- AISP provision of aerodrome mapping information ()
In terms of CP1, the information exchange covered in this section:
Click here to expand...
the following CP1 requirement, however only specifically to the enabler role of the AO that provides data for the service:
| A3SG-REF-004 | CP1/AF5.1.3 | Aero-Map | Operational stakeholders R/T aerodrome dig. charts | Operational stakeholders must implement... digital aerodrome charts service… that support the exchange of the aeronautical information… as described in the deployment programme |
The data provision by the airport is only required for major airports as described in CP1
| A3SG-REF-029 | CP1/AF1.2 | Scope | Major airports | Adolfo Suarez Madrid-Barajas; Amsterdam Schiphol; Barcelona El Prat; Berlin Brandenburg Airport; Brussels National; Copenhagen Kastrup; Dublin; Düsseldorf International; Frankfurt International; Milan-Malpensa; Munich Franz Josef Strauss; Nice Cote d’Azur; Palma De Mallorca Son Sant Joan; Paris-CDG; Paris-Orly; Rome-Fiumicino; Stockholm-Arlanda; Vienna Schwechat; |
In terms of SDP
Click here to expand...
It covers the roles stated in the SDP, but focusing only on the AO to AISP information exchange. It is an enabler of the IER-03 that is the publication of maps by an AISP.
| A3SG-REF-022 | SDP/AF5.3 | Aero-Map | Aerodrome Mapping Service roles | The Aerodrome Mapping information exchange shall be implemented by: • Airports are primary data provider supporting Aerodrome mapping service. • AISPs are the primary provider of the service. (Airport operators providing aeronautical information services qualify as AISP) • AUs that are the recommended primary consumers of the service and the information it provides |
It does not cover the following functionality stated in the SDP regarding the provision of maps, it is however an enabler of this as this information exchange is focused in the exchange of data between AO and AISP that will enable the other exchange described in A3SG-IER-03 .
| A3SG-REF-023 | SDP/AF5.3 | Aero-Map | Aerodrome Mapping Service functionality | The provider of the Aerodrome Mapping Service ensures that systems implementing the service: • Shall allow selecting aerodrome features and maps as GIS layers. • May allow information filtering with spatial, temporal and logical operators. |
It covers the technical aspects stated in the SDP related to the provision of aerodrome map data. It is complemented in terms of formats with AIXM 5.1 that is the primary exchange format for aeronautical features.
| A3SG-REF-024 | SDP/AF5.3 | Aero-Map | Aerodrome Mapping Service technical aspects | The provider of the Aerodrome Mapping Service ensures that systems implementing the service: • Shall output data in formats which are based on Open Geospatial Consortium standards (e.g. simple GML features, SHAPE files, GeoJSON) • May be based on the AMXM to facilitate GIS integration. Using AMXM will satisfy the related EUROCAE WG-44 Industry standards in terms of data format as referenced in Annex |