Dataset Listing

Jemez River Basin - LiDAR - Terrestrial Laser Scan (2011-2013)

Terrestrial Laser Scans for Debris 1, Debris 2 and Burn ZOB locations

Variables:  Point Cloud

Date Range:  (2011-08-18 to 2013-05-17)

Dataset Creators/Authors:  Caitlin Orem; Jon Pelletier

Contact:  Jon D. Pelletier, Department of Geosciences, University of Arizona, 1040 E. Fourth St., Tucson, AZ 85721, jdpellet@email.arizona.edu

Field Area:   Jemez River Basin | Jemez 2011 Burned ZOB

Description
Keywords & XML
Citation
Publications
Acknowledgements
  • Description

    Terrestrial Laser Scan (TLS) datasets were collected for various projects pursued by the University of Arizona Critical Zone Observatory located in the Jemez River Basin within the Valles Caldera National Preserve. Three locations were TLS surveyed a total of four times over the course of two years. The locations are the Debris1 alluvial fan, Debris2 alluvial fan, and the BurnZOB small upland basin. The four surveys were completed after the Las Conchas fire in the summer of 2011. The approximate dates for each scan were 8/19/11, 6/4/12, 9/22/12, and 5/14/13.

    All TLS data was collected using a Leica C10 scanner set up in the field by Jon Pelletier and Caitlin Orem. All scans were scanned for both points (on the medium scan setting) and photographs (meaning pictures were taken to then extrapolate RGB data from for each point). GPS data was collected in the field with a Leica Real-Time Kinematic Global Positioning System (RTK-GPS) unit. At each scan station at least three permanently located targets were scanned so all scans at a study site could be registered to one point cloud. At least three targets at each study site were surveyed with Real-Time Kinematic Global Positioning System (RTK-GPS) receivers until a temporary accuracy reading of less than 0.01 m was reached in each of the four cardinal directions.

    All scans for each individual survey were uploaded to Leica Cyclone so scans could be registered together into one point cloud. GPS data for the base station was processed in Leica Geo Office and imported into Cyclone to georeference the point cloud. Data was then exported from Cyclone in .pts format (columns of x, y, z, intensity, r, g, b). Cloud Compare software was used to take the .pts file to .las.

    Horizontal coordinate system is UTM 13N WGS84 METERS.

    Vertical coordinate system is NAVD88.


    Comments
    All collections start early (~7 am) the first day and end mid-afternoon on second day. All collections were done moving from the base of the catchment (near the road) up to the top and then moving along the western slope of the catchment near the road. All surveys were completed in the field and processed by Caitlin Orem.
  • Keywords

    Terrestrial laser scan, post-wildfire, Las Conchas fire, Valles Caldera, Jemez Mountains, New Mexico

    XML Metadata

    criticalzone.org/catalina-jemez/data/xml-metadata-test/4182/

    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 Jemez River Basin and Santa Catalina Mountains Critical Zone Observatory EAR-0724958.

    Citation for This Webpage

    Caitlin Orem; Jon Pelletier (2013). "CZO Dataset: Jemez River Basin - LiDAR (2011-2013) - Terrestrial Laser Scan." Retrieved 25 Aug 2019, from http://criticalzone.org/catalina-jemez/data/dataset/4182/

  • Publications

    Primary Publications
  • Acknowledgements

    Funding

    National Science Foundation EAR-0724958

Data

Jemez River Basin - Debris 1

(is1/)   Data Level 1,  Metadata

Jemez River Basin - Debris 2

(is2/)   Data Level 1,  Metadata

Jemez River Basin - Burn ZOB

(ZOB/)   Data Level 1,  Metadata

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.

Explore Further

data |

Explore Further