You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 8
Next »
The following actors are involved in this information exchange:
- The Information Provider is the AISP
- The Information Consumer is the AU primarily, but possibly others.
Purpose
This exchange addresses the need for an AISP to publish aerodrome maps.
Applicability from a regulatory perspective relates to the major aerodromes referred in CP1
The information exchanged is under the form of graphical data picturing the layout of an aerodrome.
Digital Aerodrome Map can be used to present actual/real-time information about closure of runway, taxiway, work in progress on aerodrome movement area, temporary erected obstacles.
The aerodrome maps are calculated from the aerodrome mapping data referred to in A3SG-IER-02 Aerodrome Mapping Data Exchange and A3SG-IER-04 Aerodrome Events Data Exchange.
Interaction
The information is expected to be exchanged between the identified stakeholders taking into account the following interaction characteristics:
- It shall allow selecting aerodrome maps as GIS layers.
- The exchange of information is based on consumer demand, and does not correspond directly to any publication cycle.
Non Functional Requirements
There is no non functional requirement identified.
Constraints
This exchange of information is constraint to be performed as follows:
- Shall be based on Graphical formats in the scope of the Open Geospatial Consortium standards.
This information exchange relates to the requirements stated by CP1 and the SDP as described here.
There are two aerodrome mapping exchanges:
In terms of CP1, the information exchange covered in this section:
Click here to expand...
It captures all requirements related to digital aerodrome charts service, focusing on the maps publication by an AISP:
| 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 |
In terms of SDP
Click here to expand...
It covers the roles stated in the SDP, but focusing on the AISP as primary provider, and the AUs as the recommended consumers.
| 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 fully covers the functionality stated in the SDP.
| 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 publication of maps.
| 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 |
It covers the information elements stated in the SDP.
| A3SG-REF-028 | SDP/AF5.3 | Aero-Map | Aerodrome Mapping Service Information | Digital Aerodrome Map can be used to present actual/real-time information about closure of runway, taxiway, work in progress on aerodrome movement area, temporary erected obstacles. |