Blue River Basin

Division 5 · Water District 36

Draft - NLDI/CDSS verified

Bootstrap review report — d5_wd36_blue_river_basin

Generated 2026-08-14 06:36 UTC for Division 5 / Water District 36.

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: BLUE 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
BLUE RIVER (assumed mainstem)	243
SNAKE RIVER	41
PERU CREEK	31
TENMILE CREEK	30
WILLOW CREEK	29
BRUSH CREEK	22
SPRING CREEK	21
BEAVER CREEK	21
SWAN RIVER	21
BUSHEE CREEK	20
ROCK CREEK	19
STRAIGHT CREEK	13
MIDDLE BARTON CREEK	12
BLACK CREEK	12
ACORN CREEK	12
SPRUCE CREEK	10
SLATE CREEK	10
BOULDER CREEK	10
GILBERT CREEK	9
WEST TENMILE CREEK	9
ELLIOTT CREEK	8
OTTER CREEK	8
CATARACT CREEK	7
KEYSTONE CREEK	7
HARSHA GULCH	7
SQUAW CREEK	7
MINERS CREEK	6
SALT LICK CREEK	6
HARRIGAN CREEK	6
SHANE GULCH	5

2. Diversion / return classification

Auto-classified from structureType + name patterns: 505 diversions, 71 returns, 626 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)

20 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
3600881	GREEN MTN HYDRO-ELECTRIC	other	diversion	Power Generation
3600943	KEYSTONE HYDRO POWER PROJECT	other	diversion	Industrial
3603512	SPRUCE VALLEY RECHARGE FACILITY	other	return	Augmentation
3604620	VIDLER - RICE/SODA CREEK/PHILLIPS POOL	other	return	Augmentation
3604658	STRAIGHT CREEK TUNNEL DRAIN SYSTEM	other	diversion	Industrial, Municipal, Transmountain Export
3604923	CLIMAX INTEGRATED WATER SYSTEM	other	diversion	Commercial, Domestic, Fire, Industrial, Irrigation, Municipal
3605001	VAIL PASS WELL & EAST PL	other	diversion	Domestic
3605003	OFFERSON WELL NO 1	other	diversion	Commercial, Domestic, Irrigation
3605005	LIFTSIDE WELL NO 1 25259	other	diversion	Commercial, Domestic, Fire, Irrigation, Municipal, Other, Recreation
3605006	LIFTSIDE WELL NO 2 25260	other	diversion	Commercial, Domestic, Fire, Irrigation, Municipal, Other, Recreation
3605007	BAER WELL 1	other	diversion	Household Use Only, Stock
3605009	BLUE RIVER VALLEY WELL NO 1	other	diversion	Municipal
3605011	BLUMENHEIN WELL NO 1	other	diversion	Domestic, Industrial, Irrigation, Municipal
3605013	BRECKENRIDGE WELL NO 1	other	diversion	Commercial, Domestic
3605014	BRECKENRIDGE WELL NO 2	other	diversion	Commercial, Domestic
3605015	BRECKENRIDGE WELL NO 3	other	diversion	Commercial, Domestic
3605016	BUFFALO MOUNTAIN WELL	other	diversion	Domestic, Municipal
3605017	BUMGARNER WELL	other	diversion	Domestic
3605018	BURGER WELL	other	diversion	Commercial, Domestic
3605021	VUKOVICH WELL NO 1	other	diversion	Household Use Only, Stock

3. Suspected nested tributaries

15 flag(s) confirmed connected by USGS NLDI — real surveyed stream-network topology, not a distance guess (see VERIFICATION-PLAN.md). This confirms the two candidates' channels really do merge (ruling out a coincidental-proximity false flag) but NOT auto-applied to tributary_parent_overrides — NLDI's overlap test can't reliably tell which side is upstream once two streams have already merged near DWR's own recorded structures, only that they connect. Confirm the direction (which one is the tributary, which is the parent) from local knowledge or the evidence below, then set it yourself.

