Dataset Listing

Jemez River Basin - Streamflow / Discharge (2007-2018)

Streamflow data for Jemez River Basin

Variables:  Streamflow

Date Range:  (2007-09-30 to 2018-09-30)

Dataset Creators/Authors:  Peter Troch; Patrick Broxton; Xavier Zapata-Rios; Mark Losleben; Matej Durcik

Contact:  Peter Troch, Department of Hydrology and Water Resources, University of Arizona, 1133 E James E. Rogers Way Tucson, AZ 85721, patroch@hwr.arizona.edu

Field Area:   Jemez River Basin

Description
Keywords & XML
Citation
Publications
Acknowledgements
  • Description

    30 minute and daily streamflow data measured and computed for flumes located around the Redondo Peak (Valles Caldera National Preserve). Streamflow are derived using pressure measurements in the bottom of stilling wells to infer water levels and hence discharge in the flumes. Three types of flumes are installed: Tracom inc. 6" and 12" Parshall Flumes, and 12" 45-degree Trapezoidal Flume.

    Comments
    Data are provisional and may be subject to revision.
    Data for 2007-2008 were computed by Patrick Broxton, Graduate assistant, University of Arizona, broxtopd@hwr.arizona.edu.
    Data for 2009-2010 were computed by Adrian Harpold, postdoc University of Arizona, harpold@email.arizona.edu.
    Data from 2011 were computed by Xavier Zapata, Graduate student, University of Arizona, xavierzapata@email.arizona.edu.
    Streamflow data have not been computed for the Lower Jaramillo (FLUME_01) since wy 2009.
    Streamflow data have not been computed for the Lower Redondo (FLUME_02) and Redondo Meadow (FLUME_05) since wy 2011.
    Streamflow data have not been computed for the Upper Redondo (FLUME_06) since wy 2012.
    Added new flume Upper La Jara (FLUME_08) in wy 2012.
    Both La Jara flumes and History Grove flume were damaged after the Thompson Ridge fire in July 2013.
    Lower La Jara and History Grove flumes were reinstalled in November 2016.
    Data from 11/10/2012 to 3/10/2017 are missing for MC ZOB Flume.
  • Keywords

    hydrology, streamflow, Jaramillo Creek, La Jara Creek, History Grove, Redondo Creek, Valles Caldera, Jemez Mountains, New Mexico

    XML Metadata

    criticalzone.org/national/data/xml-metadata-test/2504/

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

  • Citation for This Dataset

    The following acknowledgment should accompany any publication or citation of these data - Logistical support and/or data were provided by the NSF-supported Jemez River Basin and Santa Catalina Mountains Critical Zone Observatory, EAR-0724958 and EAR-1331408.

    Citation for This Webpage

    Peter Troch; Patrick Broxton; Xavier Zapata-Rios; Mark Losleben; Matej Durcik (2018). "CZO Dataset: Jemez River Basin - Streamflow / Discharge (2007-2018)." Retrieved 21 May 2019, from http://criticalzone.org/national/data/dataset/2504/

  • Publications

    Primary Publications

    2009

    On the role of aspect to quantify water transit times in small mountainous catchments. Broxton P. D., Troch P. A., and Lyon S. W. (2009): Water Resources Research 45: W08427

  • Acknowledgements

    Funding

    National Science Foundation EAR-0724958
    National Science Foundation EAR-1331408

Data

Sites - Methods

(mez/)   Data Level 0

Jemez River Basin - 30-minute Streamflow Data for Water Year 2008

(.csv)   Data Level 2,  Metadata

Jemez River Basin - 30-minute Streamflow Data for Water Year 2009

(.csv)   Data Level 2,  Metadata

Jemez River Basin - 30-minute Streamflow Data for Water Year 2010

(.csv)   Data Level 2,  Metadata

Jemez River Basin - 30-minute Streamflow Data for Water Year 2011

(.csv)   Data Level 2,  Metadata

Jemez River Basin - 30-minute Streamflow Data for Water Year 2012

(.csv)   Data Level 2,  Metadata

Jemez River Basin - 30-minute Streamflow Data for Water Year 2013

(.csv)   Data Level 2,  Metadata

Jemez River Basin - 30-minute Streamflow Data for Water Year 2014

(.csv)   Data Level 2,  Metadata

Jemez River Basin - 30-minute Streamflow Data for Water Year 2015

(.csv)   Data Level 2,  Metadata

Jemez River Basin - 30-minute Streamflow Data for Water Year 2016

(.csv)   Data Level 2,  Metadata

Jemez River Basin - 30-minute Streamflow Data for Water Year 2017

(.csv)   Data Level 2,  Metadata

Jemez River Basin - 30-minute Streamflow Data for Water Year 2018

(.csv)   Data Level 2,  Metadata

Jemez River Basin - MCZOB Flume Flow Data for water years 2011-2013

(.csv)   Data Level 2,  Metadata

Jemez River Basin - MCZOB Flume Flow Data for water years 2017-2018

(7-18)   Data Level 2,  Metadata

Jemez River Basin - Daily Streamflow Data for Water Year 2008 - 2010

(.csv)   Data Level 2,  Metadata

Jemez River Basin - Daily Streamflow Data for Water Year 2011 - 2012

(.csv)   Data Level 2,  Metadata

Data Use Policy
Data Sharing Policy
Research Groups/Foci
  • 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.

  • Research Groups/Foci