This field is left empty.

categories/CodeStakeholderType.html

intended service provider

REGULATED_METEOROLOGICAL_SERVICE_PROVIDER

• METEOROLOGICAL_FEATURE_ACCESS_SERVICE
• METEOROLOGICAL_INFORMATION_SUBSCRIPTION_SERVICE

http://reference.swim.aero/information-services/service-categories/CodeServiceType.html 

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.

The service provides high quality, up-to-date, trusted, regulated meteorological information in digital form for use by service consumers within the aviation domain.

The service takes into account the following information exchange requirement that may be implemented in some service instances.

The service consumer is subscribed to the observed aerodrome meteorological information or has managed the subscription as requestedsubscribes to the service and will receive METAR/SPECIs as per the subscription or unsubscribes from the service.

The service shall distribute the METAR/SPECIs when they are available.

The service consumer

receives the METAR/SPECIs.

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.

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.requirement SWIM-TIYP-0042.

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 certificaterequirement SWIM-TIYP-0042.

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.

The service shall achieve a quality that is sufficient to ensure the service is fit for purpose.

The service shall ensure confidentiality by using SWIM Technical Infrastructure (TI) Yellow Profile bindings.

The meteorological information offered by the service shall be verified by the service provider.

The meteorological information offered by the service shall satisfy the quality requirements expressed in ICAO Annex 3be 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.Note: In the case of misalignment, the Commission Implementing Regulation (EU) 2017/373 takes precedenceof Observation.

The service provider shall ensure that the meteorological data offered by the services isreceived from the appropriate authorised originating sources. This includes:

• REGULATED_METEOROLOGICAL_SERVICE_PROVIDER acting as the designated Aeronautical Meteorological Station (AMS); and
• REGULATED_METEOROLOGICAL_SERVICE_PROVIDER acting as the designated Aerodrome Meteorological Office (AMO) for the TREND.

• PUBLISH_SUBSCRIBE
• SYNCHRONOUS_REQUEST_REPLY

The service behaviour shall be in accordance with the patterns detailed in the Message Exchange Patterns: Identification Guidelines.

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 subscription is handled by either:
  • a request-reply implementation (see Meteorological Aerodrome Observation IWXXM METAR-SPECISubscription and Request Service Subscription Interface) or
  • an email request to the service provider.
•  The distribution of the messages is handled by an AMQP 1.0 implementation (see Meteorological Aerodrome Observation Subscription IWXXM METAR-SPECI Subscription and Request Service Distribution Interface).

• service

• The service consumer remains blocked while awaiting the reply
• The service remains blocked while processing the reply
• The METAR-SPECI, the reply message, is sent from the service to the service consumer.

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.

Allows the service consumer to select and subscribe to meteorological information 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.

EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile

1.1

• for services that exchange the meteorological information as resources:
  • OGC API – Environmental Data Retrieval Standard;
  for services that exchange the meteorological information as coverages:
  • OGC Web Coverage Service (WCS) Interface Standard – Core, version 2.1;
  • OGC API - Coverages;
• for services that exchange the meteorological information as features:
  • OGC Web Feature Service 2.0 Interface Standard;
  • OGC API – Features.

Note: It it is a best practice for new services that exchange meteorological information to implement the OGC API – Environmental Data Retrieval Standard.

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.

EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile

1.1

WS_LIGHT

EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile

1.1

AMQP 1.0 shall be used to distribute messages as explained in the Publish/Subscribe Push MEP: Implementation Guidance.

GetFeature

Request, METAR/SPECI Message

The standard operations for subscription and subscription management.

The following operations shall be implement at a minimum:

• subscribe
• unsubscribe

publish

This operation allows the service provider to publish Meteorological Aerodrome Observation Message publish METAR-SPECI report(s) to service consumers based on their subscriptions.

METAR/SPECIMessage

METAR/SPECI Message

The output message containing the observed meteorological aerodrome The message that is an output of the service, containing the METAR/SPECI information.

The METAR/SPECI information shall be provided in ICAO’s Meteorological Information Exchange Model (IWXXM) format containing a collection of features.

The service shall offer meteorological information available in accordance with Appendix B.

The METAR/SPECI (IWXXM) Information Service Request Interface shall support the During temporal operator defined in the OGC Filter Encoding 2.0 Encoding Standard.

The METAR/SPECI (IWXXM) Information Service Request Interface shall support filtering based on the name and ICAO location indicator of the aerodrome of interest..

The METAR/SPECI (IWXXM) Information Service Request Interface should support filtering based on the operators defined in the OGC Filter Encoding 2.0 Encoding Standard.

The METAR/SPECI (IWXXM) InformationICAO 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.

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 on a case by case basis. Example: other filters defined based on the operators defined in the OGC Filter Encoding 2.0 Encoding Standard on a case by case basis are probability and severity threshold.

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.

WFS offers direct fine-grained access to geographic information at the feature and feature property level. 

• https://www.ogc.org/standard

• /ogcapi-edr/
• https://docs.ogc.org/is/19-086r6/19-086r6.html 

WFS offers direct fine-grained access to geographic information at the feature and feature property level. 

Note: This is   equivalent to ISO 19143 19142 - Geographic Information - Filter encodingWeb Feature Service.

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.

• Generate graphical representations of data in support of responsibilities.
• Retrieve dynamic data to support digital integrated briefing concepts.
• Ensure safe operations by responding to changes in the situation.
• Require information on unique weather constraints such as fog, snow, convection etc., or on particular operational constraints such as runway throughput, winter procedures, noise abatement procedures, free routing, etc.

• Generate graphical representations of data in support of responsibilities.
• Retrieve dynamic data to support digital integrated briefing concepts.
• Ensure safe operations by responding to changes in the situation.
• Require information on unique weather constraints such as fog, snow, convection etc., or on particular operational constraints such as runway throughput, winter procedures, noise abatement procedures, free routing, etc.

• Ensure safe operations by responding to changes in the conditions of the airspace infrastructure.
• Support real-time displays in, for example, remote towers.
• Require information on unique weather constraints such as fog, snow, convection etc., or on particular operational constraints such as runway throughput, winter procedures, noise abatement procedures, free routing, etc.

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.

• Ensure safe operations by responding to changes in the conditions of the airspace infrastructure.
• Require information on unique weather constraints such as fog, snow, convection etc., or on particular operational constraints such as runway throughput, winter procedures, noise abatement procedures, free routing, etc.

• Support situational awareness of APP and TWR units due to provision of current weather information

• MET providers shall have the possibility and ability to consume needed information to perform their tasks e.g. flight briefing or to update their forecast products based on the latest weather information

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.

• Not applicable

• CNS service providers shall have the possibility and ability to receive current wind information, especially during timeframes strong winds are forecasted.

• In case a provider of data services also offers/handles MET data, the provider shall have the possibility and ability to receive the data needed

• Not applicable

• Support airport-CDM.
• Support aerodrome processes including low visibility operations, aerodrome warnings and runway configuration management.

• Provide information to ground handlers especially in regard to hazardous weather which might affect their operations (thunderstorms, freezing rain,..)

A military defence centre.

Note: these centres, e.g., check for diplomatic clearance.

• Not applicable