Christina River Basin Critical Zone Observatory July 2010 Lidar Survey

High-resolution Lidar data (average first-return point density of 10 points m2 and 2-4 cm vertical accuracy) were obtained by NCALM for 121 km2 of the Christina River Basin Critical Zone Observatory (CRB-CZO) during both leaf-off (April 2010; see dataset CRB-10-Apr) and leaf-on (July 2010) periods. Data acquisition, ground-truthing, vegetation surveys and processing were funded and coordinated by NSF Award EAR-0922307 (PI. Qinghua Guo) to collect similar data at all six CZOs for a variety of cross-site analyses, including calibration of algorithms to extract vegetation characteristics from the LIDAR point cloud data. The CRB-CZO is particularly interested in using this LIDAR dataset for high-resolution analyses of stream channel and floodplain geomorphology.Publications associated with this dataset can be found at NCALM's Data Tracking Center

Data and Resources

Additional Info

Field Value
Last Updated August 15, 2025, 10:50 (UTC)
Created August 15, 2025, 10:50 (UTC)
encoding utf8
harvest_object_id 54c3848d-7b68-4012-8225-38af764107b2
harvest_source_id a2637971-af12-457f-ae4a-831d2202a539
harvest_source_title WIFIRE Commons
providers [{"url": "https://www.opentopography.org", "name": "OpenTopography", "roles": ["host"]}, {"url": "https://ncalm.cive.uh.edu/", "name": "National Center for Airborne Laser Mapping", "roles": ["Collector"]}, {"url": "https://nsf.gov/", "name": "National Science Foundation", "roles": ["Funder"]}, {"url": "http://www.udel.edu/czo/index.html", "name": "Christina River Basin Critical Zone Observatory", "roles": ["Partner"]}, {"url": "https://www.ucmerced.edu/", "name": "University of California, Merced", "roles": ["Partner"]}]
sci:citation N/A. Citation Guidance - https://opentopography.org/citations
sci:doi https://doi.org/10.5069/G9X63JTW
spatial {"type": "Polygon", "coordinates": [[[-75.871155, 39.964344], [-75.554982, 39.964344], [-75.554982, 39.792204], [-75.871155, 39.792204], [-75.871155, 39.964344]]]}
temporal {"endTime": "2010-07-31T00:00:00Z", "startTime": "2010-07-01T00:00:00Z"}