2020 - 2022 USGS Lidar: Southwest Central Oregon

Product: These lidar data are processed Classified LAS 1.4 files, formatted to individual 1000 m x 1000 m tiles; used to create intensity images, 3D breaklines, and hydro-flattened DEMs as necessary.

Geographic Extent:

OR_SWCentralSycan_1 (Work Unit 221824)

Four counties in Oregon (Douglas, Klamath, Lake, Modoc) covering approximately 4171 total square miles.

OR_SWCentralSycan_3 (Work Unit 300185)

Three counties in Oregon (Baker, Grant, Harney), covering approximately 393 total square miles

Dataset Description:

This project called for the planning, acquisition, processing, and derivative products of lidar data to be collected at a nominal pulse spacing (NPS) of 0.35 meters. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base LiDAR Specification, Version 2020 Rev. A. The data were developed based on a horizontal projection/datum of UTM zone 10N NAD 1983 (2011) for OR_SWCentralSycan_1 (Work Unit 221824), UTM Zone 11N NAD 1983 (2011) for OR_SWCentralSycan_3 (Work Unit 300185)), meters and vertical datum of NAVD88 Geoid18, meters. LiDAR data were delivered as processed Classified LAS 1.4 files formatted to 11461 individual 1000 m x 1000 m tiles for OR_SWCentralSycan_1 (Work Unit 221824) and 1212 individual 1000 m x 1000 m tiles for OR_SWCentralSycan_3 (Work Unit 300185), as tiled intensity imagery, and as tiled bare earth DEMs; all tiled to the same 1000 m x 1000 m schema. Continuous breaklines were produced in Esri file geodatabase format.

Ground Conditions:

LiDAR was collected in fall 2021 through Summer 2022, while no snow was on the ground and rivers were at or below normal levels.

This metadata record supports the data entry in the NOAA Digital Coast Data Access Viewer (DAV). For this data set, the DAV is leveraging the Entwine Point Tiles (EPT) hosted by USGS on Amazon Web Services.

To acquire detailed surface elevation data for use in conservation planning, design, research, floodplain mapping, dam safety assessments and elevation modeling, etc. Classified LAS files are used to show the manually reviewed bare earth surface. This allows the user to create intensity images, breaklines and raster DEMs. The purpose of these LiDAR data was to produce high accuracy 3D hydro-flattened digital elevation models (DEMs) with a 0.5 meter cell size. These raw LiDAR point cloud data were used to create classified LiDAR LAS files, intensity images, 3D breaklines, and hydro-flattened DEMs as necessary.

Contract No. G16PC00016, Task Order No. 140G0221F0222; CONTRACTOR: NV5 Geospatial

The following are the USGS lidar fields in JSON:

{

"ldrinfo" : {

"ldrspec" : "USGS-NGP Base Specification 2020 Rev. A",

"ldrsens" : "Riegl VQ1560ii",

"ldrmaxnr" : "unlimited",

"ldrnps" : "0.35",

"ldrdens" : "8.0",

"ldranps" : "0.35",

"ldradens" : "8.16",

"ldrfltht" : "2500",

"ldrfltsp" : "145",

"ldrscana" : "29",

"ldrscanr" : "204",

"ldrpulsr" : "1268",

"ldrpulsd" : "3",

"ldrpulsw" : "0.45",

"ldrwavel" : "1064",

"ldrmpia" : "1",

"ldrbmdiv" : "0.18",

"ldrswatw" : "2772.0",

"ldrswato" : "20",

"ldrgeoid" : "Geoid18",

"ldrcrs" : "NAD 1983 2011 UTM zone 10N, Meter"

},

"ldrinfo" : {

"ldrspec" : "USGS-NGP Base Specification 2020 Rev. A",

"ldrsens" : "Riegl VQ1560ii",

"ldrmaxnr" : "unlimited",

"ldrnps" : "0.35",

"ldrdens" : "8.0",

"ldranps" : "0.35",

"ldradens" : "8.16",

"ldrfltht" : "2500",

"ldrfltsp" : "145",

"ldrscana" : "29",

"ldrscanr" : "204",

"ldrpulsr" : "1268",

"ldrpulsd" : "3",

"ldrpulsw" : "0.45",

"ldrwavel" : "1064",

"ldrmpia" : "1",

"ldrbmdiv" : "0.18",

"ldrswatw" : "2772.0",

"ldrswato" : "20",

"ldrgeoid" : "Geoid18",

"ldrcrs" : "NAD 1983 2011 UTM zone 10N, Meter"

},

"ldraccur" : {

"ldrchacc" : "0",

"rawnva" : "0.0",

"rawnvan" : "0"

},

"lasinfo" : {

"lasver" : "1.4",

"lasprf" : "6",

"laswheld" : "Withheld (ignore) points were identified in these files using the standard LAS Withheld bit.",

"lasolap" : "Any overage point deemed geometrically reliable will be used within the normal classification schema. Overage points are not specifically flagged with any special bit value.",

"lasintr" : "16"

}}

Any conclusions drawn from the analysis of this information are not the responsibility of NOAA, the Office for Coastal Management or its partners.

Data is available online for bulk and custom downloads.

None

Users should be aware that temporal changes may have occurred since this data set was collected and some parts of this data may no longer represent actual surface conditions. Users should not use this data for critical applications without a full awareness of its limitations.

MicroStation Connect; TerraScan Version 21.016; TerraModeler Version 21.008; GeoCue Version 2020.1.22.1; Esri ArcGIS 10.6; Global Mapper 19/20; RiProcess 1.8.6; Windows 10 Operating System

\\point_cloud\tilecls\*.las

Lidar horizontal accuracy is a function of Global Navigation Satellite System (GNSS) derived positional error, flying altitude, and INS derived attitude error. The obtained RMSEr value is multiplied by a conversion factor of 1.7308 to yield the horizontal component of the National Standards for Spatial Data Accuracy (NSSDA) reporting standard where a theoretical point will fall within the obtained radius 95% of the time. Based on a flying altitude of 2083 meters, an IMU error of 0.002 decimal degrees, and a GNSS positional error of 0.015 meters, this project was compiled to meet 0.23 meter horizontal accuracy at the 95% confidence level (0.13 m RMSEr).

This data set was produced to meet ASPRS Positional Accuracy Standard for Digital Geospatial Data (2014) for a 10-cm RMSEz Vertical Accuracy Class.

USGS Determined Vertical Accuracy:

Non-Vegetated Vertical Accuracy (NVA) = 7.43 cm at 95% Confidence Level or 3.79 cm RMSE

Vegetated Vertical Accuracy (VVA) = 16.37 cm at 95th Percentile

These LAS data files include all data points collected. No points have been removed or excluded. A visual qualitative assessment was performed to ensure data completeness. No void areas or missing data exist. The raw point cloud is of good quality and the data pass Non-Vegetated Vertical Accuracy specifications.

Data cover the entire area specified for this project.

Data is backed up to cloud storage.

The NOAA Office for Coastal Management (OCM) ingested references to the USGS Entwine Point Tile (EPT) files hosted on Amazon Web Services (AWS) into the Digital Coast Data Access Viewer (DAV). The DAV accesses the point cloud as it resides on AWS under the usgs-lidar-public-container.