The Eel River CZO operates on several spatial scales from a zero order hillslope to the entire Eel River on the north coast of California. Rivendell, Angelo, Sagehorn, South Fork, and Eel River GIS boundaries. GIS polygon shapefiles. All files are in geographic projection (Lat/Long) with a datum of WGS84.
The watershed boundaries are from USGS Watershed Boundary Dataset (WBD) http://nhd.usgs.gov/wbd.html. Rivendell and Angelo boundaries are created from LiDAR by the CZO. Sagehorn Ranch is a privately held, active commercial ranch with no public access. Please contact the CZO if you are interested in data from Sagehorn Ranch.
Eel River Watershed (drainage area 9534 km^2): Entire eel river. Greatest extent of CZO research.
South Fork Eel Watershed (drainage area 1784 km^2).
Angelo Reserve Boundary (30.0 km^2): Angelo Coast Range Reserve is a University of California Natural Reserve System protected land. It is the central focus of CZO research. http://angelo.berkeley.edu
Sagehorn Ranch Boundary (21.1 km^2): Sagehorn Ranch is a private ranch with active cattle raising. The owners have allowed the CZO to place instrumentation on their lands. Access is only by explicit agreement by owners.
Rivendell Cachement (0.0076 km^2): Rivendell is a small, heavily instrumented hillslope within the Angelo Reserve. It has roughly 700 instruments deployed as of 2016. Data is online at http://sensor.berkeley.edu
GIS, watershed, boundary
XML is in ISO-19115 geographic metadata format, compatible with ESRI Geoportal Server.
Citation for This Dataset
Bode, Collin, 'GIS research boundaries', 2015, Eel River CZO
Citation for This Webpage
Collin Bode; USGS (2015). "CZO Dataset: Eel River to Rivendell - GIS/Map Data (2004-2015) - Research and Watershed GIS Boundaries." Retrieved 25 Mar 2019, from http://criticalzone.org/eel/data/dataset/4897/
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.