pair	NLDI evidence
SPRUCE CREEK <-> MAINSTEM	tributary's downstream NHD trace (comid 1312177) first overlaps MAINSTEM's own downstream trace at index 5 (next-nearest candidate: none)
MARTIN CREEK <-> ELLIOTT CREEK	tributary's downstream NHD trace (comid 1312325) first overlaps ELLIOTT CREEK's own downstream trace at index 1 (next-nearest candidate: ('MAINSTEM', 2))
MINERS CREEK <-> TENMILE CREEK	tributary's downstream NHD trace (comid 1312893) first overlaps TENMILE CREEK's own downstream trace at index 3 (next-nearest candidate: ('MAINSTEM', 5))
SNAKE RIVER <-> PERU CREEK	tributary's downstream NHD trace (comid 1314043) first overlaps PERU CREEK's own downstream trace at index 2 (next-nearest candidate: ('MAINSTEM', 10))
ELLIOTT CREEK <-> MARTIN CREEK	tributary's downstream NHD trace (comid 1312315) first overlaps MARTIN CREEK's own downstream trace at index 0 (next-nearest candidate: ('MAINSTEM', 1))
GILBERT CREEK <-> QUAKING ASP CREEK	tributary's downstream NHD trace (comid 1312703) first overlaps QUAKING ASP CREEK's own downstream trace at index 0 (next-nearest candidate: ('MAINSTEM', 1))
SAWMILL CREEK <-> BEAVER CREEK	tributary's downstream NHD trace (comid 1312117) first overlaps BEAVER CREEK's own downstream trace at index 2 (next-nearest candidate: none)
BIG GULCH <-> MAINSTEM	tributary's downstream NHD trace (comid 1312213) first overlaps MAINSTEM's own downstream trace at index 1 (next-nearest candidate: ('COLORADO RIVER', 24))
KEYSTONE CREEK <-> SNAKE RIVER	tributary's downstream NHD trace (comid 1314057) first overlaps SNAKE RIVER's own downstream trace at index 0 (next-nearest candidate: ('MAINSTEM', 6))
HARSHA GULCH <-> ELLIOTT CREEK	tributary's downstream NHD trace (comid 1312127) first overlaps ELLIOTT CREEK's own downstream trace at index 2 (next-nearest candidate: none)
DEEP CREEK <-> MAINSTEM	tributary's downstream NHD trace (comid 1312279) first overlaps MAINSTEM's own downstream trace at index 1 (next-nearest candidate: none)
HARRIGAN CREEK <-> MAINSTEM	tributary's downstream NHD trace (comid 1312659) first overlaps MAINSTEM's own downstream trace at index 2 (next-nearest candidate: ('ACORN CREEK', 3))
SODA CREEK <-> SNAKE RIVER	tributary's downstream NHD trace (comid 1313401) first overlaps SNAKE RIVER's own downstream trace at index 3 (next-nearest candidate: ('MAINSTEM', 4))
MEADOW CREEK <-> TENMILE CREEK	tributary's downstream NHD trace (comid 1313555) first overlaps TENMILE CREEK's own downstream trace at index 1 (next-nearest candidate: ('MAINSTEM', 4))
PERU CREEK <-> SNAKE RIVER	tributary's downstream NHD trace (comid 1314263) first overlaps SNAKE RIVER's own downstream trace at index 0 (next-nearest candidate: ('MAINSTEM', 11))

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
BRUSH CREEK	COLORADO RIVER	0.86	1.3	ambiguous -- tied earliest overlap at index 0: ['COLORADO RIVER', 'MAINSTEM']
BLACK CREEK	COLORADO RIVER	0.26	0.32	ambiguous -- tied earliest overlap at index 2: ['COLORADO RIVER', 'MAINSTEM']
QUAKING ASP CREEK	GILBERT CREEK	0.01	0.62	ambiguous -- tied earliest overlap at index 1: ['GILBERT CREEK', 'MAINSTEM']
TENMILE CREEK	SAWMILL CREEK	0.72	2.86	ambiguous -- tied earliest overlap at index 5: ['SAWMILL CREEK', 'MAINSTEM']
MUMFORD GULCH	BIG GULCH	0.15	2.76	ambiguous -- tied earliest overlap at index 6: ['BIG GULCH', 'MAINSTEM']
SALT LICK CREEK	COLORADO RIVER	0.0	0.01	ambiguous -- tied earliest overlap at index 0: ['COLORADO RIVER', 'MAINSTEM']
PEBBLE CREEK	COLORADO RIVER	0.35	1.41	ambiguous -- tied earliest overlap at index 1: ['COLORADO RIVER', 'MAINSTEM']
SWAN RIVER	SODA CREEK	2.24	3.73	ambiguous -- tied earliest overlap at index 5: ['SODA CREEK', 'MAINSTEM']

