2019 - 2020 USGS Lidar: Ohio Statewide - Phase 1

OH_Statewide_Phase1_1 - Work Unit 182846 (Blocks 1 and 10)

Block 1 includes Cuyahoga, Medina, and Summit Counties

Block 10 includes Henry, Fulton, and Williams Counties

OH_Statewide_Phase1_5 - Work Unit 210007 (Blocks 9 and 13)

Block 9 includes Allen, Auglaize, Hancock, Hardin, Putnam, and Wyandot Counties

Block 13 includes Allen, Auglaize, Mercer, Shelby, and Van Wert Counties

OH_Statewide_Phase1_6 - Work Unit 215019 (Blocks 5 and 8)

Block 5 includes Ashland, Crawford, Huron, Lorain, and Richland Counties

Block 8 includes Crawford, Hardin, Marion, Morrow, and Wyandot Counties.

OH_Statewide_Phase1_8 - Work Unit 228248 (Re-flight of 4 files in Block 3)

Includes a small part of Lorain County

OH_Statewide_Phase1_2 - Work Unit 198017 (Blocks 11 and 12)

Block 11 includes Defiance, Paulding, and Putnam Counties

Block 12 includes Allen, Paulding, Putnam, and Van Wert Counties

OH_Statewide_Phase1_3 - Work Unit 206353 (Blocks 4 and 6)

Blocks 4 & 6 which includes Ashland, Crawford, Erie, Huron, Lorain, Morrow, and Richland Counties.

OH_Statewide_Phase1_4 - Work Unit 208917 (Block 7)

Block 7 includes Crawford, Seneca, and Wyandot Counties

OH_Statewide_Phase1_7 - Work Unit 215686 (Blocks 2 and 3)

Blocks 2 & 3 include Ashtabula, Geauga, Lake, Portage, and Trumbull Counties

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, in Ohio State Plane North NAD83 (2011), US survey feet coordinates, 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 USGS Project Report that provides information about the project, vertical accuracy results, and the point classes and sensors used.

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

Link to the lidar report for OH_Statewide_Phase1_1 - Work Unit 182846 (Block 1) which includes Cuyahoga, Medina, and Summit Counties.

Link to the lidar report for OH_Statewide_Phase1_1 - Work Unit 182846 (Block 10) which includes Henry, Fulton, and Williams Counties.

Link to the lidar report for OH_Statewide_Phase1_2 - Work Unit 198017 (Block 11) which includes Defiance, Paulding, and Putnam Counties.

Link to the lidar report for OH_Statewide_Phase1_2 - Work Unit 198017 (Block 12) which includes Allen, Paulding, Putnam, and Van Wert Counties.

Link to the lidar report for OH_Statewide_Phase1_3 - Work Unit 206353 (Blocks 4 & 6) which includes Ashland, Crawford, Erie, Huron, Lorain, Morrow, and Richland Counties.

Link to the lidar report for OH_Statewide_Phase1_4 - Work Unit 208917 (Block 7) which includes Crawford, Seneca, and Wyandot Counties.

Link to the lidar report for OH_Statewide_Phase1_5 - Work Unit 210007 (Block 9) which includes Allen, Auglaize, Hancock, Hardin, Putnam, and Wyandot Counties.

Link to the lidar report for OH_Statewide_Phase1_5 - Work Unit 210007 (Block 13) which includes Allen, Auglaize, Mercer, Shelby, and Van Wert Counties.

Link to the lidar report for OH_Statewide_Phase1_6 - Work Unit 215019 (Block 5) which includes Ashland, Crawford, Huron, Lorain, and Richland Counties.

Link to the lidar report for OH_Statewide_Phase1_6 - Work Unit 215019 (Block 8) which includes Crawford, Hardin, Marion, Morrow, and Wyandot Counties.

Link to the lidar report for OH_Statewide_Phase1_7 - Work Unit 215686 (Blocks 2 & 3) which includes Ashtabula, Geauga, Lake, Portage, and Trumbull Counties.

Link to the lidar report for OH_Statewide_Phase1_8 - Work Unit 228248 which includes a small part of Lorain County.

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.

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.

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

Lidar Point Cloud Classification: The point cloud underwent a classification process to determine bare-earth points and non-ground points utilizing "first and only" as well as "last of many" lidar returns. This process determined Processed, but Unclassified (Class 1), Bare Earth Ground (Class 2), Low Noise (Class 7), Water (Class 9), Bridge Decks (Class 17), High Noise (Class 18), and Ignored Ground (Class 20). The bare-earth (Class 2 - Ground) lidar points underwent a manual QA/QC step to verify the quality of the DEM as well as a peer-based QC review. This included a review of the DEM surface to remove artifacts and ensure topographic quality. After the bare-earth surface is finalized, it is then used to generate all hydro-breaklines through a semi-automated process. All ground (Class 2) lidar data inside of the Lake Pond and Double Line Drain hydro flattening breaklines were then classified to water (Class 9) using TerraScan/LP360 macro functionality. A buffer of 2.3 feet (0.7 meters) was also used around each hydro-flattened feature to classify these ground (Class 2) points to Ignored Ground (Class 20). All Lake Pond Island and Double Line Drain Island features were checked to ensure that the ground (Class 2) points were reclassified to the correct classification after the automated classification was completed. All overlap data was processed through automated functionality provided by TerraScan to classify the overlapping flight line data to approved classes by USGS. The overlap data was classified using standard LAS overlap bit. These classes were created through automated processes only and were not verified for classification accuracy. Due to software limitations within TerraScan, these classes were used to trip the withheld bit within various software packages. These processes were reviewed and accepted by USGS through numerous conference calls and pilot study areas. All data was 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. Woolpert proprietary software and LP360 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 the vertical units were converted to meters (NAVD88 Geoid12B).

The NOAA Office for Coastal Management (OCM) created references to the Entwine Point Tile (EPT) files 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/OH_Statewide_Phase1_1_2019/ept.json

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

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

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

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

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

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

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