Data Management Plan

Products: This VA_UpperMiddleNeck_2018_D18 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 1.3. The original data was developed based on a horizontal projection/datum of NAD83 (2011), Albers Equal Area, 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.

Process Steps:

• 2020-02-10 00:00:00 - 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 re-projected to Albers Equal Area; NAD83 (2011), meters; NAVD88 (GEOID12B), meters. 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). The classified point cloud data was delivered in tiles without overlap using the project tiling scheme. (Citation: Collected and Processed Lidar)
• 2023-11-28 00:00:00 - The NOAA Office for Coastal Management (OCM) downloaded this data set from the USGS RockyWeb portal. The total number of files downloaded and processed was 11,503. The data were in Albers and UTM18 (NAD83 2011), meters, and NAVD88 (Geoid12B) elevations in meters. The data were classified as: 1 - Unclassified, 2 - Ground,, 7 - Noise, 9 - Water, 17 - Bridge Decks, and 20 - Ignored Ground. OCM processed all classifications of points to the Digital Coast Data Access Viewer (DAV). OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. An internal OCM script was run to check the number of points by classification and by flight ID and the gps and intensity ranges. 2. Internal OCM scripts were run on the laz files to convert from orthometric (NAVD88) elevations to ellipsoid elevations using the Geoid12B model, to convert to geographic coordinates, to assign the geokeys, to sort the data by gps time and zip the data to database and to http.

Data is available online for bulk or custom downloads

Data is backed up to cloud storage.