Skip to main content

Rhine water levels (Journey line), Official data

Eight Rhine gauges from Maxau to Emmerich, Kaub among them, with the change over 24 hours. In German for German channels.

Feed idfd_fb8104ebd9f5
TypeOfficial data, no AI: Straight from the authority or licensed provider that publishes the data, or worked out by code (moon phase, calendar). Wording and languages fixed in code. No AI at any step.
PlansEnterprise
Also as Live dataRhine water levels (Journey line), Live data
Sourceriver-gauges-and-flood-levels
MarketsPublic bodies
ScheduleDaily 06:30
TemplateJourney line, in whichever of its 11 visual variants a channel chooses when it adds the feed
Shapes9x16, 4x5, 1x1, 16x9, 2x3
LanguagesGerman, each written by the feed's own code, never by AI
FreshnessAn event older than 24 hours is kept but never published

Example video​

The 1x1 cut of this feed's example, drawn in the Broadcast news variant with an example brand. A channel draws it in the variant it chose and in its own brand. Open the video on its own.

Use cases​

  • Council and authority announcements, the moment they are published.
  • Dates people plan around: waste collection, opening hours, public events.
  • Open data made visible: air quality, water levels, traffic or budget figures.

What it carries​

This feed carries what its template takes: the fields, what each may hold and a worked example are on the Journey line page, the same for every feed drawn with it. A picture is always a file from your media library: media:// followed by its id or its name. Anything the template does not list is refused, and so is anything over its limit, with a 400 schema_validation error that names the field.

Ask Reelwire for the whole JSON Schema, the document this feed is checked against, without signing in:

curl "https://app.reelwire.io/v1/formats/feed/fd_fb8104ebd9f5"

Which template draws a feed is Reelwire's decision and can change, so a producer asks by the feed, as above, rather than by its template.

Delivery JSON​

Every event of this feed is delivered to Reelwire in this envelope. You do not send it yourself: add the feed to a channel under Ready-made feeds, and each event becomes a post on that channel. data is the document described above, left empty here: the template's delivery JSON shows one filled in.

{
  "eventId": "01M2SQMKK3G1NVFXV31DCBVB95",
  "occurredAt": "2026-09-23T07:00:00Z",
  "feedId": "fd_fb8104ebd9f5",
  "locale": "en",
  "data": {}
}

feedId names this feed and never changes, even when the feed is renamed. eventId is set once per event, so an event delivered twice is published once. occurredAt is when it happened, which is what the freshness limit is measured from.