My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Tamarack Negotiation with Boulder/Centennial
CWCB
>
Water Supply Protection
>
DayForward
>
1001-2000
>
Tamarack Negotiation with Boulder/Centennial
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/26/2010 4:37:47 PM
Creation date
6/8/2009 10:31:28 AM
Metadata
Fields
Template:
Water Supply Protection
File Number
8461.400
Description
SPWRAP
State
CO
Basin
South Platte
Water Division
1
Date
9/18/2008
Author
Steve Sims
Title
Tamarack Negotiation with Boulder/Centennial
Water Supply Pro - Doc Type
Court Documents
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
5
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
Mary created depletion curves using the different leakance numbers and found that while there <br />was not much of a difference between 400 and 2.6, but there was between 2.6 and 0.011 (See <br />Leakage comparison chart.pd fl. <br />To give a perspective on how this factor fits with stream leakance used in other recent cases, <br />Mary contracted with Calvin Miller to create a table comparing the various cases in District 64 <br />(Millercomparison table.pd fl. This table does not have the most recent 120 feet per day figure <br />from the latest Logan Well Users case. <br />Finally, yesterday Mary prepared an analysis that looked at the impact on the volume of recharge <br />using both a 20 foot per day and a 2.6 foot per day stream leakance. This analysis <br />indicates <br />Summary. Using the 2.6 foot Boulder/Centennial stream leakance number will result in a lesser <br />amount of recharge accretions, but not a significantly less number. If Boulder/Centennial would <br />accept 2.6, 1 recommend settlement.
The URL can be used to link to this page
Your browser does not support the video tag.