Dataset Listing

Eel River and South Fork Eel River - LiDAR, Digital Elevation Model (DEM) (2009)

Variables:  gis

Date Range:  (2009-2009)    Dataset DOI: http://dx.doi.org/10.5069/G93F4MH1

Dataset Creators/Authors:  Jonathan Perkins, Noah Finnegan

Contact:  Open Topography or NCALM

Field Area:   Eel River Watershed

Description
Keywords
Citation
Acknowledgements
  • Description

    South Fork Eel River, CA: Understanding Terrace Formation and Abandonment. NCALM Seed. PI: Jonathan Perkins and Noah Finnegan, University of California, Santa Cruz. The survey area was in the form of a 2.25 kilometer wide and 108 kilometer long corridor following the Eel River, located in California, about 250 kilometers north of San Francisco. Data were collected to study strath terrace formation and abandonment.

    Dataset is bare-earth raster dem and hillshade. Point cloud can be downloaded from OpenTopography.org.
  • Keywords

    lidar, eel river, digital elevation model

  • Citation for This Dataset

    Jonathan Perkins, 2009, National Center for Airborne Laser Mapping, OpenTopography, http://dx.doi.org/10.5069/G93F4MH1

    Citation for This Webpage

    Jonathan Perkins, Noah Finnegan (2009). "CZO Dataset: Eel River and South Fork Eel River - LiDAR, Digital Elevation Model (DEM) (2009)." Retrieved 20 Sep 2017, from http://criticalzone.org/national/data/dataset/4369/

  • Acknowledgements

    Funding

    National Science Foundation EAR EAR-1043051

Data

South Fork Eel River Mainstem - bare-earth dem raster

()   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.