Getting Started¶
DWD offers different options to access meteorological data via SWIM Services. Currently, we mainly offer AMQP 1.0 based services, specifically providing IWXXM data. An account is necessary to access the services. Please reach out to vl.kundenservice@dwd.de to start the registration process.
For connecting to the AMQP services two options are offered: using a standard "public" subscription or creating a custom subscription. Please let us know during the registration process which option you would like to use. We recommend using the standard subscription but please find the feature comparison below to help you decide which option fits your use case best.
Feature Matrix¶
| Feature | Option 1: Public Subscription | Option 2: Custom Subscription |
|---|---|---|
| Header based server-side filtering | ||
| Retrieve older Messages | ||
| Retrieve only new Messages after connection | ||
| Messages with higher priority are delivered earlier | ||
| Messages are removed when the TTL has expired | ||
| Multiple Services, Technical Messages and Heartbeats in one Subscription | ||
| Notifications about missed messages |
Option 1: Using the Standard "public" Subscription¶
The standard "public" subscription (public in this case means that every registered customer can access these subscriptions) allows you to connect to predefined queues for each data type. You can find a list of available services and their corresponding queue names in the List of Services.
You can directly connect to these queues without any prior setup. All the messages are uniquely pushed to each connected receiver. However, note that only messages published after you created your AMQP receiver will be received. If you disconnect from the service and reconnect later, you will only receive messages published after your reconnection, but there is a way to retrieve past messages using offset tracking.
Additionally, this is the only option if you want to use header-based server-side filtering to reduce the number of messages sent to your receiver. Please refer to Rabbitmq's AMQP 1.0 Filter Expressions or SQL Filtering documentation for more information on how to use filtering.
To get started with this option, please refer to the connecting to AMQP services tutorial which guides you through connecting to the AMQP service and receiving your first messages.
Option 2: Using a Custom Subscription¶
This type of subscription is dedicated for customers wanting to use additional features for their subscriptions. The custom subscription is unique per user and keeps all messages sent to those subscriptions until they are consumed or the message TTL expires. If the message TTL expires, messages are removed from the subscription and an expired message may be sent to notify the user (this feature is optional and can be discussed during the subscription request).
This type of subscription also allows prioritization of messages, meaning that messages with a higher priority are delivered earlier.
Additionally, it's possible to combine multiple services, technical messages and heartbeats in a single subscription. This reduces the number of connections needed to receive all relevant data.
Please refer to the custom subscription how-to guide for more information on creating and using a custom subscription. The subscription management section provides insights into the lifecycle and operations of custom subscriptions.