2022 USGS QL2 Lidar: Green, Iowa, Polk, Winnebago Counties, WI

WI_12County_3 (Work Unit 300206) covering approximately 590 square miles in Green County

Dates of collection for WI_12County_3 (Work Unit 300206) covering approximately 590 square miles in Green County

WI_12County_4 (Work Unit 300207) covering approximately 775 square miles in Iowa County

WI_12County_4 (Work Unit 300207) covering approximately 775 square miles in Iowa County

WI_12County_5 (Work Unit 300208) covering approximately 965 square miles in Polk County

Dates of collection for WI_12County_5 (Work Unit 300208) covering approximately 965 square miles in Polk County

WI_12County_6 (Work Unit 300209) covering approximately 585 square miles in Winnebago County

Date of collection for WI_12County_6 (Work Unit 300209) covering approximately 585 square miles in Winnebago County

Date of collection for WI_12County_6 (Work Unit 300209) covering approximately 585 square miles in Winnebago County

Create custom data files by choosing data area, product type, map projection, file format, datum, etc. A new metadata will be produced to reflect your request using this record as a base. Change to an orthometric vertical datum is one of the many options.

Bulk download of data files in LAZ format, Wisconsin county reference system coordinates in US survey feet and NAVD88 (orthometric) heights in feet.

The Data Access Viewer (DAV) allows a user to search for and download elevation, imagery, and land cover data for the coastal U.S. and its territories. The data, hosted by the NOAA Office for Coastal Management, can be customized and requested for free download through a checkout interface. An email provides a link to the customized data, while the original data set is available through a link within the viewer.

Link to the NV5 lidar report.

Link to the NV5 lidar report.

Link to the NV5 lidar report.

Link to the NV5 lidar report.

Link to the reports, breaklines, metadata, and spatial metadata.

Link to the USGS Project Report that provides information about the project, vertical accuracy results, and the point classes and sensors used.

Link to view the point cloud, using the Entwine Point Tile (EPT) format, in the 3D Potree viewer.

Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud.

Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud.

Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud.

Entwine Point Tile (EPT) is a simple and flexible octree-based storage format for point cloud data. The data is organized in such a way that the data can be reasonably streamed over the internet, pulling only the points you need. EPT files can be queried to return a subset of the points that give you a representation of the area. As you zoom further in, you are requesting higher and higher densities. A dataset in EPT will contain a lot of files, however, the ept.json file describes all the rest. The EPT file can be used in Potree and QGIS to view the point cloud.

Raw Data and Boresight Processing: The boresight for each lift was done individually as the solution may change slightly from lift to lift. The following steps describe the Raw Data Processing and Boresight process: 1) Technicians processed the raw data to LAS format flight lines using the final GPS/IMU solution. This LAS data set was used as source data for boresight. 2) Technicians first used NV5 Geospatial proprietary and commercial software to calculate initial boresight adjustment angles based on sample areas selected in the lift. These areas cover calibration flight lines collected in the lift, cross tie, and production flight lines. These areas are well distributed in the lift coverage and cover multiple terrain types that are necessary for boresight angle calculation. The technicians then analyzed the results and made any necessary additional adjustment until it was acceptable for the selected areas. 3) Once the boresight angle calculation was completed for the selected areas, the adjusted settings were applied to all of the flight lines of the lift and checked for consistency. The technicians utilized commercial and proprietary software packages to analyze how well flight line overlaps matched for the entire lift and adjusted as necessary until the results met the project specifications. 4) Once all lifts were completed with individual boresight adjustment, the technicians checked and corrected the vertical misalignment of all flight lines and also the matching between data and ground truth. The relative accuracy was less than or equal to 7 cm RMSEz within individual swaths and less than or equal to 10 cm RMSEz or within swath overlap (between adjacent swaths). 5) The technicians ran a final vertical accuracy check of the boresighted flight lines against the surveyed checkpoints after the z correction to ensure the requirement of NVA = 19.6 cm 95% Confidence Level (Required Accuracy) was met.

LAS Point Classification: The point classification was performed as described below. The bare earth surface was manually reviewed to ensure correct classification on the Class 2 (Ground) points. After the bare-earth surface was finalized, it was then used to generate all hydro-breaklines through heads-up digitization. All ground (ASPRS Class 2) LiDAR data inside of the Lake Pond and Double Line Drain hydro-flattened breaklines were then classified to Water (ASPRS Class 9) using proprietary tools. A buffer of 1.0 meter was also used around each hydro-flattened feature to classify these ground (ASPRS Class 2) points to Ignored ground (ASPRS Class 20). All Lake Pond Island and Double Line Drain Island features were checked to ensure that the ground (ASPRS Class 2) points were reclassified to the correct classification after the automated classification was completed. Any noise that was identified either through manual review or automated routines was classified to the appropriate class ( ASPRS Class 7 and/or ASPRS Class 18) followed by flagging with the withheld bit. All data were manually reviewed and any remaining artifacts removed using functionality provided by TerraScan and TerraModeler. Global Mapper was used as a final check of the bare earth dataset. GeoCue was then used to create the deliverable industry-standard LAS files for both the Point Cloud Data and the Bare Earth. NV5 Geospatial proprietary software was used to perform final statistical analysis of the classes in the LAS files, on a per tile level to verify final classification metrics and full LAS header information.

Original point clouds in LAS/LAZ format were restructured as Entwine Point Tiles and stored on Amazon Web Services. The data were re-projected horizontally to WGS84 web mercator (EPSG 3857) and and the vertical units were converted to meters (NAVD88 GEOID18).

The NOAA Office for Coastal Management (OCM) created references to the Entwine Point Tiles (EPT) that were ingested into the NOAA Digital Coast Data Access Viewer (DAV). No changes were made to the data. The DAV will access the point cloud as it resides on Amazon Web Services (AWS) under the usgs-lidar-public container.

These are the AWS URLs being accessed:

https://s3-us-west-2.amazonaws.com/usgs-lidar-public/WI_12County_3_B22/ept.json

https://s3-us-west-2.amazonaws.com/usgs-lidar-public/WI_12County_4_B22/ept.json

https://s3-us-west-2.amazonaws.com/usgs-lidar-public/WI_12County_5_B22/ept.json

https://s3-us-west-2.amazonaws.com/usgs-lidar-public/WI_12County_6_B22/ept.json