<p>The following section describes details how to subscribe and unsubscribe to this service.</p>
<p>At the moment subscribing or unsubscribing to this service is only possible by contacting the DWD Aviation Customer Service. Contact details are found in the general part of the service description.</p>
<p>The interface is used to receive the data which are subscribed to.</p>
<p>The requested information is contained directly in the AMQP message.</p>
<p>This is the connection between the service provider and the customer via AMQP1.0 to receive notification related to the customer's subscription.</p>
The interface is used to receive the data via WFS.
Pleas see the WFS documentation for detailed information<a href="https://docs.geoserver.org/latest/en/user/services/wfs/index.html">http…;
This is the connection between the service provider and the customer via WFS. You need to contact the DWD aviation customer service for getting the credentials to retreive the specific layer which is described in this sevice description.
The Service Interface Binding is SWIM Yellow Profile Compliant, using WS Light enabling HTTP GET requests and associated responses.
The Service implementation conforms with IPV4_SECURE_UNICAST as part of SWIM Yellow Profile requirements.
The interface is used to receive the data via WFS.
Pleas see the WFS documentation for detailed information<a href="https://docs.geoserver.org/latest/en/user/services/wfs/index.html">http…;
This is the connection between the service provider and the customer via WFS. You need to contact the DWD aviation customer service for getting the credentials to retreive the specific layer which is described in this sevice description.
Allows the service consumer to select and subscribe to SIGMETs for airspaces that are 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.
The standard operations for subscription and subscription management. The following operations shall be implement at a minimum:
-subscribe
-unsubscribe.
The WS Light 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 Technical Infrastructure (TI) Yellow Profile.
Allows the service consumer to request the currently valid SIGMETs. Note: This interface is used to group the operations offered by the chosen OGC standard.
Explanatory note: 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.The GetFeature operation returns a selection of features from a data store. It responds to a GetFeature Request message with a En-route Significant Weather Information Message that satisfies the query expressions specified in the request.
The WS Light 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. The interface shall use at least one of the following OGC standards:
- for services that exchange the meteorological information as resources:
- OGC API - Environmental Data Retrieval Standard;
- for services that exchange the meteorological information as features:
- OGC Web Feature Service 2.0 Interface Standard;
- OGC API - Features. 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.
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.
The standard operations for subscription and subscription management. The following operations shall be implement at a minimum:
- subscribe
-unsubscribe
The WS Light 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 Technical Infrastructure (TI) Yellow Profile.
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.
Explanatory note: 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.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.
The WS Light 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. The interface shall use at least one of the following OGC standards:
- for services that exchange the meteorological information as resources:
- OGC API - Environmental Data Retrieval Standard;
- for services that exchange the meteorological information as features:
- OGC Web Feature Service 2.0 Interface Standard;
- OGC API - Features.
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.
The message that is an output of the service, containing the METAR/SPECI information
Request message submitted to the service containing query expressions for the WFS GetFeature operation or the EDR HTTP GET operation.
Allows the service consumer to select and subscribe to TAFs 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.
The standard operations for subscription and subscription management. The following operations shall be implement at a minimum: subscribe, unsubscribe
The WS Light 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 Technical Infrastructure (TI) Yellow Profile.
Allows the service consumer to request the latest available TAFs. Note: This interface is used to group the operations offered by the chosen OGC standard.
Explanatory note: 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. The GetFeature operation returns a selection of features from a data store. It responds to a GetFeature Request message with a Meteorological Aerodrome Forecast Message that satisfies the query expressions specified in the request.
The WS Light 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. The interface shall use at least one of the following OGC standards:
- for services that exchange the meteorological information as resources:
- OGC API - Environmental Data Retrieval Standard;
- for services that exchange the meteorological information as features:
- OGC Web Feature Service 2.0 Interface Standard;
- OGC API - Features.
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.