2019 3DEP WA DNR Lidar: Springdale and North Spokane County, WA

Original Product: Classified LAS 1.4 files, formatted to individual 5,000ft x 5,000ft tiles covering the Washington DNR 3DEP Processing project area.

Geographic Extent of Original Data: This dataset and derived products encompass an area covering approximately 562,137 acres of Eastern Washington.

Original Dataset Description: The Washington DNR 3DEP Processing Lidar project called for the planning, acquisition, and processing of lidar data collected to Quality Level 1 (QL1) standards. Project specifications are based on the U.S. Geological Survey National Geospatial Program LIDAR Base Specification, Version 2.1. The data was developed based on the NAD83 2011 horizontal datum and the NAVD88 Geoid 18 vertical datum. Data was projected in Washington State Plane North, U.S. feet. Lidar data was delivered as calibrated and classified LAS 1.4 files. Non-Vegetated Vertical Accuracy (NVA) was assessed using 64 check points located on bare earth in clear, unobstructed areas. Vegetated Vertical Accuracy (VVA) was assessed using 43 check points in Tall Grass, Forest, and Shrub landcover types. Single swath nominal pulse spacing (NPS) was designed to be 0.70 meters at nadir. Aggregate Nominal Pulse Spacing (ANPS) was calculated to be 0.23 meters using all valid first return points. Derived products include: Intensity Imagery, Hydro-flattened Bare Earth Digital Elevation Models (DEMs), Highest Hit Digital Surface Models (DSMs), and 3D waters edge breaklines.

Ground Condition of Original Data: Ground condition was free of snow and acquisition occurred free of smoke, fog and cloud cover.

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.

The purpose of the lidar data was to produce a high accuracy 3D dataset that meets all necessary standards laid out by the 3D Elevation Program and the Washington DNR 3DEP Processing contract. The lidar point cloud data were used to create classified lidar LAS files, intensity images, hydro-flattened DEMs, highest hit DSMs, and 3D breaklines of rivers and lakes within the study area.

USGS Contract No. G16PC00016

CONTRACTOR: NV5 Geospatial

WU ID: 209240

WP ID: 209237

Ground Control Points were acquired and calibrated by NV5 Geospatial

All lidar data acquisition, calibration, and follow-on processing were completed by NV5 Geospatial.

The following are the USGS lidar fields in JSON:

{

"ldrinfo" : {

"ldrspec" : "U.S. Geological Survey National Geospatial Program LIDAR Base Specification, Version 2.1",

"ldrsens" : "Riegl VQ-1560i",

"ldrmaxnr" : "13",

"ldrnps" : "0.70",

"ldrdens" : "4",

"ldranps" : "0.23",

"ldradens" : "17.75",

"ldrfltht" : "1,830",

"ldrfltsp" : "145",

"ldrscana" : "58.5",

"ldrscanr" : "Uniform Point Spacing",

"ldrpulsr" : "700",

"ldrpulsd" : "3",

"ldrpulsw" : "32",

"ldrwavel" : "1064",

"ldrmpia" : "1",

"ldrbmdiv" : "0.18",

"ldrswatw" : "2,050",

"ldrswato" : "55",

"ldrgeoid" : "Geoid 18"

},

"ldraccur" : {

"ldrchacc" : "0",

"rawnva" : "0",

"rawnvan" : "0"

},

"lasinfo" : {

"lasver" : "1.4",

"lasprf" : "6",

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

"lasolap" : "Swath "overage" points were identified in these files using the standard LAS overlap bit.",

"lasintr" : "16",

"lasclass" : {

"clascode" : "1",

"clasitem" : "Processed, but Unclassified"

},

"lasclass" : {

"clascode" : "2",

"clasitem" : "Bare earth ground"

},

"lasclass" : {

"clascode" : "7",

"clasitem" : "Low Noise"

},

"lasclass" : {

"clascode" : "9",

"clasitem" : "Water"

},

"lasclass" : {

"clascode" : "17",

"clasitem" : "Bridge Decks"

},

"lasclass" : {

"clascode" : "18",

"clasitem" : "High Noise"

},

"lasclass" : {

"clascode" : "20",

"clasitem" : "Ignored Ground Near Breaklines"

}

}}

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.

LiDAR Mapping Suite 2.4, Applanix PosPac 7.1, Microstation CONNECT version 19, TerraScan Version 20, TerraModeler Version 20, TerraMatch Version 20, ESRI ArcGIS 10.3, Windows 10 Operating System

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 percent of the time. Based on a flying altitude of 1,830 meters, an IMU error of 0.003 decimal degrees, and a GNSS positional error of 0.015 meters, the Washington DNR 3DEP Processing site was compiled to meet 0.98 feet (0.30 meters) horizontal accuracy at the 95% confidence level or 0.17 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. Specifications for this project require that the NVA be 0.196 meters or better AccuracyZ at 95% confidence level. Vegetated Vertical Accuracy (VVA) is also to be computed. Specifications for this project require that the VVA be 0.300 meters or better AccuracyZ at the 95th percentile.

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:

Tested NVA RMSEz = 2.3 cm

Tested 95th percentile value for VVA is : 14.7 cm

For more information see the USGS project report and the lidar report. The links to these reports are provided in the URL section of this metadata record.

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 data passes Non-Vegetated Vertical Accuracy specifications.

Classified LAS files were tested by NV5 Geospatial for vertical accuracy. All data is seamless from one tile to the next, no gaps or no data areas.

Data is backed up to cloud storage.

The NOAA Office for Coastal Management (OCM) ingested references to the USGS Entwine Point Tiles (EPT) 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.