Skip to main content

Flood-stage alert (Meter list), Official data

A gauge on a federal waterway that reaches the flood mark where shipping is restricted, or the mark where it is stopped, with its level against the marks. Data from the Waterways and Shipping Administration's PEGELONLINE.

Feed idfd_85374dfe3724
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 dataFlood-stage alert (Meter list), Live data
Sourceriver-gauges-and-flood-levels
MarketsPublic bodies, Real estate
ScheduleChecked every half hour; posts when a gauge reaches a flood mark, once a day per gauge and mark
TemplateMeter list, in whichever of its 13 visual variants a channel chooses when it adds the feed
Shapes9x16, 4x5, 1x1, 16x9, 2x3
LanguagesEnglish, 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 Clear civic 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.
  • New listings and price changes, posted the day they go live, with the property's key facts.
  • Mortgage rates and market figures for the area, as a weekly story agents post under their own brand.
  • Viewing days and open houses, counted down on every channel the agency runs.

What it carries​

This feed carries what its template takes: the fields, what each may hold and a worked example are on the Meter list 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_85374dfe3724"

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_85374dfe3724",
  "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.