Reference · built on requestCommons signalAir, water & environment

National Water Prediction Service API

River gauge observations, stage and flow forecasts, flood categories, and reach streamflow from NOAA's National Water Prediction Service.

About

The National Water Prediction Service (NWPS) is the National Weather Service's river forecasting application, run by the National Water Center. Its API, version 1.0.0 at api.water.noaa.gov/nwps/v1, serves what the application shows: stream observations, NWS streamflow forecasts issued by the River Forecast Centers, National Water Model streamflow for stream reaches, flood category thresholds, crest history, flood impacts, low water history, and gauge metadata. A gauge is addressed by its NWS location id or its USGS id, such as ANAW1 or 13334300, and each record carries the forecast office, River Forecast Center, county, time zone, and the units it reports in. The service holds no history other than crests and low water.

Through Fibric, an operator watches the gauges that matter to your sites and proposes what to do before a forecast crest arrives.

This is a reference listing. It documents what Fibric would read from National Water Prediction Service API 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

  • Gauge lists by bounding box from /nwps/v1/gauges, and a gauge's metadata, flood categories, and status from /nwps/v1/gauges/{identifier}
  • Observed and forecast stage and flow from /nwps/v1/gauges/{identifier}/stageflow, as separate observed and forecast products with issuedTime
  • Flood category thresholds for action, minor, moderate, and major in stage and flow, plus historic and recent crests
  • Stage-to-flow ratings from /nwps/v1/gauges/{identifier}/ratings, and upstream and downstream gauges from /riverflow
  • Reach metadata and National Water Model streamflow from /nwps/v1/reaches/{reachId}/streamflow, by series such as short_range and medium_range
  • Flood impact statements paired to stages, and low water history, on the gauge record

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

  • Prepare sites ahead of a forecast crest

    When a forecast puts a gauge at minor flood or higher, the operator matches it to the properties you mapped to that gauge and proposes the prep checklist, with the forecast issue time on the proposal.

    With Storm Prep

  • Hold shipments through a flooded route

    Routes are tied to gauges. A forecast that crosses the action stage proposes a hold or reroute on the affected stops before dispatch, for your approval.

    With Weather Hold

  • Draft the evacuation roster

    A forecast at moderate or major flood for a gauge tied to a site proposes the roster for that site and refreshes it when the forecast is reissued.

    With Evacuation Roster

  • Send a rising-water notice

    The operator drafts a notice from the observed stage, the forecast crest, and the flood impact statement for that stage, ready to send to the sites downstream.

    With Severe Weather Notice

Requirements

  • The NWS location ids or USGS ids of the gauges near your sites, routes, or intakes
  • Your own stage or flow thresholds per site, since flood categories describe the gauge, not your building
  • A client that reads UTC timestamps and the per-gauge time zone the API returns
  • For ungauged streams, the National Water Model reach id, such as 23021904, from the reach endpoints
Authentication
None is required. The Swagger spec defines a BasicAuth scheme, but no operation demands it and the endpoints answer plain HTTPS requests.

Limits

  • No historical archive beyond crest and low water history; observations and forecasts cover the current window only
  • Flood categories and forecasts exist only where the NWS issues them; some gauges carry observations without a forecast
  • The companion HEFS and NWM APIs are marked experimental, not supported around the clock, and may change without notice
  • Ratings return up to 10,000 records per call by default, sorted by stage

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 National Water Prediction Service API ↗

Questions and answers

What identifies a gauge?
Either the NWS location id or the USGS site id; the spec's example is ANAW1 or 13334300. The gauge record also carries the National Water Model reach id, the forecast office, the River Forecast Center, state, county, and local time zone.
How are flood categories expressed?
As four thresholds on each gauge: action, minor, moderate, and major, each with a stage value and, where defined, a flow value in the gauge's units. Observed and forecast status report the current category, such as no_flooding, with a validTime.
Does the API cover streams without a gauge?
Partly. The reaches endpoints return National Water Model streamflow for a reach id, by series such as analysis_assimilation, short_range, medium_range, medium_range_blend, and long_range. NOAA states the NWM provides guidance and is not an NWS forecast product.
Ask about National Water Prediction Service API

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.