2021 USGS Lidar: Western Maryland
Data Set (DS) | OCM Partners (OCMP)GUID: gov.noaa.nmfs.inport:70420 | Updated: October 17, 2023 | Published / External
Summary
Short Citation
OCM Partners, 2024: 2021 USGS Lidar: Western Maryland, https://www.fisheries.noaa.gov/inport/item/70420.
Full Citation Examples
Products: This MD_Western_2021_D21 project called for the planning, acquisition, processing, and derivative products of lidar data to be collected at an aggregate nominal pulse spacing (ANPS) of 0.71 meters (2ppsm). Project specifications are based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, Version 2.1. The data was developed based on a horizontal projection/datum of NAD83 (2011), UTM 17N and 18N, meters and vertical datum of NAVD88 (GEOID18), meters. Lidar data was delivered as processed Classified LAS 1.4 files, formatted to 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.
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. This data set includes two deliveries:
1. MD_Western_1 (Work Unit 223523) which is in UTM Zone 17N
2. MD_Western_2 (Work Unit 300150) which is in UTM Zone 18N
Distribution Information
-
Create custom data files by choosing data area, product type, map projection, file format, datum, etc. A new metadata will be produced to reflect your request using this record as a base. Change to an orthometric vertical datum is one of the many options.
-
LAS/LAZ - LASer
Bulk download of data files in LAZ format, UTM Zone 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. Any conclusions drawn from the analysis of this information are not the responsibility of the U.S. Geological Survey or its partners. Acknowledgement of the U.S. Geological Survey would be appreciated for products derived from these data.
Controlled Theme Keywords
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.07° W,
-77.99° E,
39.73° N,
39.24° S
MD_Western_1 (Work Unit 223523)
2021-12-04 - 2021-12-12
Dates of collection for MD_Western_1 (Work Unit 223523)
Item Identification
Title: | 2021 USGS Lidar: Western Maryland |
---|---|
Short Name: | md2021_western_m9872_metadata |
Status: | Completed |
Creation Date: | 2021 |
Publication Date: | 2023-01-29 |
Abstract: |
Products: This MD_Western_2021_D21 project called for the planning, acquisition, processing, and derivative products of lidar data to be collected at an aggregate nominal pulse spacing (ANPS) of 0.71 meters (2ppsm). Project specifications are based on the U.S. Geological Survey National Geospatial Program Base Lidar Specification, Version 2.1. The data was developed based on a horizontal projection/datum of NAD83 (2011), UTM 17N and 18N, meters and vertical datum of NAVD88 (GEOID18), meters. Lidar data was delivered as processed Classified LAS 1.4 files, formatted to 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. 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. This data set includes two deliveries: 1. MD_Western_1 (Work Unit 223523) which is in UTM Zone 17N 2. MD_Western_2 (Work Unit 300150) which is in UTM Zone 18N |
Purpose: |
This high resolution lidar data will support the United States Geological Survey (USGS) initiatives. |
Supplemental Information: |
USGS Contract No. G17PC00015 CONTRACTOR: Fugro Geospatial, Inc. SUBCONTRACTOR: Terrasurv, Inc. Ground control and checkpoints collected by Terrasurv, Inc. All processing was completed by the prime contractor. Point Cloud File Type = LAS v1.4 Point Record Format 6, 7, 8, 9, or 10 including "File Source ID" The following are the USGS lidar fields in JSON: {
"ldrinfo" : {
"ldrspec" : "USGS-NGP Base Lidar Specification v2.1", "ldrsens" : "Riegl LMS-Q1560i", "ldrmaxnr" : "7", "ldrnps" : "0.5", "ldrdens" : "4", "ldranps" : "0.5", "ldradens" : "4", "ldrfltht" : "732", "ldrfltsp" : "125", "ldrscana" : "60", "ldrscanr" : "130; 110", "ldrpulsr" : "330; 340", "ldrpulsd" : "3", "ldrpulsw" : "0.8994", "ldrwavel" : "1064", "ldrmpia" : "1", "ldrbmdiv" : "? 0.25", "ldrswatw" : "832", "ldrswato" : "30", "ldrgeoid" : "National Geodetic Survey (NGS) GEOID18" }, "ldrinfo" : {
"ldrspec" : "USGS-NGP Base Lidar Specification v2.1", "ldrsens" : "ALS80", "ldrmaxnr" : "4", "ldrnps" : "0.50", "ldrdens" : "2", "ldranps" : "0.50", "ldradens" : "2", "ldrfltht" : "2260", "ldrfltsp" : "150", "ldrscana" : "26.5", "ldrscanr" : "52", "ldrpulsr" : "534", "ldrpulsd" : "2.5", "ldrpulsw" : "0.75", "ldrwavel" : "1064", "ldrmpia" : "1", "ldrbmdiv" : "0.26", "ldrswatw" : "2000", "ldrswato" : "18", "ldrgeoid" : "National Geodetic Survey (NGS) GEOID18" }, "ldraccur" : {
"ldrchacc" : "0", "rawnva" : "0", "rawnvan" : "0" }, "lasinfo" : {
"lasver" : "1.4", "lasprf" : "6", "laswheld" : "There were no withheld points identified in this project. All points were used in the classification.", "lasolap" : "Swath "overage" points were identified in these files using the standard LAS overlap bit.", "lasintr" : "16 bit", "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 (breakline proximity)" } }} |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
Global Change Master Directory (GCMD) Science Keywords |
EARTH SCIENCE > LAND SURFACE > TOPOGRAPHY > TERRAIN 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 > MARYLAND
|
Global Change Master Directory (GCMD) Location Keywords |
CONTINENT > NORTH AMERICA > UNITED STATES OF AMERICA > WEST VIRGINIA
|
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: | Fugro, USGS |
Support Roles
Data Steward
Date Effective From: | 2023 |
---|---|
Date Effective To: | |
Contact (Organization): | NOAA Office for Coastal Management (NOAA/OCM) |
Address: |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address: | coastal.info@noaa.gov |
Phone: | (843) 740-1202 |
URL: | https://coast.noaa.gov |
Distributor
Date Effective From: | 2023 |
---|---|
Date Effective To: | |
Contact (Organization): | NOAA Office for Coastal Management (NOAA/OCM) |
Address: |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address: | coastal.info@noaa.gov |
Phone: | (843) 740-1202 |
URL: | https://coast.noaa.gov |
Distributor
Date Effective From: | 2022 |
---|---|
Date Effective To: | |
Contact (Organization): | U.S. Geological Survey |
Address: |
12201 Sunrise Valley Drive Reston, VA 20191 USA |
URL: | USGS Home |
Metadata Contact
Date Effective From: | 2023 |
---|---|
Date Effective To: | |
Contact (Organization): | NOAA Office for Coastal Management (NOAA/OCM) |
Address: |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address: | coastal.info@noaa.gov |
Phone: | (843) 740-1202 |
URL: | https://coast.noaa.gov |
Point of Contact
Date Effective From: | 2023 |
---|---|
Date Effective To: | |
Contact (Organization): | NOAA Office for Coastal Management (NOAA/OCM) |
Address: |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address: | coastal.info@noaa.gov |
Phone: | (843) 740-1202 |
URL: | https://coast.noaa.gov |
Extents
Currentness Reference: | Ground Condition |
---|
Extent Group 1
Extent Group 1 / Geographic Area 1
W° Bound: | -79.07 | |
---|---|---|
E° Bound: | -77.99 | |
N° Bound: | 39.73 | |
S° Bound: | 39.24 | |
Description |
MD_Western_1 (Work Unit 223523) |
Extent Group 1 / Time Frame 1
Time Frame Type: | Range |
---|---|
Start: | 2021-12-04 |
End: | 2021-12-12 |
Description: |
Dates of collection for MD_Western_1 (Work Unit 223523) |
Extent Group 2
Extent Group 2 / Geographic Area 1
W° Bound: | -78 | |
---|---|---|
E° Bound: | -77.01 | |
N° Bound: | 39.73 | |
S° Bound: | 39.13 | |
Description |
MD_Western_2 (Work Unit 300150) |
Extent Group 2 / Time Frame 1
Time Frame Type: | Range |
---|---|
Start: | 2021-12-14 |
End: | 2021-12-21 |
Description: |
Dates of collection for MD_Western_2 (Work Unit 300150) |
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. Any conclusions drawn from the analysis of this information are not the responsibility of the U.S. Geological Survey or its partners. Acknowledgement of the U.S. Geological Survey would be appreciated for products derived from these data. |
Distribution Information
Distribution 1
Start Date: | 2023-08-07 |
---|---|
End Date: | Present |
Download URL: | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=9872/details/9872 |
Distributor: | NOAA Office for Coastal Management (NOAA/OCM) (2023 - Present) |
File Name: | Customized Download |
Description: |
Create custom data files by choosing data area, product type, map projection, file format, datum, etc. A new metadata will be produced to reflect your request using this record as a base. Change to an orthometric vertical datum is one of the many options. |
File Type (Deprecated): | Zip |
Compression: | Zip |
Distribution 2
Start Date: | 2023-08-07 |
---|---|
End Date: | Present |
Download URL: | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/MD_Western_2021_D21/ |
Distributor: | U.S. Geological Survey (2022 - Present) |
File Name: | Bulk Download |
Description: |
Bulk download of data files in LAZ format, UTM Zone 17N and 18N, NAD83(2011), meters coordinates and NAVD88 (Geoid18) elevations in meters. |
File Type (Deprecated): | LAZ |
Distribution Format: | LAS/LAZ - LASer |
Compression: | Zip |
URLs
URL 1
URL: | https://coast.noaa.gov/dataviewer/ |
---|---|
Name: | NOAA's Office for Coastal Management (OCM) Data Access Viewer (DAV) |
URL Type: |
Online Resource
|
File Resource Format: | HTML |
Description: |
The Data Access Viewer (DAV) allows a user to search for and download elevation, imagery, and land cover data for the coastal U.S. and its territories. The data, hosted by the NOAA Office for Coastal Management, can be customized and requested for free download through a checkout interface. An email provides a link to the customized data, while the original data set is available through a link within the viewer. |
URL 2
URL: | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/MD_Western_2021_D21/ |
---|---|
Name: | USGS Additional Info |
URL Type: |
Online Resource
|
Description: |
Link to the reports, breaklines, metadata, and spatial metadata. |
URL 3
URL: | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/MD_Western_2021_D21/USGS_MD_Western_2021_D21_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, the point classes and sensors used. |
URL 4
URL: | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/MD_Western_2021_D21/MD_Western_1_D21/reports/lidar_mapping_report/MD_Western_2021_D21_UTM_17N_Lidar_Mapping_Report.pdf |
---|---|
Name: | Lidar Report - MD_Western_1 |
URL Type: |
Online Resource
|
File Resource Format: | |
Description: |
Link to the Fugro lidar report for MD_Western_1 |
URL 5
URL: | https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/metadata/MD_Western_2021_D21/MD_Western_2_D21/reports/lidar_mapping_report/USGS_MD_Western_2021_D21_UTM_18N_Lidar_Mapping_Report.pdf |
---|---|
Name: | Lidar Report - MD_Western_2 |
URL Type: |
Online Resource
|
File Resource Format: | |
Description: |
Link to the Fugro lidar report for MD_Western_2 |
URL 6
URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/MD_Western_1_D21/ept.json |
---|---|
Name: | USGS Entwine Point Tile (EPT) - MD_Western_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 7
URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/MD_Western_2_D21/ept.json |
---|---|
Name: | USGS Entwine Point Tile (EPT) - MD_Western_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 8
URL: | https://usgs.entwine.io/data/view.html?r=[%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/MD_Western_1_D21/ept.json%22,%22https://s3-us-west-2.amazonaws.com/usgs-lidar-public/MD_Western_2_D21/ept.json%22] |
---|---|
Name: | USGS 3D View |
URL Type: |
Online Resource
|
Description: |
Link to view the point cloud, using the Entwine Point Tile (EPT) format, in the 3D Potree viewer. |
Technical Environment
Description: |
POSGNS 5.2; POSPac 6.2; RiProcess 1.8.3; RiWorld 5.0.2; RiAnalyze 6.2; RiServer 1.99.5; Microstation CONNECT 10.00.00.25; TerraScan 017.039 and 016.013; TerraModeler 016.001; Lasedit 1.35.07; GeoCue 2014.1.21.5; ArcMap 10.3; Global Mapper 17.1.2; ERDAS Imagine 2016; PhotoShop CS8; Fugro proprietary software; Windows 7 64-bit Operating System \\server\directory path\*.las \\server\directory path\*.las \\server\directory path\*.img \\server\directory path\*.gdb \\server\directory path\*.tif/tfw 1440 GB |
---|
Data Quality
Horizontal Positional Accuracy: |
This data was produced to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a 24 (cm) RMSEx/RMSEy Horizontal Accuracy Class which equates to Positional Horizontal Accuracy = +/- 58.6 cm at 95% confidence level. |
---|---|
Vertical Positional Accuracy: |
This data was produced to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a 10-cm RMSEz Vertical Accuracy Class. USGS Determined Vertical Accuracy: Non-Vegetated Vertical Accuracy (NVA) = 2.94 cm RMSE Vegetated Vertical Accuracy (VVA) = 12.87 cm at 95th Percentile |
Completeness Report: |
A complete iteration of processing (GPS/IMU Processing, Raw Lidar Data Processing, and Verification of Coverage and Data Quality) was performed to ensure that the acquired data was complete, uncorrupted, and that the entire project area had been covered without gaps between flight lines. No void areas or missing data exist. The raw point cloud is of good quality and data passes Vertical Accuracy requirements. The Classified Point Cloud data files include all data points collected except the ones from Cross ties and Calibration lines. The points that have been removed or excluded are the points fall outside the project delivery boundary. Points are classified. A visual qualitative assessment was performed to ensure data completeness. No void areas or missing data exist. The classified point cloud is of good quality and data passes Vertical Accuracy requirements. The Intensity Image files cover the entire project delivery boundary. A visual qualitative assessment was performed to ensure data completeness. No void areas or missing data exist. The Intensity Image product is of good quality. The Hydro Breaklines cover the entire project delivery boundary and extend beyond the boundary in a few locations. A visual qualitative assessment was performed to ensure data completeness. No void areas or missing data exist. The Hydro Breakline product is of good quality. The DEM raster files cover the entire project delivery boundary. The pixels that fall outside the project delivery boundary are set to Void with a unique NODATA value. The value is identified in the file headers. There are no void pixels inside the project boundary. A visual qualitative assessment was performed to ensure data completeness. No void areas or missing data exist. The bare earth surface is of good quality and passes Vertical Accuracy requirements. |
Conceptual Consistency: |
Compliance with the accuracy standard was ensured by the collection of ground control and the establishment of GPS base stations in the project area. The following checks were performed: 1) The lidar data accuracy was validated by performing a full boresight adjustment and then checking it against the ground control prior to generating a digital terrain model (DTM) or other products. 2) Lidar elevation data was validated through an inspection of edge matching and visual inspection for quality (artifact removal). The following software was used for the validation: 1) RiProcess 1.8.3, RiWorld 5.0.2, RiAnalyze 6.2, RiServer 1.99.5; and 2) Fugro proprietary software; 20220520. |
Data Management
Have Resources for Management of these Data Been Identified?: | Yes |
---|---|
Approximate Percentage of Budget for these Data Devoted to Data Management: | Unknown |
Do these Data Comply with the Data Access Directive?: | Yes |
Actual or Planned Long-Term Data Archive Location: | NCEI-CO |
How Will the Data Be Protected from Accidental or Malicious Modification or Deletion Prior to Receipt by the Archive?: |
Data is backed up to tape and to cloud storage. |
Lineage
Lineage Statement: |
The NOAA Office for Coastal Management (OCM) ingested references to the USGS Entwine Point Tile (EPT) files 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 ) - MD_Western_2
Contact Role Type: | Publisher |
---|---|
Contact Type: | Organization |
Contact Name: | USGS |
Citation URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/MD_Western_2_D21/ept.json |
Citation URL Name: | Entwine Point Tile for MD_Western_2 |
USGS AWS Entwine Point Tile (EPT) - MD_Western_1
Contact Role Type: | Publisher |
---|---|
Contact Type: | Organization |
Contact Name: | USGS |
Citation URL: | https://s3-us-west-2.amazonaws.com/usgs-lidar-public/MD_Western_1_D21/ept.json |
Citation URL Name: | Entwine Point Tile for MD_Western_1 |
Process Steps
Process Step 1
Description: |
Fugro collected LMS and ALS-derived lidar from December 04, 2021 through December 21, 2021 for the MD_Western_2021_D21 project AOI with 0.71 meters ANPS. Data was collected when environmental conditions meet the criteria specified. To be specific, the following conditions existed prior to launch of the aircraft: 1) Cloud and fog-free between the aircraft and ground, 2) Snow free, 3) No unusual flooding or inundation, and 4) Leaf off. The lidar collection for the MD_Western_2021_D21 Block 1 AOI was accomplished in 09 collections. |
---|
Process Step 2
Description: |
Under Fugro's direction, all surveying activities were performed by Fugro's approved ID/IQ subcontractor Terrasurv, Inc. A total of 40 ground control points to support the lidar collection, along with 79 NVA and 61 VVA checkpoints were collected. The National Spatial Reference System (NSRS) was used to provide control for the network. 9 Continuously Operating Reference Stations (CORS) were included in the network. The horizontal datum was the North American Datum of 1983 (NAD83 (2011)), epoch 2010.0. The vertical datum was the North American Vertical Datum of 1988 (NAVD88), realized with GEOID18. |
---|
Process Step 3
Description: |
Once boresighting was complete for the project, the project was first set up for automatic classification. The lidar data was cut to production tiles. The low noise points, high noise points and ground points were classified automatically in this process. Fugro utilized commercial software, as well as proprietary, in-house developed software for automatic filtering. The parameters used in the process were customized for each terrain type to obtain optimum results. Once the automated filtering was completed, the files were run through a visual inspection to ensure that the filtering was not too aggressive or not aggressive enough. In cases where the filtering was too aggressive and important terrain were filtered out, the data was either run through a different filter within local area or was corrected during the manual filtering process. Bridge deck points were classified as well during the interactive editing process. Interactive editing was completed in visualization software that provides manual and automatic point classification tools. Fugro utilized commercial and proprietary software for this process. All manually inspected tiles went through a peer review to ensure proper editing and consistency. After the manual editing and peer review, all tiles went through another final automated classification routine. This process ensures only the required classifications are used in the final product (all points classified into any temporary classes during manual editing will be re-classified into the project specified classifications). Once manual inspection, QC and final autofilter is complete for the lidar tiles, the LAS data was packaged to the project specified tiling scheme, clipped to project boundary and formatted to LAS v1.4. The file header was formatted to meet the project specification with File Source ID assigned. This Classified Point Cloud product was used for the generation of derived products. This product was delivered in fully compliant LAS v1.4, Point Record Format 6 with Adjusted Standard GPS Time at a precision sufficient to allow unique timestamps for each pulse. Correct and properly formatted georeference information as Open Geospatial Consortium (OGC) well known text (WKT) was assigned in all LAS file headers. Each tile has unique File Source ID assigned. The Point Source ID matches to the flight line ID in the flight trajectory files. Intensity values are included for each point, normalized to 16-bit. The following classifications are included: Class 1 - Processed, but unclassified; Class 2 - Bare earth ground; Class 7 - Low Noise; Class 9 - Water; Class 17 - Bridge Decks; Class 18 - High Noise; Class 20 - Ignored Ground (breakline proximity); Class 21 - Snow (if present and identifiable); Class 22 - Temporal exclusion (typically non-favored data in intertidal zones, use as necessary). The classified point cloud data was delivered in tiles without overlap using the project tiling scheme. |
---|---|
Process Date/Time: | 2022-04-15 00:00:00 |
Process Step 4
Description: |
Original point clouds in LAS/LAZ format were restructured as Entwine Point Tiles and stored on Amazon Web Services. The data were re-projected horizontally to WGS84 web mercator (EPSG 3857) and no changes were made to the vertical elevations in NAVD88 (GEOID18). |
---|---|
Process Contact: | U.S. Geological Survey |
Process Step 5
Description: |
The NOAA Office for Coastal Management (OCM) created references to the Entwine Point Tile (EPT) files that were ingested into the NOAA Digital Coast Data Access Viewer (DAV). No changes were made to the data. The DAV will access the 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/MD_Western_1_D21/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/MD_Western_2_D21/ept.json |
---|---|
Process Date/Time: | 2023-08-07 00:00:00 |
Process Contact: | Office for Coastal Management (OCM) |
Catalog Details
Catalog Item ID: | 70420 |
---|---|
GUID: | gov.noaa.nmfs.inport:70420 |
Metadata Record Created By: | Rebecca Mataosky |
Metadata Record Created: | 2023-08-07 18:30+0000 |
Metadata Record Last Modified By: | SysAdmin InPortAdmin |
Metadata Record Last Modified: | 2023-10-17 16:12+0000 |
Metadata Record Published: | 2023-08-07 |
Owner Org: | OCMP |
Metadata Publication Status: | Published Externally |
Do Not Publish?: | N |
Metadata Last Review Date: | 2023-08-07 |
Metadata Review Frequency: | 1 Year |
Metadata Next Review Date: | 2024-08-07 |