Abstract
This requirement describes the information published by an AISP related to the provision of aerodrome maps.
Actors
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 maps with information of applicable aerodromes.
Applicability from a regulatory perspective relates to the major aerodromes referred in CP1
Information
The information exchanged relates to the geospatial aeronautical information features of an aerodrome.
The specific list of aerodrome features aligns with those in the scope of the Aerodrome Mapping Data set features.
Interaction
The information is expected to be exchanged between the identified stakeholders taking into account the following interaction characteristics:
- It shall allow selecting aerodrome features and maps as GIS layers.
- It may allow information filtering with spatial, temporal and logical operators.
- 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 output data in formats which are based on Open Geospatial Consortium standards (e.g. simple GML features, SHAPE files, GeoJSON)
Reference and Related Requirements
This information exchange relates to the requirements stated by CP1 and the SDP as described here.
There are two aerodrome mapping exchanges:
- Airport provision of data to AISP (covered in A3SG-IER-02 Aerodrome Mapping Data Exchange)
- AISP provision of aerodrome maps (covered in this section )
In terms of CP1, the information exchange covered in this section:
In terms of SDP