Dataset Listing

National - Streamflow / Discharge - USGS and USDA Data Resources (1985-2017)

Includes Temperature, Specific Conductivity, Dissolved oxygen, pH for certain sites. Southern Sierra CZO does not have USGS gages, but it does include stream data from 2002 to 2015 on the USDA web site.

Variables:  Gage height, Discharge, Temperature, pH, Specific conductance

Date Range:  (1985-09-30 to 2017-08-01)

Dataset Creators/Authors:  USGS National Water Information System

Contact:  lmarini@illinois.edu

Field Area:   Boulder Creek Watershed | Santa Catalina Mountains | Jemez River Basin | Reynolds Creek Experimental Watershed | Susquehanna Shale Hills Critical Zone Observatory | Northeastern Puerto Rico and the Luquillo Mountains | Clear Creek Watershed | Sangamon River Basin | Calhoun Critical Zone Observatory | Providence Creek headwater catchments

Description
Keywords & XML
Citation
  • Description

    Links to USGS web services for all gages adjacent to all Critical Zone Observatories.
  • Keywords

    Hydrology, Gage height, Discharge, Temperature, pH, Specific conductance

    XML Metadata

    http://criticalzone.org/sierra/data/xml-metadata-test/6108/

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

  • Citation for This Dataset

    U.S. Geological Survey, 2016, National Water Information System data available on the World Wide Web (USGS Water Data for the Nation), accessed [June 10, 2012], at URL [http://waterdata.usgs.gov/nwis/].

    Citation for This Webpage

    USGS National Water Information System (2017). "CZO Dataset: National - Streamflow / Discharge (1985-2017) - USGS and USDA Data Resources." Retrieved 21 Sep 2017, from http://criticalzone.org/sierra/data/dataset/6108/

Data

IML - USGS SANGAMON RIVER AT FISHER, IL - Discharge, Gage Height

(0910)   Data Level 1

IML - USGS SANGAMON RIVER AT MONTICELLO - Discharge, Gage Height

(2000)   Data Level 1

IML - USGS SANGAMON RIVER AT DECATUR, IL - Discharge, Gage Height

(3540)   Data Level 1

Boulder - USGS FOURMILE CREEK NEAR CRISMAN, CO - Discharge

(7410)   Data Level 1

Boulder - USGS FOURMILE CREEK AT ORODELL, CO - Discharge, Gage Height

(7500)   Data Level 1

Boulder - USGS BOULDER CREEK NEAR BOULDER, CO - Discharge, Gage Height

(0200)   Data Level 1

Boulder - USGS BOULDER CREEK NEAR LONGMONT, CO - Discharge, Gage Height

(0500)   Data Level 1

Catalina-Jemez - USGS JEMEZ RIVER - Discharge, Gage Height

(4000)   Data Level 1

Catalina-Jemez - USGS SABINO CREEK NEAR TUCSON, AZ - Discharge, Gage Height, Precipitation

(4000)   Data Level 1

Calhoun - USGS BROAD BELOW NEAL SHOALS, SC - Discharge, Gage Height

(4493)   Data Level 1

Calhoun - USGS BROAD RIVER NEAR CARLISLE, SC - Discharge, Gage Height, Temperature, Specific Conductivity, Dissolved oxygen, pH

(6500)   Data Level 1

Calhoun - USGS ENOREE RIVER AT WHITMIRE, SC - Discharge, Gage Height, Temperature, Specific Conductivity, Dissolved oxygen, pH

(0700)   Data Level 1

Calhoun - USGS TYGER RIVER NEAR DELTA, SC - Discharge, Gage Height, Temperature, Specific Conductivity, Dissolved oxygen, pH

(0105)   Data Level 1

Shale Hills - USGS Little Juniata River at Spruce - Discharge, Gage Height

(8000)   Data Level 1

Shale Hills - USGS Shaver Creek Petersburg, PA - Discharge

(8500)   Data Level 1

Luquillo - USGS RIO SABANA AT SABANA, PR - Discharge, Gage Height

(7000)   Data Level 1

Luquillo - USGS RIO MAMEYES NR SABANA, PR - Discharge, Gage Height

(5500)   Data Level 1

Luquillo - USGS QUEBRADA SONADORA NR EL VERDE, PR - Discharge, Gage Height

(3440)   Data Level 1

Luquillo - USGS RIO BLANCO NR FLORIDA, PR - Discharge, Gage Height

(6000)   Data Level 1

Eel - USGS ELDER C NR BRANSCOMB CA - Temperature, Discharge, Suspended sediment (SS) concentration, SS discharge, Streamflow, Lab measure

(amp;)   Data Level 1

Eel - USGS SF EEL R A LEGGETT CA - Temperature, Discharge, Streamflow, Field / Lab measurements

(amp;)   Data Level 1

Sierra - Kings River Experimental Watersheds - Discharge

(0037)   Data Level 1

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.

Explore Further

data |

Explore Further