2020 USGS Lidar: Hurricane Michael, FL
Data Set (DS) | OCM Partners (OCMP)GUID: gov.noaa.nmfs.inport:69038 | Updated: February 7, 2024 | Published / External
Summary
Short Citation
OCM Partners, 2024: 2020 USGS Lidar: Hurricane Michael, FL, https://www.fisheries.noaa.gov/inport/item/69038.
Full Citation Examples
Product: These lidar data are processed Classified LAS 1.4 files, formatted to 9702 individual 5,000 ft x 5,000 ft tiles; used to create intensity images, 3D breaklines and hydro-flattened DEMs as necessary.
Geographic Extent: Florida Hurricane Michael, Florida, covering approximately 8,263 square miles. These data cover the following counties:
Bay, Calhoun, Franklin, Gadsden, Gulf, Holmes, Jackson, Jefferson (portion), Leon, Liberty, Wakulla, Walton (portion), Washington
Dataset Description: Hurricane Michael, Florida 2020 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.35 meter. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, Version 2.1. The data was developed based on a horizontal datum/projection of NAD83 (2011), State Plane North, U.S. Survey Feet and vertical datum of NAVD88 (GEOID12B), U.S. Survey Feet. Lidar data was delivered as processed Classified LAS 1.4 files, formatted to 5000 ft x 5000 ft tiles. All tiled to the same 5000 ft x 5000 ft schema.
Ground Conditions: Lidar was collected in late 2019 through early 2020, 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.
This metadata 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.
Distribution Information
-
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.
-
LAS/LAZ - LASer
Bulk download of data files in LAZ format, based on a horizontal datum/projection of Florida State Plane North, NAD83(2011), US feet and a vertical datum of NAVD88 (GEOID12B) and units in feet. This url links to the USGS copy of the files, from which the Entwine Point Tile files originated. These have not been reviewed by OCM and the link is provided here for convenience.
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, elevation, TERRAIN ELEVATION
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
Metadata Contact
NOAA Office for Coastal Management (NOAA/OCM)
coastal.info@noaa.gov
(843) 740-1202
Extents
-86.2° W,
-83.65° E,
31.03° N,
29.56° S
2019-12-20 - 2020-10-02
Dates of collection for Work Unit 229804 (Block 7: Bay (portion), Calhoun (portion) , Franklin (portion) , Gulf, Liberty (portion), and Washington (portion)) counties,
2019-12-18 - 2020-01-07
Dates of collection for Work Unit 188515 (Block 1, Wakulla and Jefferson Counties)
2019-12-18 - 2019-12-25
Dates of collection for Work Unit 212018 (Block 2, Wakulla and Jefferson Counties)
2019-12-16 - 2020-01-25
Dates of collection for Work Unit 217056 (Block 4, Leon, Gadsden, Liberty and Franklin Counties)
2020-02-14 - 2020-02-27
Dates of collection for Work Unit 227988 (Block 5, Washington, Holmes, Walton Counties)
2019-12-16 - 2020-04-21
Dates of collection for Work Unit 229801 (Block 6, Bay, Calhoun, Franklin, Gadsden, Gulf, Holmes, Jackson, Liberty, and Walton Counties)
2019-12-16 - 2020-01-07
Dates of collection for Work Unit 216141 (Block 3, Leon, Gadsden, Liberty, and Franklin Counties)
Item Identification
| Title: | 2020 USGS Lidar: Hurricane Michael, FL |
|---|---|
| Short Name: | fl2020_michael_m9686_metadata |
| Status: | Completed |
| Creation Date: | 2020 |
| Publication Date: | 2022-06-01 |
| Abstract: |
Product: These lidar data are processed Classified LAS 1.4 files, formatted to 9702 individual 5,000 ft x 5,000 ft tiles; used to create intensity images, 3D breaklines and hydro-flattened DEMs as necessary. Geographic Extent: Florida Hurricane Michael, Florida, covering approximately 8,263 square miles. These data cover the following counties: Bay, Calhoun, Franklin, Gadsden, Gulf, Holmes, Jackson, Jefferson (portion), Leon, Liberty, Wakulla, Walton (portion), Washington Dataset Description: Hurricane Michael, Florida 2020 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.35 meter. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, Version 2.1. The data was developed based on a horizontal datum/projection of NAD83 (2011), State Plane North, U.S. Survey Feet and vertical datum of NAVD88 (GEOID12B), U.S. Survey Feet. Lidar data was delivered as processed Classified LAS 1.4 files, formatted to 5000 ft x 5000 ft tiles. All tiled to the same 5000 ft x 5000 ft schema. Ground Conditions: Lidar was collected in late 2019 through early 2020, 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. This metadata 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. |
| Purpose: |
To acquire detailed surface elevation data for use in conservation planning, design, research, floodplain mapping, dam safety assessments and elevation modeling, etc. Classified LAS files are used to show the manually reviewed bare earth surface. This allows the user to create Intensity Images, Breaklines and Raster DEM. The purpose of these lidar data was to produce high accuracy 3D hydro-flattened Digital Elevation Model (DEM) with a 2.5 foot cell size. These lidar point cloud data were used to create intensity images, 3D breaklines, and hydro-flattened DEMs as necessary. |
| Supplemental Information: |
USGS Contract No. 140G0220F0002 CONTRACTOR: Dewberry. SUBCONTRACTOR: Airborne Imaging Lidar and Axis Geospatial data were acquired and calibrated by Airborne Imaging and Axis Geospatial. All follow-on processing was completed by the prime contractor.
The following are the USGS lidar fields in JSON: {
"ldrinfo" : {
"ldrspec" : "U.S. Geological Survey (USGS) - National Geospatial Program (NGP) Lidar Base Specification v2.1", "ldrsens" : "Riegl VQ-1560i", "ldrmaxnr" : "7", "ldrnps" : "0.31", "ldrdens" : "9.9", "ldranps" : "0.31", "ldradens" : "9.9", "ldrfltht" : "1300", "ldrfltsp" : "160", "ldrscana" : "60", "ldrscanr" : "375", "ldrpulsr" : "1333.3", "ldrpulsd" : "3", "ldrpulsw" : "0.325", "ldrwavel" : "1064", "ldrmpia" : "1", "ldrbmdiv" : "0.25", "ldrswatw" : "1501", "ldrswato" : "20", "ldrgeoid" : "g2012Bu0.bin" }, "ldrinfo" : {
"ldrspec" : "U.S. Geological Survey (USGS) - National Geospatial Program (NGP) Lidar Base Specification v2.1", "ldrsens" : "Riegl LMS-1560i", "ldrmaxnr" : "7", "ldrnps" : "0.31", "ldrdens" : "10", "ldranps" : "0.24", "ldradens" : "17.4", "ldrfltht" : "762", "ldrfltsp" : "120", "ldrscana" : "58.5", "ldrscanr" : "362", "ldrpulsr" : "800", "ldrpulsd" : "3", "ldrpulsw" : "0.9", "ldrwavel" : "1064", "ldrmpia" : "1", "ldrbmdiv" : "0.25", "ldrswatw" : "853", "ldrswato" : "50", "ldrgeoid" : "g2012Bu0.bin" }, "ldraccur" : {
"ldrchacc" : "0", "rawnva" : "0", "rawnvan" : "0" }, "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 are assigned per the producer's discretion. Dewberry did not classify overage points.", "lasintr" : "16", "lasclass" : {
"clascode" : "1", "clasitem" : "Processed, but Unclassified" }, "lasclass" : {
"clascode" : "2", "clasitem" : "Bare Earth Ground" }, "lasclass" : {
"clascode" : "6", "clasitem" : "Building Rooftops" }, "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" } }} |
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 > 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 > FLORIDA
|
| Global Change Master Directory (GCMD) Location Keywords |
VERTICAL LOCATION > LAND SURFACE
|
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: | Dewberry, USGS |
Support Roles
Data Steward
| Date Effective From: | 2023 |
|---|---|
| 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: | 2023 |
|---|---|
| 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: | 2022 |
|---|---|
| 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: | 2023 |
|---|---|
| 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: | 2023 |
|---|---|
| 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: | -86.2 | |
|---|---|---|
| E° Bound: | -83.65 | |
| N° Bound: | 31.03 | |
| S° Bound: | 29.56 |
Extent Group 1 / Time Frame 1
| Time Frame Type: | Range |
|---|---|
| Start: | 2019-12-20 |
| End: | 2020-10-02 |
| Description: |
Dates of collection for Work Unit 229804 (Block 7: Bay (portion), Calhoun (portion) , Franklin (portion) , Gulf, Liberty (portion), and Washington (portion)) counties, |
Extent Group 1 / Time Frame 2
| Time Frame Type: | Range |
|---|---|
| Start: | 2019-12-18 |
| End: | 2020-01-07 |
| Description: |
Dates of collection for Work Unit 188515 (Block 1, Wakulla and Jefferson Counties) |
Extent Group 1 / Time Frame 3
| Time Frame Type: | Range |
|---|---|
| Start: | 2019-12-18 |
| End: | 2019-12-25 |
| Description: |
Dates of collection for Work Unit 212018 (Block 2, Wakulla and Jefferson Counties) |
Extent Group 1 / Time Frame 4
| Time Frame Type: | Range |
|---|---|
| Start: | 2019-12-16 |
| End: | 2020-01-25 |
| Description: |
Dates of collection for Work Unit 217056 (Block 4, Leon, Gadsden, Liberty and Franklin Counties) |
Extent Group 1 / Time Frame 5
| Time Frame Type: | Range |
|---|---|
| Start: | 2020-02-14 |
| End: | 2020-02-27 |
| Description: |
Dates of collection for Work Unit 227988 (Block 5, Washington, Holmes, Walton Counties) |
Extent Group 1 / Time Frame 6
| Time Frame Type: | Range |
|---|---|
| Start: | 2019-12-16 |
| End: | 2020-04-21 |
| Description: |
Dates of collection for Work Unit 229801 (Block 6, Bay, Calhoun, Franklin, Gadsden, Gulf, Holmes, Jackson, Liberty, and Walton Counties) |
Extent Group 1 / Time Frame 7
| Time Frame Type: | Range |
|---|---|
| Start: | 2019-12-16 |
| End: | 2020-01-07 |
| Description: |
Dates of collection for Work Unit 216141 (Block 3, Leon, Gadsden, Liberty, and Franklin Counties) |
Spatial Information
Spatial Representation
Representations Used
| Grid: | No |
|---|---|
| Vector: | Yes |
| 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
| Start Date: | 2023-01-05 |
|---|---|
| End Date: | Present |
| Download URL: | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=9686/details/9686 |
| Distributor: | NOAA Office for Coastal Management (NOAA/OCM) (2023 - Present) |
| File Name: | Customized Download |
| Description: |
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. |
| File Type (Deprecated): | Zip |
| Compression: | Zip |
Distribution 2
| Start Date: | 2023-01-05 |
|---|---|
| End Date: | Present |
| Download URL: | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/FL_HurricaneMichael_2020_D20/ |
| Distributor: | U.S. Geological Survey (2022 - Present) |
| File Name: | Bulk Download |
| Description: |
Bulk download of data files in LAZ format, based on a horizontal datum/projection of Florida State Plane North, NAD83(2011), US feet and a vertical datum of NAVD88 (GEOID12B) and units in feet. This url links to the USGS copy of the files, from which the Entwine Point Tile files originated. These have not been reviewed by OCM and the link is provided here for convenience. |
| File Type (Deprecated): | LAZ |
| Distribution Format: | LAS/LAZ - LASer |
| Compression: | Zip |
URLs
URL 1
| 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 2
| URL: | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_HurricaneMichael_2020_D20/USGS_FL_HurricaneMichael_2020_D20_Project_Report.pdf |
|---|---|
| Name: | USGS Project Report |
| URL Type: |
Online Resource
|
| File Resource Format: | |
| Description: |
Link to the USGS project report. |
URL 3
| URL: | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_HurricaneMichael_2020_D20/ |
|---|---|
| Name: | USGS Additional Info |
| URL Type: |
Online Resource
|
| Description: |
Link to the reports, breaklines, and spatial metadata. |
URL 4
| URL: | https://usgs.entwine.io/data/view.html?r=%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_HurricaneMichael_1_2020%22 |
|---|---|
| Name: | USGS Potree 3D View |
| URL Type: |
Online Resource
|
| Description: |
Link to view the point cloud (using the Entwine Point Tile (EPT) format) in the 3D Potree viewer. |
URL 5
| URL: | https://usgs.entwine.io/data/view.html?r=%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_HurricaneMichael_2_2020%22 |
|---|---|
| Name: | USGS Potree 3D View |
| URL Type: |
Online Resource
|
| Description: |
Link to view the point cloud (using the Entwine Point Tile (EPT) format) in the 3D Potree viewer. |
URL 6
| URL: | https://usgs.entwine.io/data/view.html?r=%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_HurricaneMichael_3_2020%22 |
|---|---|
| Name: | USGS Potree 3D View |
| URL Type: |
Online Resource
|
| Description: |
Link to view the point cloud (using the Entwine Point Tile (EPT) format) in the 3D Potree viewer. |
URL 7
| URL: | https://usgs.entwine.io/data/view.html?r=%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_HurricaneMichael_4_2020%22 |
|---|---|
| Name: | USGS Potree 3D View |
| URL Type: |
Online Resource
|
| Description: |
Link to view the point cloud (using the Entwine Point Tile (EPT) format) in the 3D Potree viewer. |
URL 8
| URL: | https://usgs.entwine.io/data/view.html?r=%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_HurricaneMichael_5_2020%22 |
|---|---|
| Name: | USGS Potree 3D View |
| URL Type: |
Online Resource
|
| Description: |
Link to view the point cloud (using the Entwine Point Tile (EPT) format) in the 3D Potree viewer. |
URL 9
| URL: | https://usgs.entwine.io/data/view.html?r=%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_HurricaneMichael_6_2020%22 |
|---|---|
| Name: | USGS Potree 3D View |
| URL Type: |
Online Resource
|
| Description: |
Link to view the point cloud (using the Entwine Point Tile (EPT) format) in the 3D Potree viewer. |
URL 10
| URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_HurricaneMichael_1_2020/ept.json |
|---|---|
| Name: | USGS Entwine Point Tiles (EPT) |
| 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 11
| URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_HurricaneMichael_2_2020/ept.json |
|---|---|
| Name: | USGS Entwine Point Tiles (EPT) |
| 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 12
| URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_HurricaneMichael_3_2020/ept.json |
|---|---|
| Name: | USGS Entwine Point Tiles (EPT) |
| 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 13
| URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_HurricaneMichael_4_2020/ept.json |
|---|---|
| Name: | USGS Entwine Point Tiles (EPT) |
| 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 14
| URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_HurricaneMichael_5_2020/ept.json |
|---|---|
| Name: | USGS Entwine Point Tiles (EPT) |
| 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 15
| URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_HurricaneMichael_6_2020/ept.json |
|---|---|
| Name: | USGS Entwine Point Tiles (EPT) |
| 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 16
| URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_HurricaneMichael_7_2020/ept.json |
|---|---|
| Name: | USGS Entwine Point Tiles (EPT) |
| 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://usgs.entwine.io/data/view.html?r=%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_HurricaneMichael_7_2020%22 |
|---|---|
| Name: | USGS Potree 3D View |
| URL Type: |
Online Resource
|
| Description: |
Link to view the point cloud (using the Entwine Point Tile (EPT) format) in the 3D Potree viewer. |
Technical Environment
| Description: |
Riegl RiProcess; GeoCue; Microstation; Terrascan; ArcGIS 10.6; Windows 8; .las 2530 GB |
|---|
Data Quality
| Horizontal Positional Accuracy: |
Only checkpoints photo-identifiable in the intensity imagery can be used to test the horizontal accuracy of the lidar. Photo-identifiable checkpoints in intensity imagery typically include checkpoints located at the ends of paint stripes on concrete or asphalt surfaces or checkpoints located at 90 degree corners of different reflectivity, e.g. a sidewalk corner adjoining a grass surface. The xy coordinates of checkpoints, as defined in the intensity imagery, are compared to surveyed xy coordinates for each photo-identifiable checkpoint. These differences are used to compute the tested horizontal accuracy of the lidar. As not all projects contain photo-identifiable checkpoints, the horizontal accuracy of the lidar cannot always be tested. Lidar vendors calibrate their lidar systems during installation of the system and then again for every project acquired. Typical calibrations include cross flights that capture features from multiple directions that allow adjustments to be performed so that the captured features are consistent between all swaths and cross flights from all directions. This data set was produced to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a 41 cm RMSEx/RMSEy Horizontal Accuracy Class which equates to Positional Horizontal Accuracy = +/- 1 meter 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 Vertical Accuracy Non-Vegetated Vertical Accuracy (NVA) = 5.7 cm RMSE Vegetated Vertical Accuracy (VVA) = 15.87 cm at the 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 raw point cloud is of good quality and data passes Non-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 FL Hurricane Michael lidar was ingested into the Data Access Viewer for custom product generation by leveraging USGS hosted Entwine Point Tiles. |
|---|
Sources
USGS Entwine Point Tiles
| Contact Role Type: | Publisher |
|---|---|
| Contact Type: | Organization |
| Contact Name: | USGS |
| Citation URL: | https://usgs.entwine.io/ |
| Citation URL Name: | USGS Entwine Point Tiles (EPT) |
Process Steps
Process Step 1
| Description: |
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 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 technician then analyzed the results and made any necessary additional adjustment until it is 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 match 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 6 cm RMSEz within individual swaths and less than or equal to 8 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 check points after the z correction to ensure the requirement of NVA = 19.6 cm 95% Confidence Level (Required Accuracy) was met. Point classification was performed according to USGS Lidar Base Specification 2.1, and breaklines were collected for water features. Bare earth DEMs were exported from the classified point cloud using collected breaklines for hydroflattening. Synthetic points generated by Riegl processing software are present in this dataset and were used to fill MTA zones. Please see the project report for more details on the synthetic points. |
|---|---|
| Process Date/Time: | 2020-10-15 00:00:00 |
Process Step 2
| Description: |
LAS Point Classification: The point classification is performed as described below. The bare earth surface is then manually reviewed to ensure correct classification on the Class 2 (Ground) points. After the bare-earth surface is finalized, it is then used to generate all hydro-breaklines through heads-up digitization. All ground (ASPRS Class 2) lidar data inside of the WATERBODY, COASTAL and Double Line Drain hydro flattening breaklines were then classified to water (ASPRS Class 9) using TerraScan macro functionality. A buffer of 2.29 feet was also used around each hydro-flattened feature as well as Single Line Drains to classify these ground (ASPRS Class 2) points to Ignored ground (ASPRS Class 20). All WATERBODY Island, COASTAL 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. Buildings (ASPRS Class 6) were classified through an automated process in the initial ground routine. 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. The withheld bit was set on the withheld points previously identified in TerraScan before the ground classification routine was performed. The withheld bit was set on class 7 and class 18 in TerraScan after all classification was complete. These LAS files contain synthetic points. These points were generated by the Riegl processsing software to fill Multiple Time Around (MTA) zones, which are a physical phenomenon that exists in any time of flight lidar system which has multiple pulses in air and wishes to record all of them seamlessly without range gate limitations. The MTA zones only exist in narrow bands of ranges and typically are dependent on flight planning parameters and project area topography. Dewberry proprietary software was then used to create the deliverable industry-standard LAS files for both the All Point Cloud Data and the Bare Earth. Dewberry 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. |
|---|---|
| Process Date/Time: | 2021-09-01 00:00:00 |
Process Step 3
| Description: |
Data was tested at 0.27 meter nominal pulse spacing and 14.22 points per square meter (ppsm). The average density was tested on the LAS data using geometrically reliable (withheld and noise points excluded) first-return points. (A)NPD was tested using rasters which produce the average number of points within each cell. |
|---|---|
| Process Date/Time: | 2021-02-07 00:00:00 |
Process Step 4
| Description: |
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 no changes were made to the vertical (NAVD88 GEOID12B feet). |
|---|---|
| Process Contact: | U.S. Geological Survey |
Process Step 5
| Description: |
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/FL_HurricaneMichael_1_2020/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_HurricaneMichael_2_2020/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_HurricaneMichael_3_2020/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_HurricaneMichael_4_2020/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_HurricaneMichael_5_2020/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_HurricaneMichael_6_2020/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/FL_HurricaneMichael_7_2020/ept.json (Processed to DAV Feb. 7, 2024) |
|---|---|
| Process Date/Time: | 2023-01-05 00:00:00 |
| Process Contact: | Office for Coastal Management (OCM) |
Catalog Details
| Catalog Item ID: | 69038 |
|---|---|
| GUID: | gov.noaa.nmfs.inport:69038 |
| Metadata Record Created By: | Rebecca Mataosky |
| Metadata Record Created: | 2023-01-05 16:23+0000 |
| Metadata Record Last Modified By: | Rebecca Mataosky |
| Metadata Record Last Modified: | 2024-02-07 20:55+0000 |
| Metadata Record Published: | 2023-01-09 |
| Owner Org: | OCMP |
| Metadata Publication Status: | Published Externally |
| Do Not Publish?: | N |
| Metadata Last Review Date: | 2023-01-09 |
| Metadata Review Frequency: | 1 Year |
| Metadata Next Review Date: | 2024-01-09 |