Data Management Plan (Deprecated)

Product: Classified LAS 1.4 files formatted to 1,652 individual 1,000 m x 1,000 m tiles for the Rogue River Siskiyou Project Area.

Geographic Extent: This dataset and derived products encompass an area covering approximately 569 square miles within Siskiyou and Del Norte Counties in California as well as Josephine and Jackson Counties in Oregon.

Dataset Description: The Rogue River Siskiyou lidar project called for the planning, acquisition, and processing of lidar data collected at an aggregate nominal pulse spacing (ANPS) of 0.35 meters. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base lidar Specification, Version 1.3. The data was developed based on the NAD83(2011) horizontal datum and NAVD88 (GEOID12B) vertical datum. Data was projected in UTM Zone 10N. Lidar data was delivered as processed Classified LAS 1.4 files, formatted to 1,652 individual 1,000 m x 1,000 m tiles. Derived products include: tiled Intensity Imagery, tiled DZ orthos, tiled hydroflattend bare earth DEMs and 3D waters edge breaklines.

Ground Conditions: Lidar was collected in fall 2019, while the presence of snow on the ground was at a minimum and rivers were at or below normal levels. In order to post process the lidar data to meet task order specifications and meet ASPRS vertical accuracy guidelines, QSI established a total of 65 ground control points distributed throughout the Rogue River Siskiyou, Oregon project area. Lidar data was calibrated to these known ground locations. An additional 70 independent accuracy checkpoints, 43 in Bare Earth and Urban landcovers (NVA points) and 27 in Shrub, Tall Grass, and Forest categories (VVA points) were used to assess the vertical accuracy of the project data. These checkpoints were not used to calibrate or post process the data.

The NOAA Office for Coastal Management (OCM) downloaded the:

1. Lidar point data from this USGS site:

ftp://rockyftp.cr.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/OR_RogueSiskiyouNF_2019_B19/OR_RogueRiverSiskiyouNF_B1_2019/

2. Breaklines, reports and metadata from this USGS site:

ftp://rockyftp.cr.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/OR_RogueSiskiyouNF_2019_B19/OR_RogueRiverSiskiyouNF_B1_2019/

These files were processed to the Data Access Viewer (DAV) and https. The total number of laz files downloaded and processed was 1652.

The breakline data are available for download at the link provided in the URL section of this metadata record. Please note that these products have not been reviewed by the NOAA Office for Coastal Management (OCM) and any conclusions drawn from the analysis of this information are not the responsibility of NOAA or OCM.

Lineage Statement:
Quantum Spatial, Inc. collected data for the US Forest Service. The data was made available on the USGS Rockyftp site. NOAA OCM downloaded the laz files, the breaklines, metadata and reports and processed the data to be available from the Digital Coast.

Process Steps:

• 2019-10-10 00:00:00 - Lidar Pre-Processing: 1. Review flight lines and data to ensure complete coverage of the study area and positional accuracy of the laser points. 2. Resolve kinematic corrections for aircraft position data using kinematic aircraft GPS and static ground GPS data. 3. Develop a smoothed best estimate of trajectory (SBET) file that blends post-processed aircraft position with sensor head position and attitude recorded throughout the survey. 4. Calculate laser point position by associating SBET position to each laser point return time, scan angle, intensity, etc. Create raw laser point cloud data for the entire survey in *.las format. Convert data to orthometric elevations by applying a geoid correction. 5. Import raw laser points into manageable blocks to perform manual relative accuracy calibration and filter erroneous points. Classify ground points for individual flight lines. 6. Using ground classified points per each flight line, test the relative accuracy. Perform automated line-to-line calibrations for system attitude parameters (pitch, roll, heading), mirror flex (scale) and GPS/IMU drift. Calculate calibrations on ground classified points from paired flight lines and apply results to all points in a flight line. Use every flight line for relative accuracy calibration. 7. Adjust the point cloud by comparing ground classified points to supplemental ground control points.
• 2019-10-10 00:00:00 - lidar Post-Processing: 1. Classify data to ground and other client designated classifications using proprietary classification algorithms. 2. Manually QC data classification 3. After completion of classification and final QC approval, calculate NVA and VVA, and density information for the project using ground control quality check points. Single swath nominal pulse spacing (NPS) was designed to be 0.50 m at nadir. Aggregate Nominal Pulse Spacing (ANPS) was calculated to be 0.20 m using all valid first return points.
• 2021-03-12 00:00:00 - The NOAA Office for Coastal Management (OCM) downloaded the lidar point data from this USGS site: ftp://rockyftp.cr.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/OR_RogueSiskiyouNF_2019_B19/OR_RogueRiverSiskiyouNF_B1_2019/ These files were processed to the Data Access Viewer (DAV) and https. The total number of laz files downloaded and processed was 1652. The data were in UTM Zone 10 (NAD83 2011), meters coordinates and NAVD88 (Geoid12B) elevations in meters. The data were classified as: 1 - Unclassified, 2 - Ground, 7 - Low Noise, 9 - Water, 17 - Bridge Decks, 18 - High Noise, 20 - Ignored Ground. OCM processed all classifications of points to the Digital Coast Data Access Viewer (DAV). Classes available on the DAV are: 1, 2, 7, 9, 17, 18, 20. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. An internal OCM script was run to report the las format, the point data format, the global encoding bit, and the min and max elevation values by file 2. An internal OCM script was run to check the number of points by classification and by flight ID and the gps and intensity ranges. 3. Internal OCM scripts were run on the laz files to: a. Convert from orthometric (NAVD88) elevations to ellipsoid elevations using the Geoid 12B model b. Convert from UTM Zone 10 (NAD83 2011), meters coordinates to geographic coordinates c. Filter out points with elevations less than -200 meters or greater than 4000 meters d. Filter out points with coordinates outside this bounding box (-125, 40, -120, 45) e. Assign the geokeys f. Sort the data by gps time g. Zip the data to database and to http

Data is available online for bulk and custom downloads

Data is backed up to tape and to cloud storage.