CONSUMER_SIDE

Allows the service provider to distribute notifications when a new significant ash cloud occurs meeting the need of the service consumer that has subscribed for updates.

Operations

The AMQP_MESSAGING Interface Binding as detailed in the EUROCONTROL Specification for SWIM Technical Infrastructure Yellow Profile, edition 1.1

The service shall use the network bindings of the SWIM TIYP. AMQP 1.0 shall be used to distribute messages as explained in the Publish/Subscribe Push MEP: Implementation Guidance.

Description

The notification and way to retrieve the Quantitative Volcanic Ash Information Message e.g. the URL, or the volcano number. The message will include:
- publication time
- operation e.g. if it is an update or a new message
The message can include:
- identifier of the VAAC
- event type e.g. if it is live
Note: an example of the structure of the URL that is used to retrieve the QVA in IWXXM format using an EDR implementation: https://{organizaton URL}/QVACI_Iwxxm/Locations/{VolcanoNumber} Note: the URL, if provided, could be a request formatted for the Quantitative Volcanic Ash Information Subscription and Request Service Request Interface.

Interface Provision Side

Allows the service provider to distribute notifications when a new significant ash cloud occurs meeting the need of the service consumer that has subscribed for updates.

Operations

The AMQP_MESSAGING Interface Binding as detailed in the EUROCONTROL Specification for SWIM Technical Infrastructure Yellow Profile, edition 1.1

The service shall use the network bindings of the SWIM TIYP. AMQP 1.0 shall be used to distribute messages as explained in the Publish/Subscribe Push MEP: Implementation Guidance.

Description

The notification and way to retrieve the Quantitative Volcanic Ash Information Message e.g. the URL, or the volcano number. The message will include:
- publication time
- operation e.g. if it is an update or a new message
The message can include:
- identifier of the VAAC
- event type e.g. if it is live
Note: an example of the structure of the URL that is used to retrieve the QVA in IWXXM format using an EDR implementation: https://{organizaton URL}/QVACI_Iwxxm/Locations/{VolcanoNumber} Note: the URL, if provided, could be a request formatted for the Quantitative Volcanic Ash Information Subscription and Request Service Request Interface.

Interface Provision Side

Allows the service provider to distribute notifications when a new significant ash cloud occurs meeting the need of the service consumer that has subscribed for updates.

Operations

The AMQP_MESSAGING Interface Binding as detailed in the EUROCONTROL Specification for SWIM Technical Infrastructure Yellow Profile, edition 1.1

The service shall use the network bindings of the SWIM TIYP. AMQP 1.0 shall be used to distribute messages as explained in the Publish/Subscribe Push MEP: Implementation Guidance.

Description

The notification and way to retrieve the Quantitative Volcanic Ash Information Message e.g. the URL, or the volcano number. The message will include:
- publication time
- operation e.g. if it is an update or a new message
The message can include:
- identifier of the VAAC
- event type e.g. if it is live
Note: an example of the structure of the URL that is used to retrieve the QVA in IWXXM format using an EDR implementation: https://{organizaton URL}/QVACI_Iwxxm/Locations/{VolcanoNumber} Note: the URL, if provided, could be a request formatted for the Quantitative Volcanic Ash Information Subscription and Request Service Request Interface.

Interface Provision Side

Allows the service provider to distribute SIGMETs meeting the need of the service consumer that has subscribed for updates.

Operations

This operation allows the service provider to publish SIGMETs to service consumers based on their subscriptions.

Idempotent
IDEMPOTENT
Operation Message

The AMQP_MESSAGING Interface Binding as detailed in the EUROCONTROL Specification for SWIM Technical Infrastructure Yellow Profile, edition 1.1

The service shall use the network bindings of the SWIM TIYP. AMQP 1.0 shall be used to distribute messages as explained in the Publish/Subscribe Push MEP: Implementation Guidance.

Description

The message that is an output of the service, containing the SIGMET.

Interface Provision Side

Allows the service provider to distribute the latest available METAR/SPECIs meeting the need of the service consumer that has subscribed for updates.

Operations

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

Idempotent
IDEMPOTENT
Operation Message

The AMQP_MESSAGING Interface Binding as detailed in the EUROCONTROL Specification for SWIM Technical Infrastructure Yellow Profile, edition 1.1

Description

The message that is an output of the service, containing the METAR/SPECI information

Interface Provision Side

Allows the service provider to distribute the latest available TAFs meeting the need of the service consumer that has subscribed for updates.

Operations

This operation allows the service provider to publish Meteorological Aerodrome Forecast Message to service consumers based on their subscriptions.

Operation Message

The AMQP_MESSAGING Interface Binding as detailed in the EUROCONTROL Specification for SWIM Technical Infrastructure Yellow Profile, edition 1.1.

The service shall use the network bindings of the SWIM TIYP. AMQP 1.0 shall be used to distribute messages as explained in the Publish/Subscribe Push MEP: Implementation Guidance.

Description

The message that is an output of the service, containing the TAF information.

Interface Provision Side

Allows the service provider to publish Pan European Convection information notification to service consumers based on their subscription.

Operations

This operation allows the service provider to publish Pan European XML Convection information notification to service consumers based on their subscriptions.

Idempotent
IDEMPOTENT
Operation Message
Interface Provision Side
TI Primitive Message Exchange Pattern

The complete API description is available on MetSafe user portal accessible through a Token.  An access Token can be requested at [email protected].

Operations

Retrieve objects in GeoJSON inside a 4D Bounding Box.

Idempotent
NON_IDEMPOTENT
Synchronous
SYNCHRONOUS
TI Protocol Methods
Yellow Profile
Operation Message
Processing Consideration
Behaviour
Interface Binding Description

OGC:WFS2.0.0

WFS documentation can be found at:
https://docs.geoserver.org/latest/en/user/services/wfs/index.html

Interface Provision Side
TI Primitive Message Exchange Pattern
Service Interface Binding
Network Interface Binding

The ADT DNES is compliant to the Open Geospatial Consortium (OGC) Web Feature Service Temporality Extension (WFS-TE) specification, OGC 12-027r3 and the corresponding Web Feature Service (WFS) version 2.0.0 specification. For a machine- and human-readable interface description, please refer to the GetCapabilities.

Operations

A detailed description of supported operations is provided in the machine-readable WFSS capabilities document.

Idempotent
NON_IDEMPOTENT
Synchronous
ASYNCHRONOUS
Behaviour
Interface Binding Description

Both HTTP GET requests with key-value pairs as query parameters and HTTP POST requests with XML encoding of the requests, following the provisions in the WFS specification are supported.

Interface Provision Side
TI Primitive Message Exchange Pattern
Service Interface Binding
Network Interface Binding

The complete API description is available on MetSafe user portal accessible through a Token.  An access Token can be requested at [email protected].

Operations
Behaviour
Interface Binding Description

OGC:WFS2.0.0

WFS documentation can be found at:
https://docs.geoserver.org/latest/en/user/services/wfs/index.html

Interface Provision Side
TI Primitive Message Exchange Pattern
Service Interface Binding
Network Interface Binding