Eagle River Basin

Division 5 · Water District 37

Draft - NLDI/CDSS verified

Bootstrap review report — d5_wd37_eagle_river_basin

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

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: EAGLE 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
EAGLE RIVER (assumed mainstem)	283
GYPSUM CREEK	115
BRUSH CREEK	81
RED CANYON CREEK	57
GORE CREEK	50
ALKALI CREEK	47
LAKE CREEK	47
WEST LAKE CREEK	40
EAST LAKE CREEK	39
SALT CREEK	37
SPRING CREEK	34
SQUAW CREEK	32
EBY CREEK	27
UNDEFINED	22
TRAVIS CREEK	21
COLORADO RIVER	18
HOLLAND CREEK	17
ROARING FORK RIVER	17
BEAVER CREEK	15
WARREN GULCH CREEK	15
CASTEEL CREEK	14
HOMESTAKE CREEK	13
CROSS CREEK	12
UTE CREEK	11
BEARD CREEK	10
CASTLE CREEK	10
MCCOY CREEK	10
EAST FORK EAGLE RIVER	10
WEST BRUSH CREEK	9
BRUCE CREEK	9

2. Diversion / return classification

Auto-classified from structureType + name patterns: 764 diversions, 270 returns, 513 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)

28 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
3700896	E C D C GALLERY	other	diversion	Domestic, Fire, Industrial, Irrigation, Municipal
3700897	EAGLE MINE MILL SYSTEM	other	diversion	Industrial
3701088	AVON METRO MUN WTR SYSW1	other	diversion	Domestic, Fire, Industrial, Irrigation, Municipal, Power Generation, Recreation
3701119	AVON METRO MUN WTR SYSW2	other	diversion	Domestic, Fire, Industrial, Irrigation, Municipal, Power Generation, Recreation
3701431	EAST LAKE CREEK AP DIVERSION REACH	other	diversion	Domestic, Fire, Irrigation, Municipal, Other, Recreation
3701432	WEST LAKE CREEK AP DIVERSION REACH	other	diversion	Domestic, Fire, Irrigation, Municipal, Other, Recreation
3701467	RANGERS MICROHYDRO	other	diversion	Power Generation
3701468	LENGEL HYDRO-ELECTRIC TURBINE	other	diversion	Power Generation
3703500	ROLD RESERVOIR	other	diversion	Fishery, Irrigation
3703781	BACHELOR GULCH WETLANDS	other	diversion	Evaporative, Irrigation, Wildlife
3703782	ARROWHEAD WETLANDS	other	diversion	Evaporative, Irrigation, Wildlife
3705006	SOUTH FORTY WELL	other	diversion	Commercial, Domestic, Fire, Fishery, Industrial, Irrigation, Municipal, Recreation, Stock
3705008	GORE WELL NO 1	other	diversion	Domestic
3705009	LAKE CR COMM WELL NO 1	other	diversion	Domestic, Irrigation
3705013	REYNOLDS WELL	other	diversion	Domestic
3705017	SCHMIDT WELL NO 1	other	diversion	Commercial
3705018	SKELLY WELL NO 2	other	diversion	Commercial, Domestic
3705020	STERN WELL NO 1	other	diversion	Domestic
3705021	THOMPSON WELL	other	diversion	Commercial, Domestic
3705022	TOWN OF MINTURN WELL NO 1	other	diversion	Municipal
3705023	TOWN OF MINTURN WELL NO 2	other	diversion	Municipal
3705025	VAIL INTERMT WELL NO 1	other	diversion	Domestic
3705026	VAIL INTERMT WELL NO 2	other	diversion	Domestic
3705027	VAIL INTERMT WELL NO 3	other	diversion	Domestic
3705028	VAIL + 15 WELL	other	diversion	Domestic
3705029	WHITE WELL	other	diversion	Domestic, Irrigation
3705031	BELLYACHE RIDGE WELL 1	other	diversion	Domestic
3705032	BOOTH WELL NO 1	other	diversion	Irrigation

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
SALT CREEK <-> BRUSH CREEK	tributary's downstream NHD trace (comid 1319396) first overlaps BRUSH CREEK's own downstream trace at index 1 (next-nearest candidate: ('MAINSTEM', 9))
CACHE CREEK <-> ALKALI CREEK	tributary's downstream NHD trace (comid 1318918) first overlaps ALKALI CREEK's own downstream trace at index 0 (next-nearest candidate: ('MAINSTEM', 3))
CASTEEL CREEK <-> LAKE CREEK	tributary's downstream NHD trace (comid 1319572) first overlaps LAKE CREEK's own downstream trace at index 1 (next-nearest candidate: ('MAINSTEM', 2))
BRUCE CREEK <-> BRUSH CREEK	tributary's downstream NHD trace (comid 1320276) first overlaps BRUSH CREEK's own downstream trace at index 1 (next-nearest candidate: ('MAINSTEM', 10))
UTE CREEK <-> MAINSTEM	tributary's downstream NHD trace (comid 1318964) first overlaps MAINSTEM's own downstream trace at index 1 (next-nearest candidate: ('CACHE CREEK', 4))
NOLAN CREEK <-> BRUSH CREEK	tributary's downstream NHD trace (comid 1319840) first overlaps BRUSH CREEK's own downstream trace at index 5 (next-nearest candidate: ('MAINSTEM', 19))
BOOTH CREEK <-> GORE CREEK	tributary's downstream NHD trace (comid 1319310) first overlaps GORE CREEK's own downstream trace at index 0 (next-nearest candidate: ('MAINSTEM', 23))
MCCOY CREEK <-> BACHELOR GULCH	tributary's downstream NHD trace (comid 1319218) first overlaps BACHELOR GULCH's own downstream trace at index 0 (next-nearest candidate: ('MAINSTEM', 6))
MUDDY CREEK <-> ALKALI CREEK	tributary's downstream NHD trace (comid 1318912) first overlaps ALKALI CREEK's own downstream trace at index 0 (next-nearest candidate: ('MAINSTEM', 2))
KELLY CREEK <-> SALT CREEK	tributary's downstream NHD trace (comid 1319596) first overlaps SALT CREEK's own downstream trace at index 1 (next-nearest candidate: ('MAINSTEM', 17))
ROARING FORK RIVER <-> COLORADO RIVER	tributary's downstream NHD trace (comid 3175612) first overlaps COLORADO RIVER's own downstream trace at index 0 (next-nearest candidate: none)
SWAMP DRAIN <-> GYPSUM CREEK	tributary's downstream NHD trace (comid 1319366) first overlaps GYPSUM CREEK's own downstream trace at index 0 (next-nearest candidate: ('MAINSTEM', 3))
WILLOW CREEK <-> ALKALI CREEK	tributary's downstream NHD trace (comid 1318884) first overlaps ALKALI CREEK's own downstream trace at index 1 (next-nearest candidate: ('MAINSTEM', 5))
SOUTH FORK EAGLE RIVER <-> MAINSTEM	tributary's downstream NHD trace (comid 1320966) first overlaps MAINSTEM's own downstream trace at index 3 (next-nearest candidate: ('HOMESTAKE CREEK', 9))
COLORADO RIVER <-> ROARING FORK RIVER	tributary's downstream NHD trace (comid 3175612) first overlaps ROARING FORK RIVER's own downstream trace at index 0 (next-nearest candidate: none)

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
ALKALI CREEK	SPRING CREEK	0.13	0.71	ambiguous -- tied earliest overlap at index 3: ['SPRING CREEK', 'MAINSTEM']
BEARD CREEK	LAKE CREEK	0.57	0.57	ambiguous -- tied earliest overlap at index 2: ['LAKE CREEK', 'MAINSTEM']
RUBE CREEK	MILK CREEK	0.76	2.53	ambiguous -- tied earliest overlap at index 1: ['MILK CREEK', 'MAINSTEM']
MILK CREEK	ALKALI CREEK	0.08	1.47	ambiguous -- tied earliest overlap at index 1: ['ALKALI CREEK', 'MAINSTEM']
WARREN GULCH CREEK	ALKALI CREEK	0.39	0.62	ambiguous -- tied earliest overlap at index 1: ['ALKALI CREEK', 'MAINSTEM']
RED CANYON CREEK	SPRING CREEK	0.08	0.12	ambiguous -- tied earliest overlap at index 1: ['SPRING CREEK', 'MAINSTEM']

