Data Management Plan
GUID: gov.noaa.nmfs.inport:67993 | Published / External
Data Management Plan
DMP Template v2.0.1 (2015-01-01)
Please provide the following information, and submit to the NOAA DM Plan Repository.Reference to Master DM Plan (if applicable)
As stated in Section IV, Requirement 1.3, DM Plans may be hierarchical. If this DM Plan inherits provisions from a higher-level DM Plan already submitted to the Repository, then this more-specific Plan only needs to provide information that differs from what was provided in the Master DM Plan.
1. General Description of Data to be Managed
Morro Bay 2022 Topobathymetric Lidar project data were collected by NV5 Geospatial (NV5) using a Riegl VQ880GII system. Morro Bay 2022 acquisition occurred on 20220614 in two missions. The Morro Bay 2022 dataset includes topobathymetric lidar data in a LAS format 1.4, point data record format 6, with the following classifications in accordance with project specifications and the American Society for Photogrammetry and Remote Sensing (ASPRS) classification standards with the topobathymetric lidar domain profile:
1 - unclassified
1O - edge clip
2 - ground
7W - low noise
9 - NIR water surface
18W - high noise
40 - bathymetric bottom or submerged topography
41 - Green water surface
43 - Submerged object, not otherwise specified (For Morro Bay, oyster reefs have this classification,
even though exposed at low tide)
45 - water column
This dataset also includes lidar intensity values, number of returns, return number, time, and scan angle. The 100 meter buffered project area covers approximately 4,215 acres along the south central Pacific Coast of California near the town of Los Osos. LAS files were compiled in 500 m x 500 m tiles and clipped to the project boundary. The final classified lidar data were used to create topobathymetric bare earth DEMs in GeoTIFF format with 1m pixel resolution. This delivery of the Morro Bay 2022 dataset represents an area covering 97 - 500 m x 500 m LAS tiles clipped to the project boundary. This Project was completed in partnership between NOAA OCM and the NEP.
In addition to these lidar point data, the bare earth Digital Elevation Models (DEM) created from the lidar point data are also available. These data are available for custom download at the link provided in the URL section of this metadata record.
Notes: Only a maximum of 4000 characters will be included.
Notes: Data collection is considered ongoing if a time frame of type "Continuous" exists.
Notes: All time frames from all extent groups are included.
Notes: All geographic areas from all extent groups are included.
(e.g., digital numeric data, imagery, photographs, video, audio, database, tabular data, etc.)
(e.g., satellite, airplane, unmanned aerial system, radar, weather station, moored buoy, research vessel, autonomous underwater vehicle, animal tagging, manual surveys, enforcement activities, numerical model, etc.)
2. Point of Contact for this Data Management Plan (author or maintainer)
Notes: The name of the Person of the most recent Support Role of type "Metadata Contact" is used. The support role must be in effect.
Notes: The name of the Organization of the most recent Support Role of type "Metadata Contact" is used. This field is required if applicable.
3. Responsible Party for Data Management
Program Managers, or their designee, shall be responsible for assuring the proper management of the data produced by their Program. Please indicate the responsible party below.
Notes: The name of the Person of the most recent Support Role of type "Data Steward" is used. The support role must be in effect.
4. Resources
Programs must identify resources within their own budget for managing the data they produce.
5. Data Lineage and Quality
NOAA has issued Information Quality Guidelines for ensuring and maximizing the quality, objectivity, utility, and integrity of information which it disseminates.
(describe or provide URL of description):
Lineage Statement:
NV5 Geospatial collected topobathy elevation data for the NOAA Office for Coastal Management (OCM) and the Morro Bay NEP (National Estuary Program). The data were processed to be available for custom download from the NOAA Digital Coast Data Access Viewer (DAV) and for bulk download from AWS S3.
Process Steps:
- 2022-08-30 00:00:00 - Data for the Morro Bay 2022 project area were acquired by Quantum Spatial (NV5) using Riegl VQ-880-GII Topobathy Lidar systems. All derived LAS data is referenced to: Horizontal Datum-NAD83(2011) epoch: 2010.00 Projection-UTM Zone 10N Horizontal Units-meters Vertical Datum-NAVD88 (Geoid12b) Vertical Units-meters This Morro Bay 2022 redelivery dataset encompasses 97 - 500m x 500m tiles in southern California. Collected Lidar data were immediately processed by NV5 to a level that allowed QA/QC measures to determine if the sensor functioned properly and to assess the coverage of submerged topography. The initial files were inspected for sensor malfunctions and then passed through automated raster generation to develop an initial assessment of bathymetric coverage. NV5 reviewed all acquired flight lines to ensure complete coverage and positional accuracy of the laser points. NV5 resolved kinematic corrections for aircraft position data in PosPac MMS 8.5 using aircraft GNSS and Applanix's proprietary PP-RTX solution. This was used to correct continuous onboard measurements of aircraft position recorded throughout the flight. A final smoothed best estimate trajectory (SBET) was developed, blending post-processed aircraft position with attitude data. Using the SBETs, sensor head position and attitude were calculated throughout the survey. Following final SBET creation, NV5 used RiUnite 1.0.1 to calculate laser point positioning by associating SBET positions to each laser point return time. The speed of light and its direction of travel is changed or refracted when entering the water column from air. A refraction correction was applied to account for this difference by adjusting depth (distance traveled) and horizontal positioning (change of angle/direction) of all submerged points in the Lidar data. TerraSolid v19 and NV5's proprietary software LasMonkey were used to classify water surface points and derive water surface models. Separate models were created for each scanner of each collected swath to ensure temporal differences and wave or water surface height variations between flight lines were accurately accounted for when applying refraction correction to submerged data. These models, along with the Lidar points and the SBETs, were processed in LasMonkey's refraction tool to accurately adjust the positioning of bathymetric points. Using raster-based QC methods, output data were verified to ensure the refraction tool functioned properly. Once all submerged points were refracted by flight line, data were exported to LAS 1.4 format and combined into 500 m x 500 m tiles. NV5 used custom algorithms in Terrascan v19 to classify the initial ground/submerged topography surface points. Data were further calibrated using StripAlign 2.1 based on classified hard surface areas of swath overlap. Relative accuracy was compared and verified through the use Delta-Z (DZ) orthos created using NV5's Las Product Creator. Absolute vertical accuracy of calibrated data were assessed using ground survey data and complete coverage was again verified. After a final automated classification, NV5 performed manual editing to review all classification and improve the final Topobathymetric surface. NV5's LasMonkey software was used to update LAS header information, including all projection and coordinate reference system information. The final Lidar data are in LAS format 1.4 and point data record format 6. The final classification scheme is: 1 - unclassified 1O - edge clip 2 - ground 7W - low noise 9 - NIR water surface 18W - high noise 40 - bathymetric bottom or submerged topography 41 - Green water surface 43 - Submerged object, not otherwise specified (For Morro Bay, oyster reefs have this classification, even though exposed at low tide) 45 - water column
- 2022-10-05 00:00:00 - The NOAA Office for Coastal Management (OCM) received 97 LAS files from NV5 Geospatial. The files contained lidar elevation and intensity measurements. The data were in UTM Zone 10N NAD83(2011), meters coordinates and NAVD88 (Geoid12B) elevations in meters. The point classifications were: 1 - Unclassified, 2 - Ground, 7 - Low Noise, 9 - Water, 18 - High Noise, 40 - Bathymetric Point, 41 - Water Surface, 45 - Water Column. OCM processed all point classes to the Digital Coast Data Access Viewer (DAV). OCM performed the following processing 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 las files to: a. Convert from NAVD88 (Geoid12B) elevations to ellipsoid elevations b. Convert from UTM Zone 10N NAD83 (2011), meters coordinates to geographic coordinates c. Assign the geokeys, to sort the data by gps time and zip the data to database and to the S3 Amazon bucket.
- 2023-02-10 00:00:00 - In February 2023, the NOAA Office for Coastal Management (OCM) received 3 LAS files from NV5 Geospatial. The files contained lidar elevation and intensity measurements and replace 3 existing files. The files are: MRR22_038, MRR22_046, and MRR22_055. These 3 files include class 43 points that are classified as "Submerged object, not otherwise specified (For Morro Bay, oyster reefs have this classification, even though exposed at low tide)." The data were in UTM Zone 10N NAD83(2011), meters coordinates and NAVD88 (Geoid12B) elevations in meters. The point classifications were: 1 - Unclassified, 2 - Ground, 7 - Low Noise, 9 - Water, 18 - High Noise, 40 - Bathymetric Point, 41 - Water Surface, 43 - Submerged Object, 45 - Water Column. OCM processed all point classes to the Digital Coast Data Access Viewer (DAV). OCM performed the following processing 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 las files to: a. Convert from NAVD88 (Geoid12B) elevations to ellipsoid elevations b. Convert from UTM Zone 10N NAD83 (2011), meters coordinates to geographic coordinates c. Assign the geokeys, to sort the data by gps time and zip the data to database and to the S3 Amazon bucket.
(describe or provide URL of description):
6. Data Documentation
The EDMC Data Documentation Procedural Directive requires that NOAA data be well documented, specifies the use of ISO 19115 and related standards for documentation of new data, and provides links to resources and tools for metadata creation and validation.
Missing/invalid information:
- 1.7. Data collection method(s)
- 3.1. Responsible Party for Data Management
- 5.2. Quality control procedures employed
- 7.1.1. If data are not available or has limitations, has a Waiver been filed?
- 7.4. Approximate delay between data collection and dissemination
- 8.3. Approximate delay between data collection and submission to an archive facility
(describe or provide URL of description):
7. Data Access
NAO 212-15 states that access to environmental data may only be restricted when distribution is explicitly limited by law, regulation, policy (such as those applicable to personally identifiable information or protected critical infrastructure information or proprietary trade information) or by security requirements. The EDMC Data Access Procedural Directive contains specific guidance, recommends the use of open-standard, interoperable, non-proprietary web services, provides information about resources and tools to enable data access, and includes a Waiver to be submitted to justify any approach other than full, unrestricted public access.
None
Notes: The name of the Organization of the most recent Support Role of type "Distributor" is used. The support role must be in effect. This information is not required if an approved access waiver exists for this data.
Notes: This field is required if a Distributor has not been specified.
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/9629/index.html
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
Data is available online for bulk and custom downloads.
Notes: This field is required if applicable.
8. Data Preservation and Protection
The NOAA Procedure for Scientific Records Appraisal and Archive Approval describes how to identify, appraise and decide what scientific records are to be preserved in a NOAA archive.
(Specify NCEI-MD, NCEI-CO, NCEI-NC, NCEI-MS, World Data Center (WDC) facility, Other, To Be Determined, Unable to Archive, or No Archiving Intended)
Notes: This field is required if archive location is World Data Center or Other.
Notes: This field is required if archive location is To Be Determined, Unable to Archive, or No Archiving Intended.
Notes: Physical Location Organization, City and State are required, or a Location Description is required.
Discuss data back-up, disaster recovery/contingency planning, and off-site data storage relevant to the data collection
Data is backed up to tape and to cloud storage.
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.