Dataset Listing

Jemez River Basin - LiDAR - Post-Fire (2012)

Jemez River Basin, NM: Post-fire Landscape Response

Variables:  Digital Elevation Model, Classified Point Cloud

Standard Variables:  Lidar point cloud|Digital elevation model

Date Range:  (2012-2012)    Dataset DOI: 10.5069/G9319SVB

Dataset Creators/Authors:  Jon Pelletier

Contact:  Jon D. Pelletier, Department of Geosciences, University of Arizona, 1040 E. Fourth St., Tucson, AZ 85721,

Field Area:   Jemez River Basin

Keywords & XML
  • Description

    Jemez River Basin, NM: Post-fire landscape response NCALM Project. Jon Pelletier, University of Arizona. The survey area is defined by an 206 square kilometer irregular polygon located 12 kilometers west of Los Alamos, NM. Data were collected from May 25-28, 2012 to quantify extreme post-fire landscape response in the Jemez River basin, New Mexico.There area additional datasets covering the portions of the Catalina-Jemez Critical Zone Observatory (CZO) on OpenTopography including the Jemez River Basin Snow-on LiDAR Survey and Jemez River Basin Snow-off LiDAR Survey.

    High-resolution LiDAR survey covers the area of 206 km2 in the north-east part of the Jemez River basin which was burned in the 2011 Las Conchas fire. The dataset contains point cloud tiles in LAS format with the average point density of 15.24 pts/m2 and 1-m Digital Elevation Model (DEM) derived from ground-class points. This dataset, together with 2010 LiDAR datasets, are being used to quantify extreme post-fire landscape changes. DEM was made using the same smoothness parameters (in terrascan) as the 2010 DEM data sets. this 2012 data is important for anyone who wants to difference the 2010 and 2012 bare-earth DEMs. The differences between 2010 and 2012 surveys is in the horizontal and vertical datums. The 2012 survey was referenced to the current iteration of NAD83 which is NAD_83(2011)(EPOCH:2010.0000) and the 2010 survey was referenced to the then-current iteration of NAD83 which was NAD_83(CORS96)(EPOCH:2002.0000). The error between these two datum realizations is less than 1 cm. The vertical datum for 2010 data was based on GEOID 03 and for 2012 data was GEOID 09. The error for these GEOID models is less than 6 cm. Both horizontal and datum errors are smaller than estimated survey horizontal and elevation accuracies (1 sigma).
  • Keywords

    DEM, Digital Elevation Model, LiDAR, Critical Zone, Valles Caldera, Jemez River, New Mexico

    XML Metadata

    XML is in ISO-19115 geographic metadata format, compatible with ESRI Geoportal Server.

  • Citation for This Dataset

    LiDAR data acquisition and processing completed by the National Center for Airborne Laser Mapping (NCALM - NCALM funding provided by NSF's Division of Earth Sciences, Instrumentation and Facilities Program. EAR-1043051.

    Citation for This Webpage

    Jon Pelletier (2012). "CZO Dataset: Jemez River Basin - LiDAR (2012) - Post-Fire." Retrieved 07 Dec 2019, from

  • Acknowledgements


    National Science Foundation EAR-1043051


Jemez River Basin - Data are distributed by OpenTopography

(13.1)   Data Level 2

Jemez River Basin - Digital Elevation Model (DEM derived from ground-class points)

(.zip)   Data Level 2,  Metadata

Data Use Policy
Data Sharing Policy
Related Datasets
Research Groups/Foci
  • 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 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

  • Related Datasets

    Jemez River Basin (2010). LiDAR, Snow-off...
    Jemez River Basin (2010). LiDAR, Snow-on...

  • Research Groups/Foci

CZO Field Areas


CZO Authors

Explore Further

data |

Explore Further