4. Gage placement risk

1 gage(s) would currently fail placement (> 2.5mi from the nearest centerline anchor — same failure mode as the Clear Creek at Derby bug). Options: raise the cutoff (check it doesn't sweep in an unrelated stream first — see the Little Dry Creek case), or add a manual override.

gage	name	nearest stream	distance (mi)
WUREXDCO	WURTZ EXTENSION DITCH NEAR TENNESSEE PASS	SOUTH FORK EAGLE RIVER	2.74

41 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:07 from 23 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	5% of schematic structures have data

Independent check: PASS — 100.0000% agreement across 103,516 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.11% day-level agreement with USGS's own published records for the same gages, across 17 co-listed station(s) and 286,670 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.

23 gage(s) / 304,607 daily values (1910-10-01–2026-07-06); 521 structure(s) with diversion records; 2162 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. 16 gage(s) and 151 structure(s) report in 2026, but structure reporting only reached half its modern level around ~1951. 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)
1910s	1	0
1920s	1	0
1940s	3	0
1950s	4	208
1960s	8	0
1970s	10	244
1980s	10	268
1990s	12	239
2000s	16	132
2010s	14	141
2020s	15	143

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
▸ EAST FORK EAGLE RIVER NEAR CLIMAX, CO EAGCLICO	↓ decreasing	-39.9%	p=0.042	25	—
▸ EAGLE RIVER BELOW MILK CREEK NEAR WOLCOTT, CO EAGMILCO	↓ decreasing	-37.5%	p=0.002	21	~2017
▸ GORE CREEK AT MOUTH NEAR MINTURN, CO GORCRECO	↓ decreasing	-14.9%	p=0.006	31	~2011
▸ LAKE CREEK NEAR EDWARDS, CO LAKNEDCO	↓ decreasing	-14.0%	p=0.003	33	~2011
▸ EAGLE RIVER AT RED CLIFF, CO. EAGREDCO	↓ decreasing	-5.3%	p=0.000	97	~1952
▸ HOMESTAKE CREEK AT GOLD PARK, CO. HOMGOLCO	↓ decreasing	-4.9%	p=0.047	61	—

