Service Definition Identification
status| service definition identification | title | Service definition for the IWXXM METAR-SPECI Subscription and Request Service |
|---|---|---|
edition | 00.00.05 | |
reference date | 2024-06-17 |
| Table of Contents | ||||
|---|---|---|---|---|
|
| title | Status Key |
|---|
| Status | ||
|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
Service Identification
-17 |
| Table of Contents | ||||
|---|---|---|---|---|
|
Service Identification
| service identification | service name | IWXXM METAR-SPECI Subscription and Request Service |
|---|
Service Abstract
| service abstract | The IWXXM METAR-SPECI Subscription and Request Service provides the service consumer with METAR/SPECI report(s) for one or more aerodromes of a State as it becomes available. The service consumer can subscribe to the service, specifying the aerodrome of interest, and receive information as it becomes available. It is also possible to send a direct request, using a request-reply mechanism, to the service to get the relevant meteorological information. The meteorological information is issued by the designated Aeronautical Meteorological Station. The meteorological information is only intended to be used by service consumers within the aviation domain. |
|---|
Service Definition Provider
service definition provider | name | EUROCONTROL |
|---|---|---|
| description | EUROCONTROL is an intergovernmental organisation with 41 Member and 2 Comprehensive Agreement States. | |
| point of contact | swim@eurocontrol.int |
Geographical Extent of Information
| geographical extent of information | The service shall make METAR/SPECI report(s) available for one or more aerodrome(s)within a State. Note: it is expected that a single service will be implemented per State, covering all of the aerodromes within the State. |
|---|
Service Categories
Service Standard Reference
| Info | ||
|---|---|---|
| ||
This field is left empty. |
service standard reference | reference | |
|---|---|---|
| implemented options | ||
| deviations/additions |
Operational Environment
Operational Environment
| operational environment | operational needs | A list of operational needs that this service contributes to satisfying is available in Appendix B. This service satisfies these by offering meteorological information as regulated by Commission Implementing Regulation (EU) 2017/373 of 1 March 2017 and ICAO Annex 3. The scope of the meteorological information satisfies the EU Implementing Regulation 2021/116 - Common Project One. |
|---|---|---|
| capabilities | The service provides high quality, up-to-date, trusted, regulated meteorological information in digital form for use by service consumers within the aviation domain. | |
information exchange requirements | The service takes into account the following information exchange requirements:
|
Service Functions
| service functions | function | name | Request the latest METAR/SPECIs |
|---|---|---|---|
| description | The service consumer shall be able to request the latest METAR/SPECIs for an aerodrome or group of aerodromes. | ||
| real-world effect | The meteorological information is received and can be used by the service consumer. | ||
| function | name | Subscribe to METAR/SPECIs | |
| description | The service consumer shall be able to subscribe/unsubscribe in order to receive METAR/SPECIs based on ICAO location indicator codes for aerodromes. | ||
| real-world effect | The service consumer subscribes to the service and will receive METAR/SPECIs as per the subscription or unsubscribes from the service. | ||
| function | name | Distribute METAR/SPECIs | |
| description | The service shall distribute the METAR/SPECIs when they are available. | ||
| real-world effect | The service consumer receives the METAR/SPECIs. |
Service Access and Use Conditions
service access and use conditions | legal constraints | ||
|---|---|---|---|
service policies | business policy | ||
operational policy | There shall be a service policy to ensure that only service consumers within the aviation domain can use the service. The service policy shall include a requirement that service consumers cannot pass the information obtained from the service to non-aviation users without prior authorisation from the service provider. | ||
technical policy | |||
service consumption constraints | There shall be a service consumption constraint to ensure that a service consumer does not impose undue loads on computer and network resources, for example, by polling it at a higher frequency than the status is normally provided. |
Security Constraints
security constraints | authentication | The service shall ensure consumer authentication in accordance with EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile requirement SWIM-TIYP-0042. The service shall ensure provider authentication in accordance with EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile requirement SWIM-TIYP-0042. |
|---|---|---|
authorisation | 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. | |
confidentiality | 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. | |
integrity | 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. |
Quality of Service
quality of service | performance | capacity | The service shall achieve a quality that is sufficient to ensure the service is fit for purpose. |
|---|---|---|---|
| response time | The service shall achieve a quality that is sufficient to ensure the service is fit for purpose. | ||
| reliability | availability | The service shall achieve a quality that is sufficient to ensure the service is fit for purpose. | |
| recoverability | The service shall achieve a quality that is sufficient to ensure the service is fit for purpose. | ||
| security | confidentiality | The service shall ensure confidentiality by using SWIM Technical Infrastructure (TI) Yellow Profile bindings. | |
| integrity | The service shall ensure integrity by using SWIM Technical Infrastructure (TI) Yellow Profile bindings. |
Quality of Data
| quality of data | The meteorological information offered by the service shall be verified by the service provider. The meteorological information offered by the service shall be encoded according to the rules of the IWXXM standard. The meteorological information offered by the service shall satisfy the WMO No. 8 (2018) Guide to Meteorological Instruments and Methods of Observation. |
|---|
Source of Information
source of information | source | The service provider shall ensure that the meteorological data offered by the services isreceived from the appropriate authorised originating sources. This includes:
|
|---|
Service Validation Information
Service Validation Information
| Info | ||
|---|---|---|
| ||
This field is left empty. |
service validation information | description |
|---|
Application Message Exchange Pattern
application message exchange pattern |
|---|
Service Behaviour
service behaviour | typical behaviour | The service behaviour shall be in accordance with the patterns detailed in the Message Exchange Patterns: Identification Guidelines. The typical service behaviour, is:
The interfaces have different behaviour. A combination of an AMQP 1.0 implementation and an OGC implementation shall be used for the basic behaviour. The typical behaviour for PUBLISH_SUBSCRIBE means that:
The typical behaviour for REQUEST_REPLY (as used in IWXXM METAR-SPECISubscription and Request Service Request Interface) is as follows: Synchronous Request/Reply
|
|---|
Service Monitoring
service monitoring | A service monitoring mechanism should be made available to service consumers. |
|---|
Service Interfaces
statusservice interfaces | interface | name | IWXXM METAR-SPECI Subscription and Request Service Request Interface |
|---|---|---|---|
| description | Allows the service consumer to request the latest available METAR/SPECIs. Note: This interface is used to group the operations offered by the chosen OGC standard. | ||
| provider/consumer side | Provider side | ||
| interface | name | IWXXM METAR-SPECI Subscription and Request Service Subscription Interface | |
| description | Allows the service consumer to select and subscribe to METAR/SPECIs for aerodromes of interest. It allows the service consumer to manage the subscriptions e.g. to unsubscribe. Note: This is an optional interface. Many service providers will prefer to receive subscription requests by email. | ||
| provider/consumer side | Provider side | ||
| interface | name | IWXXM METAR-SPECI Subscription and Request Service Distribution Interface | |
| description | Allows the service provider to distribute the latest available METAR/SPECIs meeting the need of the service consumer that has subscribed for updates. | ||
| provider/consumer side | Consumer side |
SWIM TI Profile and Interface Bindings
IWXXM METAR-SPECI Subscription and Request Service Request Interface
SWIM TI profile and interface bindings | profile name | EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile |
|---|---|---|
profile version | 1.1 | |
| selected service interface binding | WS_LIGHT | |
| selected network interface binding | The service shall use the network bindings of the SWIM TIYP. | |
| description | The interface shall use at least one of the following OGC standards:
Note: it is a best practice for new services that exchange meteorological information to implement the OGC API – Environmental Data Retrieval Standard. Existing services based on the OGC Web Feature Service 2.0 Interface Standard should indicate an end-of-life date. |
IWXXM METAR-SPECI Subscription and Request Service Subscription Interface
SWIM TI profile and interface bindings | profile name | EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile |
|---|---|---|
profile version | 1.1 | |
| selected service interface binding | ||
| selected network interface binding | The service shall use the network bindings of the SWIM Technical Infrastructure (TI) Yellow Profile. | |
| description |
IWXXM METAR-SPECI Subscription and Request Service Distribution Interface
SWIM TI profile and interface bindings | profile name | EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile |
|---|---|---|
profile version | 1.1 | |
| selected service interface binding | SWIM_TI_YP_1_1_AMQP_MESSAGING | |
| selected network interface binding | The service shall use the network bindings of the SWIM TIYP. | |
| description | AMQP 1.0 shall be used to distribute messages as explained in the Publish/Subscribe Push MEP: Implementation Guidance. |
Service Interface Protocols and Data Format
service interface protocols and data format | transport / messaging protocols | The service shall use TLS1.2 or later in accordance with EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile. | |
|---|---|---|---|
| data format |
|
Service Operations
IWXXM METAR-SPECI Subscription and Request Service Request Interface
| Info | ||
|---|---|---|
| ||
The OGC Web Feature Service Interface Standard and OGC API – Environmental Data Retrieval Standard are used to implement the service operations. It is not the intention to repeat the standardised operations here. However, the table below illustrates how the WFS GetFeature operation would look in the context of this service. |
Service operations | operation | operation name | GetFeature |
|---|---|---|---|
description | The GetFeature operation returns a selection of features from a data store. It responds to a GetFeature Request message with a Meteorological Aerodrome Observation Message that satisfies the query expressions specified in the request. | ||
messages | Request, METAR/SPECI |
IWXXM METAR-SPECI Subscription and Request Service Subscription Interface
Service operations | reference | url | Meteorological SWIM Services Subscription Interface Standard |
|---|---|---|---|
description | The standard operations for subscription and subscription management. The following operations shall be implement at a minimum:
|
IWXXM METAR-SPECI Subscription and Request Service Distribution Interface
Service operations | operation | operation name | publish |
|---|---|---|---|
description | This operation allows the service provider to publish METAR-SPECI report(s) to service consumers based on their subscriptions. | ||
messages | METAR/SPECI |
Service Messages
messages | METAR/SPECI |
|---|
Service Messages
| Info | ||
|---|---|---|
| ||
The OGC Web Feature Service Interface Standard and OGC API – Environmental Data Retrieval Standard detail the basic messages such as request and response messages. It is not the intention to repeat the standardised messages here. The table below provides extra details for the METAR/SPECI message. |
service messages | message | name | METAR/SPECI |
|---|---|---|---|
| description | The message that is an output of the service, containing the METAR/SPECI information. | ||
| direction | Out | ||
| data format | The METAR/SPECI information shall be provided in ICAO’s Meteorological Information Exchange Model (IWXXM) format containing a collection of features. | ||
| message | name | Request | |
| description | Request message submitted to the service containing query expressions for the WFS GetFeature operation or the EDR HTTP GET operation. | ||
| direction | In | ||
| data format | |||
| reference | url | Meteorological SWIM Services Subscription Interface Standard | |
| description | The standard messages for subscription and subscription management. |
Information Definition (Minimum) and (Extended)
| information definition | The service shall offer meteorological information in accordance with ICAO Annex 3. The service shall offer meteorological information in accordance with the rules of latest applicable version of IWXXM. Note: the latest applicable version of IWXXM (IWXXM 2023-1) contains the METAR/SPECI schema version 3.1.0. |
|---|
Filter Encoding
| filter encoding | The IWXXM METAR/SPECI Subscription and Request Service Request Interface shall support filtering based on the ICAO location indicator of the aerodrome of interest. The IWXXM METAR/SPECI Subscription and Request Service Subscription Interface shall allow for the selection of subscription based on clearly defined criteria. The service may support other filters based on the operators defined in the OGC Filter Encoding 2.0 Encoding Standard on a case by case basis. |
|---|
Machine-Readable Service Interface Definition
| Info | ||
|---|---|---|
| ||
This field is left empty. No machine-readable service interface definition is provided. |
machine-readable service interface definition | reference |
|---|
Model View
| Info | ||
|---|---|---|
| ||
This field is left empty. No model view is provided. |
model view | reference |
|---|
Abbreviations and Acronyms
| abbreviations and acronyms | abbreviation | code | AMO |
|---|---|---|---|
| term | Aerodrome Meteorological Office | ||
| abbreviation | code | AMQP | |
| term | Advanced Message Queuing Protocol | ||
| abbreviation | code | AMS | |
| term | Aeronautical Meteorological Station | ||
| abbreviation | code | API | |
| term | Application Programming Interface | ||
| abbreviation | code | EDR | |
| term | Environmental Data Retrieval | ||
| abbreviation | code | EU | |
| term | European Union | ||
| abbreviation | code | HTTP | |
| term | Hypertext Transfer Protocol | ||
| abbreviation | code | ICAO | |
| term | International Civil Aviation Organization | ||
| abbreviation | code | IWXXM | |
| term | ICAO Meteorological Information Exchange Model | ||
| abbreviation | code | JSON | |
| term | JavaScript Object Notation | ||
| abbreviation | code | MEP | |
| term | Message Exchange Pattern | ||
| abbreviation | code | METAR | |
| term | Aviation routine weather report (in aeronautical meteorological code) | ||
| abbreviation | code | OGC | |
| term | Open Geospatial Consortium | ||
| abbreviation | code | PANS-MET | |
| term | ICAO Procedures for Air Navigation Services – Meteorology | ||
| abbreviation | code | SPECI | |
| term | Aerodrome SPECIAL meteorological report (in meteorological code) | ||
| abbreviation | code | SWIM | |
| term | System wide information management | ||
| abbreviation | code | TI | |
| term | Technical Infrastructure | ||
| abbreviation | code | TIYP | |
| term | Technical Infrastructure Yellow Profile | ||
| abbreviation | code | TLS | |
| term | Transport Layer Security | ||
| abbreviation | code | TREND | |
| term | A concise statement of the Expected Significant changes in the meteorological conditions at that Aerodrome to be appended to a local routine or local SPECIAL report, or a METAR or SPECI. | ||
| abbreviation | code | WFS | |
| term | Web Feature Service | ||
| abbreviation | code | WMO | |
| term | World Meteorological Organization | ||
| abbreviation | code | XML | |
| term | Extensible Markup Language |
Appendix A: References
| references | reference | title | EU Implementing Regulation 2021/116 - Common Project One |
|---|---|---|---|
| version | 1 February 2021 | ||
| description | Commission Implementing Regulation (EU) 2021/116 of 1 February 2021 on the establishment of the Common Project One supporting the implementation of the European Air Traffic Management Master Plan provided for in Regulation (EC) No 550/2004 of the European Parliament and of the Council, amending Commission Implementing Regulation (EU) No 409/2013 and repealing Commission Implementing Regulation (EU) No 716/2014. | ||
| url | https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32021R0116 | ||
| document type | |||
| reference | title | ICAO Annex 3 Meteorological Service for International Air Navigation | |
| version | |||
| description | The object of the meteorological service outlined in Annex 3 is to contribute to the safety, efficiency and regularity of air navigation. This is achieved by providing necessary meteorological information to operators, flight crew members, air traffic services units, search and rescue units, airport management and others concerned with aviation. Close liaison is essential between those supplying meteorological information and those using it. | ||
| url | https://store.icao.int/en/annex-3-meteorological-service-for-international-air-navigation | ||
| document type | |||
| reference | title | ICAO Procedures for Air Navigation Services – Meteorology (PANS-MET) | |
| version | tbd | ||
| description | |||
| url | |||
| document type | |||
| reference | title | WMO No. 8 (2018) Guide to Meteorological Instruments and Methods of Observation | |
| version | 2021/2018 edition | ||
| description | |||
| url | https://community.wmo.int/en/activity-areas/imop/wmo-no_8 | ||
| document type | |||
| reference | title | Commission Implementing Regulation (EU) 2017/373 | |
| version | 1 March 2017 (as amended) | ||
| description | Commission Implementing Regulation (EU) 2017/373 of 1 March 2017 laying down common requirements for providers of air traffic management/air navigation services and other air traffic management network functions and their oversight, repealing Regulation (EC) No 482/2008, Implementing Regulations (EU) No 1034/2011, (EU) No 1035/2011 and (EU) 2016/1377 and amending Regulation (EU) No 677/2011. | ||
| url | https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A02017R0373-20230126 | ||
| document type | |||
| reference | title | OGC API – Environmental Data Retrieval Standard | |
| version | 1.1 | ||
| description | OGC API standards define modular API building blocks to spatially enable Web APIs in a consistent way. The OpenAPI specification is used to define the API building blocks. | ||
| url | |||
| document type | SERVICE_SPECIFICATION | ||
| reference | title | ICAO Meteorological Information Exchange Model (IWXXM) | |
| version | |||
| description | The ICAO Meteorological Information Exchange Model (IWXXM) is an exchange model capturing Meteorological information. It was introduced to support the exchange of meteorological information in accordance with ICAO Annex 3. | ||
| url | https://github.com/wmo-im/iwxxm | ||
| document type | INFORMATION_DEFINITION | ||
| reference | title | OGC Web Feature Service 2.0 Interface Standard | |
| version | 2.0 | ||
| description | WFS offers direct fine-grained access to geographic information at the feature and feature property level. Note: This is equivalent to ISO 19142 - Geographic Information - Web Feature Service. | ||
| url | https://www.ogc.org/standard/wfs/ | ||
| document type | SERVICE_SPECIFICATION | ||
| reference | title | OGC API – Features | |
| version | |||
| description | OGC API Features provides API building blocks to create, modify and query features on the Web. | ||
| url | https://www.ogc.org/standard/ogcapi-features/ | ||
| document type | SERVICE_SPECIFICATION | ||
| reference | title | OGC Filter Encoding 2.0 Encoding Standard | |
| version | |||
| description | This jointly developed OGC and ISO TC/211 International Standard describes an XML and KVP encoding of a system neutral syntax for expressing projections, selection and sorting clauses collectively called a query expression. These components are modular and intended to be used together or individually by other standards which reference this International Standard. Note: This is equivalent to ISO 19143 - Geographic Information - Filter encoding. | ||
| url | https://www.ogc.org/docs/is | ||
| document type | SERVICE_SPECIFICATION | ||
| reference | title | Message Exchange Patterns: Identification Guidelines | |
| version | JULY 2nd, 2019 | ||
| description | Document intended to facilitate the understanding of message exchange patterns from an application and Technical Infrastructure perspective. | ||
| url | https://reference.swim.aero/technical-infrastructure/message-exchange-patterns-identification-guidelines.html | ||
| document type | SERVICE_BEHAVIOUR_DESCRIPTION | ||
| reference | title | Publish/Subscribe Push MEP: Implementation Guidance | |
| version | JULY 2nd, 2019 | ||
| description | This document intends to serve as implementation guidance of the Publish/Subscribe Push Message Exchange Pattern using SWIM-TI Yellow Profile Service Bindings. | ||
| url | https://reference.swim.aero/technical-infrastructure/guidance-for-pub-sub-push-implementation.html | ||
| document type |
| Anchor | ||||
|---|---|---|---|---|
|
Transversal
- Support integration of existing and/or tailored weather information with operational processes to aid decision-making and improve understanding of the operational impact of adverse weather.
By service consumer role
| Stakeholder/Role | Description of stakeholder/role | Needs for aerodrome observations | Notes |
|---|---|---|---|
| CIVIL_AIRSPACE_USER | A generic term designating an organization operating aircraft and its pilots, the flight operations centres (FOC) responsible for the strategic planning of a flight and the entity responsible for the execution of a flight which is traditionally a flight deck. |
| This role is recognised in the SESAR Deployment Programme as a recommended service consumer of the aerodrome and en-route services. |
| MILITARY_AIRSPACE_USER | Airspace User under the authority of a military organisation. |
| This role is recognised in the SESAR Deployment Programme as a service consumer of the aerodrome and en-route services. Although the military is not obliged to use SWIM, they currently rely on civil weather information and therefore it will be essential for their operations to use SWIM-services. |
| CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER | Any public or private entity providing air navigation services for general air traffic. |
| This role is recognised in the SESAR Deployment Programme as a service consumer of the aerodrome and en-route services. The real-time aspects will have an impact on the service architecture. |
| MILITARY_AIR_NAVIGATION_SERVICE_PROVIDER | Any public or private entity providing air navigation services for military air traffic. |
| This role is recognised in the SESAR Deployment Programme as a service consumer of the aerodrome and en-route services. Although the military is not obliged to use SWIM, they currently rely on civil weather information and therefore it will be essential for their operations to use SWIM-services. |
| AIR_TRAFFIC_SERVICE_PROVIDER | A generic term meaning variously, flight information service, alerting service, air traffic advisory service, air traffic control service (area control service, approach control service or aerodrome control service). |
| This role is recognised in the SESAR Deployment Programme as a service consumer of the aerodrome and en-route services under the term of ANSP. |
| REGULATED_METEOROLOGICAL_SERVICE_PROVIDER | An office designated to provide meteorological service for international air navigation. |
| This role is not recognised by the SESAR Deployment Program as a service consumer. However, it is recognised in ATM Master Plan (https://atmmasterplan.eu/data/enablers/20417016.) Moreover, looking at the EU Reg. 2017/373, a MET Service Provider has to support stakeholders and for that MET-data is needed from other MET-providers. Also such MET-data is needed for their own purpose to evaluate the correctness of forecasts. |
| AERONAUTICAL_INFORMATION_SERVICE_PROVIDER | A service established within the defined area of coverage responsible for the provision of aeronautical information/data necessary for the safety, regularity and efficiency of air navigation. |
| |
| A provider of CNS services. |
| Some equipment e.g. ground radar at airports have to be shut down if the wind rises above a certain windspeed threshold to avoid damage | |
| PROVIDER_OF_DATA_SERVICES | A public or private entity responsible for the management of a Data Service Provision (e.g. to one or several Virtual Centre). |
| |
| NETWORK_MANAGER | The organization responsible for enabling the optimum use of airspace and ensure that Airspace Users can operate preferred trajectories while allowing maximum access to airspaces and air navigation services. |
| |
| AIRPORT_OPERATOR | The civilian or military agency, group or individual which exercises control over the operations of the civil airport or military airfield. |
| This role is recognised in the SESAR Deployment Programme as a service consumer of the aerodrome services. |
| AIRSIDE_GROUND_HANDLER | A stakeholder involved in the services necessary for an aircraft's arrival at, and departure from, an airport, other than air traffic services. |
| |
| MILITARY_DEFENCE_CENTRE | A military defence centre. Note: these centres, e.g., check for diplomatic clearance. |
|