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.
", "serviceDefinitionProvider": { "pointOfContact": [ null ], "provider": "EUROCONTROL", "providerDescription": "EUROCONTROL is an intergovernmental organisation with 42 Member and 2 Comprehensive Agreement States.
" }, "serviceCategorisation": { "serviceType": "SWIM_DEFINITION", "intendedConsumer": [ "AIR_TRAFFIC_SERVICE_PROVIDER", "AIRPORT_OPERATOR", "CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER", "CIVIL_AIRSPACE_USER", "MILITARY_AIR_NAVIGATION_SERVICE_PROVIDER", "MILITARY_AIRSPACE_USER", "PROVIDER_OF_DATA_SERVICES" ], "informationCategory": [ "AERONAUTICAL_INFORMATION_EXCHANGE" ], "applicationMessageExchangePattern": [ { "name": "SYNCHRONOUS_REQUEST_REPLY" } ], "other": [ { "name": "Service Type", "value": "AERONAUTICAL_AERODROME_MAP_ACCESS_SERVICE", "categorisationScheme": { "url": "http://reference.swim.aero/information-services/service-categories/CodeServiceType.html" } } ] }, "generalDescription": { "operationalEnvironment": { "operationalNeeds": [ { "name": "Aerodrome Maps", "description": "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 \u00e2\u0080\u0093 Map part. The capability to request airport layout features (i.e. aerodrome mapping data) is realized by the Aeronautical Information Request Service." }, { "name": "Information Exchange Requirements", "description": "Information Exchange Requirements", "reference": { "description": "IER 1 - Aerodrome Maps Exchange (A3SG-IER-03)", "url": "https://ext.eurocontrol.int/swim_confluence/display/ASW/A3SG-IER-03+Aerodrome+Maps+Exchange" } } ], "capabilities": [ { "name": "Aeronautical Aerodrome Maps", "description": "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": [ { "name": "Discover Capabilities", "description": "The service consumer shall be able to discover the capabilities exposed by the service such as layers and styles.", "realWorldEffect": "The service consumer knows the capabilities of the service." }, { "name": "Request Aeronautical Aerodrome Map", "description": "The service consumer shall be able to request the aeronautical aerodrome map and be able to select which layers to include on it.", "realWorldEffect": "The service consumer receives the requested map." }, { "name": "Request aeronautical aerodrome map by geographic area", "description": "The service consumer shall be able to select the geographic area to be used when generating the map.", "realWorldEffect": "The service consumer receives the requested map." }, { "name": "Request aeronautical aerodrome map by identifier", "description": "The service consumer shall be able to select an individual aerodrome to be used when generating the map.Note: The service shall support ICAO aerodrome location indicators as a minimum.", "realWorldEffect": "The service consumer receives the requested map." }, { "name": "Request aeronautical aerodrome map by AIRAC cycle", "description": "The service consumer shall be able to specify the AIRAC cycle (current and next) of the aerodrome map request.", "realWorldEffect": "Service consumer receives the requested map." } ], "qualitiesOfService": { "performance": [ { "name": "Capacity", "description": "The service shall achieve a quality that is sufficient to ensure the service is fit for purpose." }, { "name": "Response time", "description": "The service shall achieve a quality that is sufficient to ensure the service is fit for purpose." } ], "reliability": [ { "name": "Availability", "description": "The service shall achieve a quality that is sufficient to ensure the service is fit for purpose." }, { "name": "Recoverability", "description": "The service shall achieve a quality that is sufficient to ensure the service is fit for purpose." } ], "security": [ { "name": "Confidentiality", "description": "The service shall ensure confidentiality by using SWIM Technical Infrastructure (TI) Yellow Profile bindings." }, { "name": "Integrity", "description": "The service shall ensure integrity by using SWIM Technical Infrastructure (TI) Yellow Profile bindings." } ] }, "qualityOfData": [ { "name": "Quality of Data", "description": "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 2017The 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 GuidelinesThe aeronautical aerodrome map offered by the service shall be generated from aeronautical data that follows:- Aerodrome Mapping Data Sets Supporting Material" } ], "accessAndUseConditions": [ { "name": "Authentication", "type": "SECURITY_CONSTRAINT", "description": "The service may offer unauthenticated/public use.If the use is authenticated, the service shall ensure consumer authentication in accordance with the EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile through the use of a X.509 certificate or the use of a username/password (SASL).The service shall ensure provider authentication in accordance with EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile through the use of a X.509 certificate." }, { "name": "Authorisation", "type": "SECURITY_CONSTRAINT", "description": "The service shall ensure that satisfactory authorisation is put in place according to EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile requirement SWIM-TIYP-0070." }, { "name": "Confidentiality", "type": "SECURITY_CONSTRAINT", "description": "The service shall ensure 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 or above." }, { "name": "Integrity", "type": "SECURITY_CONSTRAINT", "description": "The service shall ensure 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 or above." }, { "name": "Business Policies", "type": "", "description": "Due care should be taken if an application consuming the service is used in cockpit/flight." } ], "validation": [ { "type": "NOT_VALIDATED", "description": { "validationResults": "The service definition is based on work carried out in SESAR.\r\n\r\nA similar service was implemented in the context of the Airport Data Toolkit pre-operational trial.\r\n\r\nNo further validation has taken place on this service definition." } } ] }, "informationDescription": { "sourceOfInformation": "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", "informationDefinition": [ { "name": "Aeronautical Aerodrome Map Request", "definition": "The service shall offer aeronautical aerodrome map layers based on a graphical representation (i.e. portrayal) of aerodrome mapping data (AMD).\r\n\r\nNote: A map is the result of a request to portray information represented by one or more layers.\r\n\r\nThe service shall conform with the OGC Web Map Service 1.3.0 Interface Standard.\r\n\r\nThe EPSG:3857 coordinate reference system shall be used as a minimum for the projection.\r\n\r\nIf an aeronautical aerodrome map layer corresponds to one of the layers listed in Appendix B, the layer name in Appendix B shall be used to expose the capabilities of the service.\r\n\r\nIf the service consumer requests a combination of layers exposed by the service, the generation of the aeronautical aerodrome map shall be according to the OGC Web Map Service 1.3.0 Interface Standard.\r\n\r\nNote: The GetCapabilities operation will expose the available layers, styles and coordinate reference systems.\r\n\r\nNote: The structuring and styling of the layers is a service design decision to be taken when implementing the service.\r\n\r\nNote: The coordinate reference system and naming of the layers used in the service are subject to the requirements provided in this service definition.", "airmCorrespondence": "urn:aero:airm:1.0.0:ContextualModel:ATMBusinessTerms:Aerodrome_mapping_data" } ] }, "technicalDescription": { "serviceMonitoring": { "monitoringDescription": "A service monitoring mechanism shall be made available to service consumers." }, "behaviour": [ { "name": "Typical Behaviour", "description": "The service behaviour shall be 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 shall be used for the basic behaviour.The typical behaviour is as follows:*Synchronous Request/Reply- 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." } ] }, "serviceInterface": [ { "name": "Aeronautical Aerodrome Map Request Service Interface", "description": "The interface is used to group the operations offered by the OGC Web Map Service 1.3.0 Interface Standard.", "provisionSide": "PROVIDER_SIDE", "serviceInterfaceBinding": { "name": "EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile", "description": "The OGC Web Map Service 1.3.0 Interface Standard shall be used.\r\n\r\nAll standardised operations for Basic WMS shall be implemented.\r\n\r\nAll standardised operations for Queryable WMS should be implemented.\r\n\r\nOther operations (such as GetLegend) may be implemented." }, "networkInterfaceBinding": { "reference": { "description": "The service shall use TLS1.2 or later in accordance with EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile.", "url": "https://reference.swim.aero/technical-infrastructure/foundation.html" }, "name": "Network Interface Binding", "description": "The service shall use the network bindings of the SWIM TIYP." }, "operations": [ { "name": "GetMap", "description": "The GetMap operation returns an Aeronautical Aerodrome Map that satisfies the query expressions specified in the GetMap Request message.", "idempotency": "IDEMPOTENT", "messages": [ { "name": "Request", "direction": "IN" }, { "name": "Aeronautical Aerodrome Map", "direction": "OUT" } ], "binding_method": "WS_LIGHT" } ], "messages": [ { "name": "Aeronautical Aerodrome Map", "description": "This is the map that is generated on the server as a result of the GetMap query to the service.", "schema": { "description": "It is in a graphical format supported by the OGC Web Map Service 1.3.0 Interface Standard. The desired output format may be included in the query to the service.\r\n\r\nIf the queryable WMS is implemented, the information that results from the query shall be aligned with the terms and definitions of the AIXM 5.1.1 exchange language.", "url": "https://www.aixm.aero/page/aixm-51-511" }, "isError": false } ], "messageExchangePattern": "REQUEST_REPLY" } ], "references": { "serviceDocument": [ { "documentType": "SERVICE_SPECIFICATION", "title": "Appendix A: References", "version": "-", "description": "" }, { "documentType": "SERVICE_SPECIFICATION", "title": "Appendix B: Information Definition for Aeronautical Aerodrome Map Request Service", "version": "-", "description": "" }, { "documentType": "SERVICE_SPECIFICATION", "title": "Appendix C:Operational Needs", "version": "-", "description": "" }, { "documentType": "SERVICE_SPECIFICATION", "title": "Appendix D: Example Configurations", "version": "-", "description": "" } ], "implementedStandard": [ { "title": "Implemented Standards", "standardType": "EUROCONTROL_SPECIFICATION_FOR_SWIM_INFORMATION_DEFINITION", "conformanceStatement": "Conformance - This field is left empty.", "description": "This field is left empty." } ] } } }