Hydrohistorian
Laramie River
Bootstrap review report — d1_wd48_laramie_river
Generated 2026-08-13 22:06 UTC for Division 1 / Water District 48.
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: LARAMIE 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 |
|---|---|
| LARAMIE RIVER (assumed mainstem) | 16 |
| MCINTYRE CREEK | 7 |
| JIMMY CREEK | 5 |
| LA GARDE CREEK | 4 |
2. Diversion / return classification
Auto-classified from structureType + name patterns: 59 diversions, 0 returns, 2 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)
None flagged — no unclassified structure's decreed water right clearly disagreed with its current classification (checked up to the API-budget cap; see bootstrap.py's cross_check_classification for the cap).
3. Suspected nested tributaries
None flagged — every tributary candidate is clearly closer to the mainstem than to any other tributary.
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) |
|---|---|---|---|
| SKYDCLCO | SKYLINE DITCH AT CHAMBERS LAKE | MAINSTEM | 3.46 |
2 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:19 from 6 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 | current | newest gage reading is 6 day(s) old |
| diversion record | stale | newest diversion record is 658 day(s) old (DWR publishes ~1 year in arrears) |
| structure coverage | sparse | 22% of schematic structures have data |
Independent check: PASS — 100.0000% agreement across 116,356 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 3 co-listed station(s) and 44,121 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.
6 gage(s) / 171,319 daily values (1904-07-01–2026-08-14); 61 structure(s) with diversion records; 143 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. 4 gage(s) and 52 structure(s) report in 2026, but structure reporting only reached half its modern level around ~1974. 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 | 1 | 0 |
| 1920s | 2 | 0 |
| 1930s | 4 | 0 |
| 1940s | 4 | 0 |
| 1950s | 4 | 0 |
| 1960s | 4 | 0 |
| 1970s | 5 | 50 |
| 1980s | 4 | 47 |
| 1990s | 5 | 47 |
| 2000s | 5 | 51 |
| 2010s | 5 | 52 |
| 2020s | 5 | 52 |
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 |
|---|---|---|---|---|---|
|
▸
JOE WRIGHT CREEK ABOVE JOE WRIGHT RESERVOIR, CO JOECRECO |
no clear trend | +9.1% | p=0.052 | 45 | ~1989 |
5 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: 22% of 72 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 (454 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.
No reach shows a statistically significant long-term gain/loss shift.
Cross-gage pattern fingerprint
Not enough gages with a long enough common-coverage window yet to fingerprint shared patterns.
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: 159 across 143 structure(s); 0 structure(s) carry 0 court-case references.
Compliance screens (19 advisory flags)
Screened 56 of 143 structures with rights (57 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.
- HILLS DITCH (4800512): Observed p99 daily rate 29.2 cfs (max 31.8) exceeds total decreed absolute 11.0 cfs across 3766 recorded day(s).
- WRIGHT DITCH 2 (4800508): Observed p99 daily rate 24.6 cfs (max 29.1) exceeds total decreed absolute 15.0 cfs across 6420 recorded day(s).
- PARKER DITCH (4800506): Observed p99 daily rate 23.7 cfs (max 37.2) exceeds total decreed absolute 14.1 cfs across 5392 recorded day(s).
- HANCE DITCH (4800566): Observed p99 daily rate 23.0 cfs (max 23.4) exceeds total decreed absolute 19.4 cfs across 1914 recorded day(s).
- GRACE CREEK DITCH (4800565): Observed p99 daily rate 20.3 cfs (max 22.6) exceeds total decreed absolute 19.4 cfs across 9720 recorded day(s).
- MANSFIELD DITCH (4800518): Observed p99 daily rate 20.1 cfs (max 35.5) exceeds total decreed absolute 15.6 cfs across 6594 recorded day(s).
- LAMB DITCH (4800542): Observed p99 daily rate 19.9 cfs (max 24.3) exceeds total decreed absolute 18.9 cfs across 8412 recorded day(s).
- MARTIN DITCH 1 (4800509): Observed p99 daily rate 19.1 cfs (max 44.2) exceeds total decreed absolute 15.5 cfs across 6134 recorded day(s).
- LA GARDE DITCH 1 (4800558): Observed p99 daily rate 17.5 cfs (max 22.9) exceeds total decreed absolute 15.4 cfs across 4160 recorded day(s).
- UPPER HILLS DITCH (4800511): Observed p99 daily rate 17.4 cfs (max 23.8) exceeds total decreed absolute 10.0 cfs across 4788 recorded day(s).
Seniority (top structures by decreed rate)
| Structure | Senior priority date | Rights | Decreed abs (cfs) | Decreed abs (AF) | Conditional? |
|---|---|---|---|---|---|
| LARAMIE RIVER TUNNEL SYS (4800576) | 1902-08-25 | 1 | 300.0 | 0 | — |
| LARAMIE RIVER DITCH (4800577) | 1891-08-07 | 1 | 300.0 | 0 | — |
| SAND CREEK DITCH SYSTEM (4800572) | 1899-06-15 | 1 | 288.0 | 0 | — |
| RAWAH LOWER SUPPLY DITCH (4800500) | 1902-08-25 | 1 | 275.0 | 0 | — |
| RAWAH DITCH LAR R SYS (4800582) | 1902-08-25 | 1 | 225.0 | 0 | — |
| BOB CREEK DITCH DIVR (4800573) | 1897-09-24 | 1 | 60.0 | 0 | — |
| MCINTYRE DITCH LAR R SYS (4800581) | 1902-08-25 | 1 | 40.0 | 0 | — |
| TIMOTHY DITCH (4800507) | 1904-07-05 | 1 | 34.4 | 0 | — |
| YELTON DITCH (4800514) | 1882-07-01 | 1 | 30.1 | 0 | — |
| JIMMY CREEK DITCH (4800553) | 1884-06-01 | 3 | 29.9 | 0 | — |
| MANSFIELD DITCH 3 (4800580) | 1904-09-01 | 1 | 29.4 | 0 | — |
| LONE TREE DITCH (4800535) | 1894-10-24 | 1 | 25.0 | 0 | — |
| MANSFIELD DITCH 2 (4800519) | 1880-06-01 | 2 | 21.7 | 0 | — |
| MARTIN DITCH 2 (4800510) | 1887-04-30 | 2 | 20.5 | 0 | — |
| DAVY DITCH (4800531) | 1900-09-15 | 1 | 20.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
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 17–Aug 23 ⇅ |
% Hist Median ⇅ | Rank ⇅ | Δ1wk ⇅ | Δ4wk ⇅ | Yrs ⇅ | Status ⇅ |
|---|---|---|---|---|---|---|---|---|
| CAPDCPCO | CAMERON PASS DITCH NEAR CAMERON PASS | 0.0 | 0% | 0 | +0 | +0 | 0.0 | NO_DATA |
| LARRIVCO | LARAMIE RIVER NEAR GLENDEVEY, CO. | 15.6 | 41% | 0 | -2 | -23 | 120.3 | OK |
| LAPTUNCO | LARAMIE POUDRE TUNNEL @ 10 FT PARSHALL FLUME | 11.9 | 70% | 42 | -4 | -10 | 96.5 | OK |
Call details in gantt above
2 alert(s) · 1 warning(s) · 3 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.