2017 USGS Topobathy Lidar: Everglades National Park, FL
OCM Partners
Data Set
(DS)
| ID: 69618
| Published / External
Created: 2023-04-18
|
Last Modified: 2023-10-17
Project (PRJ) | ID: 49401
ID: 69618
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | 2017 USGS Topobathy Lidar: Everglades National Park, FL |
---|---|
Short Name | fl2017_everglades_m9818_metadata |
* Status | Completed |
Creation Date | 2017 |
Revision Date | |
• Publication Date | 2018-08-30 |
* » Abstract |
Product: These lidar data are processed Classified LAS 1.4 files, formatted to individual 1000 m x 1000 m tiles; used to create intensity images, 2D breaklines and Topobathy DEMs as necessary. Geographic Extent: Florida Everglades National Park covering approximately 1,211 square miles. Dataset Description: Florida Everglades National Park 2018 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 meters. Project specifications are based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, Version 1.2. The data was developed based on a horizontal projection/datum of NAD83 (2011), Universal Transverse Mercator, meters and vertical datum of NAVD88 (GEOID12B), meters. Lidar data was delivered as processed Classified LAS 1.4 files, formatted to individual 1000 m x 1000 m tiles, as tiled Intensity Imagery, and as tiled bare earth topobathy DEMs; all tiled to the same 1000 m x 1000 m schema. Ground Conditions: Lidar was collected in early to mid 2017, 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, Dewberry established a total of 47 ground control points that were used to calibrate the lidar to known ground locations established throughout the Florida Everglades National Park project area. An additional 120 independent accuracy checkpoints, 61 in Bare Earth and Urban landcovers (61 NVA points), 59 in Tall Grass and Brushland/Low Trees categories (59 VVA points), were used to assess the vertical accuracy of the data. These checkpoints were not used to calibrate or post process the data. This metadata record reflects the data that are available from the NOAA Digital Coast Data Access Viewer (DAV). The NOAA Office for Coastal Management (OCM) downloaded 3320 laz point data files from these USGS sites: https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/FL_Everglades_NP_LiDAR_2017_D16/FL_Everglades_N_2017/LAZ/ https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/FL_Everglades_NP_LiDAR_2017_D16/FL_Everglades_S_2017/LAZ/ The data were processed to the NOAA Digital Coast Data Access Viewer (DAV) to make the data available for bulk and custom downloads. |
* 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 Topobathy Digital Elevation Model (DEM) with a 0.5 meter cell size. These lidar point cloud data were used to create intensity images, 2D breaklines, and Topobathy DEMs as necessary. |
Notes | |
Other Citation Details | |
• Supplemental Information |
USGS Contract No. G16PC00020 CONTRACTOR: Dewberry Lidar data were acquired and calibrated by Dewberry, and all follow-on processing was completed by Dewberry.
The following are the USGS lidar fields in JSON: {
"ldrinfo" : {
"ldrspec" : "U.S. Geological Survey (USGS) - National Geospatial Program (NGP) Lidar Base Specification v1.2", "ldrsens" : "Riegl LMS-Q680i", "ldrmaxnr" : "Unlimited", "ldrnps" : "0.35", "ldrdens" : "8", "ldranps" : "0.35", "ldradens" : "8", "ldrfltht" : "400", "ldrfltsp" : "130", "ldrscana" : "60", "ldrscanr" : "191", "ldrpulsr" : "400", "ldrpulsd" : "3", "ldrpulsw" : "0.9", "ldrwavel" : "1550", "ldrmpia" : "1", "ldrbmdiv" : "1", "ldrswatw" : "462", "ldrswato" : "30", "ldrgeoid" : "National Geodetic Survey (NGS) GEOID12B" }, "ldrinfo" : {
"ldrspec" : "U.S. Geological Survey (USGS) - National Geospatial Program (NGP) Lidar Base Specification v1.2", "ldrsens" : "Riegl VQ-820G", "ldrmaxnr" : "Unlimited", "ldrnps" : "0.35", "ldrdens" : "8", "ldranps" : "0.35", "ldradens" : "8", "ldrfltht" : "400", "ldrfltsp" : "130", "ldrscana" : "60", "ldrscanr" : "200", "ldrpulsr" : "522", "ldrpulsd" : "1.2", "ldrpulsw" : "0.36", "ldrwavel" : "532", "ldrmpia" : "1", "ldrbmdiv" : "1", "ldrswatw" : "307", "ldrswato" : "30", "ldrgeoid" : "National Geodetic Survey (NGS) GEOID12B" }, "ldraccur" : {
"ldrchacc" : "0.227", "rawnva" : "0.085", "rawnvan" : "60", "clsnva" : "0.070", "clsnvan" : "61", "clsvva" : "0.350", "clsvvan" : "59" }, "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 were identified in these files using the standard LAS overlap bit.", "lasintrz" : "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" : "40", "clasitem" : "Submerged Topography/Bathymetry" }, "lasclass" : {
"clascode" : "41", "clasitem" : "Water Surface" }, "lasclass" : {
"clascode" : "45", "clasitem" : "Water Column/No Bottom Found" } }} |
DOI (Digital Object Identifier) | |
DOI Registration Authority | |
DOI Issue Date |
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 > BATHYMETRY/SEAFLOOR TOPOGRAPHY > BATHYMETRY |
Global Change Master Directory (GCMD) Science Keywords | EARTH SCIENCE > OCEANS > COASTAL PROCESSES > COASTAL ELEVATION |
ISO 19115 Topic Category | elevation |
Temporal Keywords
Thesaurus | Keyword |
---|---|
* 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 |
Global Change Master Directory (GCMD) Location Keywords | VERTICAL LOCATION > SEA FLOOR |
None | Everglades National Park |
None | Miami-Dade County |
None | Monroe County |
Stratum Keywords
Thesaurus | Keyword |
---|---|
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 |
• Country | |
• » Location Description |
Data Set Information
* Data Set Scope Code | Data Set |
---|---|
• Data Set Type | Elevation |
• Maintenance Frequency | None Planned |
Maintenance Note | |
» Data Presentation Form | Model (digital) |
• Entity Attribute Overview | |
Entity Attribute Detail Citation | |
Entity Attribute Detail URL | |
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
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2023 |
Date Effective To | |
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 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | Distributor |
---|---|
* » Date Effective From | 2023 |
Date Effective To | |
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 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | Metadata Contact |
---|---|
* » Date Effective From | 2023 |
Date Effective To | |
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 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | Point of Contact |
---|---|
* » Date Effective From | 2023 |
Date Effective To | |
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 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
Extents
Currentness Reference | Ground Condition |
---|
Extent Group 1
Extent Description |
---|
Extent Group 1 / Geographic Area 1
* » W° Bound | -81.167515 |
---|---|
* » E° Bound | -80.436127 |
* » N° Bound | 25.764331 |
* » S° Bound | 25.14161 |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Range |
---|---|
* » Start | 2017-04-19 |
End | 2017-06-12 |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Spatial Information
Spatial Resolution
Angular Distance | |
---|---|
Angular Distance Units | |
Horizontal Distance | |
Horizontal Distance Units | |
Vertical Distance | |
Vertical Distance Units | |
Equivalent Scale Denominator | |
Level of Detail Description |
Spatial Representation
Grid Representation Used? | No |
---|---|
Vector Representation Used? | Yes |
Text / Table Representation Used? | No |
TIN Representation Used? | No |
Stereo Model Representation Used? | No |
Video Representation Used? | No |
Grid Representation
Dimension Count | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Cell Geometry | |||||||||||||
Transformation Parameter Available? | |||||||||||||
Axis Dimension |
|||||||||||||
|
|||||||||||||
Axis Dimension |
|||||||||||||
|
Vector Representation
Topology Level | |
---|---|
Complex Object Present? | |
Complex Object Count | |
Composite Object Present? | |
Composite Object Count | |
Curve Object Present? | |
Curve Object Count | |
Point Object Present? | |
Point Object Count | |
Solid Object Present? | |
Solid Object Count | |
Surface Object Present? | |
Surface Object Count |
Reference Systems
Reference System
EPSG Code | EPSG:6319 | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Horizontal Resolution |
|||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
Vertical Resolution |
|||||||||||||||||||||||||||||
|
Reference System
EPSG Code | |||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Horizontal Resolution |
|||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
Vertical Resolution |
|||||||||||||||||||||||||||||
|
Access Information
Data License | |
---|---|
Data License URL | |
Data License Statement | |
* » Security Class | Unclassified |
* Security Classification System | |
Security Handling Description | |
• Data Access Policy | |
» 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. |
Metadata Access Constraints | |
Metadata Use Constraints |
Distribution Information
Start Date | 2023-04-18 |
---|---|
End Date | Present |
» Download URL | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=9818/details/9818 |
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 Date/Time | |
File Type (Deprecated) | Zip |
Distribution Format | |
File Size | |
Application Version | |
Compression | Zip |
Review Status |
Start Date | 2023 |
---|---|
End Date | Present |
» Download URL | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/9818/index.html |
Distributor | NOAA Office for Coastal Management (NOAA/OCM) (2023 - Present) |
File Name | Bulk Download |
Description |
Bulk download of data files in LAZ format, geographic coordinates, orthometric heights. Note that the vertical datum (hence elevations) of the files here are different than described in this document. They will be in an orthometric datum. |
File Date/Time | |
File Type (Deprecated) | LAZ |
Distribution Format | LAS/LAZ - LASer |
File Size | |
Application Version | |
Compression | Zip |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Archive Information
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
Location | |
---|---|
File Identifier | |
File Name | |
URL | |
Description | |
DOI | |
Archive Date | |
Archive Update Frequency |
URLs
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 | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Everglades_NP_LiDAR_2017_D16/ |
---|---|
Name | USGS Additional Info |
URL Type | Online Resource |
File Resource Format | |
Description |
Link to the reports, breaklines, metadata, spatial metadata, and shapefiles. |
URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Everglades_NP_LiDAR_2017_D16/USGS_FL_Everglades_NP_LiDAR_2017_D16_Project_Report.pdf |
---|---|
Name | USGS Project Report |
URL Type | Online Resource |
File Resource Format | |
Description |
Link to the USGS project report which provides information about the project, the vertical accuracy results, the point classifications and the sensors used. |
URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/FL_Everglades_NP_LiDAR_2017_D16/FL_Everglades_S_2017/reports/Everglades_National_Park_Topobathy_Lidar_Project_Report_USGS_20180830.pdf |
---|---|
Name | Lidar Report |
URL Type | Online Resource |
File Resource Format | |
Description |
Link to the lidar report. |
URL | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/entwine/geoid18/9818/ept.json |
---|---|
Name | Entwine Point Tile (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 | https://coast.noaa.gov/lidar/viewer/v/noaapotree.html?r=https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/entwine/geoid18/9818/ept.json |
---|---|
Name | Potree 3D View |
URL Type | Online Resource |
File Resource Format | |
Description |
Link to view the point cloud (using the Entwine Point Tile (EPT) format) in the 3D Potree viewer. |
URL | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/9818/supplemental/fl2017_everglades_np_m9818.kmz |
---|---|
Name | Browse Graphic |
URL Type | Browse Graphic |
File Resource Format | kmz |
Description |
This graphic displays the footprint for this lidar data set. |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
Activity Log
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Issues
Issue Date | |
---|---|
Author | |
Issue |
Issue Date | |
---|---|
Author | |
Issue |
Issue Date | |
---|---|
Author | |
Issue |
Technical Environment
Description |
|
---|
Data Quality
Representativeness | |
---|---|
Accuracy | |
Analytical Accuracy | |
Horizontal Positional Accuracy | |
Vertical Positional Accuracy |
The project specifications require that only Non-Vegetated Vertical Accuracy (NVA) be computed for raw lidar point cloud swath files. The required accuracy (ACCz) is: 19.6 cm at a 95% confidence level, derived according to NSSDA, i.e., based on RMSE of 10 cm in the "bare earth" and "urban" land cover classes. Dewberry Determined Vertical Accuracy The NVA was tested with 60 checkpoints located in bare earth and urban (non-vegetated) areas. These check points were not used in the calibration or post processing of the lidar point cloud data. The checkpoints were distributed throughout the project area and were surveyed using GPS techniques. See survey report for additional survey methodologies. Elevations from the unclassified lidar surface were measured for the x,y location of each check point. Elevations interpolated from the lidar surface were then compared to the elevation values of the surveyed control points. AccuracyZ has been tested to meet 19.6 cm or better Non-Vegetated Vertical Accuracy at 95% confidence level using RMSE(z) x 1.9600 as defined by the National Standards for Spatial Data Accuracy (NSSDA); assessed and reported using National Digital Elevation Program (NDEP)/ASRPS Guidelines. Tested 0.085 meters NVA at a 95% confidence level using RMSE(z) x 1.9600 as defined by the National Standards for Spatial Data Accuracy (NSSDA). The NVA of the raw lidar point cloud swath files was calculated against TINs derived from the final calibrated and controlled swath data using 60 independent checkpoints located in Bare Earth and Urban land cover classes. USGS Determined Vertical Accuracy Non-Vegetated Vertical Accuracy (NVA) = 7.29 cm at the 95% Confidence Level or 3.7 cm RMSE Vegetated Vertical Accuracy (VVA) = 33.51 cm at the 95th Percentile Bathymetric Vertical Accuracy = 38.73 cm at the 95% Confidence Level Refer to the USGS project report in the URL section of this metadata record. |
Quantitation Limits | |
Bias | |
Comparability | |
Completeness Measure | |
Precision | |
Analytical Precision | |
Field Precision | |
Sensitivity | |
Detection Limit | |
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 data passes Non-Vegetated Vertical Accuracy specifications. |
Conceptual Consistency |
Data covers the entire area specified for this project. |
» Quality Control Procedures Employed |
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 |
» Is Access to the Data Limited Based on an Approved Waiver? | |
» If Distributor (Data Hosting Service) is Needed, Please Indicate | |
» Approximate Delay Between Data Collection and Dissemination | |
» If Delay is Longer than Latency of Automated Processing, Indicate Under What Authority Data Access is Delayed | |
» Actual or Planned Long-Term Data Archive Location | NCEI-CO |
» Approximate Delay Between Data Collection and Archiving | |
» 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 |
Data were collected and processed by Dewberry and were made available on the USGS rockyweb site. The data were downloaded from the USGS rockyweb site by the NOAA Office for Coastal Management (OCM) where the data were processed to make it available for custom download from the NOAA Digital Coast Data Access Viewer (DAV) and bulk download from AWS S3. |
---|
Sources
Citation Title | USGS LAZ Files |
---|---|
Contact Role Type | Publisher |
Contact Type | Organization |
Contact Name | USGS |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Scale Denominator | |
Citation URL | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/FL_Everglades_NP_LiDAR_2017_D16/ |
Citation URL Name | USGS Rockyweb |
Citation URL Description | |
Source Contribution |
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Process Steps
Process Step Number | 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 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 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 1.2, and 2D breaklines were collected for water features. Topobathy DEMs were exported from the classified point cloud. |
Process Date/Time | 2017-01-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 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) and Class 40 (Submerged Topography/Bathymetry) 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 Inland Water Void breaklines were then classified to water (ASPRS Class 9) using TerraScan macro functionality. Refraction correction was performed on all data within the Land/Water Interface breaklines. All ground (ASPRS Class 2) lidar data were then classified to submerged topography/bathymetry (ASPRS Class 40), and water surface (ASPRS Class 41) were classified using Terrascan macro functionality on both Green sensor and Near Infrared sensor data within the Land/Water Interface breaklines. Submerged topography/bathymetry (ASPRS Class 40) were then classified to water column/ no bottom found (ASPRS Class 45) within the Topobathy Void breaklines. 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 us used as a final check of the bare earth dataset. GeoCue was then used to create the deliverable industry-standard LAS files for both the 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 | 2018-05-15 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 3 |
---|---|
» Description |
The NOAA Office for Coastal Management (OCM) downloaded 3320 laz point data files from these USGS sites: https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/FL_Everglades_NP_LiDAR_2017_D16/FL_Everglades_N_2017/LAZ/ https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/FL_Everglades_NP_LiDAR_2017_D16/FL_Everglades_S_2017/LAZ/ In the Everglades_S folder, file 17RMJ900210 was found to be corrupt. USGS was notified of the issue. For a workaround, this same file was also included in the https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/FL_Everglades_NP_LiDAR_2017_D16/FL_Everglades_S_Hydroflattened_2017/LAZ/ folder. Comparison between the two files indicated that the files were exactly the same. The file in the Hydroflattened folder however, was not corrupt. This non-corrupt file from the Hydroflattened folder was downloaded and used for processing. USGS confirmed this solution. The data were in UTM Zone 17N (NAD83 2011), meters coordinates and NAVD88 (Geoid12B) elevations in meters. The data were classified as: 1 - Unclassified, 2 - Ground, 7 - Low Noise, 9 - Water, 17 - Bridge Decks, 18 - High Noise, 40 - Bathymetric Bottom, 41 - Water Surface, 45 - No bathymetric bottom found (water column). OCM processed all classifications of points to the Digital Coast Data Access Viewer (DAV). Classes available on the DAV are: 1, 2, 7, 9, 17, 18, 40, 41, 45. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. Internal OCM scripts were run to check the number of points by classification and by flight ID and the gps, elevation, and intensity ranges. 2. Internal OCM scripts were run on the laz files to: a. Convert from orthometric (NAVD88) elevations to NAD83 (2011) ellipsoid elevations using the Geoid12B model b. Convert the laz files from UTM Zone 17N (NAD83 2011), meters coordinates to geographic coordinates c. Assign the geokeys, sort the data by gps time and zip the data to database and AWS S3. |
Process Date/Time | 2023-09-07 00:00:00 |
Process Contact | Office for Coastal Management (OCM) |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Acquisition Information
Instruments
Instrument Unavailable Reason |
---|
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Platforms
Platform Unavailable Reason |
---|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
FAQs
Date | |
---|---|
Author | |
Question | |
Answer |
Child Items
Rubric scores updated every 15m
Score | Type | Title |
---|---|---|
Related Items
Item Type | Relationship Type | Title |
---|---|---|
Catalog Details
Catalog Item ID | 69618 |
---|---|
Metadata Record Created By | Rebecca Mataosky |
Metadata Record Created | 2023-04-18 14:55+0000 |
Metadata Record Last Modified By | SysAdmin InPortAdmin |
» Metadata Record Last Modified | 2023-10-17 16:12+0000 |
Metadata Record Published | 2023-09-08 |
Owner Org | OCMP |
Metadata Publication Status | Published Externally |
Do Not Publish? | N |
Metadata Workflow State | Published / External |
Metadata Last Review Date | 2023-09-08 |
Metadata Review Frequency | 1 Year |
Metadata Next Review Date | 2024-09-08 |
Tags |
---|