Variables: TmStamp_UTC, Stage_m, Water_TempC, Cond (conductivity), spc_cond (specific conductivity), dischg_m3s_m3s (discharge in cubic meters per second), dischg_cfs (discharge in cubic feet per second)
Date Range: (2015-10-22 to 2018-08-07. 2015 2015-11-03 to 2015-11-19: no flow and building up ice 2015-11-20 to 2015-12-01: ice 2016 2016-12-15 : ice 2016-12-20 to 2016-12-25 : ice 2016-01-05 to 2016-01-08: ice 2016-01-09 to 2016-01-10: ice 2016-01-13 to 2016-01-14: ice 2016-01-18 to 2016-01-31: ice 2016-02-11 to 2016-02-21: ice 2016-04-20: debris buildup 2016-06-10 to 2016-11-30: no flow – summer was dry 2017 2017-01-07 to 2017-01-12: ice 2017-05-03: debris buildup 2017-05-17 to 2017-05-29: debris buildup 2017-06-08 to 2017-06-16: debris buildup 2017-06-29 to 2017-07-11: debris buildup 2017-10-17: erroneous data spikes 2017-11-20 to 2017-11-21: ice 2017-12-13 to 2018-01-01: ice )
Dataset Creators/Authors: Susan Brantley
Contact: Dr. Susan Brantley, Professor of Geosciences, The Pennsylvania State University, 2217 Earth and Environmental Systems Institute, University Park, PA, 16802, 814.865.1619, email@example.com.
hydrology, stream flow, water, discharge, stage, conductivity, specific conductivity, stream water temperature
XML is in ISO-19115 geographic metadata format, compatible with ESRI Geoportal Server.
The following acknowledgment should accompany any publication or citation of these data: Logistical support and/or data were provided by the NSF-supported Shale Hills Susquehanna Critical Zone Observatory.
Susan Brantley (2018). "CZO Dataset: Shale Hills - Streamflow / Discharge, Groundwater Temperatures, Electrical Conductivity (2015-2018)." Retrieved 19 Jun 2019, from http://criticalzone.org/national/data/dataset/6786/
(html) Data Level 1, Metadata
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.