Dataset Listing

Boulder Creek catchment and vicinity - Geology, Geomorphology (2006)

Geomorphic inferences from regolith thickness, chemical denudation and CRN erosion rates near the glacial limit

Variables:  OBJECT_ID & NEW_ID (identification index), WELL_NUMBE (well number assigned by the Colorado Department of Water Resources), POINT_X (UTM Northing – NAD 1983 UTM Zone 13N), POINT_Y (UTM Easting – NAD 1983 UTM Zone 13N), QUADRANGLE (Colorado state 7.5' quadrangle), TOWNSHIP (township notation in quadrangle), RANGE (range notation in quadrangle), SECTION (section number in quadrangle), QUARTER (quarter location within QUARTER_1), QUARTER_1 (quarter location within section), OVERBURDEN & OVRBRDN_M (overburden thickness in ft & m), ALLUVIAL_ & ALLUVIAL_M (alluvial thickness in ft & m), HIGHLY & HIGHLY_M (highly weathered thickness in ft & m), TOTAL & TOTAL_M (total weathered thicknessin ft & m), DEPTH & DEPTH_M (depth to bedrock in ft & m), MINIMUM & MINMM_M (minimum drilled well depth in ft & m), DIST_FLTS (using geologic map of Colorado by Green (1992) distance to nearest fault or dike in m), DIST_STREAMS (using geologic map of Colorado by Green (1992) distance to nearest third-order stream (or larger) in m), ROCK_TYPE (code corresponds to geologic unit in geologic map of Colorado by Green (1992): 1 = sedimentary units; 2 = Od; 3 = Ogo; 4 = Yg; 5 = Xg; 6 = Xb; 7 = Xq; 8 = Xfh; 9 = Tki; 10 = Tgv; 11 = water), SLOPE (approximate local slope in degrees), NOTES (well drillers' notes)

Standard Variables:  Alluvium depth|Water depth|Distance|Groundwater Depth|Recorder code

Date Range:  (2006-01-01 to 2006-12-31)

Dataset Creators/Authors:  David P. Dethier; Eli D. Lazarus


Field Area:   Boulder Creek Watershed

Keywords & XML
  • Description

    These data accompany the analysis of regolith weathering across ~940 km2 of the Front Range (Colorado, USA) described by Dethier & Lazarus (2006).

    Collected data from 1872 paper records of well-drillers' logs held on file at the Colorado Department of Water Resources (Denver office). We used every interpretable record from the Allens Park, Eldorado Springs, Gold Hill, Nederland, Tungsten, and Ward quadrangles. We recorded the thickness of overburden, alluvium, and highly weathered regolith, along with the total weathered thickness, depth to fresh bedrock, total well depth, and any drillers’ notes. We then digitized well locations (and their associated data) on topographic quadrangles in ESRI ArcMap. The maximum probable location error for any well in the dataset is the area of a 1/16 section (approximately 0.16 km2). See Dethier & Lazarus (2016) a detailed description of the methods.
  • Keywords

    regolith, weathering

    XML Metadata

    XML is in ISO-19115 geographic metadata format, compatible with ESRI Geoportal Server.

  • Citation for This Dataset

    David P. Dethier, Eli D.Lazarus. 2006 Geomorphic inferences from regolith thickness, chemical denudation and CRN erosion rates near the glacial limit, Boulder Creek catchment and vicinity, Colorado, Geomorphology, Volume 75, Issues 3–4, May 2006, Pages 384-399

    Citation for This Webpage

    David P. Dethier; Eli D. Lazarus (2006). "CZO Dataset: Boulder Creek catchment and vicinity - Geology, Geomorphology (2006)." Retrieved 08 Apr 2020, from


Boulder Creek catchment and vicinity - regolith thickness, chemical denudation and CRN erosion rates

(59/1)   Data Level 0

Data Use Policy
Data Sharing Policy
  • Data Use Policy

    DRAFT v.0.4.0

    1. Use our data freely. All CZO Data Products* except those labelled Private** are released to the public and may be freely copied, distributed, edited, remixed, and built upon under the condition that you give acknowledgement as described below. Non-CZO data products — like those produced by USGS or NOAA — have their own use policies, which should be followed.

    2. Give proper citation and acknowledgement. Publications, models and data products that make use of these datasets must include proper citation and acknowledgement. Most importantly, provide a citation in a similar way as a journal article (i.e. author, title, year of publication, name of CZO “publisher”, edition or version, and URL or DOI access information. See Also include at least a brief acknowledgement such as: “Data were provided by the NSF-supported Southern Sierra Critical Zone Observatory” (replace with the appropriate observatory name).

    3. Let us know how you will use the data. The dataset creators would appreciate hearing of any plans to use the dataset. Consider consultation or collaboration with dataset creators.

    *CZO Data Products.  Defined as a data collected with any monetary or logistical support from a CZO.

    **Private. Most private data will be released to the public within 1-2 years, with some exceptionally challenging datasets up to 4 years. To inquire about potential earlier use, please contact us.

  • Data Sharing Policy

    DRAFT v.0.2.5

    All CZO investigators and collaborators who receive material or logistical support from a CZO agree to:

    1. Share data privately within 1 year. CZO investigators and collaborators agree to provide CZO Data Products* — including data files and metadata for raw, quality controlled and/or derived data — to CZO data managers within one year of collection of samples, in situ or experimental data. By default, data values will be held in a Private CZO Repository**, but metadata will be made public and will provide full attribution to the Dataset Creators†.

    2. Release data to public within 2 years. CZO Dataset Creators will be encouraged after one year to release data for public access. Dataset Creators may chose to publish or release data sooner.

    3. Request, in writing, data privacy up to 4 years. CZO PIs will review short written applications to extend data privacy beyond 2 years and up to 4 years from time of collection. Extensions beyond 3 years should not be the norm, and will be granted only for compelling cases.

    4. Consult with creators of private CZO datasets prior to use. In order to enable the collaborative vision of the CZO program, data in private CZO repositories will be available to other investigators and collaborators within that CZO. Releasing or publishing any derivative of such private data without explicit consent from the dataset creators will be considered a serious scientific ethics violation.

    * CZO Data Products. Defined as data collected with any monetary or logistical support from a CZO. Logistical support includes the use of any CZO sensors, sampling infrastructure, equipment, vehicles, or labor from a supported investigator, student or staff person. CZO Data Products can acknowledge multiple additional sources of support.

    ** Private CZO Repository. Defined as a password-protected directory on each CZO’s data server. Files will be accessible by all investigators and collaborators within the given CZO and logins will be maintained by that local CZO’s data managers. Although data values will not be accessible by the public or ingested into any central data system (i.e. CUAHSI HIS), metadata will be fully discoverable by the public. This provides the dual benefit of giving attribution and credit to dataset creators and the CZO in general, while maintaining protection of intellectual property while publications are pending.

    † Dataset Creators. Defined as the people who are responsible for designing, collecting, analyzing and providing quality assurance for a dataset. The creators of a dataset are analogous to the authors of a publication, and datasets should be cited in an analogous manner following the emerging international guidelines described at

CZO Field Areas


CZO Authors


Geomorphology article

Explore Further

data |

Explore Further