Reference · built on requestCommons signalAir, water & environment

PEGELONLINE

Raw water levels and discharge from gauges on Germany's federal waterways, with 30 days of history, from the WSV REST API.

Request accessPricing ↗

About

PEGELONLINE is the gauge data service of the Wasserstraßen- und Schifffahrtsverwaltung des Bundes (WSV), the German federal waterways and shipping administration. It publishes raw hydrological readings from inland and coastal gauges along the federal waterways: water level, discharge, and related series, unchecked and as measured. The REST API serves station metadata, the current reading, and 30 days of history as JSON, CSV, or a PNG hydrograph, with no key.

Through Fibric, an operator reads the gauges on the stretch your freight or your site depends on, compares each reading with the low-water and high-water states the API reports, and proposes a hold, a reroute, or a notice for your approval, with the gauge reading on file.

This is a reference listing. It documents what Fibric would read from PEGELONLINE and what it could propose, based on the publisher's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Stations from stations.json: uuid, number, shortname, longname, river kilometre, agency, coordinates, and water body, filterable with waters=RHEIN,MAIN
  • Timeseries per station with shortname, longname, unit, equidistance in minutes, and gaugeZero, listed with includeTimeseries=true
  • The current reading from currentmeasurement.json: timestamp, value, and the stateMnwMhw and stateNswHsw classifications against low and high water
  • Measurements for the last 30 days from measurements.json or .csv, with start as an ISO 8601 duration such as P15D or a timestamp
  • Forecast timeseries where a gauge carries one, requested with hasTimeseries=WV and includeForecastTimeseries=true
  • A rendered hydrograph as measurements.png for embedding, and the same gauges over WMS, WFS, SOS 2.0, and an MQTT broker

Proposed actions

Read-only. This feed informs operators; it changes nothing.

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Hold barge freight when the Rhine runs low

    The operator polls the W series at the gauges on your inbound route, reads each value with its stateMnwMhw flag, and proposes a delay notice or a revised promise date for your approval when a gauge reports low water.

    With Inbound Delay, Promise Date

  • Warn a riverside site before high water

    When a gauge near your building reports a high-water state or a rising forecast series, the operator drafts the notice and the preparation checklist. You approve it; the gauge reading and its timestamp stay on the record.

    With Storm Prep, Severe Weather Notice

  • Attach the gauge record to a delay claim

    Low water restricts barge loads. The operator collects the readings for the affected stretch while they are still inside the 30-day window and attaches them to the carrier exception or the detention claim you file.

    With Carrier Exception, Detention Claim

Requirements

  • The station uuid or shortname of each gauge you follow, taken from stations.json
  • The timeseries shortname you need, such as W for water level or Q for discharge
  • A polling schedule inside the 30-day window, since older readings leave the API
  • Acceptance that the readings are unchecked raw data, as the WSV states in its terms
Authentication
No key. The REST API answers plain HTTPS GET requests and supports client caching through the Cache-Control, Expires, and ETag headers.

Limits

  • The API keeps 30 days of history; a longer series must be collected as it passes or sourced elsewhere
  • The WSV publishes unchecked raw data and gives no warranty on correctness, currency, or completeness
  • Forecast timeseries exist only for the gauges that carry a WV series
  • The scope is gauges along the federal waterways; a river outside that network has no gauge here

Access and pricing

Reference listing. Public feed access is separate from Fibric integration. If you request this feed, your quote covers the build, usage, and support.

Request PEGELONLINE ↗

Questions and answers

Do I need an API key for PEGELONLINE?
No. The REST API at pegelonline.wsv.de/webservices/rest-api/v2/ answers GET requests without registration. Data is released under DL-DE->Zero-2.0. The WSV asks you to treat the readings as unchecked raw data and offers no warranty on them.
How far back can I read measurements?
30 days. measurements.json takes a start parameter as an ISO 8601 duration such as P15D or as a timestamp and returns the readings inside that window. Older readings are not served by the REST API; keep your own copy if you need a longer series.
Which values come with a reading?
A timestamp and a value in the unit of the timeseries, cm for W and m³/s for Q. Water-level readings also carry stateMnwMhw and stateNswHsw, which classify the value against the gauge's low-water and high-water marks, and the station lists a gaugeZero with its reference datum.
Ask about PEGELONLINE

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This Commons signal listing is developed, published, and supported by Fibric. It reads public data published by Wasserstraßen- und Schifffahrtsverwaltung des Bundes, WSV (pegelonline.wsv.de). Upstream agencies and projects are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy