My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
SPDSS_Task43-2_Phase2_DenverBasinRegionAquiferProperty
CWCB
>
Decision Support Systems
>
DayForward
>
SPDSS_Task43-2_Phase2_DenverBasinRegionAquiferProperty
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/17/2013 9:20:52 AM
Creation date
6/11/2008 11:57:10 AM
Metadata
Fields
Template:
Decision Support Systems
Title
SPDSS Task 43.2 - Denver Basin Region Aquifer Property - Phase 2
Description
This Technical Memorandum was undertaken under Task 43.2, and summarizes the compilation, analysis and mapping of existing published aquifer property data for the Denver Basin Region.
Decision Support - Doc Type
Task Memorandum
Date
2/13/2006
DSS Category
Groundwater
DSS
South Platte
Basin
South Platte
Contract/PO #
C153953
Grant Type
Non-Reimbursable
Bill Number
SB01-157, HB02-1152, SB03-110, HB04-1221, SB05-084, HB06-1313, SB07-122
Prepared By
CDM
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
67
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
This will include accounting for the K of the non-sandstone and siltstone <br />materials, smoothing, and addition of control points in areas where data are <br />sparse to develop K values appropriate for groundwater modeling <br />Aquifer storage coefficient data are still unavailable in the Upper and Lower <br />Dawson and the Upper Arapahoe Aquifers. Storage coefficient point values in <br />other aquifers are generally clustered in small areas. This aquifer property data <br />is needed when evaluating water supply and in undertaking transient (time- <br />dependent) groundwater modeling, so the lack of this data could be a source of <br />uncertainty in evaluating the modeling results, especially with respect to <br />pumping effects. <br />5.0 Recommendations <br />• When aquifer property data are collected by well owners as part of their routine <br />well installation and testing, the State should request aquifer pumping test <br />results and other aquifer property data, such as core sample analyses, as part of <br />the well permitting process <br />• Aquifer property and specific capacity data from well construction and testing <br />reports should be entered into HydroBase when they are received. <br />• The HydroBase structure should be revised to accommodate multiple laboratory <br />test data values from a single borehole, and to identify data from confining units <br />to provide a more comprehensive database for aquifer property data. Both sets <br />of data could be a benefit in groundwater modeling. <br />• The number of allowable characters should be expanded in the "data source" <br />and the "ptsource" fields in the Wells and Pumping test tables, respectively, to <br />allow a bibliographic reference (up to approximately 240 characters) rather than <br />the 10 characters currently allowed. <br />• If transmissivity and hydraulic conductivity data derived from aquifer pumping <br />tests are available, they should be used instead of the specific capacity-derived <br />data; and likewise, if specific capacity-derived data are available, they should be <br />used instead of laboratory test-derived data. <br />• Encourage collection of multi-well aquifer test data, where feasible, from which <br />high quality aquifer property data (T, K, and S/Sy) can be obtained. This could <br />be accomplished during the well permitting process with a request that well <br />operators installing replacement wells defer abandonment of their original well <br />until the new replacement well can be used as a pumping well in an aquifer test <br />during which the original well is used as an observation well. <br />SPDSS Phase 2 Task 43.2 TM -Final 27 <br />2/ 13/ 2006 <br />
The URL can be used to link to this page
Your browser does not support the video tag.