Dataset Listing

Gordon Gulch Upper - Well Water Levels - GGU_Slug_Test (2016)

GGU_GW_1, GGU_GW_2, GGU_GW_6

Variables:  None

Date Range:  (2016-01-01 to 2016-01-02)

Dataset Creators/Authors:  Steven Henning

Contact:  Steven Henning (steven.henning@colorado.edu)

Field Area:   Gordon Gulch

Description
Keywords & XML
Citation
  • Description

    A series of slug tests were performed at groundwater monitoring wells in upper Gordon Gulch. The spefic wells tested were GGU_GW1, GGU_GW2, GGU_GW3, GGU_GW4, GGU_GW5, and GGU_GW6. Slug tests were perfomed by Steven Henning, a master's candidate at CU Boulder. Tests were performed on 8/6-7/2015 and 9/12-13/015. The tests were perfomed to determine the hydraulic conductivity of the aquifer material around the monitoring wells.

    Comments
    Slug testes were performed fl]ollowing ASTM D4041 and ASTM D4044 standards. Materials used include 3 weighted slugs of various volumes, electric tape, an In-Situ Level Troll 700 pressure transducer, and An In-Situ RuggerReader field computer. To initate a falling head slug test, depth to water in each well was first checked with an electric tape. Then the pressure transducer was lowered into the well to a depth below the estimated elevation of the bottom of the slug that was to be dropped. Then the depth to water was remeasured witht the electric tape and entered into the RuggedReader to calibrate the depth to water with the transducer. After calibrating the pressure transducer, active logging of the depth to water was started to get a steady baseline recorded. After approximately 30 seconds of background recording, the slug was rapidly lowered intothe well to create an instantaneous rise in water level and head within the well. Initial displacement was noted and the water level was allowed to begin recovering. After the change in head had be reduced to 10% of the inital change, the test and water level recoding was stopped. This process is repeated for a rising head test, with the exception of the slug being rapidly withdrawn from the well rather than being lowered into it. In some cases the testing of the well was stopped before the water level recoved to within 10% of its starting value to to time constraints or inclement weather. The data gathered from the pressure transducers has not been edited, but at least 2 of the 26 tests performed (Well4, Falling Test 2; Well6, Rising Test 3) show instrument error that should be accounted for in some way before using the data.
  • Keywords

    None

    XML Metadata

    criticalzone.org/boulder/data/xml-metadata-test/6541/

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

  • Citation for This Dataset

    None

    Citation for This Webpage

    Steven Henning (2016). "CZO Dataset: Gordon Gulch Upper - Well Water Levels (2016) - GGU_Slug_Test." Retrieved 21 Mar 2019, from http://criticalzone.org/boulder/data/dataset/6541/

Data

Upper Gordon Gulch Wells - GGU_Slug_Tests_Results

(.pdf)   Data Level 0

Upper Gordon Gulch Wells - GGU_Slug_Raw_Data

(.zip)   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 http://www.datacite.org/whycitedata). 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 http://www.datacite.org/whycitedata.


CZO Field Areas

 

Explore Further

data |

Explore Further