2019 - 2020 USGS Lidar DEM: Ohio Statewide - Phase 1
Data Set (DS) | OCM Partners (OCMP)GUID: gov.noaa.nmfs.inport:80072 | Updated: June 26, 2026 | Published / External
-
View As
- Full List View
- EXPORTS
- InPort XML
- ISO 19115
- WAF Files
- View in Hierarchy
Summary
Short Citation
OCM Partners, 2026: 2019 - 2020 USGS Lidar DEM: Ohio Statewide - Phase 1, https://www.fisheries.noaa.gov/inport/item/80072.
Full Citation Examples
Original Product: 1.25-foot bare-earth raster digital elevation model (DEM) data tiles in GeoTIFF format.
Original Dataset Full Geographic Extent: Approximately 12,808.6 square miles across northern Ohio
OH_Statewide_Phase1_1 - Work Unit 182846 (Blocks 1 and 10) approximately 1369 and 732 square miles
OH_Statewide_Phase1_2 - Work Unit 198017 (Blocks 11 and 12) approximately 793 and 849 square miles
OH_Statewide_Phase1_3 - Work Unit 206353 (Blocks 4 and 6) approximately 1750 (collectively) square miles
OH_Statewide_Phase1_4 - Work Unit 208917 (Block 7) approximately 1000 square miles
OH_Statewide_Phase1_5 - Work Unit 210007 (Blocks 9 and 13) approximately 1047 and 952 square miles
OH_Statewide_Phase1_6 - Work Unit 215019 (Blocks 5 and 8) approximately 1986 (collectively) square miles
OH_Statewide_Phase1_7 - Work Unit 215686 (Blocks 2 and 3) approximately 2600 (collectively) square miles
OH_Statewide_Phase1_8 - Work Unit 228248 (Re-flight of 4 files in Block 3) approximately 0.2 square miles
Original Dataset Description: The OH Statewide Phase 1 2019 B19 lidar project called for the planning, acquisition, processing, and production of derivative products of QL1 lidar data to be collected at a nominal pulse spacing (NPS) of 0.35 meters. Project specifications were based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, Version 1.3. Lidar data was delivered as processed LAS 1.4 files formatted to individual 1,250-foot x 1,250-foot tiles
Ground Conditions: Lidar was collected from November 4, 2019 through May 2, 2020 (with a re-flight of a small area, due to cloud gaps in Block 3 (Lorain County) in December 2021) 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 and meet ASPRS vertical accuracy guidelines, Woolpert established ground control points that were used to calibrate the lidar to known ground locations established throughout the project area. Additional independent accuracy checkpoints were collected and used to assess the vertical accuracy of the data. These checkpoints were not used to calibrate or post process the data.
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 GeoTIFF files hosted by USGS on Amazon Web Services.
This project will support the 3DEP mission, the Natural Resources Conservation Service (NRCS) high resolution elevation enterprise program and the Federal Emergency Management Agency (FEMA) Risk Mapping, Assessment and Planning (MAP) program.
Data Access & Downloads
-
Create custom data files by choosing data area, map projection, file format, etc. A new metadata will be produced to reflect your request using this record as a base.
-
GeoTIFF
Bulk download of data files in GeoTIFF format, in Ohio State Plane North NAD83 (2011), US survey feet coordinates, orthometric heights in feet.
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.
Controlled Theme Keywords
COASTAL ELEVATION, DIGITAL ELEVATION/TERRAIN MODEL (DEM), elevation, TERRAIN ELEVATION
URLs
-
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.
-
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 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.
Child Items
No Child Items for this record.
Contact Information
Point of Contact
NOAA Office for Coastal Management (NOAA/OCM)
coastal.info@noaa.gov
(843) 740-1202
https://coast.noaa.gov
Metadata Contact
NOAA Office for Coastal Management (NOAA/OCM)
coastal.info@noaa.gov
(843) 740-1202
https://coast.noaa.gov
Extents
-84.83° W,
-80.47° E,
42° N,
40.338481° S
2019-11-26 - 2020-05-02
OH_Statewide_Phase1_7 - Work Unit 215686 (Blocks 2 and 3)
Blocks 2 & 3 include Ashtabula, Geauga, Lake, Portage, and Trumbull Counties
2020-02-23 - 2020-04-27
OH_Statewide_Phase1_4 - Work Unit 208917 (Block 7)
Block 7 includes Crawford, Seneca, and Wyandot Counties
2019-11-09 - 2020-05-02
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
2019-11-04 - 2020-04-27
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
2020-02-22 - 2020-04-19
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.
2019-11-09 - 2021-12-21
OH_Statewide_Phase1_8 - Work Unit 228248 (Re-flight of 4 files in Block 3)
Includes a small part of Lorain County
2019-11-04 - 2020-02-21
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
2019-11-08 - 2020-04-19
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.
Item Identification
| Title: | 2019 - 2020 USGS Lidar DEM: Ohio Statewide - Phase 1 |
|---|---|
| Short Name: | oh2019_stwde_phase1_dem_m14622 |
| Status: | Completed |
| Creation Date: | 2019 |
| Publication Date: | 2026 |
| Abstract: |
Original Product: 1.25-foot bare-earth raster digital elevation model (DEM) data tiles in GeoTIFF format. Original Dataset Full Geographic Extent: Approximately 12,808.6 square miles across northern Ohio OH_Statewide_Phase1_1 - Work Unit 182846 (Blocks 1 and 10) approximately 1369 and 732 square miles OH_Statewide_Phase1_2 - Work Unit 198017 (Blocks 11 and 12) approximately 793 and 849 square miles OH_Statewide_Phase1_3 - Work Unit 206353 (Blocks 4 and 6) approximately 1750 (collectively) square miles OH_Statewide_Phase1_4 - Work Unit 208917 (Block 7) approximately 1000 square miles OH_Statewide_Phase1_5 - Work Unit 210007 (Blocks 9 and 13) approximately 1047 and 952 square miles OH_Statewide_Phase1_6 - Work Unit 215019 (Blocks 5 and 8) approximately 1986 (collectively) square miles OH_Statewide_Phase1_7 - Work Unit 215686 (Blocks 2 and 3) approximately 2600 (collectively) square miles OH_Statewide_Phase1_8 - Work Unit 228248 (Re-flight of 4 files in Block 3) approximately 0.2 square miles Original Dataset Description: The OH Statewide Phase 1 2019 B19 lidar project called for the planning, acquisition, processing, and production of derivative products of QL1 lidar data to be collected at a nominal pulse spacing (NPS) of 0.35 meters. Project specifications were based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, Version 1.3. Lidar data was delivered as processed LAS 1.4 files formatted to individual 1,250-foot x 1,250-foot tiles Ground Conditions: Lidar was collected from November 4, 2019 through May 2, 2020 (with a re-flight of a small area, due to cloud gaps in Block 3 (Lorain County) in December 2021) 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 and meet ASPRS vertical accuracy guidelines, Woolpert established ground control points that were used to calibrate the lidar to known ground locations established throughout the project area. Additional independent accuracy checkpoints were collected and used to assess the vertical accuracy of the data. These checkpoints were not used to calibrate or post process the data. 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 GeoTIFF files hosted by USGS on Amazon Web Services. |
| Purpose: |
This project will support the 3DEP mission, the Natural Resources Conservation Service (NRCS) high resolution elevation enterprise program and the Federal Emergency Management Agency (FEMA) Risk Mapping, Assessment and Planning (MAP) program. |
| Supplemental Information: |
USGS Contract No. G16PC00022, Task Order No. 140G0219F0279. Contractor: Woolpert. Raster File Type = TIFF Bit Depth/Pixel Type = 32-bit float Raster Cell Size = 1.25 Feet Interpolation or Re-sampling Technique = Triangulated Irregular Network Required Vertical Accuracy = 19.6 cm NVA |
Keywords
Theme Keywords
| Thesaurus | Keyword |
|---|---|
| Global Change Master Directory (GCMD) Science Keywords |
EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION
|
| Global Change Master Directory (GCMD) Science Keywords |
EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN ELEVATION > DIGITAL ELEVATION/TERRAIN MODEL (DEM)
|
| Global Change Master Directory (GCMD) Science Keywords |
EARTH SCIENCE > OCEANS > COASTAL PROCESSES > COASTAL ELEVATION
|
| ISO 19115 Topic Category |
elevation
|
Spatial Keywords
| Thesaurus | Keyword |
|---|---|
| Global Change Master Directory (GCMD) Location Keywords |
CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA
|
| Global Change Master Directory (GCMD) Location Keywords |
CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > OHIO
|
| Global Change Master Directory (GCMD) Location Keywords |
VERTICAL LOCATION > LAND SURFACE
|
| UNCONTROLLED | |
| None | Allen County |
| None | Ashland County |
| None | Ashtabula County |
| None | Auglaize County |
| None | Craford County |
| None | Crawford County |
| None | Cuyahoga County |
| None | Defiance County |
| None | Erie County |
| None | Fulton County |
| None | Geauga County |
| None | Hancock County |
| None | Hardin County |
| None | Henry County |
| None | Holmes County |
| None | Huron County |
| None | Knox County |
| None | Lake County |
| None | Lorain County |
| None | Marion County |
| None | Medina County |
| None | Mercer County |
| None | Morrow County |
| None | Paulding County |
| None | Portage County |
| None | Putnam County |
| None | Richland County |
| None | Seneca County |
| None | Shelby County |
| None | Summit County |
| None | Trumbull County |
| None | Van Wert County |
| None | Williams County |
| None | Wyandot County |
Instrument Keywords
| Thesaurus | Keyword |
|---|---|
| Global Change Master Directory (GCMD) Instrument Keywords |
LIDAR > Light Detection and Ranging
|
Platform Keywords
| Thesaurus | Keyword |
|---|---|
| Global Change Master Directory (GCMD) Platform Keywords |
Airplane > Airplane
|
Physical Location
| Organization: | Office for Coastal Management |
|---|---|
| City: | Charleston |
| State/Province: | SC |
Data Set Information
| Data Set Scope Code: | Data Set |
|---|---|
| Data Set Type: | Elevation |
| Maintenance Frequency: | None Planned |
| Data Presentation Form: | Model (digital) |
| Distribution Liability: |
Any conclusions drawn from the analysis of this information are not the responsibility of NOAA, the Office for Coastal Management or its partners. |
| Data Set Credit: | Woolpert, USGS |
Support Roles
Data Steward
| Date Effective From: | 2026 |
|---|---|
| Date Effective To: | |
| Contact (Organization): | NOAA Office for Coastal Management (NOAA/OCM) |
| Address: |
2234 South Hobson Ave Charleston, SC 29405-2413 |
| Email Address: | coastal.info@noaa.gov |
| Phone: | (843) 740-1202 |
| URL: | https://coast.noaa.gov |
Distributor
| Date Effective From: | 2026 |
|---|---|
| Date Effective To: | |
| Contact (Organization): | NOAA Office for Coastal Management (NOAA/OCM) |
| Address: |
2234 South Hobson Ave Charleston, SC 29405-2413 |
| Email Address: | coastal.info@noaa.gov |
| Phone: | (843) 740-1202 |
| URL: | https://coast.noaa.gov |
Distributor
| Date Effective From: | 2020 |
|---|---|
| Date Effective To: | |
| Contact (Organization): | U.S. Geological Survey |
| Address: |
12201 Sunrise Valley Drive Reston, VA 20191 USA |
| URL: | USGS Home |
Metadata Contact
| Date Effective From: | 2026 |
|---|---|
| Date Effective To: | |
| Contact (Organization): | NOAA Office for Coastal Management (NOAA/OCM) |
| Address: |
2234 South Hobson Ave Charleston, SC 29405-2413 |
| Email Address: | coastal.info@noaa.gov |
| Phone: | (843) 740-1202 |
| URL: | https://coast.noaa.gov |
Point of Contact
| Date Effective From: | 2026 |
|---|---|
| Date Effective To: | |
| Contact (Organization): | NOAA Office for Coastal Management (NOAA/OCM) |
| Address: |
2234 South Hobson Ave Charleston, SC 29405-2413 |
| Email Address: | coastal.info@noaa.gov |
| Phone: | (843) 740-1202 |
| URL: | https://coast.noaa.gov |
Extents
| Currentness Reference: | Ground Condition |
|---|
Extent Group 1
Extent Group 1 / Geographic Area 1
| W° Bound: | -84.83 | |
|---|---|---|
| E° Bound: | -80.47 | |
| N° Bound: | 42 | |
| S° Bound: | 40.338481 |
Extent Group 1 / Time Frame 1
| Time Frame Type: | Range |
|---|---|
| Start: | 2019-11-26 |
| End: | 2020-05-02 |
| Description: |
OH_Statewide_Phase1_7 - Work Unit 215686 (Blocks 2 and 3) Blocks 2 & 3 include Ashtabula, Geauga, Lake, Portage, and Trumbull Counties |
Extent Group 1 / Time Frame 2
| Time Frame Type: | Range |
|---|---|
| Start: | 2020-02-23 |
| End: | 2020-04-27 |
| Description: |
OH_Statewide_Phase1_4 - Work Unit 208917 (Block 7) Block 7 includes Crawford, Seneca, and Wyandot Counties |
Extent Group 1 / Time Frame 3
| Time Frame Type: | Range |
|---|---|
| Start: | 2019-11-09 |
| End: | 2020-05-02 |
| Description: |
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 |
Extent Group 1 / Time Frame 4
| Time Frame Type: | Range |
|---|---|
| Start: | 2019-11-04 |
| End: | 2020-04-27 |
| Description: |
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 |
Extent Group 1 / Time Frame 5
| Time Frame Type: | Range |
|---|---|
| Start: | 2020-02-22 |
| End: | 2020-04-19 |
| Description: |
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. |
Extent Group 1 / Time Frame 6
| Time Frame Type: | Range |
|---|---|
| Start: | 2019-11-09 |
| End: | 2021-12-21 |
| Description: |
OH_Statewide_Phase1_8 - Work Unit 228248 (Re-flight of 4 files in Block 3) Includes a small part of Lorain County |
Extent Group 1 / Time Frame 7
| Time Frame Type: | Range |
|---|---|
| Start: | 2019-11-04 |
| End: | 2020-02-21 |
| Description: |
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 |
Extent Group 1 / Time Frame 8
| Time Frame Type: | Range |
|---|---|
| Start: | 2019-11-08 |
| End: | 2020-04-19 |
| Description: |
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. |
Spatial Information
Spatial Resolution
| Horizontal Distance: | 1.25 Foot |
|---|
Spatial Representation
Representations Used
| Grid: | Yes |
|---|---|
| Vector: | No |
| Text / Table: | No |
| TIN: | No |
| Stereo Model: | No |
| Video: | No |
Reference Systems
Reference System 1
Coordinate Reference System |
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Reference System 2
Coordinate Reference System |
|||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||
Access Information
| Security Class: | Unclassified |
|---|---|
| Data Access Procedure: |
Data is available online for bulk and custom downloads. |
| Data Access Constraints: |
None |
| Data Use Constraints: |
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. |
Distribution Information
Distribution 1
| Download URL: | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=14622/details/14622 |
|---|---|
| Distributor: | NOAA Office for Coastal Management (NOAA/OCM) (2026 - Present) |
| File Name: | Customized Download |
| Description: |
Create custom data files by choosing data area, map projection, file format, etc. A new metadata will be produced to reflect your request using this record as a base. |
| File Type (Deprecated): | Zip |
| Compression: | Zip |
Distribution 2
| Download URL: | https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/OH_Statewide_Phase1_2019_B19/ |
|---|---|
| Distributor: | U.S. Geological Survey (2020 - Present) |
| File Name: | Bulk Download |
| Description: |
Bulk download of data files in GeoTIFF format, in Ohio State Plane North NAD83 (2011), US survey feet coordinates, orthometric heights in feet. |
| File Type (Deprecated): | LAZ |
| Distribution Format: | GeoTIFF |
URLs
URL 1
| URL: | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/OH_Statewide_Phase1_2019_B19/OH_Statewide_Phase1_2019_B19_WP_Report.pdf |
|---|---|
| Name: | USGS Work Project Report |
| URL Type: |
Online Resource
|
| File Resource Format: | |
| Description: |
Link to the USGS Project Report that provides information about the project, vertical accuracy results, and the point classes and sensors used. |
URL 2
| URL: | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/OH_Statewide_Phase1_2019_B19/ |
|---|---|
| Name: | USGS Additional Info |
| URL Type: |
Online Resource
|
| Description: |
Link to the reports, breaklines, metadata, spatial metadata, and shapefiles. |
URL 3
| URL: | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/OH_Statewide_Phase1_2019_B19/OH_Statewide_Phase1_1_2019/reports/OH_Statewide_Phase_1_Lidar_Project_Report_Block_1.pdf |
|---|---|
| Name: | Lidar Report - OH_Statewide_Phase1_1 (Block 1) |
| URL Type: |
Online Resource
|
| File Resource Format: | |
| Description: |
Link to the lidar report for OH_Statewide_Phase1_1 - Work Unit 182846 (Block 1) which includes Cuyahoga, Medina, and Summit Counties. |
URL 4
| URL: | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/OH_Statewide_Phase1_2019_B19/OH_Statewide_Phase1_1_2019/reports/OH_Statewide_Phase_1B_Lidar_Project_Report_Block_10.pdf |
|---|---|
| Name: | Lidar Report - OH_Statewide_Phase1_1 (Block 10) |
| URL Type: |
Online Resource
|
| File Resource Format: | |
| Description: |
Link to the lidar report for OH_Statewide_Phase1_1 - Work Unit 182846 (Block 10) which includes Henry, Fulton, and Williams Counties. |
URL 5
| URL: | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/OH_Statewide_Phase1_2019_B19/OH_Statewide_Phase1_2_2019/reports/OH_Statewide_Phase_1_Lidar_Project_Report_Block_11.pdf |
|---|---|
| Name: | Lidar Report - OH_Statewide_Phase1_2 (Block 11) |
| URL Type: |
Online Resource
|
| File Resource Format: | |
| Description: |
Link to the lidar report for OH_Statewide_Phase1_2 - Work Unit 198017 (Block 11) which includes Defiance, Paulding, and Putnam Counties. |
URL 6
| URL: | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/OH_Statewide_Phase1_2019_B19/OH_Statewide_Phase1_2_2019/reports/OH_Statewide_Phase_1_Lidar_Project_Report_Block_12.pdf |
|---|---|
| Name: | Lidar Report - OH_Statewide_Phase1_2 (Block 12) |
| URL Type: |
Online Resource
|
| File Resource Format: | |
| Description: |
Link to the lidar report for OH_Statewide_Phase1_2 - Work Unit 198017 (Block 12) which includes Allen, Paulding, Putnam, and Van Wert Counties. |
URL 7
| URL: | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/OH_Statewide_Phase1_2019_B19/OH_Statewide_Phase1_3_2019/reports/OH_Statewide_Phase_1_Lidar_Project_Report_206353.pdf |
|---|---|
| Name: | Lidar Report - OH_Statewide_Phase1_3 (Blocks 4 & 6) |
| URL Type: |
Online Resource
|
| File Resource Format: | |
| Description: |
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. |
URL 8
| URL: | https://coast.noaa.gov/dataviewer/ |
|---|---|
| Name: | NOAA's Office for Coastal Management (OCM) Data Access Viewer (DAV) |
| URL Type: |
Online Resource
|
| File Resource Format: | HTML |
| Description: |
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. |
URL 9
| URL: | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/OH_Statewide_Phase1_2019_B19/OH_Statewide_Phase1_4_2019/reports/OH_Statewide_Phase_1_Lidar_Project_Report_Block_7.pdf |
|---|---|
| Name: | Lidar Report - OH_Statewide_Phase1_4 (Block 7) |
| URL Type: |
Online Resource
|
| File Resource Format: | |
| Description: |
Link to the lidar report for OH_Statewide_Phase1_4 - Work Unit 208917 (Block 7) which includes Crawford, Seneca, and Wyandot Counties. |
URL 10
| URL: | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/OH_Statewide_Phase1_2019_B19/OH_Statewide_Phase1_5_2019/reports/OH_Statewide_Phase_1_Lidar_Project_Report_Block_9.pdf |
|---|---|
| Name: | Lidar Report - OH_Statewide_Phase1_5 (Block 9) |
| URL Type: |
Online Resource
|
| File Resource Format: | |
| Description: |
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. |
URL 11
| URL: | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/OH_Statewide_Phase1_2019_B19/OH_Statewide_Phase1_5_2019/reports/OH_Statewide_Phase_1_Lidar_Project_Report_Block_13.pdf |
|---|---|
| Name: | Lidar Report - OH_Statewide_Phase1_5 (Block 13) |
| URL Type: |
Online Resource
|
| File Resource Format: | |
| Description: |
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. |
URL 12
| URL: | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/OH_Statewide_Phase1_2019_B19/OH_Statewide_Phase1_6_2019/reports/OH_Statewide_Phase_1_Lidar_Project_Report_Block_5.pdf |
|---|---|
| Name: | Lidar Report - OH_Statewide_Phase1_6 (Block 5) |
| URL Type: |
Online Resource
|
| File Resource Format: | |
| Description: |
Link to the lidar report for OH_Statewide_Phase1_6 - Work Unit 215019 (Block 5) which includes Ashland, Crawford, Huron, Lorain, and Richland Counties. |
URL 13
| URL: | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/OH_Statewide_Phase1_2019_B19/OH_Statewide_Phase1_6_2019/reports/OH_Statewide_Phase_1_Lidar_Project_Report_Block_8.pdf |
|---|---|
| Name: | Lidar Report - OH_Statewide_Phase1_6 (Block 8) |
| URL Type: |
Online Resource
|
| File Resource Format: | |
| Description: |
Link to the lidar report for OH_Statewide_Phase1_6 - Work Unit 215019 (Block 8) which includes Crawford, Hardin, Marion, Morrow, and Wyandot Counties. |
URL 14
| URL: | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/OH_Statewide_Phase1_2019_B19/OH_Statewide_Phase1_7_2019/reports/79574_Lidar_Report_215686.pdf |
|---|---|
| Name: | Lidar Report - OH_Statewide_Phase1_7 (Blocks 2 & 3) |
| URL Type: |
Online Resource
|
| File Resource Format: | |
| Description: |
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. |
URL 15
| URL: | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/OH_Statewide_Phase1_2019_B19/OH_Statewide_Phase1_8_2019/reports/OH_Statewide_Phase1_8_2019_WU228248_Lidar_Project_Report.pdf |
|---|---|
| Name: | Lidar Report - OH_Statewide_Phase1_8 |
| URL Type: |
Online Resource
|
| File Resource Format: | |
| Description: |
Link to the lidar report for OH_Statewide_Phase1_8 - Work Unit 228248 which includes a small part of Lorain County. |
URL 16
| URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase1_1_2019/ept.json |
|---|---|
| Name: | USGS Entwine Point Tile (EPT) - OH_Statewide_Phase1_1_2019 |
| URL Type: |
Online Resource
|
| File Resource Format: | json |
| Description: |
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. |
URL 17
| URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase1_2_2019/ept.json |
|---|---|
| Name: | USGS Entwine Point Tile (EPT) - OH_Statewide_Phase1_2_2019 |
| URL Type: |
Online Resource
|
| File Resource Format: | json |
| Description: |
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. |
URL 18
| URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase1_3_2019/ept.json |
|---|---|
| Name: | USGS Entwine Point Tile (EPT) - OH_Statewide_Phase1_3_2019 |
| URL Type: |
Online Resource
|
| File Resource Format: | json |
| Description: |
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. |
URL 19
| URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase1_4_2019/ept.json |
|---|---|
| Name: | USGS Entwine Point Tile (EPT) - OH_Statewide_Phase1_4_2019 |
| URL Type: |
Online Resource
|
| File Resource Format: | json |
| Description: |
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. |
URL 20
| URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase1_5_2019/ept.json |
|---|---|
| Name: | USGS Entwine Point Tile (EPT) - OH_Statewide_Phase1_5_2019 |
| URL Type: |
Online Resource
|
| File Resource Format: | json |
| Description: |
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. |
URL 21
| URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase1_6_2019/ept.json |
|---|---|
| Name: | USGS Entwine Point Tile (EPT) - OH_Statewide_Phase1_6_2019 |
| URL Type: |
Online Resource
|
| File Resource Format: | json |
| Description: |
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. |
URL 22
| URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase1_7_2019/ept.json |
|---|---|
| Name: | USGS Entwine Point Tile (EPT) - OH_Statewide_Phase1_7_2019 |
| URL Type: |
Online Resource
|
| File Resource Format: | json |
| Description: |
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. |
URL 23
| URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/OH_Statewide_Phase1_8_2019/ept.json |
|---|---|
| Name: | USGS Entwine Point Tile (EPT) - OH_Statewide_Phase1_8_2019 |
| URL Type: |
Online Resource
|
| File Resource Format: | json |
| Description: |
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. |
URL 24
Technical Environment
| Description: |
Microsoft Windows 10 Version 1803 (Build 17134.1304); ArcMap 10.7; ArcCatalog 10.7; TerraScan ver. 20; TerraModeler ver. 20; LP360 v2019.1.30.4. |
|---|
Data Quality
| Horizontal Positional Accuracy: |
The data sets were produced to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a Positional Horizontal Accuracy = +/- 36.4 cm at a 95% confidence level. |
|---|---|
| Vertical Positional Accuracy: |
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 DEM Vertical Accuracy: Non-Vegetated Vertical Accuracy (NVA) = 7.16 cm at 95% Confidence Level or 3.7 cm RMSE Vegetated Vertical Accuracy (VVA) = 15.24 cm at 95th Percentile |
| Completeness Report: |
Datasets contain complete coverage of tiles. No points have been removed or excluded. A visual qualitative assessment was performed to ensure data completeness. There are no void areas or missing data. The DEM is of good quality and data passes Non-Vegetated and Vegetated Vertical Accuracy specifications. |
| Conceptual Consistency: |
Data covers the entire area specified for this project. |
Data Management
| Have Resources for Management of these Data Been Identified?: | Yes |
|---|---|
| Approximate Percentage of Budget for these Data Devoted to Data Management: | Unknown |
| Do these Data Comply with the Data Access Directive?: | Yes |
| Actual or Planned Long-Term Data Archive Location: | NCEI-CO |
| How Will the Data Be Protected from Accidental or Malicious Modification or Deletion Prior to Receipt by the Archive?: |
Data is backed up to tape and to cloud storage. |
Lineage
| Lineage Statement: |
The NOAA Office for Coastal Management (OCM) ingested references to the USGS GeoTIFF files that are hosted on Amazon Web Services (AWS), into the Digital Coast Data Access Viewer (DAV). The DAV accesses the raster data as it resides on AWS. |
|---|
Sources
USGS AWS GeoTIFF Files - OH_Statewide_Phase1_1
| Contact Role Type: | Publisher |
|---|---|
| Contact Type: | Organization |
| Contact Name: | USGS |
| Citation URL: | https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/OH_Statewide_Phase1_2019_B19/OH_Statewide_Phase1_1_2019/TIFF/ |
| Citation URL Name: | USGS AWS GeoTIFF Files for OH_Statewide_Phase1_1_2019 |
USGS AWS GeoTIFF Files - OH_Statewide_Phase1_2
| Contact Role Type: | Publisher |
|---|---|
| Contact Type: | Organization |
| Contact Name: | USGS |
| Citation URL: | https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/OH_Statewide_Phase1_2019_B19/OH_Statewide_Phase1_2_2019/TIFF/ |
| Citation URL Name: | USGS AWS GeoTIFF Files for OH_Statewide_Phase1_2_2019 |
USGS AWS GeoTIFF Files - OH_Statewide_Phase1_3
| Contact Role Type: | Publisher |
|---|---|
| Contact Type: | Organization |
| Contact Name: | USGS |
| Citation URL: | https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/OH_Statewide_Phase1_2019_B19/OH_Statewide_Phase1_3_2019/TIFF/ |
| Citation URL Name: | USGS AWS GeoTIFF Files for OH_Statewide_Phase1_3_2019 |
USGS AWS GeoTIFF Files - OH_Statewide_Phase1_4
| Contact Role Type: | Publisher |
|---|---|
| Contact Type: | Organization |
| Contact Name: | USGS |
| Citation URL: | https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/OH_Statewide_Phase1_2019_B19/OH_Statewide_Phase1_4_2019/TIFF/ |
| Citation URL Name: | Entwine Point Tile file forOH_Statewide_Phase1_4_2019 |
USGS AWS GeoTIFF Files - OH_Statewide_Phase1_5
| Contact Role Type: | Publisher |
|---|---|
| Contact Type: | Organization |
| Contact Name: | USGS |
| Citation URL: | https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/OH_Statewide_Phase1_2019_B19/OH_Statewide_Phase1_5_2019/TIFF/ |
| Citation URL Name: | USGS AWS GeoTIFF Files for OH_Statewide_Phase1_5_2019 |
USGS AWS GeoTIFF Files - OH_Statewide_Phase1_6
| Contact Role Type: | Publisher |
|---|---|
| Contact Type: | Organization |
| Contact Name: | USGS |
| Citation URL: | https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/OH_Statewide_Phase1_2019_B19/OH_Statewide_Phase1_6_2019/TIFF/ |
| Citation URL Name: | USGS AWS GeoTIFF Files for OH_Statewide_Phase1_6_2019 |
USGS AWS GeoTIFF Files - OH_Statewide_Phase1_7
| Contact Role Type: | Publisher |
|---|---|
| Contact Type: | Organization |
| Contact Name: | USGS |
| Citation URL: | https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/OH_Statewide_Phase1_2019_B19/OH_Statewide_Phase1_7_2019/TIFF/ |
| Citation URL Name: | USGS AWS GeoTIFF Files for OH_Statewide_Phase1_7_2019 |
USGS AWS GeoTIFF Files - OH_Statewide_Phase1_8
| Contact Role Type: | Publisher |
|---|---|
| Contact Type: | Organization |
| Contact Name: | USGS |
| Citation URL: | https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/OH_Statewide_Phase1_2019_B19/OH_Statewide_Phase1_8_2019/TIFF/ |
| Citation URL Name: | USGS AWS GeoTIFF Files for OH_Statewide_Phase1_8_2019 |
Process Steps
Process Step 1
| Description: |
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. |
|---|---|
| Process Date/Time: | 2021-06-08 00:00:00 |
Process Step 2
| Description: |
Hydro-Flattened Digital Elevation Models (DEMs): Class 2 (ground) lidar points in conjunction with the hydro breaklines as well bridge breaklines were used to create a 1.25-foot hydro-flattened bare-earth raster DEM. Using automated scripting routines within ArcMap, a GeoTIFF file was created for each tile. Each surface is reviewed using Global Mapper to check for any surface anomalies or incorrect elevations found within the surface. |
|---|---|
| Process Date/Time: | 2020-09-23 00:00:00 |
Process Step 3
| Description: |
The NOAA Office for Coastal Management (OCM) created references to the USGS GeoTIFF 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 raster data as it resides on Amazon Web Services (AWS). These are the GeoTIFF files that are being accessed: https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/OH_Statewide_Phase1_2019_B19/OH_Statewide_Phase1_1_2019/TIFF/ https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/OH_Statewide_Phase1_2019_B19/OH_Statewide_Phase1_2_2019/TIFF/ https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/OH_Statewide_Phase1_2019_B19/OH_Statewide_Phase1_3_2019/TIFF/ https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/OH_Statewide_Phase1_2019_B19/OH_Statewide_Phase1_4_2019/TIFF/ https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/OH_Statewide_Phase1_2019_B19/OH_Statewide_Phase1_5_2019/TIFF/ https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/OH_Statewide_Phase1_2019_B19/OH_Statewide_Phase1_6_2019/TIFF/ https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/OH_Statewide_Phase1_2019_B19/OH_Statewide_Phase1_7_2019/TIFF/ https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/OPR/Projects/OH_Statewide_Phase1_2019_B19/OH_Statewide_Phase1_8_2019/TIFF/ |
|---|---|
| Process Date/Time: | 2026-06-26 00:00:00 |
| Process Contact: | Office for Coastal Management (OCM) |
| ROR: | https://ror.org/05v14bq57 |
Acquisition Information
Instruments
Instrument 1
| Identifier: | Leica Terrain Mapper |
|---|---|
| Instrument / Gear: | Instrument |
| Instrument Type: | Lidar |
| Description: |
Leica Terrain Mapper is a compact laser-based system designed for the acquisition of high-density topographic and return signal intensity data from a variety of airborne platforms, at flying heights up to 5500 m AGL |
Related Items
| Item Type | Relationship Type | Title |
|---|---|---|
| Data Set (DS) | Cross Reference |
2019 - 2020 USGS Lidar: Ohio Statewide - Phase 1 |
Catalog Details
| Catalog Item ID: | 80072 |
|---|---|
| GUID: | gov.noaa.nmfs.inport:80072 |
| Metadata Record Created By: | Rebecca Mataosky |
| Metadata Record Created: | 2026-06-26 14:23+0000 |
| Metadata Record Last Modified By: | Rebecca Mataosky |
| Metadata Record Last Modified: | 2026-06-26 18:29+0000 |
| Metadata Record Published: | 2026-06-26 |
| Owner Org: | OCMP |
| Metadata Publication Status: | Published Externally |
| Do Not Publish?: | N |
| Metadata Last Review Date: | 2023-04-11 |
| Metadata Review Frequency: | 1 Year |
| Metadata Next Review Date: | 2024-04-11 |