4. Gage placement risk

None — every gage with a resolvable position is within the placement cutoff.

47 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_patterns from 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_wdids against any local accounting source you have for this basin.
Review the rendered schematic for this district before relying on it.

Reconstruct conditions as of

Evolution of the network

Computed 2026-08-20 09:06 from 46 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 D (2/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	stale	newest diversion record is 658 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 37,314 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 — 99.89% day-level agreement with USGS's own published records for the same gages, across 40 co-listed station(s) and 414,582 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.

46 gage(s) / 442,160 daily values (1904-08-01–2026-07-06); 525 structure(s) with diversion records; 1247 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. 15 gage(s) and 211 structure(s) report in 2026, but structure reporting only reached half its modern level around ~1969. 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	1	0
1910s	3	0
1920s	1	0
1930s	3	0
1940s	15	0
1950s	14	0
1960s	14	66
1970s	15	184
1980s	16	227
1990s	16	176
2000s	15	184
2010s	15	173
2020s	15	204

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
▸ ELLIOTT CREEK FEEDER CANAL TO GREEN MTN RES, CO GREELCCO	↓ decreasing	-87.5%	p=0.032	22	—
▸ SNAKE RIVER AT KEYSTONE SKI AREA SNAKEYCO	no clear trend	-8.7%	p=0.317	27	~2015
▸ BLUE RIVER AT DILLON, CO. BLUADICO	↓ decreasing	-7.6%	p=0.000	50	~1930
▸ SNAKE RIVER AT DILLON, CO. SNADILCO	no clear trend	-7.0%	p=0.103	43	~1930
▸ BOULDER CREEK AT UPPER STATION, NEAR DILLON, CO. BOCUPPCO	no clear trend	+6.7%	p=0.093	28	~1981
▸ BLUE RIVER AT BLUE RIVER, CO. BLUABLCO	↓ decreasing	-6.5%	p=0.016	43	—
▸ TENMILE CREEK AT DILLON, CO. TENDILCO	↓ decreasing	-6.5%	p=0.003	40	~1930
▸ TENMILE CREEK BL NORTH TENMILE C, AT FRISCO, CO. TENFRICO	↑ increasing	+4.3%	p=0.004	68	~1981
▸ BLUE RIVER BELOW GREEN MOUNTAIN RESERVOIR, CO BLUGRECO	↓ decreasing	-3.7%	p=0.012	89	~1986

37 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 633 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 (1950–2026)

Mass-balance kinks computed for every summer month back to 1950 (3195 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.

BLUE RIVER BELOW GREEN MOUNTAIN RESERVOIR, CO: reach shifted from +268 cfs to +587 cfs summer mean (more gaining, p=0.002, 77 yr) [sedimentary uplands: moderate groundwater connectivity -- gain/loss shifts can be real aquifer response; corroborate with nearby well records]
TENMILE CREEK BELOW WEST TENMILE CREEK, CO: reach shifted from -55 cfs to -48 cfs summer mean (more gaining, p=0.043, 11 yr) [mountain crystalline canyon: minimal groundwater storage -- large or shifting unaccounted losses here are more consistent with data/measurement issues or unmodeled plumbing than with aquifer exchange]
BLUE RIVER BELOW DILLON, CO.: reach shifted from +207 cfs to -52 cfs summer mean (more losing, p=0.000, 67 yr) [sedimentary uplands: moderate groundwater connectivity -- gain/loss shifts can be real aquifer response; corroborate with nearby well records] [5 alluvial wells within 2 mi of the gage; pooled water table -2.0 ft (1973–2011, no_trend)]
BOULDER CREEK AT UPPER STATION, NEAR DILLON, CO.: reach shifted from -15 cfs to -5 cfs summer mean (more gaining, p=0.041, 27 yr) [sedimentary uplands: moderate groundwater connectivity -- gain/loss shifts can be real aquifer response; corroborate with nearby well records]

Groundwater now has its own tab: 29 monitored well(s), water-table trends, stream corridors, and the advisory depletion screen.

Reservoirs now has its own tab: 64 reservoir(s), end-of-year storage back to 1964, click-to-chart histories.

Cross-gage pattern fingerprint

Over the 69-year window with full coverage (1958–2026), the dominant shared pattern across 3 gage(s) explains 85% of year-to-year variance (almost certainly a basin-wide climate/snowpack driver).

All gages in this window move with the shared pattern -- no localized outlier.

Structures most implicated by reconciliation (as of 2026-07-06)

Which structures' data absorbed the most correction when the current mass-balance snapshot was reconciled -- see the Historical tab for the full picture on any date.

DILLON SNOW RETURN FLOW (return): +16.6 cfs (100% of that reach's correction)

The basin's aquifer story, from 104 water-level measurements across 29 monitored well(s) (27 alluvial, 0 bedrock, rest unclassified) — plus 25 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 0 well(s) with enough record for a trend test: 0 declining, 0 rising.

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.

TENMILE CREEK BELOW WEST TENMILE CREEK, CO: 0 alluvial well(s) nearby. Glover screen: 0.7 cfs of nearby metered alluvial pumping → est. lagged depletion 0.6–0.7 cfs (uncalibrated T/S ranges; flagged for SPDSS calibration, AWAS cross-check, and expert review — DWR's AWAS is the authority).

BLUE RIVER BELOW DILLON, CO.: 5 alluvial well(s) nearby; pooled water table -2.0 ft (1973–2011, no_trend, p=0.9641)

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.

64 reservoir(s) with 6,955 storage measurement(s), 1964–2025. Basin storage as of 2024-10-31 (the record's own end — reservoir records publish ~annually): 295,455 AF across 4 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
▸ DILLON RESERVOIR (3604512)	217,354	2024-10-31
▸ GREEN MOUNTAIN RESERVOIR (3603543)	76,976	2024-10-31
▸ CLINTON GULCH RESERVOIR (3603575)	4,205	2021-10-31
▸ BLACK LAKE AND RESERVOIR (3603533)	1,997	2010-10-31
▸ CATARACT LAKE AND RESERVOIR (3603538)	1,653	2010-10-31
▸ GOOSE PASTURE TARN (3603542)	805	2024-10-31
▸ MIN LAKE MOHAWK NO 2 (3603586)	444	1992-10-31
▸ LOWER BLACK CREEK RESERVOIR (3603556)	400	1988-09-22

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: 2639 across 1247 structure(s); 97 structure(s) carry 0 court-case references.

Abandonment radar (6 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 ~1969 — idleness that begins before then may be unreported use, not nonuse (flagged † below).

SODA CREEK DITCH (3600809) (1900-07-01, 2.7 cfs decreed): last active 1969 — 11 years idle
BENTON CREEK NO 1 DITCH (3600522) (1912-10-06, 4.2 cfs decreed): last active 1970 — 10 years idle
BENTON CREEK NO 2 DITCH (3600523) (1904-10-30, 2.2 cfs decreed): last active 1970 — 10 years idle
COULTER NO 1 DITCH (3600575) (1904-08-31, 0.8 cfs decreed): last active 1970 — 10 years idle
COULTER NO 2 DITCH (3600576) (1913-04-24, 0.2 cfs decreed): last active 1970 — 10 years idle
ENGLE DITCH (3600614) (1942-09-25, 4.1 cfs decreed): last active 1970 — 10 years idle

Compliance screens (171 advisory flags)

Screened 279 of 1247 structures with rights (341 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.

MIN FLOW BLUE RIVER 5 - DILLON TO STRAIG (3602043): Observed p99 daily rate 947.0 cfs (max 1900.0) exceeds total decreed absolute 50.0 cfs across 5100 recorded day(s).
MIN FLOW BLUE RIVER 4 - SWAN RIVER TO DI (3602037): Observed p99 daily rate 528.4 cfs (max 715.0) exceeds total decreed absolute 32.0 cfs across 4986 recorded day(s).
BLUE VALLEY RANCH HYDRO (3600985): Observed p99 daily rate 222.0 cfs (max 222.0) exceeds total decreed absolute 129.0 cfs across 14666 recorded day(s).
MIN FLOW BLUE RIVER 3 - SWAN RIVER UP TO (3602030): Observed p99 daily rate 177.0 cfs (max 339.0) exceeds total decreed absolute 20.0 cfs across 5822 recorded day(s).
ELLIOTT CREEK FEEDER (3600606): Observed p99 daily rate 118.0 cfs (max 200.0) exceeds total decreed absolute 90.0 cfs across 17164 recorded day(s).
MIN FLOW SNAKE RIVER LOW - NORTH FORK TO (3602033): Observed p99 daily rate 107.0 cfs (max 108.0) exceeds total decreed absolute 12.0 cfs across 4350 recorded day(s).
MIN FLOW STRAIGHT CREEK (3602040): Observed p99 daily rate 90.6 cfs (max 125.0) exceeds total decreed absolute 2.5 cfs across 3580 recorded day(s).
CON-HOOSIER SYS MCCULLOUGH DITCH (3604690): Observed p99 daily rate 76.0 cfs (max 128.4) exceeds total decreed absolute 60.0 cfs across 8214 recorded day(s).
CON-HOOSIER TUNNEL (3604699): Observed p99 daily rate 65.7 cfs (max 163.5) exceeds total decreed absolute 20.0 cfs across 26128 recorded day(s).
HOAGLAND CANAL (ELLIOT) (3600662): Observed p99 daily rate 65.0 cfs (max 69.9) exceeds total decreed absolute 25.0 cfs across 9969 recorded day(s).

Seniority (top structures by decreed rate)

Structure	Senior priority date	Rights	Decreed abs (cfs)	Decreed abs (AF)	Conditional?
GREEN MTN HYDRO-ELECTRIC (3600881)	1935-08-01	1	1726.0	0	—
BLUE RIVER DIVERSION PROJECT (3604684)	1946-06-24	1	654.0	0	yes
TOWN OF BRECKENRIDGE WHITEWATER PARK (3607293)	2000-12-21	1	500.0	0	—
CLIMAX INTEGRATED WATER SYSTEM (3604923)	1903-01-01	13	416.5	103	yes
CON-HOOSIER SYS BLUE RIVER DITCH (3604683)	1948-05-13	3	200.0	0	—
BLUE VALLEY RANCH HYDRO (3600985)	1981-03-09	1	129.0	0	—
MIN FLOW BLUE RIVER 9 - BOULDER CK TO SL (3602047)	1904-05-23	3	125.0	0	—
MIN FLOW BLUE RIVER 10 - SLATE CK TO GMR (3602048)	1904-05-23	2	125.0	0	—
MIN FLOW BLUE RIVER 8 - ROCK CK TO BOULD (3602046)	1987-10-02	1	115.0	0	—
ELLIOTT CREEK FEEDER (3600606)	1935-08-01	1	90.0	0	—
CON-HOOSIER EAST HOOSIER DITCH (3604689)	1929-08-05	2	90.0	0	—
MIN FLOW BLUE RIVER 11 - GMR TO COLORADO (3602049)	1987-10-02	1	85.0	0	—
LOBACK DITCH (3600709)	1930-12-31	4	75.8	0	—
MIN FLOW BLUE RIVER 7 - ROCK CK TO WILLO (3602045)	1987-10-02	1	75.0	0	—
CON-HOOSIER SYS MCCULLOUGH DITCH (3604690)	1948-05-13	3	60.0	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

Administration number

DWR administration numbers encode appropriation and adjudication dates; lower is more senior.