2015 USGS Lidar: Shawano County, WI

Geographic Extent: Shawano County, Wisconsin, covering approximately 909 square miles.

Dataset Description of Original Data: The Shawano County, WI LiDAR project called for the planning, acquisition, processing and derivative products of LIDAR data to be collected at a nominal pulse spacing (NPS) of 0.7 meters. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base LIDAR Specification, Version 1.2. The data was developed based on a horizontal projection/datum of NAD83 UTM Zone 16, meters; NAVD1988 (Geoid 12B), meters. LiDAR data was delivered in RAW flight line swath format, processed to create Classified LAS 1.4 Files formatted to 1,143 individual 1,500-meter x 1,500-meter tiles. Tile names correspond to the US National Grid. Corresponding 1-meter gridded bare earth raster DEM files tiles were created using the same 1,500-meter x 1,500-meter schema. Hydro-flattened breaklines were produced in Esri file geodatabase as well as Esri shapefile format.

Ground Conditions: LiDAR collection began in Fall 2015, while no snow was on the ground and rivers were at or below normal levels. In order to post process the LiDAR data to meet task order specifications, Quantum Spatial established a total of 140 control points (40 calibration control points and 100 QC checkpoints). These were used to calibrate the LIDAR to known ground locations established throughout the project area.

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.

Classified LAS files are used to show the manually reviewed bare earth surface. This allows the user to create breaklines and raster DEMs. The purpose of these lidar data was to produce high accuracy 3D hydro-flattened digital elevation model (DEM) with a 1-meter cell size. These raw lidar point cloud data were used to create classified lidar LAS files, 3D breaklines, hydro-flattened DEMs, and contours as necessary.

USGS Contract: G10PC00026 Task Order Number: G15PD00640

CONTRACTOR: Quantum Spatial

Lidar data were acquired and calibrated by Quantum Spatial.

All follow-on processing was completed by the prime contractor.

The following are the USGS lidar fields in JSON:

{

"ldrinfo" : {

"ldrspec" : "USGS-NGP Base Specification v1.2",

"ldrsens" : "Optech_Orion_H300",

"ldrmaxnr" : "3",

"ldrnps" : "0.98",

"ldrdens" : "2.67",

"ldranps" : "0.98",

"ldradens" : "2.67",

"ldrfltht" : "1700",

"ldrfltsp" : "140",

"ldrscana" : "38",

"ldrscanr" : "52",

"ldrpulsr" : "225",

"ldrpulsd" : "4",

"ldrpulsw" : "0.41",

"ldrwavel" : "1064",

"ldrmpia" : "1",

"ldrbmdiv" : "0.25",

"ldrswatw" : "1170.71",

"ldrswato" : "30",

"ldrgeoid" : "National Geodetic Survey (NGS) Geoid12B"

},

"ldraccur" : {

"ldrchacc" : "0.196",

"rawnva" : "0.088",

"rawnvan" : "55",

"clsnva" : "0.079",

"clsnvan" : "55",

"clsvva" : "0.278",

"clsvvan" : "45"

},

"lasinfo" : {

"lasver" : "1.4",

"lasprf" : "6",

"laswheld" : "Withheld (ignore) points were 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" : "10",

"clasitem" : "Ignored Ground"

},

"lasclass" : {

"clascode" : "17",

"clasitem" : "Bridge Decks"

},

"lasclass" : {

"clascode" : "18",

"clasitem" : "High noise"

}

}}

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 Version 8; TerraScan Version 15; TerraModeler Version 15; GeoCue Version 2014.1.21.1; Esri ArcGIS 10; Global Mapper 16; Leica Cloud Pro 1.2; Windows 7 Operating System

\\PSIHQ_NX3200\Projects\Projects\26737_Shawano_County_LiDAR 91.4 GB and \\matrix\matrix\LIDAR\26737_Shawano_County 4.58 TB

The specifications require that only raw Nonvegetated Vertical Accuracy (NVA) be computed for raw lidar point cloud swath files. Specifications for this project require that the raw NVA be 19.6 cm or better AccuracyZ at 95 percent confidence level.

The raw NVA was tested using 55 independent survey points located in open terrain. These checkpoints were not used in the calibration or post-processing of the lidar point cloud data. The surveyed checkpoints were distributed throughout the project area and surveyed using GNSS procedures and methodologies that provide reliable and consistent results to meet the project's accuracy requirements. Please see the "Survey Accuracy Requirements" and "Field Methodology" sections in the Survey Report for more information. Elevations from the unclassified lidar surface were measured for the x,y location of each check point. Elevations interpolated from the unclassified lidar surface were then compared to the elevation values of the surveyed control. The RMSEz was computed to be 0.045 meters and AccuracyZ to be 0.088 meters. This meets the required AccuracyZ value of 19.6 cm raw NVA at 95 percent confidence level using (RMSEz * 1.9600) as defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASPRS Guidelines.

These raw 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 Nonvegetated 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 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 under the usgs-lidar-public-container.