2017 NRCS/FEMA/USGS Lidar: South Central VA
Data Set (DS) | OCM Partners (OCMP)GUID: gov.noaa.nmfs.inport:71879 | Updated: January 16, 2024 | Published / External
Summary
Short Citation
OCM Partners, 2024: 2017 NRCS/FEMA/USGS Lidar: South Central VA, https://www.fisheries.noaa.gov/inport/item/71879.
Full Citation Examples
Product: These lidar data are processed Classified LAS 1.4 files, formatted to 11495 individual 1500 m x 1500 m tiles; used to create intensity images, 3D breaklines and hydro-flattened DEMs as necessary.
Geographic Extent: Virginia and West Virginia, covering approximately 9431 square miles.
Dataset Description: VA FEMA NRCS South Central 2017 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.7 meter. 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 11495 individual 1500 m x 1500 m tiles, as tiled Intensity Imagery, and as tiled bare earth DEMs; all tiled to the same 1500 m x 1500 m schema.
Ground Conditions: Lidar was collected from mid 2017 to mid 2018, 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 63 ground control points that were used to calibrate the lidar to known ground locations established throughout the VA FEMA NRCS South Central project area. An additional 331 independent accuracy checkpoints, 190 in Bare Earth and Urban landcovers (190 NVA points),141 in Tall Grass and Brushland/Low Trees categories (141 VVA points), were used to assess the vertical accuracy of the data. These checkpoints were not used to calibrate or post process the data.
Data were subsequently reprocessed to Entwine Point Tile (EPT) format in web mercator projection with vertical meters. The EPT form of the data is used by the NOAA Digital Coast Data Access Viewer, which this metadata record is supporting. Additional processing steps may have been done by the Data Access Viewer and will be recorded in the lineage section.
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.
-
Not Applicable
JSON file describing an entwine point tiles repository of the dataset.
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
-82.662724° W,
-77.181093° E,
38.84003° N,
36.485989° S
2017-04-14 - 2018-05-24
Item Identification
Title: | 2017 NRCS/FEMA/USGS Lidar: South Central VA |
---|---|
Status: | Completed |
Publication Date: | 2019-08-08 |
Abstract: |
Product: These lidar data are processed Classified LAS 1.4 files, formatted to 11495 individual 1500 m x 1500 m tiles; used to create intensity images, 3D breaklines and hydro-flattened DEMs as necessary. Geographic Extent: Virginia and West Virginia, covering approximately 9431 square miles. Dataset Description: VA FEMA NRCS South Central 2017 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.7 meter. 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 11495 individual 1500 m x 1500 m tiles, as tiled Intensity Imagery, and as tiled bare earth DEMs; all tiled to the same 1500 m x 1500 m schema. Ground Conditions: Lidar was collected from mid 2017 to mid 2018, 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 63 ground control points that were used to calibrate the lidar to known ground locations established throughout the VA FEMA NRCS South Central project area. An additional 331 independent accuracy checkpoints, 190 in Bare Earth and Urban landcovers (190 NVA points),141 in Tall Grass and Brushland/Low Trees categories (141 VVA points), were used to assess the vertical accuracy of the data. These checkpoints were not used to calibrate or post process the data. Data were subsequently reprocessed to Entwine Point Tile (EPT) format in web mercator projection with vertical meters. The EPT form of the data is used by the NOAA Digital Coast Data Access Viewer, which this metadata record is supporting. Additional processing steps may have been done by the Data Access Viewer and will be recorded in the lineage section. |
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 1 meter 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. G16PC00020 CONTRACTOR: Dewberry SUBCONTRACTOR: Leading Edge Geomatics (LEG) and Axis Geospatial, LLC Lidar data were acquired and calibrated by Aerial Scanning Services. 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 v1.2", "ldrsens" : "Riegl VQ-780i", "ldrmaxnr" : "15", "ldrnps" : "1.0", "ldrdens" : "1.0", "ldranps" : "0.7", "ldradens" : "2.0", "ldrfltht" : "1600", "ldrfltsp" : "100", "ldrscana" : "60", "ldrscanr" : "74", "ldrpulsr" : "300", "ldrpulsd" : "3", "ldrpulsw" : "0.9", "ldrwavel" : "1064", "ldrmpia" : "1", "ldrbmdiv" : "0.25", "ldrswatw" : "1848", "ldrswato" : "55", "ldrgeoid" : "National Geodetic Survey (NGS) Geoid12B" }, "ldrinfo" : {
"ldrspec" : "U.S. Geological Survey (USGS) - National Geospatial Program (NGP) Lidar Base Specification v1.2", "ldrsens" : "Riegl LMS-Q1560", "ldrmaxnr" : "15", "ldrnps" : "0.7", "ldrdens" : "2.0", "ldranps" : "0.7", "ldradens" : "2.0", "ldrfltht" : "2087", "ldrfltsp" : "150", "ldrscana" : "58.52", "ldrscanr" : "153", "ldrpulsr" : "687", "ldrpulsd" : "3", "ldrpulsw" : "0.90", "ldrwavel" : "1064", "ldrmpia" : "1", "ldrbmdiv" : "0.25", "ldrswatw" : "2338", "ldrswato" : "15", "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-1560i", "ldrmaxnr" : "15", "ldrnps" : "0.7", "ldrdens" : "2.0", "ldranps" : "0.7", "ldradens" : "2.0", "ldrfltht" : "2087", "ldrfltsp" : "150", "ldrscana" : "58.52", "ldrscanr" : "153", "ldrpulsr" : "687", "ldrpulsd" : "3", "ldrpulsw" : "0.90", "ldrwavel" : "1064", "ldrmpia" : "1", "ldrbmdiv" : "0.25", "ldrswatw" : "2338", "ldrswato" : "15", "ldrgeoid" : "National Geodetic Survey (NGS) Geoid12B" }, "ldraccur" : {
"ldrchacc" : "0.672", "rawnva" : "0.117", "rawnvan" : "183", "clsnva" : "0.113", "clsnvan" : "190", "clsvva" : "0.211", "clsvvan" : "141" }, "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.", "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" : "10", "clasitem" : "Ignored Ground" }, "lasclass" : {
"clascode" : "17", "clasitem" : "Bridge Decks" }, "lasclass" : {
"clascode" : "18", "clasitem" : "High Noise" } }} |
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 |
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: | FEMA, NRCS, USGS, Dewberry |
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 |
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: | -82.662724 | |
---|---|---|
E° Bound: | -77.181093 | |
N° Bound: | 38.84003 | |
S° Bound: | 36.485989 |
Extent Group 1 / Time Frame 1
Time Frame Type: | Range |
---|---|
Start: | 2017-04-14 |
End: | 2018-05-24 |
Spatial Information
Spatial Representation
Representations Used
Grid: | No |
---|---|
Vector: | Yes |
Text / Table: | No |
TIN: | No |
Stereo Model: | No |
Video: | No |
Vector Representation 1
Point Object Present?: | Yes |
---|---|
Point Object Count: | 247071407452 |
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 or 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-01-12 |
---|---|
End Date: | Present |
Download URL: | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=10029/details/10029 |
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: | 2024-01-12 |
---|---|
End Date: | Present |
Download URL: | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/entwine/Geoid12b/10029/ept.json |
Distributor: | NOAA Office for Coastal Management (NOAA/OCM) (2024 - Present) |
File Name: | Entwine Point Tile |
Description: |
JSON file describing an entwine point tiles repository of the dataset. |
Distribution Format: | Not Applicable |
Compression: | LAZ |
URLs
URL 1
URL: | https://usgs.entwine.io/data/view.html?r=[%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/VA_South_Central_B1_2017%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/VA_South_Central_B2_2017%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/VA_South_Central_B3_2017%22] |
---|---|
Name: | 3D data browser |
URL Type: |
Online Resource
|
File Resource Format: | Browser app |
Description: |
Online 3D browser allowing viewing and interrogation of the point cloud. |
URL 2
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. |
Data Quality
Vertical Positional Accuracy: |
Tested Non-Vegetated Vertical Accuracy = 0.117 meters 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 183 independent checkpoints located in Bare Earth and Urban land cover classes. 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. Eight checkpoints (NVA-10, 125, 127, 141, 143, 147, 153, and 157) were removed from the raw swath vertical accuracy testing due to proximity to vegetation. Only non-vegetated terrain checkpoints are used to test the raw swath data because the raw swath data has not been classified to remove vegetation, structures, and other above ground features from the ground classification. Three of these points (NVA-10, 125, and 127) were located in open terrain, but were obscured by overhead branches or transient objects (vehicles). Points NVA- 141, 143, 153, and 157 were removed due to sensor noise modeled by the lidar point cloud. These high points caused erroneous high values during the swath vertical accuracy testing; therefore, these points were removed from the final calculations. Once the data underwent the classification process, the vegetation, objects and high noise were removed from the final ground classification and these seven checkpoints were added back into the final vertical accuracy testing. NVA-147 was positioned next to a steep mountain slope and close to mature trees. The erroneously high survey elevation is likely the result of multipathing errors, which result when vertical obstructions either partially block or "bounce" the GPS signal, producing incorrect position information. This point was removed from all testing. The NVA was tested with 183 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. |
---|---|
Completeness Report: |
These LAS data files include all data points collected. No points have been removed or excluded, including synthetic points. Additional information regarding the synthetic points can be found in the final project report delivered to USGS. 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. |
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
Sources
Entwine Point Tiles
Contact Role Type: | Publisher |
---|---|
Contact Type: | Organization |
Contact Name: | USGS |
Citation URL: | https://usgs.entwine.io/data/view.html?r=[%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/VA_South_Central_B1_2017%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/VA_South_Central_B2_2017%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/VA_South_Central_B3_2017%22] |
Citation URL Name: | Entwine Point Tiles |
Citation URL Description: |
Entwine Point Tiles for 3 blocks making up this mission. |
Source Contribution: |
Data referenced by the Digital Coast Data Access Viewer. |
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 Prime Contractor, LLC 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 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 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. 3, and breaklines were collected for water features. Bare earth DEMs were exported from the classified point cloud using collected breaklines for hydroflattening. |
---|---|
Process Date/Time: | 2018-04-30 00:00:00 |
Process Step 2
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 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 1. 2, and breaklines were collected for water features. Bare earth DEMs were exported from the classified point cloud using collected breaklines for hydroflattening. |
---|---|
Process Date/Time: | 2018-04-30 00:00:00 |
Process Step 3
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 Lake Pond and Double Line Drain hydro flattening breaklines were then classified to water (ASPRS Class 9) using TerraScan macro functionality. A buffer of 0.7 meters was also used around each hydro-flattened feature to classify these ground (ASPRS Class 2) points to Ignored ground (ASPRS Class 10). 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. 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 is 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-12-31 00:00:00 |
Process Step 4
Description: |
Data were converted to Entwine Point Tiles (EPT) in Web Mercator projection and units of meters by USGS. NOAA is leveraging the EPT files for use in the Digital Coast Data Access Viewer and created this metadata to support that usage. |
---|---|
Process Contact: | Office for Coastal Management (OCM) |
Source: | Entwine Point Tiles |
Catalog Details
Catalog Item ID: | 71879 |
---|---|
GUID: | gov.noaa.nmfs.inport:71879 |
Metadata Record Created By: | Blake Waring |
Metadata Record Created: | 2024-01-16 19:18+0000 |
Metadata Record Last Modified By: | Blake Waring |
Metadata Record Last Modified: | 2024-01-16 19:49+0000 |
Metadata Record Published: | 2024-01-16 |
Owner Org: | OCMP |
Metadata Publication Status: | Published Externally |
Do Not Publish?: | N |
Metadata Last Review Date: | 2024-01-16 |
Metadata Review Frequency: | 3 Years |
Metadata Next Review Date: | 2027-01-16 |