ActorsÂ
The following actors are involved in this information exchange:
- The Information Provider is the AISP
- The Information Consumer is the
PurposeÂ
 As described in PANS-AIM, Aerodrome mapping data serves...
Aerodrome mapping data includes aerodrome geographic information that supports applications which
improve the user’s situational awareness or supplements surface navigation, thereby increasing safety margins and
operational efficiency. Aerodrome mapping data sets with appropriate data element accuracy support requirements for
collaborative decision making, common situational awareness and aerodrome guidance applications are intended to be
used, among others, in the following air navigation applications:
a) position and route awareness including moving maps with own ship position, surface guidance and navigation
(e.g. A-SMGCS);
b) traffic awareness including surveillance and runway incursion detection and alerting;
c) facilitation of aerodrome-related aeronautical information, including NOTAM;
d) resource and aerodrome facility management; and
e) aeronautical chart production.
The data may also be used in other applications such as training/flight simulator and synthetic vision systems
The information exchanged is aerodrome mapping data that is expressed as aeronautical information features.
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Â
InteractionÂ
The information is expected to be exchanged between the identified stakeholders taking into account the following interaction characteristics:
- The information exchange may enable filtering
- by feature type and name.Â
- based on spatial, temporal and logical operators.
Non Functional Requirements
There is no non functional requirement identified.
ConstraintsÂ
This exchange of information is constraint to be performed as follows:Â
This information exchanged relates to the requirements stated by CP1 and the SDP as described here:
In Â
 Click here to expand...
It corresponds with the following requirements associated to AIFS, but specialized to aerodrome data :
| A3SG-REF-002 | CP1/AF5.1.3 | AIFS | Operational stakeholders R/T AIFS | Operational stakeholders must implement aeronautical information feature on request; filtering possible by feature type, name and an advanced filter with spatial, temporal and logical operators … that support the exchange of the aeronautical information… as described in the deployment programme |
In terms of SDP
 Click here to expand...
It extends the information scope stated in the SDP to include aerodrome data. The AIFS requirements of the SDP are only focused on the AIP/SUP data:
| A3SG-REF-018 | SDP/AF5.3 | AIFS | AIFS purpose | This service supports consumption of published AIP and AIP SUP data |
It covers functionality requirements stated in the SDP:
| A3SG-REF-020 | SDP/AF5.3 | AIFS | AIFS functionality | The provider of the aeronautical information feature service ensures that systems implementing the service: • Shall allow the retrieval of aeronautical information features. • May enable filtering by feature type and name. • May allow advanced filtering based on spatial, temporal and logical operators. |
It covers roles the roles stated in the SDP, taking into account that airports in the context of AIFS provide information when acting as AISP.
| A3SG-REF-019 | SDP/AF5.3 | AIFS | AIFS roles | The aeronautical information feature exchange shall be implemented by: • AISPs that are the primary provider of the service • Airports when aerodrome information is provided by an Airport • AUs, ANSPs that are the primary consumers of the service and the information it provides |