...
- 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:
...
| Expand |
|---|
It covers roles 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 |
|