Cucharas River
Bootstrap review report — d2_wd16_cucharas_river
Generated 2026-08-13 22:23 UTC for Division 2 / Water District 16.
This is a review checklist, not a finished config. Everything below is a suggestion from live DWR data — confirm or correct each section in config.yaml before running this basin for real.
1. Stream-name patterns
Assumed mainstem pattern: CUCHARAS RIVER (highest-count waterSource value). Candidates below by structure count — decide which are real tributaries worth their own centerline vs. noise, and add them to longitudinal.tributary_stream_patterns in priority order (more-specific names, e.g. "WEST FORK X", must precede substrings of themselves, e.g. "X").
| waterSource | structure count |
|---|---|
| CUCHARAS RIVER (assumed mainstem) | 100 |
| WAHATOYA CREEK | 21 |
| SANTA CLARA CREEK | 17 |
| MIDDLE CREEK | 12 |
| SOUTH ABEYTA CREEK | 12 |
| BEAR CREEK | 10 |
| INDIAN CREEK | 9 |
| ECHO CREEK | 8 |
| SCHOOL CREEK | 7 |
| STORY CREEK | 5 |
| STAPLIN CREEK | 4 |
| DEER CREEK | 4 |
| NORTH ABEYTA CREEK | 4 |
| WHITE CREEK | 3 |
| BONNETT CREEK | 3 |
| SOUTH FORK CUCHARAS RIVER | 3 |
2. Diversion / return classification
Auto-classified from structureType + name patterns: 203 diversions, 6 returns, 64 unclassified (neither pattern matched — these render as neither on the schematic unless added to return_flow_wdids/force_diversion_wdids or a type is added to the diversion/return type lists).
This layer needs the least manual work — it's the same heuristic the engine uses at runtime. Spot-check a sample rather than reviewing every row; if you have a water-year accounting spreadsheet for this basin, cross-reference it against the 'other' bucket specifically (that's where a real augmentation return with an unusual DWR structureType will hide).
2b. Cross-checked against decreed water rights (CDSS)
42 structure(s) have a decreed water right (CDSS waterrights/netamount) that disagrees with the structureType/name-pattern classification above. Same-agency evidence (DWR/HydroBase), not independent of DWR the way the NLDI topology check is — worth a glance, not an automatic correction.
| wdid | structure | currently | decreed uses suggest | decreed uses |
|---|---|---|---|---|
| 1602805 | WALSENBURG 2015 EXCHANGE | other | diversion | Municipal |
| 1602806 | WALSENBURG 2017 EXCHANGE WALSENBURG D | other | diversion | Municipal |
| 1602807 | WALSENBURG 2017 EXCHANGE GOMEZ DITCH | other | diversion | Municipal |
| 1602808 | WALSENBURG 2018 EXCHANGE MARIA STEVENS RES | other | diversion | Municipal |
| 1602809 | WALSENBURG 2018 EXCHANGE WWTF | other | diversion | Municipal |
| 1602810 | WALSENBURG 2018 EXCHANGE GOMEZ DITCH | other | diversion | Municipal |
| 1602811 | WALSENBURG 2018 EXCHANGE WALSENBURG D | other | diversion | Municipal |
| 1602812 | WALSENBURG 2018 EXCHANGE LAKE MIRIAM | other | diversion | Municipal |
| 1602813 | WALSENBURG 2018 EXCHANGE COLER RESERVOIR | other | diversion | Municipal |
| 1602814 | WALSENBURG 2018 EXCHANGE LA VETA TOWN LAKE | other | diversion | Municipal |
| 1602815 | WALSENBURG 2018 EXCHANGE BRUCE CANYON RES | other | diversion | Municipal |
| 1602816 | WALSENBURG 2018 EXCHANGE BAKER CREEK | other | diversion | Municipal |
| 1602817 | WALSENBURG 2018 EXCHANGE WHITE CREEK | other | diversion | Municipal |
| 1602819 | HVE COLER SYSTEM EXCHANGE | other | return | Augmentation |
| 1605000 | NAVAJO RANCH WELL NO 1 | other | diversion | Stock |
| 1605001 | NAVAJO RANCH WELL NO 2 | other | diversion | Domestic, Municipal |
| 1605002 | NAVAJO RANCH WELL NO 3 | other | diversion | Domestic |
| 1605003 | NAVAJO RANCH WELL NO 4 | other | diversion | Domestic |
| 1605004 | NAVAJO RANCH WELL NO 5 | other | diversion | Domestic |
| 1605005 | NAVAJO RANCH WELL NO 6 | other | diversion | Domestic |
| 1605006 | NAVAJO RANCH WELL NO 7 | other | diversion | Domestic |
| 1605007 | NAVAJO RANCH WELL NO 8 | other | diversion | Domestic |
| 1605008 | NAVAJO RANCH WELL NO 9 | other | diversion | Domestic |
| 1605009 | NAVAJO RANCH WELL 12507F | other | diversion | Commercial, Domestic, Irrigation, Municipal |
| 1605010 | CF&I WELL NO 1 16308 | other | diversion | Domestic, Industrial, Irrigation |
| 1605011 | CF&I WELL NO 2 16309 | other | diversion | Domestic, Industrial, Irrigation |
| 1605012 | CF&I WELL NO 3 16310 | other | diversion | Domestic, Industrial, Irrigation |
| 1605013 | CF&I WELL NO 4 16311 | other | diversion | Domestic, Industrial, Irrigation |
| 1605014 | CF&I WELL NO 5 16312 | other | diversion | Domestic, Industrial, Irrigation |
| 1605017 | CF&I WELL NO 9 16316 | other | diversion | Domestic, Industrial, Irrigation |
| 1605018 | CF&I WELL NO 10 16317 | other | diversion | Domestic, Industrial, Irrigation |
| 1605019 | CF&I WELL NO 11 16318 | other | diversion | Domestic, Industrial, Irrigation |
| 1605020 | CF&I WELL NO 12 16319 | other | diversion | Domestic, Industrial, Irrigation |
| 1605022 | CF&I WELL NO 14 16323 | other | diversion | Domestic, Irrigation |
| 1605023 | HVE WELL 1 | other | diversion | Domestic, Fire, Irrigation, Stock |
| 1605024 | HVE WELL 2 | other | diversion | Domestic, Fire, Irrigation, Stock |
| 1605037 | CAPPS WELL 5 (MAX) | other | diversion | Domestic, Irrigation, Stock |
| 1605043 | DISERT WELL NO 2 | other | diversion | Domestic, Irrigation, Stock |
| 1605051 | MALDONADO WELL 12262-F | other | diversion | Commercial, Domestic, Stock |
| 1605052 | MALDONADO WELL NO 1 | other | diversion | Domestic, Industrial, Irrigation, Stock |
| 1605061 | RIO SOUTH WELL NO 2 | other | diversion | Commercial, Industrial, Municipal |
| 1605092 | DISERT WELL NO 3 | other | diversion | Domestic, Irrigation, Stock |
3. Suspected nested tributaries
Still need a human decision — these tributary pairs are comparably close to EACH OTHER as to the mainstem — one may actually join the other rather than the mainstem directly (like Leavenworth Creek -> South Clear Creek in the Clear Creek basin). NLDI couldn't resolve these (no nearby flowline, or ambiguous/no downstream overlap within range) — if you know the real topology, set it in longitudinal.tributary_parent_overrides.
| tributary | possible parent | dist to possible parent (mi) | dist to mainstem (mi) | NLDI result |
|---|---|---|---|---|
| SANTA CLARA CREEK | STORY CREEK | 0.23 | 1.34 | NLDI check failed: 429 Client Error: Too Many Requests for url: https://api.water.usgs.gov/nldi/linked-data/comid/position?f=json&coords=POINT%28-104.861946+37.4484%29 |
| WAHATOYA CREEK | MIDDLE CREEK | 2.78 | 3.7 | NLDI check failed: 429 Client Error: Too Many Requests for url: https://api.water.usgs.gov/nldi/linked-data/comid/position?f=json&coords=POINT%28-105.171036+37.58713%29 |
| STAPLIN CREEK | WAHATOYA CREEK | 0.4 | 1.28 | NLDI check failed: 429 Client Error: Too Many Requests for url: https://api.water.usgs.gov/nldi/linked-data/comid/position?f=json&coords=POINT%28-104.982932+37.427387%29 |
| MIDDLE CREEK | SOUTH ABEYTA CREEK | 0.84 | 1.18 | NLDI check failed: 429 Client Error: Too Many Requests for url: https://api.water.usgs.gov/nldi/linked-data/comid/position?f=json&coords=POINT%28-105.037771+37.511968%29 |
| BEAR CREEK | SANTA CLARA CREEK | 2.16 | 4.64 | NLDI check failed: 429 Client Error: Too Many Requests for url: https://api.water.usgs.gov/nldi/linked-data/comid/position?f=json&coords=POINT%28-104.788617+37.538123%29 |
| SOUTH ABEYTA CREEK | MIDDLE CREEK | 0.38 | 0.78 | NLDI check failed: 429 Client Error: Too Many Requests for url: https://api.water.usgs.gov/nldi/linked-data/comid/position?f=json&coords=POINT%28-105.045689+37.522317%29 |
| STORY CREEK | SANTA CLARA CREEK | 0.4 | 1.96 | NLDI check failed: 429 Client Error: Too Many Requests for url: https://api.water.usgs.gov/nldi/linked-data/comid/position?f=json&coords=POINT%28-104.850562+37.44744%29 |
| DEER CREEK | WAHATOYA CREEK | 0.13 | 1.21 | NLDI check failed: 429 Client Error: Too Many Requests for url: https://api.water.usgs.gov/nldi/linked-data/comid/position?f=json&coords=POINT%28-104.994898+37.478595%29 |
4. Gage placement risk
None — every gage with a resolvable position is within the placement cutoff.
14 more gage(s) pass but are within 2x the cutoff distance — worth a glance if the structure dataset changes later.
Next steps
- Fill in
tributary_stream_patternsfrom section 1. - Resolve section 3's flags (or confirm none apply).
- Resolve section 4's at-risk gages.
- Cross-reference
return_flow_wdids/force_diversion_wdidsagainst any local accounting source you have for this basin. - Review the rendered schematic for this district before relying on it.
Evolution of the network
Computed 2026-08-20 08:38 from 14 gage(s) with cached period-of-record data. Statistical tests (Mann-Kendall trend, Pettitt changepoint) require at least 8 years spanning at least 10 years of record -- gages below that report no signal, not "no change."
Data provenance & quality
Where these numbers come from and how far they can be trusted. Grade C (3/6 points) — the components below are the finding; the letter alone is not. Sources: DWR HydroBase snapshot HydroBase_CO_20260707 (imported 2026-08-19) for history, plus the CDSS REST API for current conditions.
| Check | State | What was measured |
|---|---|---|
| gage freshness | stale | newest gage reading is 45 day(s) old (target 7) |
| diversion record | expected-lag | newest diversion record is 293 day(s) old (DWR publishes ~1 year in arrears) |
| structure coverage | sparse | 7% of schematic structures have data |
Independent check: PASS — 100.0000% agreement across 232,577 stored values re-checked against DWR's authoritative record (HydroBase_CO_20260707), over 20 structures. 0 disagreement(s) beyond a 0.01 cfs tolerance. Checked 2026-08-19; a rotating sample covers the whole basin across successive runs, and the structures this report cites are checked every time.
Federal cross-check: PASS — 100.00% day-level agreement with USGS's own published records for the same gages, across 2 co-listed station(s) and 20,246 overlapping days (within max(2%, 0.5 cfs) daily). Pre-1950 records at some gages carry known between-agency day-stamp and transcription differences — scored at each year's best ±1-day alignment; residual disagreement is real historical divergence, flagged for review.
14 gage(s) / 98,216 daily values (1923-01-01–2026-07-06); 218 structure(s) with diversion records; 1044 with decreed rights. Methodology has not yet had independent expert review — treat every figure as an advisory screen, not an administrative or legal conclusion.
Read this first: the measurement network itself evolved
This basin was not always measured the way it is today — the API-era record is dense and recent, the early record sparse. 13 gage(s) and 60 structure(s) report in 2026, but structure reporting only reached half its modern level around ~1941. Every historical claim below is checked against this: long-term shifts that co-move with the growth of the network carry an explicit measurement-evolution caution, and abandonment screens whose idleness begins before the modern reporting era are flagged †.
| Decade | Gages with data (median yr) | Structures reporting (median yr) |
|---|---|---|
| 1900s | 0 | 1 |
| 1910s | 0 | 61 |
| 1920s | 1 | 0 |
| 1930s | 1 | 16 |
| 1940s | 1 | 114 |
| 1950s | 1 | 0 |
| 1960s | 1 | 24 |
| 1970s | 1 | 58 |
| 1980s | 1 | 87 |
| 1990s | 2 | 66 |
| 2000s | 3 | 56 |
| 2010s | 7 | 95 |
| 2020s | 13 | 82 |
Gage flow trend & changepoints
Every located gage with a period of record — dot size scales with the strength of its flow trend (|Sen slope| in %/decade, the same statistic as the table below), color with direction. An amber ring marks a detected Pettitt changepoint. Click a gage to chart its trend and shift.
| Gage | Trend | Change / decade | Significance | Years | Changepoint |
|---|---|---|---|---|---|
|
▸
CUCHARAS RIVER BELOW CUCHARAS RESERVOIR CUCBCRCO |
↓ decreasing | -359.2% | p=0.003 | 28 | ~2010 |
|
▸
CITY OF WALSENBURG COLER OUTLET DITCH BELOW MARTIN RESERVOIR WCOBMRCO |
↓ decreasing | -143.5% | p=0.002 | 18 | ~2019 |
|
▸
CITY OF WALSENBURG WATER SUPPLY DIVERSION AT CUCHARAS RIVER WWSCURCO |
↓ decreasing | -24.3% | p=0.041 | 18 | — |
|
▸
CUCHARAS RIVER AT BOYD RANCH NEAR LA VETA CRBRLVCO |
↓ decreasing | -3.6% | p=0.021 | 87 | — |
10 other gage(s) show no significant trend or changepoint (not shown).
Mass-balance (network closure) trend
Structure divrec-history backfill coverage as of the last check: 7% of 718 schematic-relevant structures. 0 year(s) clear the 30% coverage gate so far -- the trend activates automatically once qualifying years span a full decade. No action needed; the nightly backfill keeps extending the record.
Reach gain/loss shifts (1993–2026)
Mass-balance kinks computed for every summer month back to 1993 (255 reach-snapshots) — which reaches gain or lose water, and how that has shifted across decades. Each shift is cross-checked against the observation record above: as more diversions became metered, "unaccounted" water shrinks mechanically, which can masquerade as a hydrologic shift.
- CUCHARAS RIVER AT HARRISON BRIDGE NEAR LA VETA, CO: reach shifted from +3 cfs to +43 cfs summer mean (more gaining, p=0.009, 22 yr) [sedimentary plains/foothills: moderate groundwater connectivity -- gain/loss shifts can be real aquifer response; corroborate with nearby well records]
- CUCHARAS RIVER BELOW CUCHARAS RESERVOIR: reach shifted from -17 cfs to +44 cfs summer mean (more gaining, p=0.039, 23 yr) [sedimentary plains/foothills: moderate groundwater connectivity -- gain/loss shifts can be real aquifer response; corroborate with nearby well records]
Groundwater now has its own tab: 88 monitored well(s), water-table trends, stream corridors, and the advisory depletion screen.
Reservoirs now has its own tab: 43 reservoir(s), end-of-year storage back to 1901, click-to-chart histories.
Cross-gage pattern fingerprint
Over the 18-year window with full coverage (2009–2026), the dominant shared pattern across 3 gage(s) explains 61% of year-to-year variance (almost certainly a basin-wide climate/snowpack driver).
CRBRLVCO doesn't move with that shared pattern -- a real, localized signal (a new diversion, land-use change, or a gage-specific data problem) worth a closer look, not necessarily noise.
The basin's aquifer story, from 366 water-level measurements across 88 monitored well(s) (42 alluvial, 0 bedrock, rest unclassified) — plus 0 administered well(s) reporting metered pumping through diversion records. Observation wells and pumping wells are different populations and are never conflated. Click a well to chart its record.
Well map
Every monitored well with a location — hover for identity, click to chart its water-level record below. ● alluvial ● bedrock / confined (Denver Basin, High Plains, etc. — one-way, no human-timescale recharge) ● unclassified — marker size scales with the strength of the well's water-level trend (|Sen slope| in ft/decade — the same Mann-Kendall/Sen statistic as the trends table below); the smallest, faintest dots have too little record to test.
3D aquifer x-ray
Every aquifer unit as its own 3D head surface — alluvial water table on top, Denver Basin members (Dawson, Denver, Arapahoe, Laramie–Fox Hills) stacked beneath where measured — interpolated from measured water levels and animated through time. Units are never mixed; surfaces exist only inside each unit's well coverage (no extrapolation); thin epochs are suppressed with their reason shown. Vertical scale exaggerated for readability; z is head elevation in feet. Advisory — measured heads, not a calibrated model.
Water-table trends
Of 4 well(s) with enough record for a trend test: 1 declining, 3 rising.
| Fastest-declining wells | Setting | ft / decade | Span | p |
|---|---|---|---|---|
| ▸ SC02906719ACA | alluvial | -0.42 | 34 yr | 0.002 |
Stream corridors — the surface connection
For each reach whose gain/loss has shifted (Trends tab), the wells within 2 miles of its anchoring gage, their pooled water-table history over the same era, and an advisory Glover screen of lagged stream depletion from nearby metered pumping. v1 proximity = distance to the reach's anchoring gage; segment-based reach join is a flagged upgrade.
CUCHARAS RIVER AT HARRISON BRIDGE NEAR LA VETA, CO: 0 alluvial well(s) nearby
Wells labeled by administrative world before anything else is said about them: tributary alluvium participates in the priority system; designated-basin and Denver Basin bedrock aquifers are governed differently and are excluded from stream-connection reasoning. Read bedrock declines differently too: deep bedrock aquifers recharge negligibly on human timescales, so a falling bedrock level is storage mining — effectively permanent — not a drought response that a wet year undoes. All screens advisory.
43 reservoir(s) with 9,076 storage measurement(s), 1901–2016. Basin storage as of 2016-05-31 (the record's own end — reservoir records publish ~annually): 5 AF across 2 reservoir(s). Storage change is real water the mass balance must credit — a losing reach beside a filling reservoir isn't losing water, it's banking it.
Reservoir map — how full is each vessel?
Each reservoir drawn as a vessel: bubble size ∝ its record-high storage, fill level = last recorded storage as a share of its surveyed capacity (USACE National Inventory of Dams) where a confident NID match exists — the tooltip names the matched dam — and of its own record high otherwise (a wrong capacity would be worse than an honest record high, so only confident joins upgrade). Hover for numbers, click to chart its history below the map. A dashed teal ring marks reservoirs reporting live DWR telemetry — their fill reflects yesterday's storage, drawn as a dotted tail on charts and treated as provisional until the next verified HydroBase snapshot supersedes it. ● <25% ● 25–60% ● 60–90% ● >90%
Basin storage, end of each water year
End-of-water-year totals; per-year reservoir counts shown because reporting coverage varies -- a total is only comparable to years with similar counts.
Largest reservoirs on record
Click a reservoir to chart its full storage history.
| Reservoir | Last recorded storage (AF) | As of |
|---|---|---|
| ▸ COLER SEEPAGE RESERVOIR (1603893) | 2,239 | 1969-10-01 |
| ▸ LAKE OEHM RESERVOIR (COLER SYSTEM OUTLET (1603716) | 1,717 | 2013-10-30 |
| ▸ LAKE MIRIAM RESERVOIR (1603715) | 1,636 | 2013-10-30 |
| ▸ MARTIN RESERVOIR (1603832) | 879 | 1967-10-01 |
| ▸ MARIA STEVENS RESERVOIR (1603718) | 799 | 2013-10-30 |
| ▸ WALSENBURG RESERVOIR (1603724) | 479 | 2013-10-30 |
| ▸ BRITTON RESERVOIR NO 3 (1603861) | 240 | 1961-11-01 |
| ▸ CASTLE ROCK RESERVOIR (1603763) | 175 | 1961-10-01 |
Decrees, seniority, and administrative calls connected to this basin's flow network. Advisory reading aids on public DWR data — not administrative or legal conclusions. Rights on file: 1229 across 1044 structure(s); 218 structure(s) carry 0 court-case references.
Abandonment radar (25 screens)
Absolute rights with 10+ years of no recorded diversions. Screens only — storage, alternate points, and plan operations can explain nonuse lawfully. And diversion REPORTING itself only reached its modern level ~1941 — idleness that begins before then may be unreported use, not nonuse (flagged † below).
- ANTONIO D VALDEZ DITCH (1600806) (1907-09-19, 4.0 cfs decreed): last active 1924 — 101 years idle † predates modern reporting era — last recorded activity predates this basin's modern reporting era (~1941) -- early absence of record is weak evidence of nonuse
- FIELDEN RESERVOIR (1603777) (1896-10-01, 0.0 cfs decreed): last active 1924 — 101 years idle † predates modern reporting era — last recorded activity predates this basin's modern reporting era (~1941) -- early absence of record is weak evidence of nonuse
- FROHLICH & PAUL DITCH (1600810) (1883-06-05, 2.0 cfs decreed): last active 1945 — 80 years idle
- PAPOOSE SPRING (1600873) (1934-04-30, 0.0 cfs decreed): last active 1945 — 80 years idle
- J B FARR DITCH (1600916) (1891-06-20, 0.4 cfs decreed): last active 1945 — 80 years idle
- GOEMMER DITCH (1600882) (1904-04-30, 1.0 cfs decreed): last active 1949 — 76 years idle
- ARNOLD DITCH NO 2 (1600928) (1873-06-01, 2.0 cfs decreed): last active 1949 — 76 years idle
- JOHN GRIBBLE DITCH (1600794) (1883-04-10, 1.6 cfs decreed): last active 1964 — 61 years idle
- SAMUEL J CAPPS DITCH (1600927) (1884-06-01, 0.5 cfs decreed): last active 1969 — 56 years idle
- BRESSAN SPRING DITCH (1600824) (1921-07-31, 1.2 cfs decreed): last active 1970 — 55 years idle
Compliance screens (91 advisory flags)
Screened 128 of 1044 structures with rights (147 have diversion history on file). A flag is a lead for expert review — augmentation plans, exchanges, and free-river conditions can make over-decree diversions lawful and are deliberately not modeled.
- LAKE MIRIAM DITCH (1600584): Observed p99 daily rate 50.0 cfs (max 104.0) exceeds total decreed absolute 23.1 cfs across 19054 recorded day(s). Structure holds an Augmentation-use decree -- diversions above the direct-flow decree can be lawful under plan operations; interpret with care.
- BUTTE DITCH (1600574): Observed p99 daily rate 15.9 cfs (max 43.6) exceeds total decreed absolute 8.0 cfs across 16039 recorded day(s).
- WALSENBURG DITCH (1600636): Observed p99 daily rate 15.0 cfs (max 29.8) exceeds total decreed absolute 5.6 cfs across 29225 recorded day(s).
- DURAN DITCH (1600626): Observed p99 daily rate 13.9 cfs (max 38.4) exceeds total decreed absolute 6.5 cfs across 22092 recorded day(s). Structure holds an Augmentation-use decree -- diversions above the direct-flow decree can be lawful under plan operations; interpret with care.
- KUHN RADCLIFF PIPELINE (1600869): Observed p99 daily rate 12.0 cfs (max 12.0) exceeds total decreed absolute 0.0 cfs across 202 recorded day(s).
- OSO DITCH (1600608): Observed p99 daily rate 10.0 cfs (max 10.0) exceeds total decreed absolute 2.0 cfs across 12842 recorded day(s).
- SPANISH PEAKS DITCH (1600622): Observed p99 daily rate 10.0 cfs (max 13.0) exceeds total decreed absolute 7.9 cfs across 34972 recorded day(s).
- FRANCISCO DAIGRE MILL (1600628): Observed p99 daily rate 8.5 cfs (max 15.3) exceeds total decreed absolute 7.0 cfs across 25889 recorded day(s).
- NORTH VETA CANON DITCH (1600896): Observed p99 daily rate 8.0 cfs (max 15.9) exceeds total decreed absolute 6.0 cfs across 14392 recorded day(s). Structure holds an Augmentation-use decree -- diversions above the direct-flow decree can be lawful under plan operations; interpret with care.
- MEXICAN DITCH (1600604): Observed p99 daily rate 7.2 cfs (max 14.2) exceeds total decreed absolute 4.9 cfs across 22346 recorded day(s).
Seniority (top structures by decreed rate)
| Structure | Senior priority date | Rights | Decreed abs (cfs) | Decreed abs (AF) | Conditional? |
|---|---|---|---|---|---|
| HOLITA DITCH (1600579) | 1910-05-23 | 1 | 48.0 | 0 | — |
| LAKE MIRIAM DITCH (1600584) | 1868-05-03 | 9 | 23.1 | 0 | — |
| SOUTH ABEYTA HIGHLAND (1600870) | 1888-02-14 | 1 | 12.8 | 0 | — |
| GOMEZ DITCH (1600577) | 1868-06-08 | 2 | 10.2 | 0 | — |
| MARCHIORI DITCH (1600845) | 1907-12-31 | 1 | 10.0 | 0 | — |
| WALSENBURG PIPELINE (1600637) | 1863-05-30 | 8 | 9.4 | 0 | — |
| BUTTE DITCH (1600574) | 1871-05-01 | 4 | 8.0 | 0 | — |
| SPANISH PEAKS DITCH (1600622) | 1863-05-30 | 3 | 7.9 | 0 | — |
| FRANCISCO DAIGRE MILL (1600628) | 1863-05-30 | 3 | 7.0 | 0 | — |
| DURAN DITCH (1600626) | 1871-06-13 | 6 | 6.5 | 0 | — |
| MARTIN DITCH NO 1 (1600865) | 1886-04-01 | 3 | 6.4 | 0 | — |
| ROCKY FLAT DITCH (1600614) | 1871-05-01 | 5 | 6.2 | 0 | — |
| MENEGATTI FLOOD DITCH (1600647) | 1913-08-31 | 1 | 6.0 | 0 | — |
| NORTH VETA CANON DITCH (1600896) | 1873-03-01 | 1 | 6.0 | 0 | — |
| WALSENBURG DITCH (1600636) | 1866-04-30 | 1 | 5.6 | 0 | — |
No inventory or legal-document changes detected since the daily watch began.
If a call were placed at a given seniority, which structures in this basin would be out of priority, and how much of their decreed rate would be curtailed? Computed from this basin's cached decrees.
What this does and doesn't model. Seniority arithmetic only: every right junior to the call is treated as curtailed. It does not model reach applicability — structures downstream of the calling point are not administered by it — and it applies no futile-call judgment. Read it as “who is junior to this date, and by how much,” not as a prediction of what the Division Engineer would actually order.
Pick a calling right
Real decrees from this basin, ordered by administration number — that is, by actual seniority. The years will look out of order, and that is correct: an administration number encodes the adjudication date as well as the appropriation date, so a right appropriated in 1970 can be administered ahead of one from 1950. A senior call curtails almost everything; a junior one curtails almost nothing.
Or enter an administration number directly
DWR administration numbers encode appropriation and adjudication dates; lower is more senior.
Ribbon width ∝ flow. Hover any diversion/return branch for its data source (live telemetry vs. annual divrec) and age — use that to judge how much to trust a given number.
| Gage ⇅ | Station ⇅ | Avg cfs Aug 10–Aug 16 ⇅ |
% Hist Median ⇅ | Rank ⇅ | Δ1wk ⇅ | Δ4wk ⇅ | Yrs ⇅ | Status ⇅ |
|---|---|---|---|---|---|---|---|---|
| CUCBCRCO | CUCHARAS RIVER BELOW CUCHARAS RESERVOIR | 0.0 | 0% | 0 | -0 | -0 | 26.2 | SHORT_RECORD |
| CRHBLVCO | CUCHARAS RIVER AT HARRISON BRIDGE NEAR LA VETA, CO | 0.0 | 0% | 0 | +0 | +0 | 25.7 | SHORT_RECORD |
| WWSCURCO | CITY OF WALSENBURG WATER SUPPLY DIVERSION AT CUCHARAS RIVER | 0.0 | 0% | 0 | +0 | +0 | 17.1 | SHORT_RECORD |
| WCLOUTCO | CITY OF WALSENBURG CITY LAKE OUTFLOW | 0.0 | 0% | 0 | -0 | -0 | 14.4 | SHORT_RECORD |
| WCOBMRCO | CITY OF WALSENBURG COLER OUTLET DITCH BELOW MARTIN RESERVOIR | 0.0 | 0% | 0 | +0 | -0 | 17.2 | SHORT_RECORD |
| LVMPCRCO | LA VETA MUNICIPAL PIPELINE AT CUCHARAS RIVER, CO | 0.1 | 16% | 0 | -0 | -0 | 16.9 | SHORT_RECORD |
| GOMDITCO | GOMEZ DITCH | 0.0 | 0% | 0 | +0 | +0 | 10.4 | SHORT_RECORD |
| GOMRETCO | GOMEZ DITCH CITY RETURN FLOW | 0.0 | 0% | 0 | +0 | +0 | 10.4 | SHORT_RECORD |
| MEXDITCO | MEXICAN DITCH | 0.0 | 0% | 0 | +0 | +0 | 10.3 | SHORT_RECORD |
| LVRET1CO | LA VETA #1 RETURN FLOW | 0.0 | 0% | 0 | +0 | +0 | 10.3 | SHORT_RECORD |
| CRHW10CO | CUCHARAS RIVER AT HIGHWAY 10 | 0.6 | 114% | 51 | +1 | +1 | 8.3 | SHORT_RECORD |
| CRBRLVCO | CUCHARAS RIVER AT BOYD RANCH NEAR LA VETA | 2.5 | 18% | 0 | +1 | +0 | 85.9 | OK |
Call details in gantt above
11 alert(s) · 6 warning(s) · 12 info. Each gage contributes at most one flag per category (its single most-severe match), so this list shouldn't multiply-count the same underlying condition.