Flux-PIHM (Shi and Davis, 2013) was applied in August 2015 to reanalysis discharge in Shale Hills catchment. Flux-PIHM is a fully coupled land surface hydrologic model, which can be used to reproduce discharge, groundwater level, soil water content in different soil layers, snow depth, evapotranspiration, etc. This file present estimation of discharge and related hydrologic processes from Jan 2008 to Aug 2015 based on national databases and local measurement, in order to provide a continuous discharge estimation and to be a supplement of data in the case of data missing from field measurements.
Soil, and Bedrock Data: Field campaign in 2003(Lin et al. 2006; Lin 2006); Soil Survey Geographic;
Vegetation type: National Land Cover Database;
Surface Elevation: USGS NED;
Forcing data: NLDAS, SURFRAD, MODIS (Corrected by local flux tower data):
TMP/SURFRAD (Corrected by Local Flux Tower data; For missing Data, use NLDAS)
RH/SURFRAD (Corrected by Local Flux Tower data; For missing Data, use NLDAS)
SOLAR/SURFRAD (For missing Data, use NLDAS)
LONGWV/SURFRAD (For missing Data, use NLDAS)
PRES/SURFRAD (Corrected by Local Flux Tower data; For missing Data, use NLDAS)
Corrected using: V_Corrected=V_SURFRAD*mean2010(V_FluxTower)/mean2010(V_SURFRAD)
Discharge units in reanalysis are often compared with precipitation and evapotranspiration, so it was expressed in m/day. It can be transformed to m^3/s by multiplying total area of sh (84710m^2) and being divided by 86400 (s/day):
Q = q(m/day)*84710/86400 (m^3/s) = q(m/day)*84710 (m^3/day), where q is the value in reanalysis results.
Discharge, Flux-PIHM, Hydrology reanalysis
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 Shale Hills Susquehanna Critical Zone Observatory.
Citation for This Webpage
Shi, Yuning; Xiao, Dacheng (2015). "CZO Dataset: Shale Hills - Streamflow / Discharge (2008-2015) - Discharge Reanalysis." Retrieved 16 Sep 2019, from http://criticalzone.org/shale-hills/data/dataset/4610/
Data Use Policy
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
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.