Surface Water Data Portal
Readings as of July 28, 2026 at 4:53 PM PT ยท not current conditions
Data and sources
This site holds 119 stream gauges, 48 rain gauges, 10 reservoirs and 146 named places. Each one is a reading from a named source with a capture time, or it is not on the site.
These counts come from the same snapshot as every page and every download below.
Every reading on these pages was captured once, on July 28, 2026 at 4:53 PM PT, from Valley Water's own public sensor feed. Nothing here updates on its own, so do not read these numbers as current conditions.
The capture time in the masthead is the age of the reading. In a storm that is the number to check first: a stage in feet means very little without knowing when it was measured.
These are the files this site is rendered from, not a curated extract of them. If a number on a page disagrees with these, the page is wrong.
gauges.json 82 KB
All 119 stream gauges with position, current stage and flow, the USGS cross reference where Valley Water publishes one, and every numbered threshold with the district's own description of what floods at it.
storm-february-2017.json 319 KB
The February 2017 window: every station requested, the two that hold a record, the six that do not and the dates that prove why, both peak readings, and every peak-to-peak interval with a note saying whether this site is willing to quote it as a travel time.
Both files are plain JSON, served from this site, no key and no rate limit.
Stage, flow, storage, rainfall, watershed assignment, forecast and flood watch flags, and the numbered thresholds with their written descriptions. The threshold prose that the street index is built from exists nowhere else.
Instantaneous 15-minute discharge and stage, the daily record as a fallback, and the site service that publishes when each station's record begins and ends. That last one is what lets this site prove a gap rather than assert one.
Action, minor, moderate and major flood stages per gauge, and the written impact library naming what goes under at each stage. 145 gauges in this county, 39 of them carrying at least one real threshold.
The California Data Exchange Center is the usual source for reservoir storage, and its robots file disallows every bot on the site, so nothing here is taken from it. api.weather.gov is the same. Where that leaves a gap, the gap is named on the page instead of being filled from somewhere else.
A data portal that does not separate these two is asking to be trusted rather than checked. Everything in the left column is a number a sensor reported. Everything in the right column is arithmetic this site did on those numbers, and the arithmetic is stated.
| Field | Reported or computed | How |
|---|---|---|
| Stage, flow, storage, rainfall | Reported | Valley Water's sensor feed, with the sensor's own timestamp. |
| Flood thresholds and their descriptions | Reported | Valley Water, quoted verbatim and marked as quoted. |
| Headroom below threshold 1 | Computed | Threshold stage minus current stage. Shown only when both exist. |
| Downstream order on a creek | Computed | Sorted on real latitude, per watershed, using a declared drainage direction. South county drains toward Monterey Bay, so its sign is flipped. |
| Reservoir percent full | Computed | Reported storage against Valley Water's published capacity. Anderson's published capacity is 89,073 acre-feet and its storage is restricted under a federal seismic order, which is why the percentage is low rather than wrong. |
| Storm peaks | Computed | The highest reading in the window, carrying that reading's own timestamp. |
| Peak-to-peak intervals | Computed | Timestamp subtraction between two peaks, quoted as a travel time only inside a single storm pulse. |
| Street and landmark matches | Extracted | Candidate place names pulled out of Valley Water's threshold prose. Never resolved, never inferred: the agency's whole sentence is always shown beside the match. |
When a sensor or an agency's feed has nothing for a period, that period appears here as a labeled hole with its dates, next to the reading it belongs beside. Nothing is estimated to fill it and no row is quietly dropped.
Readings come from each agency's own published interface. Where an agency does not permit automated access, its data is absent here and says so, rather than arriving from somewhere less reliable.