17 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: 5% of 694 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 (1950 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.

LAKE CREEK NEAR EDWARDS, CO: reach shifted from -122 cfs to -517 cfs summer mean (more losing, p=0.018, 33 yr) [sedimentary uplands: moderate groundwater connectivity -- gain/loss shifts can be real aquifer response; corroborate with nearby well records]
EAGLE RIVER BELOW GYPSUM, CO.: reach shifted from +1086 cfs to +94 cfs summer mean (more losing, p=0.000, 77 yr) [sedimentary plains/foothills: moderate groundwater connectivity -- gain/loss shifts can be real aquifer response; corroborate with nearby well records]
BEAVER CREEK AT AVON, CO: reach shifted from -4 cfs to -222 cfs summer mean (more losing, p=0.000, 49 yr) [sedimentary uplands: moderate groundwater connectivity -- gain/loss shifts can be real aquifer response; corroborate with nearby well records] [measurement-evolution caution: this shift co-moves with the growth of the gage/metering network (rho=0.65) -- part of it may be unaccounted water becoming accounted, not hydrologic change]
CROSS CREEK NEAR MINTURN, CO: reach shifted from +63 cfs to -94 cfs summer mean (more losing, p=0.000, 65 yr) [sedimentary uplands: moderate groundwater connectivity -- gain/loss shifts can be real aquifer response; corroborate with nearby well records]
HOMESTAKE CREEK AT GOLD PARK, CO.: reach shifted from -461 cfs to +44 cfs summer mean (more gaining, p=0.043, 60 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]

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

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

Cross-gage pattern fingerprint

Over the 63-year window with full coverage (1964–2026), the dominant shared pattern across 3 gage(s) explains 71% 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.

The basin's aquifer story, from 273 water-level measurements across 131 monitored well(s) (113 alluvial, 0 bedrock, rest unclassified) — plus 28 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.

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

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

BEAVER CREEK AT AVON, CO: 1 alluvial well(s) nearby

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

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.

69 reservoir(s) with 5,201 storage measurement(s), 1951–2025. Basin storage as of 2024-10-31 (the record's own end — reservoir records publish ~annually): 45,217 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
▸ HOMESTAKE PROJ RESERVOIR (3704516)	42,078	2024-10-31
▸ HOMESTAKE RESERVOIR (3703519)	38,278	1987-10-31
▸ EAGLE PARK RESERVOIR (3703699)	3,138	2024-10-01
▸ ROBINSON RESERVOIR (3703527)	1,967	2019-10-31
▸ BLACK LAKE (3703608)	527	2019-10-31
▸ CHALK MOUNTAIN RESERVOIR (3703513)	202	2019-10-31
▸ LEDE RESERVOIR (3703520)	183	2020-06-11
▸ BLACK LAKE NO 2 (3703510)	98	2019-10-31

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: 4157 across 2162 structure(s); 100 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 ~1951 — idleness that begins before then may be unreported use, not nonuse (flagged † below).

OHNECK NO 2 DITCH (3700738) (1917-05-01, 2.3 cfs decreed): last active 1951 — 69 years idle
PETERSON NO 4 DITCH (3700759) (1906-08-29, 0.2 cfs decreed): last active 1952 — 68 years idle
SHIVELY DITCH (3700802) (1892-11-01, 1.2 cfs decreed): last active 1953 — 67 years idle
BIGHORN PIPELINE (3700881) (1963-04-04, 1.6 cfs decreed): last active 1953 — 67 years idle
MAHONEY DITCH (3700690) (1927-04-01, 2.8 cfs decreed): last active 1955 — 65 years idle
NOTTINGHAM DITCH (93) (3700733) (1887-05-26, 2.0 cfs decreed): last active 1955 — 65 years idle
BIG SPRING (3700879) (1935-05-01, 0.1 cfs decreed): last active 1955 — 65 years idle
BEAVER MEADOWS DITCH (3700507) (1923-09-01, 1.1 cfs decreed): last active 1956 — 64 years idle
JOHNSON & HOWARD DITCH (3700666) (1900-05-14, 3.0 cfs decreed): last active 1956 — 64 years idle
WELLS NO 2 DITCH (3700852) (1930-05-01, 2.4 cfs decreed): last active 1956 — 64 years idle

Compliance screens (194 advisory flags)

Screened 369 of 2162 structures with rights (415 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.

NOTTINGHAM & PUDER DITCH (3700736): Observed p99 daily rate 55.5 cfs (max 55.5) exceeds total decreed absolute 24.6 cfs across 11400 recorded day(s). Structure holds an Augmentation-use decree -- diversions above the direct-flow decree can be lawful under plan operations; interpret with care.
COLUMBINE DITCH HDG 3 (3704641): Observed p99 daily rate 36.0 cfs (max 66.6) exceeds total decreed absolute 30.0 cfs across 22790 recorded day(s). Structure holds an Augmentation-use decree -- diversions above the direct-flow decree can be lawful under plan operations; interpret with care.
BOLTS DITCH (3700514): Observed p99 daily rate 31.7 cfs (max 31.7) exceeds total decreed absolute 30.0 cfs across 4392 recorded day(s). Structure holds an Augmentation-use decree -- diversions above the direct-flow decree can be lawful under plan operations; interpret with care.
TERRELL AND FORD DITCH (3700830): Observed p99 daily rate 27.6 cfs (max 31.5) exceeds total decreed absolute 23.8 cfs across 15370 recorded day(s).
COWEN SPRINGS (3700558): Observed p99 daily rate 26.5 cfs (max 26.5) exceeds total decreed absolute 3.0 cfs across 3148 recorded day(s).
CREAMERY DITCH (3700560): Observed p99 daily rate 26.5 cfs (max 28.8) exceeds total decreed absolute 21.6 cfs across 18331 recorded day(s). Structure holds an Augmentation-use decree -- diversions above the direct-flow decree can be lawful under plan operations; interpret with care.
EMPIRE ZINC CO PIPELINE (3700590): Observed p99 daily rate 23.4 cfs (max 23.4) exceeds total decreed absolute 16.0 cfs across 4394 recorded day(s).
EMPIRE ZINC CO PIPELINE (3700591): Observed p99 daily rate 23.4 cfs (max 23.4) exceeds total decreed absolute 1.0 cfs across 4392 recorded day(s).
C K P DITCH (3700545): Observed p99 daily rate 22.6 cfs (max 30.1) exceeds total decreed absolute 2.4 cfs across 20209 recorded day(s). Structure holds an Augmentation-use decree -- diversions above the direct-flow decree can be lawful under plan operations; interpret with care.
EAGLE DITCH (3700579): Observed p99 daily rate 21.2 cfs (max 21.2) exceeds total decreed absolute 13.2 cfs across 3240 recorded day(s).

Seniority (top structures by decreed rate)

Structure	Senior priority date	Rights	Decreed abs (cfs)	Conditional?
AVON WHITEWATER COURSE RICD BOB SR (3701416)	2005-12-31	1	1400.0	—
AVON WHITEWATER COURSE RICD BOB JR (3701417)	2005-12-31	1	1400.0	—
AVON WHITEWATER COURSE RICD BABY BOB (3701418)	2005-12-31	1	1400.0	—
TOWN OF VAIL WHITEWATER PARK STRUCTURE 1 (3701412)	2000-10-10	1	810.0	yes
TOWN OF VAIL WHITEWATER PARK STRUCTURE 2 (3701413)	2000-10-10	1	756.0	yes
TOWN OF VAIL WHITEWATER PARK STRUCTURE 3 (3701414)	2000-10-10	1	719.0	yes
HOMESTAKE PROJ TUNNEL (3704614)	1952-09-22	1	300.0	yes
HOMESTAKE PROJ CONDUIT-HOMESTAKE CREEK (3704643)	1952-09-22	1	181.9	yes
MIN FLOW EAGLE RIVER BRUSH CREEK TO COLO (3702012)	1980-03-17	1	130.0	—
MIN FLOW EAGLE RIVER LAKE CR TO BRUSH CR (3702059)	1980-03-17	1	110.0	—
MIN FLOW EAGLE RIVER GORE CR TO LAKE CR (3702041)	1980-03-17	1	85.0	—
WARREN E WURTS DITCH (3704648)	1929-06-08	1	85.0	—
HOMESTAKE PROJ CONDUIT-EAST FORK (3704644)	1952-09-22	1	74.6	yes
HOMESTAKE PROJ CONDUIT-FRENCH CREEK (3701253)	1952-09-22	1	62.2	yes
STRATTON AND CO DITCH (3700823)	1881-07-01	14	54.4	—

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.