EUROCONTROL
EUROCONTROL is an intergovernmental organisation with 42 Member and 2 Comprehensive Agreement States.
Aeronautical Aerodrome Map Request Service 1.0.0
Abstract
The Aeronautical Aerodrome Map Request Service provides a capability for on-request aeronautical aerodrome maps that are generated from aerodrome mapping data. Note: Aerodrome mapping data are based on the ICAO Annex 15 notion of aerodrome mapping data and the related aerodrome mapping datasets. Aeronautical aerodrome maps are a graphical representation of aerodrome mapping data. The service generates aeronautical aerodrome maps from current or next AIRAC cycle aerodrome mapping data available in the service back-end. The service encodes the aeronautical aerodrome maps in a graphical format. The consumer of the service can specify in the aerodrome map request: - the individual aerodrome, - the aerodrome map layers to be included, and - the geographical area of interest. The provided aeronautical aerodrome map is used in visualisation contexts as a backdrop map. The service capability enables various use cases (e.g. Digital NOTAM overlay in ePIB applications). The Aeronautical Aerodrome Map Request Service definition provides a common specification for the implementation of Aeronautical Aerodrome Map Request Service instances that conform with EU Implementing Regulation 2021/116 - Common Project One. Note: In the context of European SWIM deployment the Aeronautical Aerodrome Map Request Service capability realizes the SESAR Deployment Programme Aerodrome Mapping Service - Map part. The capability to request airport layout features (i.e. aerodrome mapping data) is realized by the Aeronautical Information Request Service.
Service Type
SWIM_COMPLIANT
Abbreviation
EUROCONTROL
Life Cycle
Business Activity Type
INFORMATION_MANAGEMENT
Intended Consumer
Information Exchange Category
AERONAUTICAL_INFORMATION_EXCHANGE
Application Message Exchange Pattern Entity
ICAO Region
Worldwide
Geospatial Categorisation Description
Worldwide
In-Operation Date
15-May-2025
Provider
Provider Type
AERONAUTICAL_INFORMATION_SERVICE_PROVIDER
Point of Contact
General
Operational Needs
There is a need for aeronautical aerodrome maps in support of integrated digital briefing applications (e.g. ePIB). Aerodrome maps can be used to ensure common situational awareness using them as backdrops in applications that display changes in the availability of the aerodrome infrastructure (e.g. Digital NOTAM overlay). Another example is the use of aerodrome maps in applications in support of aerodrome surface management.
A list of aerodrome map related operational needs is available in Appendix C.
The aeronautical aerodrome maps offered by the service satisfy the EU Implementing Regulation 2021/116 - Common Project One.
Note: Aerodrome mapping data are based on the ICAO Annex 15 notion of aerodrome mapping data and the related aerodrome mapping datasets. Aeronautical aerodrome maps are a graphical representation of aerodrome mapping data.
Note: In the context of European SWIM deployment the Aeronautical Aerodrome Map Request Service capability realizes the SESAR Deployment Programme Aerodrome Mapping Service - Map part. The capability to request airport layout features (i.e. aerodrome mapping data) is realized by the Aeronautical Information Request Service.
Information Exchange Requirements
Capabilities
The service provides aeronautical aerodrome maps based on service consumer requests (for example, for a specified geographical area, based on a specific map layer or for a specific aerodrome).
Functionality
The service consumer is able to discover the capabilities exposed by the service such as layers and styles.
The service consumer is able to request the aeronautical aerodrome map and be able to select which layers to include on it.
The service consumer is able to select the geographic area to be used when generating the map.
The service consumer is able to select an individual aerodrome to be used when generating the map.
The service consumer is able to specify the AIRAC cycle (current and next) of the aerodrome map request.
Access and Use
In order to be able to access and use AAMR Subscription and Request Service, Consumers need to become clients and sign the Client Agreement.
More in detail:
1. the data consumer has to register as a Data User or Commercial User Client,
2. the Organisation of the Data Consumer requires an AIMSL (B2B) license,
3. the Data Consumer user requires an EACP (European Aviation Common PKI) user certificate for authentication/authorisation purposes,
4. the Data Consumer user has to be able to use WMS.
The service consumers may use the data in order to integrate it in data products or facilitate their operations. Reselling the data is prohibited.
Customers can be negatively impacted when data usage is disproportionate and for extended periods. As protection mechanism, the service will restrict excessive requests originated from the same client.
The authentication requires all users to sign the requests using an X.509 certificate.
In order to consume the services, the Data Consumer user must have the appropriate user roles corresponding to the licenses allocated to their organisation. The service ensures that satisfactory authorisation is put in place according to EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile requirement SWIM-TIYP-0070.
The service ensures point-to-point confidentiality in accordance with EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile through the use of Transport Layer Security (TLS) 1.2.
The service ensures point-to-point integrity in accordance with EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile through the use of Transport Layer Security (TLS) 1.2.
Due care should be taken if an application consuming the service is used in cockpit/flight.
Quality of Service
??? NFR not defined for WMS
??? NFR not defined for WMS
The availability of the service is at least 99,975%.
The unplanned unavailability of the services shall not exceed 30 minutes (RTO = 30 minutes). In case of incidents the service ensures that no data is lost (RPO = 15) followed by operational procedures to recover potential data losses.
The service ensures confidentiality by using SWIM Technical Infrastructure (TI) Yellow Profile bindings.
The service ensures integrity by using SWIM Technical Infrastructure (TI) Yellow Profile bindings. Data integrity is ensured by the mTLS (which is based on TLS v1.2).
Validation
Service Support
Abbreviations
AIS Data Maintenance
Aeronautical Information Management
AIM Service Layer
Aeronautical Information Regulation And Control
Aeronautical Information Service
Aerodrome Mapping Data
Aeronautical Information Exchange Model
Business to Business
Create, Read, Update, Delete
European Aviation Common PKI
European Union Aviation Safety Agency
Enhanced European AIS Database
Electronic Pre-flight Information Bulletin
European Petroleum Survey Group
European Union
Factory Acceptance Testing
Hypertext Transport Protocol
International Civil Aviation Organization
Interface Control Document
Information Exchange Requirements
Mutual TLS
Notice To Air Missions
Open Geospatial Consortium
Public Key Infrastructure
Representational State Transfer
Recovery Point Objective
Recovery Time Objective
Site Acceptance Testing
Single European Sky ATM Research
System Quality Testing
System-Wide Information Management
Technical Infrastructure
Transport Layer Security
Uniform Resource Locator
Web Map Service
Web Service
Extensible Markup Language
Information
Information Definition
The service offers aeronautical aerodrome map layers based on a graphical representation (i.e. portrayal) of aerodrome mapping data (AMD).
Note: A map is the result of a request to portray information represented by one or more layers.
The service conforms with the OGC Web Map Service 1.3.0 Interface Standard. The EPSG:3857 coordinate reference system is used for the projection. If an aeronautical aerodrome map layer corresponds to one of the layers listed in Appendix B, the layer name in Appendix B is used to expose the capabilities of the service. If the service consumer requests a combination of layers exposed by the service, the generation of the aeronautical aerodrome map is according to the OGC Web Map Service 1.3.0 Interface Standard.
The layers are based on AIXM 5.1.1 AMD Features with geometry. Naming and grouping of the layers is defined according to the Appendix B.
Note: The GetCapabilities operation exposes the available layers, styles and coordinate reference systems.
Note: The coordinate reference system and naming of the layers used in the service are subject to the requirements provided in this service definition.
https://swim-eurocontrol.atlassian.net/wiki/spaces/ASW/pages/60031410/Aeronautical+Aerodrome+Map+Request+Service+-+Service+Definition
Filtering
Property based filtering is applied when aerodromeId parameter in GetMap request is used.
Source of Information
The service provider shall ensure that the aeronautical data offered by the services is received from the appropriate authorised originating sources. This includes:
- AIRPORT_OPERATOR,
- CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER,
- MILITARY_AIR_NAVIGATION_SERVICE_PROVIDER,
- AIR_TRAFFIC_SERVICE_PROVIDER,
- AERONAUTICAL_INFORMATION_SERVICE_PROVIDER,
- COMMUNICATION_NAVIGATION_AND_SURVEILLANCE_SERVICE_PROVIDER,
- AIRSIDE_GROUND_HANDLER,
- Owners of Obstacles.
- AIRPORT_OPERATOR,
- CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER,
- MILITARY_AIR_NAVIGATION_SERVICE_PROVIDER,
- AIR_TRAFFIC_SERVICE_PROVIDER,
- AERONAUTICAL_INFORMATION_SERVICE_PROVIDER,
- COMMUNICATION_NAVIGATION_AND_SURVEILLANCE_SERVICE_PROVIDER,
- AIRSIDE_GROUND_HANDLER,
- Owners of Obstacles.
Technical
Technical Constraint
The visibility of map layers in this service shall be restricted to minimum scale of 1:25 000 (including).
The aeronautical aerodrome map offered by the service shall be generated from aeronautical data that satisfies the applicable sections of Commission Implementing Regulation (EU) 2017/373 of 1 March 2017
The aeronautical aerodrome map offered by the service shall be generated from aeronautical data that applies the AIXM 5.1.1 coding guidelines. This includes:
- Common Coding Guidelines
- Technical Coding Guidelines
The aeronautical aerodrome map offered by the service shall be generated from aeronautical data that follows:
- Aerodrome Mapping Data Sets Supporting Material
WMS operation DescribeLayer is not supported.
Service Monitoring
A service monitoring mechanism is not available to service consumers.
Behaviour
The service behaviour is in accordance with the Synchronous Request/Reply pattern detailed in Message Exchange Patterns: Identification Guidelines. The OGC Web Map Service 1.3.0 Interface Standard is used.
The behaviour in normal conditions is as follows:
- The request message is sent from the service consumer to the service
- The service consumer remains blocked while awaiting the reply
- The service remains blocked while processing the reply
- The aeronautical aerodrome map, the reply message, is sent from the service to the service consumer.
All RESTful responses provide feedback of type information, warning or error depending on the execution success.
The complete list of the response feedback is available in the ADM XML Primer document, appendix A.2 Error, info and warning messages supported by SDD.
Interfaces
The interface is used to group the operations offered by the OGC Web Map Service 1.3.0 Interface Standard.
Operations
The GetCapabilities operation returns metadata about the operations, services, and data (âcapabilitiesâ) that are offered the WMS service.
Idempotent
IDEMPOTENT
Operation Message
Binding Method
SWIM_TI_YP_1_1_WS_LIGHT
The GetMap operation returns an Aeronautical Aerodrome Map that satisfies the query expressions specified in the GetMap Request message.
Idempotent
IDEMPOTENT
Operation Message
Binding Method
SWIM_TI_YP_1_1_WS_LIGHT
Parameter
The GetFeatureInfo operation returns the spatial and attribute data for the features at a given location on a map. It is similar to the WFS GetFeature operation, but less flexible in both input and output. The one advantage of GetFeatureInfo is that the request uses an (x,y) pixel value from a returned WMS image. This is easier to use for a client that is not able to perform true geographic referencing.
Idempotent
IDEMPOTENT
Operation Message
Binding Method
SWIM_TI_YP_1_1_WS_LIGHT
The GetLegendGraphic operation provides a mechanism for generating legend graphics as images, beyond the LegendURL reference of WMS Capabilities. It generates a legend based on the style defined on the server, or alternatively based on a user-supplied SLD.
Idempotent
IDEMPOTENT
Binding Method
SWIM_TI_YP_1_1_WS_LIGHT
Endpoints
Endpoint for Aeronautical Aerodrome Map Request Service is RESTful Request-Reply interface WMS.
Url
URL:/swim/wms
Reference
Service Interface Binding
The web service is bound to the REST architectural style.
Network Interface Binding
SWIM TI Yellow Profile specification
Messages
References
Service Documents
Aeronautical Aerodrome Map Request Service - Service Definition - Aeronautical SWIM Services - SWIM Confluence (atlassian.net)
Reference
https://swim-eurocontrol.atlassian.net/wiki/spaces/ASW/pages/60031410/Aeronautical+Aerodrome+Map+Request+Service+-+Service+Definition
Aeronautical Aerodrome Map Request Service - Service Definition - Aeronautical SWIM Services - SWIM Confluence (atlassian.net)
Reference
https://swim-eurocontrol.atlassian.net/wiki/spaces/ASW/pages/60031410/Aeronautical+Aerodrome+Map+Request+Service+-+Service+Definition
Aeronautical Aerodrome Map Request Service - Service Definition - Aeronautical SWIM Services - SWIM Confluence (atlassian.net)
Reference
https://swim-eurocontrol.atlassian.net/wiki/spaces/ASW/pages/60031410/Aeronautical+Aerodrome+Map+Request+Service+-+Service+Definition
Aeronautical Aerodrome Map Request Service - Service Definition - Aeronautical SWIM Services - SWIM Confluence (atlassian.net)
Reference
https://swim-eurocontrol.atlassian.net/wiki/spaces/ASW/pages/60031410/Aeronautical+Aerodrome+Map+Request+Service+-+Service+Definition
urn:aero:airm:1.0.0:ContextualModel:ATMBusinessTerms:Aerodrome_mapping_data
Implemented Standards
This International Standard specifies the behaviour of a service that produces spatially referenced maps dynamically from geographic information. It specifies operations to retrieve a description of the maps offered by a server to retrieve a map, and to query a server about features displayed on a map. This International Standard is applicable to pictorial renderings of maps in a graphical format; it is not applicable to retrieval of actual feature data or coverage data values.
The styling of the map output conforms with the WMS specification made by the Styled Layer Descriptor (SLD) 1.1.0 standard.
REST (Representational State Transfer) is a set of constraints for designing and developing web-based systems that are scalable, reliable, and loosely coupled. REST APIs use HTTP methods (such as GET, POST, PUT, DELETE) to define actions that can be performed on resources. These methods align with CRUD (Create, Read, Update, Delete) operations, which are used to manipulate resources over the web.
Extensible Markup Language (XML) is a markup language and file format for storing, transmitting, and reconstructing arbitrary data. It defines a set of rules for encoding documents in a format that is both human-readable and machine-readable.
Revision Save Date
Mon, 05/26/2025 - 14:05
Schema version
v2