These dataset listings are out of date and have been archived.

See the updated listings on HydroShare.org >

---

Sangamon River Basin

3,690 km², 180-291 m elevation, 11 °C, 1000 mm/yr

The Sangamon River Basin includes a broad range of variations typical of the glaciated Midwest, which offer an opportunity to better understand the critical zone in this region. The basin is characterized by low-relief landscapes with poorly drained soils. The hydrological and biogeochemical cycles are strongly affected by freeze–thaw cycles and artificial drainage systems. The landscape is covered with patchy, thin loess (<1.5 m). This basin has a poorly integrated, natural drainage network with extensive areas of poorly drained soils. Weathering profiles are relatively thin and usually grade to unweathered fine-grained glacial till within 5 m of the land surface. Soil patterns generally reflect glacial depositional patterns, except where modified by stream processes in valleys.

National - Streamflow / Discharge - USGS and USDA Data Resources (1985-2017)
22 components  •   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 (1660 - 2115 m elevation)  •   Hydrology  •   USGS National Water Information System

---

Clear Creek Watershed

270 km², 197-248 m elevation, 9 °C, 889 mm/yr

The Clear Creek, Iowa, watershed covers approximately 270 km2 in East Central Iowa and joins the Iowa River in Coralville, Iowa. Clear Creek is representative of most U.S. Midwestern watersheds with regards to land use (predominantly agricultural), soil type/order (Alfisols and Mollisols), and climate (humid-continental). The combination of extensive agricultural activities, increased urbanization, highly erodible soils, and a humid climate on the steep slopes within the watershed have influenced the erosion processes in the watershed.

National - Streamflow / Discharge - USGS and USDA Data Resources (1985-2017)
22 components  •   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 (1660 - 2115 m elevation)  •   Hydrology  •   USGS National Water Information System

---

Minnesota River Basin

44,000 km², 210-294 m elevation, 5 °C, 747 mm/yr

The Minnesota River flows more than 335 miles from its source near the Minnesota-South Dakota border to its confluence with the Mississippi River at Minneapolis/St. Paul. It winds through diverse landscapes and drains nearly 20 percent of Minnesota (16,770 square miles total, 14,840 in Minnesota). Agriculture, primarily corn and soybean production, accounts for the majority of the basin’s land use. As the river enters the Twin Cities Metropolitan area, the basin is characterized by densely populated urban landscapes. The Minnesota River has been cited as one of the most polluted rivers in the state and the nation. In 2008, it was listed on American Rivers top 10 most endangered rivers in the United States. It is the focus of a major restoration effort by local, state, and federal agencies, as well as citizen and nonprofit groups.

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.