2019 - 2020 USGS Lidar: Hurricane Florence, NC
Data Set (DS) | OCM Partners (OCMP)GUID: gov.noaa.nmfs.inport:72221 | Updated: June 19, 2024 | Published / External
Summary
Short Citation
OCM Partners, 2025: 2019 - 2020 USGS Lidar: Hurricane Florence, NC, https://www.fisheries.noaa.gov/inport/item/72221.
Full Citation Examples
Product: These lidar data are processed Classified LAS 1.4 files, formatted to individual 750 m x 750 m tiles; used to create intensity images, 3D breaklines, and hydro-flattened DEMs as necessary.
Geographic Extent: Eastern North Carolina
NC_HurricaneFlorence_1 (Work Unit 186825) covering approximately 2543 total square miles in 13 counties: Bladen, Brunswick, Columbus, Dillon, Duplin, Hoke, Horry, Marlboro, New Hanover, Pender, Robeson, Sampson, Scotland
NC_HurricaneFlorence_2 (Work Unit 196896) covering approximately 1717 total square miles in 8 counties: Brunswick, Carteret, Craven, Duplin, Jones, New Hanover, Onslow, Pender
NC_HurricaneFlorence_3 (Work Unit 198494) covering approximately 1124 total square miles in 9 counties: Craven, Duplin, Greene, Jones, Lenoir, Onslow, Pitt, Wayne, Wilson
NC_HurricaneFlorence_4 (Work Unit 208939) covering approximately 516 total square miles in 5 counties: Franklin, Granville, Mecklenburg, Vance, Warren
NC_HurricaneFlorence_5 (Work Unit 210877) covering approximately 2152 total square miles in 7 counties: Cumberland, Duplin, Harnett, Johnston, Sampson, Wake, Wayne
NC_HurricaneFlorence_6 (Work Unit 224678) covering approximately 2239 total square miles in 9 counties: Beaufort, Bertie, Dare, Edgecombe, Hyde, Martin, Pitt, Tyrrell, Washington
NC_HurricaneFlorence_7 (Work Unit 217033) covering approximately 1834 total square miles in 8 counties: Bladen, Columbus, Cumberland, Dillon, Hoke, Horry, Robeson, Sampson
NC_HurricaneFlorence_8 (Work Unit 218544) covering approximately 1181 total square miles in 11 counties: Brunswick, Franklin, Granville, Halifax, Johnston, Mecklenburg, Nash, Wake, Warren, Wayne, Wilson
NC_HurricaneFlorence_9 (Work Unit 220804) covering approximately 2546 total square miles in 17 counties: Bertie, Camden, Chesapeake, Chowan, Currituck, Edgecombe, Gates, Greensville, Halifax, Hertford, Martin, Northampton, Pasquotank, Perquimans, Southampton, Suffolk, Virginia Beach
NC_HurricaneFlorence_10 (Work Unit 225700) covering approximately 1833 total square miles in 11 counties: Beaufort, Carteret, Craven, Duplin, Greene, Jones, Lenoir, Pamlico, Pitt, Wayne, Wilson
NC_HurricaneFlorence_11 (Work Unit 225793) covering approximately 2120 total square miles in 11 counties: Brunswick, Edgecombe, Franklin, Greene, Greensville, Halifax, Nash, Northampton, Pitt, Warren, Wilson
Dataset Description:
The NC_HurricaneFlorence_2020_D20 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 meters. Project specifications were based on the U.S. Geological Survey National Geospatial Program Base LiDAR Specification, Version 2.1. The data were developed based on a horizontal projection/datum of NAD 1983 2011 UTM Zones 17N and 18N, Meters and vertical datum of NAVD88 Geoid18, Meters. LiDAR data were delivered as processed Classified LAS 1.4 files formatted to individual 750 m x 750 m tiles, as tiled intensity imagery, and as tiled bare earth DEMs; all tiled to the same 750 m x 750 m schema. Continuous breaklines were produced in Esri file geodatabase format.
Ground Conditions: LiDAR was collected in winter 2019 and 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 record supports the data entry in the NOAA Digital Coast Data Access Viewer (DAV). For this data set, the DAV is leveraging the Entwine Point Tiles (EPT) hosted by USGS on Amazon Web Services.
Distribution Information
-
Not Applicable
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, UTM Zones 17N and 18N NAD83 (2011) meters coordinates and NAVD88 (Geoid18) elevations in meters.
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
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
-79.5° W,
-77.94° E,
34.92° N,
33.87° S
NC_HurricaneFlorence_1 (Work Unit 186825) covering approximately 2543 total square miles in 13 counties: Bladen, Brunswick, Columbus, Dillon, Duplin, Hoke, Horry, Marlboro, New Hanover, Pender, Robeson, Sampson, Scotland
2019-12-10 - 2020-02-15
Dates of collection for NC_HurricaneFlorence_1 (Work Unit 186825)
Item Identification
Title: | 2019 - 2020 USGS Lidar: Hurricane Florence, NC |
---|---|
Short Name: | nc2019_florence_m10082_metadata |
Status: | Completed |
Publication Date: | 2022-05-09 |
Abstract: |
Product: These lidar data are processed Classified LAS 1.4 files, formatted to individual 750 m x 750 m tiles; used to create intensity images, 3D breaklines, and hydro-flattened DEMs as necessary. Geographic Extent: Eastern North Carolina NC_HurricaneFlorence_1 (Work Unit 186825) covering approximately 2543 total square miles in 13 counties: Bladen, Brunswick, Columbus, Dillon, Duplin, Hoke, Horry, Marlboro, New Hanover, Pender, Robeson, Sampson, Scotland NC_HurricaneFlorence_2 (Work Unit 196896) covering approximately 1717 total square miles in 8 counties: Brunswick, Carteret, Craven, Duplin, Jones, New Hanover, Onslow, Pender NC_HurricaneFlorence_3 (Work Unit 198494) covering approximately 1124 total square miles in 9 counties: Craven, Duplin, Greene, Jones, Lenoir, Onslow, Pitt, Wayne, Wilson NC_HurricaneFlorence_4 (Work Unit 208939) covering approximately 516 total square miles in 5 counties: Franklin, Granville, Mecklenburg, Vance, Warren NC_HurricaneFlorence_5 (Work Unit 210877) covering approximately 2152 total square miles in 7 counties: Cumberland, Duplin, Harnett, Johnston, Sampson, Wake, Wayne NC_HurricaneFlorence_6 (Work Unit 224678) covering approximately 2239 total square miles in 9 counties: Beaufort, Bertie, Dare, Edgecombe, Hyde, Martin, Pitt, Tyrrell, Washington NC_HurricaneFlorence_7 (Work Unit 217033) covering approximately 1834 total square miles in 8 counties: Bladen, Columbus, Cumberland, Dillon, Hoke, Horry, Robeson, Sampson NC_HurricaneFlorence_8 (Work Unit 218544) covering approximately 1181 total square miles in 11 counties: Brunswick, Franklin, Granville, Halifax, Johnston, Mecklenburg, Nash, Wake, Warren, Wayne, Wilson NC_HurricaneFlorence_9 (Work Unit 220804) covering approximately 2546 total square miles in 17 counties: Bertie, Camden, Chesapeake, Chowan, Currituck, Edgecombe, Gates, Greensville, Halifax, Hertford, Martin, Northampton, Pasquotank, Perquimans, Southampton, Suffolk, Virginia Beach NC_HurricaneFlorence_10 (Work Unit 225700) covering approximately 1833 total square miles in 11 counties: Beaufort, Carteret, Craven, Duplin, Greene, Jones, Lenoir, Pamlico, Pitt, Wayne, Wilson NC_HurricaneFlorence_11 (Work Unit 225793) covering approximately 2120 total square miles in 11 counties: Brunswick, Edgecombe, Franklin, Greene, Greensville, Halifax, Nash, Northampton, Pitt, Warren, Wilson Dataset Description: The NC_HurricaneFlorence_2020_D20 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 meters. Project specifications were based on the U.S. Geological Survey National Geospatial Program Base LiDAR Specification, Version 2.1. The data were developed based on a horizontal projection/datum of NAD 1983 2011 UTM Zones 17N and 18N, Meters and vertical datum of NAVD88 Geoid18, Meters. LiDAR data were delivered as processed Classified LAS 1.4 files formatted to individual 750 m x 750 m tiles, as tiled intensity imagery, and as tiled bare earth DEMs; all tiled to the same 750 m x 750 m schema. Continuous breaklines were produced in Esri file geodatabase format. Ground Conditions: LiDAR was collected in winter 2019 and 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 record supports the data entry in the NOAA Digital Coast Data Access Viewer (DAV). For this data set, the DAV is leveraging the Entwine Point Tiles (EPT) hosted by USGS on Amazon Web Services. |
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 DEMs. The purpose of these LiDAR data was to produce high accuracy 3D hydro-flattened digital elevation models (DEMs) with a 0.5 meter cell size. These raw LiDAR point cloud data were used to create classified LiDAR LAS files, intensity images, 3D breaklines, and hydro-flattened DEMs as necessary. |
Supplemental Information: |
Contract No. G16PC00016, Task Order No. 140G0220F0001; CONTRACTOR: NV5 Geospatial The following are the USGS lidar fields in JSON: {
"ldrinfo" : {
"ldrspec" : "USGS-NGP Base Specification v2.1", "ldrsens" : "Riegl VQ1560i (3546)", "ldrmaxnr" : "unlimited", "ldrnps" : "0.35", "ldrdens" : "8.0", "ldranps" : "0.35", "ldradens" : "8.16", "ldrfltht" : "1400", "ldrfltsp" : "160", "ldrscana" : "29", "ldrscanr" : "180", "ldrpulsr" : "2000", "ldrpulsd" : "3", "ldrpulsw" : "0.25", "ldrwavel" : "1064", "ldrmpia" : "1", "ldrbmdiv" : "0.18", "ldrswatw" : "1552.0", "ldrswato" : "20", "ldrgeoid" : "Geoid18", "ldrcrs" : "NAD 1983 2011 UTM Zone 18N, Meter" }, "ldrinfo" : {
"ldrspec" : "USGS-NGP Base Specification v2.1", "ldrsens" : "Riegl VQ1560i (3061)", "ldrmaxnr" : "unlimited", "ldrnps" : "0.35", "ldrdens" : "8.0", "ldranps" : "0.35", "ldradens" : "8.16", "ldrfltht" : "1400", "ldrfltsp" : "160", "ldrscana" : "29", "ldrscanr" : "180", "ldrpulsr" : "1000", "ldrpulsd" : "3", "ldrpulsw" : "0.25", "ldrwavel" : "1064", "ldrmpia" : "1", "ldrbmdiv" : "0.18", "ldrswatw" : "1552.0", "ldrswato" : "20", "ldrgeoid" : "Geoid18", "ldrcrs" : "NAD 1983 2011 UTM Zone 18N, Meter" }, "ldrinfo" : {
"ldrspec" : "USGS-NGP Base Specification v2.1", "ldrsens" : "Riegl VQ1560i (3070)", "ldrmaxnr" : "unlimited", "ldrnps" : "0.35", "ldrdens" : "8.0", "ldranps" : "0.35", "ldradens" : "8.16", "ldrfltht" : "1400", "ldrfltsp" : "160", "ldrscana" : "29", "ldrscanr" : "180", "ldrpulsr" : "2000", "ldrpulsd" : "3", "ldrpulsw" : "0.25", "ldrwavel" : "1064", "ldrmpia" : "1", "ldrbmdiv" : "0.18", "ldrswatw" : "1552.0", "ldrswato" : "20", "ldrgeoid" : "Geoid18", "ldrcrs" : "NAD 1983 2011 UTM Zone 18N, Meter" }, "ldrinfo" : {
"ldrspec" : "USGS-NGP Base Specification v2.1", "ldrsens" : "Riegl VQ1560ii (4046)", "ldrmaxnr" : "unlimited", "ldrnps" : "0.35", "ldrdens" : "8.0", "ldranps" : "0.35", "ldradens" : "8.16", "ldrfltht" : "1400", "ldrfltsp" : "160", "ldrscana" : "29", "ldrscanr" : "180", "ldrpulsr" : "1000", "ldrpulsd" : "3", "ldrpulsw" : "0.25", "ldrwavel" : "1064", "ldrmpia" : "1", "ldrbmdiv" : "0.18", "ldrswatw" : "1552.0", "ldrswato" : "20", "ldrgeoid" : "Geoid18", "ldrcrs" : "NAD 1983 2011 UTM Zone 18N, Meter" }, "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" : "Any overage point deemed geometrically reliable will be used within the normal classification schema. Overage points are not specifically flagged with any special bit value.", "lasintr" : "16", "lasclass" : {
"clascode" : "1", "clasitem" : "Processed, but Unclassified" }, "lasclass" : {
"clascode" : "2", "clasitem" : "Bare-Earth Ground" }, "lasclass" : {
"clascode" : "7", "clasitem" : "Low Noise" }, "lasclass" : {
"clascode" : "9", "clasitem" : "Water" }, "lasclass" : {
"clascode" : "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 > NORTH CAROLINA
|
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: | NV5 Geospatial, USGS |
Support Roles
Data Steward
Date Effective From: | 2024 |
---|---|
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: | 2024 |
---|---|
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): | U.S. Geological Survey |
Address: |
12201 Sunrise Valley Drive Reston, VA 20191 USA |
URL: | USGS Home |
Metadata Contact
Date Effective From: | 2024 |
---|---|
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: | 2024 |
---|---|
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: | -79.5 | |
---|---|---|
E° Bound: | -77.94 | |
N° Bound: | 34.92 | |
S° Bound: | 33.87 | |
Description |
NC_HurricaneFlorence_1 (Work Unit 186825) covering approximately 2543 total square miles in 13 counties: Bladen, Brunswick, Columbus, Dillon, Duplin, Hoke, Horry, Marlboro, New Hanover, Pender, Robeson, Sampson, Scotland |
Extent Group 1 / Time Frame 1
Time Frame Type: | Range |
---|---|
Start: | 2019-12-10 |
End: | 2020-02-15 |
Description: |
Dates of collection for NC_HurricaneFlorence_1 (Work Unit 186825) |
Extent Group 2
Extent Group 2 / Geographic Area 1
W° Bound: | -78.04 | |
---|---|---|
E° Bound: | -76.48 | |
N° Bound: | 34.94 | |
S° Bound: | 33.94 | |
Description |
NC_HurricaneFlorence_2 (Work Unit 196896) covering approximately 1717 total square miles in 8 counties: Brunswick, Carteret, Craven, Duplin, Jones, New Hanover, Onslow, Pender |
Extent Group 2 / Time Frame 1
Time Frame Type: | Range |
---|---|
Start: | 2019-12-08 |
End: | 2020-01-08 |
Description: |
Dates of collection for NC_HurricaneFlorence_2 (Work Unit 196896) |
Extent Group 3
Extent Group 3 / Geographic Area 1
W° Bound: | -77.89 | |
---|---|---|
E° Bound: | -77.08 | |
N° Bound: | 35.59 | |
S° Bound: | 34.88 | |
Description |
NC_HurricaneFlorence_3 (Work Unit 198494) covering approximately 1124 total square miles in 9 counties: Craven, Duplin, Greene, Jones, Lenoir, Onslow, Pitt, Wayne, Wilson |
Extent Group 3 / Time Frame 1
Time Frame Type: | Range |
---|---|
Start: | 2019-12-08 |
End: | 2020-01-26 |
Description: |
Dates of collection for NC_HurricaneFlorence_3 (Work Unit 198494) |
Extent Group 4
Extent Group 4 / Geographic Area 1
W° Bound: | -78.52 | |
---|---|---|
E° Bound: | -78.17 | |
N° Bound: | 36.56 | |
S° Bound: | 36.13 | |
Description |
NC_HurricaneFlorence_4 (Work Unit 208939) covering approximately 516 total square miles in 5 counties: Franklin, Granville, Mecklenburg, Vance, Warren |
Extent Group 4 / Time Frame 1
Time Frame Type: | Range |
---|---|
Start: | 2020-01-30 |
End: | 2020-02-02 |
Description: |
Dates of collection for NC_HurricaneFlorence_4 (Work Unit 208939) |
Extent Group 5
Extent Group 5 / Geographic Area 1
W° Bound: | -78.71 | |
---|---|---|
E° Bound: | -77.93 | |
N° Bound: | 35.82 | |
S° Bound: | 34.85 | |
Description |
NC_HurricaneFlorence_5 (Work Unit 210877) covering approximately 2152 total square miles in 7 counties: Cumberland, Duplin, Harnett, Johnston, Sampson, Wake, Wayne |
Extent Group 5 / Time Frame 1
Time Frame Type: | Range |
---|---|
Start: | 2019-12-12 |
End: | 2020-01-26 |
Description: |
NC_HurricaneFlorence_5 (Work Unit 210877) |
Extent Group 6
Extent Group 6 / Geographic Area 1
W° Bound: | -77.44 | |
---|---|---|
E° Bound: | -75.79 | |
N° Bound: | 35.94 | |
S° Bound: | 35.39 | |
Description |
NC_HurricaneFlorence_6 (Work Unit 224678) covering approximately 2239 total square miles in 9 counties: Beaufort, Bertie, Dare, Edgecombe, Hyde, Martin, Pitt, Tyrrell, Washington |
Extent Group 6 / Time Frame 1
Time Frame Type: | Range |
---|---|
Start: | 2019-12-16 |
End: | 2020-02-08 |
Description: |
Dates of collection for NC_HurricaneFlorence_6 (Work Unit 224678) |
Extent Group 7
Extent Group 7 / Geographic Area 1
W° Bound: | -79.11 | |
---|---|---|
E° Bound: | -78.32 | |
N° Bound: | 34.96 | |
S° Bound: | 34.26 | |
Description |
NC_HurricaneFlorence_7 (Work Unit 217033) covering approximately 1834 total square miles in 8 counties: Bladen, Columbus, Cumberland, Dillon, Hoke, Horry, Robeson, Sampson |
Extent Group 7 / Time Frame 1
Time Frame Type: | Range |
---|---|
Start: | 2019-12-12 |
End: | 2020-01-08 |
Description: |
NC_HurricaneFlorence_7 (Work Unit 217033) |
Extent Group 8
Extent Group 8 / Geographic Area 1
W° Bound: | -78.57 | |
---|---|---|
E° Bound: | -77.94 | |
N° Bound: | 36.55 | |
S° Bound: | 35.57 | |
Description |
NC_HurricaneFlorence_8 (Work Unit 218544) covering approximately 1181 total square miles in 11 counties: Brunswick, Franklin, Granville, Halifax, Johnston, Mecklenburg, Nash, Wake, Warren, Wayne, Wilson |
Extent Group 8 / Time Frame 1
Time Frame Type: | Range |
---|---|
Start: | 2019-12-16 |
End: | 2020-02-23 |
Description: |
Dates of collection for NC_HurricaneFlorence_8 (Work Unit 218544) |
Extent Group 9
Extent Group 9 / Geographic Area 1
W° Bound: | -77.46 | |
---|---|---|
E° Bound: | -76.01 | |
N° Bound: | 36.57 | |
S° Bound: | 35.93 | |
Description |
NC_HurricaneFlorence_9 (Work Unit 220804) covering approximately 2546 total square miles in 17 counties: Bertie, Camden, Chesapeake, Chowan, Currituck, Edgecombe, Gates, Greensville, Halifax, Hertford, Martin, Northampton, Pasquotank, Perquimans, Southampton, Suffolk, Virginia Beach |
Extent Group 9 / Time Frame 1
Time Frame Type: | Range |
---|---|
Start: | 2020-01-18 |
End: | 2020-02-28 |
Description: |
Dates of collection for NC_HurricaneFlorence_9 (Work Unit 220804) |
Extent Group 10
Extent Group 10 / Geographic Area 1
W° Bound: | -78.03 | |
---|---|---|
E° Bound: | -76.06 | |
N° Bound: | 35.62 | |
S° Bound: | 34.8 | |
Description |
NC_HurricaneFlorence_10 (Work Unit 225700) covering approximately 1833 total square miles in 11 counties: Beaufort, Carteret, Craven, Duplin, Greene, Jones, Lenoir, Pamlico, Pitt, Wayne, Wilson |
Extent Group 10 / Time Frame 1
Time Frame Type: | Range |
---|---|
Start: | 2019-12-08 |
End: | 2020-01-26 |
Description: |
Dates of collection for NC_HurricaneFlorence_10 (Work Unit 225700) |
Extent Group 11
Extent Group 11 / Geographic Area 1
W° Bound: | -78.03 | |
---|---|---|
E° Bound: | -77.45 | |
N° Bound: | 36.56 | |
S° Bound: | 35.6 | |
Description |
NC_HurricaneFlorence_11 (Work Unit 225793) covering approximately 2120 total square miles in 11 counties: Brunswick, Edgecombe, Franklin, Greene, Greensville, Halifax, Nash, Northampton, Pitt, Warren, Wilson |
Extent Group 11 / Time Frame 1
Time Frame Type: | Range |
---|---|
Start: | 2019-12-15 |
End: | 2020-02-28 |
Description: |
Dates of collection for NC_HurricaneFlorence_11 (Work Unit 225793) |
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: | 2024-02-26 |
---|---|
End Date: | Present |
Download URL: | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=10082/details/10082 |
Distributor: | NOAA Office for Coastal Management (NOAA/OCM) (2024 - 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. |
Distribution Format: | Not Applicable |
Compression: | Zip |
Distribution 2
Start Date: | 2023 |
---|---|
End Date: | Present |
Download URL: | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/NC_HurricaneFlorence_2020_D20/ |
Distributor: | U.S. Geological Survey (2023 - Present) |
File Name: | Bulk Download |
Description: |
Bulk download of data files in LAZ format, UTM Zones 17N and 18N NAD83 (2011) meters coordinates and NAVD88 (Geoid18) elevations in meters. |
Distribution Format: | LAS/LAZ - LASer |
Compression: | LAZ |
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://s3-us-west-2.amazonaws.com/usgs-lidar-public/NC_HurricaneFlorence_1_2020/ept.json |
---|---|
Name: | USGS Entwine Point Tile (EPT) - NC_HurricaneFlorence_1 |
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 3
URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NC_HurricaneFlorence_2_2020/ept.json |
---|---|
Name: | USGS Entwine Point Tile (EPT) - NC_HurricaneFlorence_2 |
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 4
URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NC_HurricaneFlorence_3_2020/ept.json |
---|---|
Name: | USGS Entwine Point Tile (EPT) - NC_HurricaneFlorence_3 |
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 5
URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NC_HurricaneFlorence_4_2020/ept.json |
---|---|
Name: | USGS Entwine Point Tile (EPT) - NC_HurricaneFlorence_4 |
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 6
URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NC_HurricaneFlorence_5_2020/ept.json |
---|---|
Name: | USGS Entwine Point Tile (EPT) - NC_HurricaneFlorence_5 |
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 7
URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NC_HurricaneFlorence_6_2020/ept.json |
---|---|
Name: | USGS Entwine Point Tile (EPT) - NC_HurricaneFlorence_6 |
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 8
URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NC_HurricaneFlorence_7_2020/ept.json |
---|---|
Name: | USGS Entwine Point Tile (EPT) - NC_HurricaneFlorence_7 |
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 9
URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NC_HurricaneFlorence_8_2020/ept.json |
---|---|
Name: | USGS Entwine Point Tile (EPT) - NC_HurricaneFlorence_8 |
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 10
URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NC_HurricaneFlorence_9_2020/ept.json |
---|---|
Name: | USGS Entwine Point Tile (EPT) - NC_HurricaneFlorence_9 |
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/NC_HurricaneFlorence_10_2020/ept.json |
---|---|
Name: | USGS Entwine Point Tile (EPT) - NC_HurricaneFlorence_10 |
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/NC_HurricaneFlorence_11_2020/ept.json |
---|---|
Name: | USGS Entwine Point Tile (EPT) - NC_HurricaneFlorence_11 |
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 14
URL: | https://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Elevation/metadata/NC_HurricaneFlorence_2020_D20/ |
---|---|
Name: | USGS Additional Info |
URL Type: |
Online Resource
|
Description: |
Link to the reports, breaklines, metadata, and spatial metadata. |
URL 15
URL: | https://prd-tnm.s3.amazonaws.com/StagedProducts/Elevation/metadata/NC_HurricaneFlorence_2020_D20/USGS_NC_HurricaneFlorence_2020_D20_Project_Report.pdf |
---|---|
Name: | USGS 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 16
URL: | https://prd-tnm.s3.amazonaws.com/StagedProducts/Elevation/metadata/NC_HurricaneFlorence_2020_D20/NC_HurricaneFlorence_1_2020/reports/35630_NC_QL1_UTM17_Lidar_ProjectReport.pdf |
---|---|
Name: | Lidar Report - NC_HurricaneFlorence_1 |
URL Type: |
Online Resource
|
File Resource Format: | |
Description: |
Link to the NV5 lidar report for NC_HurricaneFlorence_1 |
URL 17
URL: | https://prd-tnm.s3.amazonaws.com/StagedProducts/Elevation/metadata/NC_HurricaneFlorence_2020_D20/NC_HurricaneFlorence_2_2020/reports/35630_NC_QL1_UTM18_Lidar_ProjectReport.pdf |
---|---|
Name: | Lidar Report - NC_HurricaneFlorence_2 |
URL Type: |
Online Resource
|
File Resource Format: | |
Description: |
Link to the NV5 lidar report for NC_HurricaneFlorence_2 |
URL 18
URL: | https://prd-tnm.s3.amazonaws.com/StagedProducts/Elevation/metadata/NC_HurricaneFlorence_2020_D20/NC_HurricaneFlorence_3_2020/reports/35630_NC_QL1_UTM18_Block2_Lidar_ProjectReport.pdf |
---|---|
Name: | Lidar Report - NC_HurricaneFlorence_3 |
URL Type: |
Online Resource
|
File Resource Format: | |
Description: |
Link to the NV5 lidar report for NC_HurricaneFlorence_3 |
URL 19
URL: | https://prd-tnm.s3.amazonaws.com/StagedProducts/Elevation/metadata/NC_HurricaneFlorence_2020_D20/NC_HurricaneFlorence_4_2020/reports/35630_NC_QL1_WU208939_ProjectReport.pdf |
---|---|
Name: | Lidar Report - NC_HurricaneFlorence_4 |
URL Type: |
Online Resource
|
File Resource Format: | |
Description: |
Link to the NV5 lidar report for NC_HurricaneFlorence_4 |
URL 20
URL: | https://prd-tnm.s3.amazonaws.com/StagedProducts/Elevation/metadata/NC_HurricaneFlorence_2020_D20/NC_HurricaneFlorence_5_2020/reports/35630_NC_QL1_UTM17_Block4_Lidar_ProjectReport.pdf |
---|---|
Name: | Lidar Report - NC_HurricaneFlorence_5 |
URL Type: |
Online Resource
|
File Resource Format: | |
Description: |
Link to the NV5 lidar report for NC_HurricaneFlorence_5 |
URL 21
URL: | https://prd-tnm.s3.amazonaws.com/StagedProducts/Elevation/metadata/NC_HurricaneFlorence_2020_D20/NC_HurricaneFlorence_6_2020/reports/NC_HurricaneFlorence_WU224678_ProjectReport.pdf |
---|---|
Name: | Lidar Report - NC_HurricaneFlorence_6 |
URL Type: |
Online Resource
|
File Resource Format: | |
Description: |
Link to the NV5 lidar report for NC_HurricaneFlorence_6 |
URL 22
URL: | https://prd-tnm.s3.amazonaws.com/StagedProducts/Elevation/metadata/NC_HurricaneFlorence_2020_D20/NC_HurricaneFlorence_7_2020/reports/NC_HurricaneFlorence_2020_D20_WU217003.pdf |
---|---|
Name: | Lidar Report - NC_HurricaneFlorence_7 |
URL Type: |
Online Resource
|
File Resource Format: | |
Description: |
Link to the NV5 lidar report for NC_HurricaneFlorence_7 |
URL 23
URL: | https://prd-tnm.s3.amazonaws.com/StagedProducts/Elevation/metadata/NC_HurricaneFlorence_2020_D20/NC_HurricaneFlorence_8_2020/reports/NC_QL1_WU218544_Lidar_ProjectReport.pdf |
---|---|
Name: | Lidar Report - NC_HurricaneFlorence_8 |
URL Type: |
Online Resource
|
File Resource Format: | |
Description: |
Link to the NV5 lidar report for NC_HurricaneFlorence_8 |
URL 24
URL: | https://prd-tnm.s3.amazonaws.com/StagedProducts/Elevation/metadata/NC_HurricaneFlorence_2020_D20/NC_HurricaneFlorence_9_2020/reports/NC_HurricaneFlorence_2020_D20_WU220804.pdf |
---|---|
Name: | Lidar Report - NC_HurricaneFlorence_9 |
URL Type: |
Online Resource
|
File Resource Format: | |
Description: |
Link to the NV5 lidar report for NC_HurricaneFlorence_9 |
URL 25
URL: | https://prd-tnm.s3.amazonaws.com/StagedProducts/Elevation/metadata/NC_HurricaneFlorence_2020_D20/NC_HurricaneFlorence_10_2020/reports/35630_NC_Lot11b4_UTM18_Report.pdf |
---|---|
Name: | Lidar Report - NC_HurricaneFlorence_10 |
URL Type: |
Online Resource
|
File Resource Format: | |
Description: |
Link to the NV5 lidar report for NC_HurricaneFlorence_10 |
URL 26
URL: | https://prd-tnm.s3.amazonaws.com/StagedProducts/Elevation/metadata/NC_HurricaneFlorence_2020_D20/NC_HurricaneFlorence_11_2020/reports/NC_HurricaneFlorence_2020_D20_WU225793_ProcessingReport.pdf |
---|---|
Name: | Lidar Report - NC_HurricaneFlorence_11 |
URL Type: |
Online Resource
|
File Resource Format: | |
Description: |
Link to the NV5 lidar report for NC_HurricaneFlorence_11 |
Technical Environment
Description: |
MicroStation Connect; TerraScan Version 21.016; TerraModeler Version 21.008; GeoCue Version 2020.1.22.1; Esri ArcGIS 10.6; Global Mapper 19/20; RiProcess 1.8.6; Windows 10 Operating System \\point_cloud\tilecls\*.las |
---|
Data Quality
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: The number of Checkpoints tested for NVA : 502 NVA RMSEz = 3.34 cm NVA Accuracy z at 95% confidence interval (RMSEz * 1.96) = 6.55 cm The number of checkpoints tested for VVA : 345 The 95th percentile value for VVA is : 18.32 cm For more information see the USGS project report and the lidar reports. The links to these reports are provided in the URL section of this metadata record. |
---|---|
Completeness Report: |
These LAS data files include all data points collected. No points have been removed or excluded. A visual qualitative assessment was performed to ensure data completeness. No void areas or missing data exist. The raw point cloud is of good quality and the data pass Non-Vegetated Vertical Accuracy specifications. |
Conceptual Consistency: |
Data cover 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-NC |
How Will the Data Be Protected from Accidental or Malicious Modification or Deletion Prior to Receipt by the Archive?: |
Data is backed up to cloud storage. |
Lineage
Lineage Statement: |
The NOAA Office for Coastal Management (OCM) ingested references to the USGS Entwine Point Tiles (EPT) hosted on Amazon Web Services (AWS) into the Digital Coast Data Access Viewer (DAV). The DAV accesses the point cloud as it resides on AWS under the usgs-lidar-public-container. |
---|
Sources
USGS AWS Entwine Point Tile (EPT) - NC_HurricaneFlorence_1
Contact Role Type: | Publisher |
---|---|
Contact Type: | Organization |
Contact Name: | USGS |
Citation URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NC_HurricaneFlorence_1_2020/ept.json |
Citation URL Name: | Entwine Point Tile for NC_HurricaneFlorence_1 |
USGS AWS Entwine Point Tile (EPT) - NC_HurricaneFlorence_10
Contact Role Type: | Publisher |
---|---|
Contact Type: | Organization |
Contact Name: | USGS |
Citation URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NC_HurricaneFlorence_10_2020/ept.json |
Citation URL Name: | Entwine Point Tile for NC_HurricaneFlorence_10 |
USGS AWS Entwine Point Tile (EPT) - NC_HurricaneFlorence_11
Contact Role Type: | Publisher |
---|---|
Contact Type: | Organization |
Contact Name: | USGS |
Citation URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NC_HurricaneFlorence_11_2020/ept.json |
Citation URL Name: | Entwine Point Tile for NC_HurricaneFlorence_11 |
USGS AWS Entwine Point Tile (EPT) - NC_HurricaneFlorence_2
Contact Role Type: | Publisher |
---|---|
Contact Type: | Organization |
Contact Name: | USGS |
Citation URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NC_HurricaneFlorence_2_2020/ept.json |
Citation URL Name: | Entwine Point Tile for NC_HurricaneFlorence_2 |
USGS AWS Entwine Point Tile (EPT) - NC_HurricaneFlorence_3
Contact Role Type: | Publisher |
---|---|
Contact Type: | Organization |
Contact Name: | USGS |
Citation URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NC_HurricaneFlorence_3_2020/ept.json |
Citation URL Name: | Entwine Point Tile for NC_HurricaneFlorence_3 |
USGS AWS Entwine Point Tile (EPT) - NC_HurricaneFlorence_4
Contact Role Type: | Publisher |
---|---|
Contact Type: | Organization |
Contact Name: | USGS |
Citation URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NC_HurricaneFlorence_4_2020/ept.json |
Citation URL Name: | Entwine Point Tile for NC_HurricaneFlorence_4 |
USGS AWS Entwine Point Tile (EPT) - NC_HurricaneFlorence_5
Contact Role Type: | Publisher |
---|---|
Contact Type: | Organization |
Contact Name: | USGS |
Citation URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NC_HurricaneFlorence_5_2020/ept.json |
Citation URL Name: | Entwine Point Tile for NC_HurricaneFlorence_5 |
USGS AWS Entwine Point Tile (EPT) - NC_HurricaneFlorence_6
Contact Role Type: | Publisher |
---|---|
Contact Type: | Organization |
Contact Name: | USGS |
Citation URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NC_HurricaneFlorence_6_2020/ept.json |
Citation URL Name: | Entwine Point Tile for NC_HurricaneFlorence_6 |
USGS AWS Entwine Point Tile (EPT) - NC_HurricaneFlorence_7
Contact Role Type: | Publisher |
---|---|
Contact Type: | Organization |
Contact Name: | USGS |
Citation URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NC_HurricaneFlorence_7_2020/ept.json |
Citation URL Name: | Entwine Point Tile for NC_HurricaneFlorence_7 |
USGS AWS Entwine Point Tile (EPT) - NC_HurricaneFlorence_8
Contact Role Type: | Publisher |
---|---|
Contact Type: | Organization |
Contact Name: | USGS |
Citation URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NC_HurricaneFlorence_8_2020/ept.json |
Citation URL Name: | Entwine Point Tile for NC_HurricaneFlorence_8 |
USGS AWS Entwine Point Tile (EPT) - NC_HurricaneFlorence_9
Contact Role Type: | Publisher |
---|---|
Contact Type: | Organization |
Contact Name: | USGS |
Citation URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NC_HurricaneFlorence_9_2020/ept.json |
Citation URL Name: | Entwine Point Tile for NC_HurricaneFlorence_9 |
Process Steps
Process Step 1
Description: |
Raw Data and Boresight Processing: The boresight for each lift was done individually as the solution may change slightly from lift to lift. The following steps describe the Raw Data Processing and Boresight process: 1) Technicians processed the raw data to LAS format flight lines using the final GPS/IMU solution. This LAS data set was used as source data for boresight. 2) Technicians first used NV5 Geospatial proprietary and commercial software to calculate initial boresight adjustment angles based on sample areas selected in the lift. These areas cover calibration flight lines collected in the lift, cross tie, and production flight lines. These areas are well distributed in the lift coverage and cover multiple terrain types that are necessary for boresight angle calculation. The technicians then analyzed the results and made any necessary additional adjustment until it was acceptable for the selected areas. 3) Once the boresight angle calculation was completed for the selected areas, the adjusted settings were applied to all of the flight lines of the lift and checked for consistency. The technicians utilized commercial and proprietary software packages to analyze how well flight line overlaps matched for the entire lift and adjusted as necessary until the results met the project specifications. 4) Once all lifts were completed with individual boresight adjustment, the technicians checked and corrected the vertical misalignment of all flight lines and also the matching between data and ground truth. The relative accuracy was less than or equal to 7 cm RMSEz within individual swaths and less than or equal to 10 cm RMSEz or within swath overlap (between adjacent swaths). 5) The technicians ran a final vertical accuracy check of the boresighted flight lines against the surveyed checkpoints after the z correction to ensure the requirement of NVA = 19.6 cm 95% Confidence Level (Required Accuracy) was met. |
---|---|
Process Date/Time: | 2022-01-01 00:00:00 |
Process Step 2
Description: |
LAS Point Classification: The point classification was performed as described below. The bare earth surface was manually reviewed to ensure correct classification on the Class 2 (Ground) points. After the bare-earth surface was finalized, it was then used to generate all hydro-breaklines through heads-up digitization. All ground (ASPRS Class 2) LiDAR data inside of the Lake Pond and Double Line Drain hydro-flattened breaklines were then classified to Water (ASPRS Class 9) using proprietary tools. A buffer of 0.5 meter was also used around each hydro-flattened feature to classify these ground (ASPRS Class 2) points to Ignored ground (ASPRS Class 20). All Lake Pond Island and Double Line Drain Island features were checked to ensure that the ground (ASPRS Class 2) points were reclassified to the correct classification after the automated classification was completed. Any noise that was identified either through manual review or automated routines was classified to the appropriate class ( ASPRS Class 7 and/or ASPRS Class 18) followed by flagging with the withheld bit. All data were manually reviewed and any remaining artifacts removed using functionality provided by TerraScan and TerraModeler. Global Mapper was used as a final check of the bare earth dataset. GeoCue was then used to create the deliverable industry-standard LAS files for point cloud data. NV5 Geospatial proprietary software was used to perform final statistical analysis of the classes in the LAS files, on a per tile level to verify final classification metrics and full LAS header information. |
---|---|
Process Date/Time: | 2022-01-01 00:00:00 |
Process Step 3
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 GEOID18 meters). |
---|---|
Process Contact: | U.S. Geological Survey |
Process Step 4
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/NC_HurricaneFlorence_1_2020/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NC_HurricaneFlorence_2_2020/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NC_HurricaneFlorence_3_2020/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NC_HurricaneFlorence_4_2020/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NC_HurricaneFlorence_5_2020/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NC_HurricaneFlorence_6_2020/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NC_HurricaneFlorence_7_2020/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NC_HurricaneFlorence_8_2020/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NC_HurricaneFlorence_9_2020/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NC_HurricaneFlorence_10_2020/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/NC_HurricaneFlorence_11_2020/ept.json |
---|---|
Process Date/Time: | 2024-02-26 00:00:00 |
Process Contact: | Office for Coastal Management (OCM) |
Related Items
Item Type | Relationship Type | Title |
---|---|---|
Data Set (DS) | Cross Reference |
2019-2020 NOAA NGS Topobathy Lidar: Coastal VA, NC, SC The NOAA NGS topobathy data cover the immediate coastline areas that are coincident to the USGS topo data coverage. |
Catalog Details
Catalog Item ID: | 72221 |
---|---|
GUID: | gov.noaa.nmfs.inport:72221 |
Metadata Record Created By: | Rebecca Mataosky |
Metadata Record Created: | 2024-02-26 19:03+0000 |
Metadata Record Last Modified By: | Rebecca Mataosky |
Metadata Record Last Modified: | 2024-06-19 15:48+0000 |
Metadata Record Published: | 2024-02-27 |
Owner Org: | OCMP |
Metadata Publication Status: | Published Externally |
Do Not Publish?: | N |
Metadata Last Review Date: | 2024-02-27 |
Metadata Review Frequency: | 1 Year |
Metadata Next Review Date: | 2025-02-27 |