Data Management Plan
Office for Coastal Management
Data Set (DS) | Cat ID: 52596 | 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
Fugro was contracted in July 2017 by the State of Maine Department of Marine Resources (SMDMR), Maine Coastal Program (MCP), and the NOAA Office for Coastal Management (OCM) to conduct an Airborne LiDAR Bathymetry (ALB) survey in the vicinity of Blue Hill Bay in Maine, and to deliver fully processed and verified hydrographic survey data.The ALB survey was conducted with the SHOALS-1000T and Riegl VQ-820-G lidar systems in a concurrent acquisition. The SHOALS system, with a high power laser, provided the better probability for deep sounding detections at a reduced point density (about 0.15 pts/m2); whilst the VQ-820-Q provided high density coverage (up to 8.5 pts/m2) but at reduced depth detection.
This metadata record describes the topographic and bathymetric LiDAR elevations generated from data collected with the SHOALS-1000T LiDAR system along Blue Hill Bay on the coastline of Maine. Data were collected by Fugro for NOAA OCM. The SHOALS system is a bathymetric LiDAR sensor for use in coastal mapping and charting activities because the laser's ability to penetrate the water column and detect targets up to 2.5 times the Secchi disk depth. Survey coverage was based on a delimiting polygon provided by NOAA OCM, which envelopes the area between the 0 m contour (NAVD88) down to approximated -10 meters. An additional horizontal buffer of 100 meters from the 0 m contour expanded the survey area coverage to include the adjacent emerged topography. SHOALS data have been processed on Optech SHOALS-GCS and QPS Fledermaus software packages for: auto-processing; calibration, cleaning and editing, validation, basic classification, and exported to LAS format.
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.
A topographic and bathymetric reflectance raster are also available. These data are available for download at the link provided in the URL section of this metadata record.
A link to custom download the concurrently collected topographic and bathymetric data (collected with the Riegl VQ-820-G lidar system) is provided in the URL section of this metadata record.
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)
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.
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):
- The airborne raw files from the SHOALS sensor are downloaded into SHOALS-GCS software version 6.32. The system collects bathymetric LiDAR data at 2.5 kHz Pulse Repetition Rate for an approximated point density of 0.15 pts/m2 at 400 m altitude (AGL) and 100 kts (speed over ground). The SHOALS system also collects RGB imagery at 1 Hz using a Prosilica GX330 digital camera. Aircraft position, velocity, angular and acceleration information collected with an Applanix POS AV 510 v6 equipment were processed using Applanix POSPac v 7.1 software to produce a Smoothed Best Estimate Trajectory (SBET) solution file that is used by RiProcess to produce 3D positions for each LiDAR shot (point clouds). SHOALS-GCS auto-processing routine estimates the water surface and bottom surface points for each laser shot and applied the refraction correction automatically. Upon inspection and QA/QC in Fledermaus software version 7.7, anomalous data were flagged as invalid and bathymetry properly validated. All LiDAR points including bathymetric, topographic, water surface, noise and rejections were exported to LAS format. Elevations referenced to NAVD88 datum were reduced with the application with VDatum v3.6.1. and GEOID12b. Data was exported to LAS format 1.4 for delivery. LAS data has the following classification: Emerged and topographic points (1), Noise and Rejections (7), Bathymetry (40), Derived water surface (42), and Submerged objects (wrecks, rocks, pilings) (43).
- 2018-04-01 00:00:00 - The delivered LAS files were reviewed and processed to classify the point cloud and compute vertical accuracy. A variety of LAStools executables were used to tile the swaths, classify points (noise, ground, and bathymetric points), generate gridded products, and perform the final quantitative accuracy assessment. Global Mapper was used to perform qualitative assessments of the point clouds and gridded products at each step of the classification process. ArcGIS Pro was used to organize and visualize all delivered products and generate web services for team reviews. The final classification includes class 1 (unclassified), class 2 (bare ground), class 7 (low noise), class 40 (bathymetric point), class 42 (derived water surface), and class 43 (submerged objects).
- 2018-05-09 00:00:00 - The NOAA Office for Coastal Management (OCM) received 92 las files. The files contained topobathy elevation and intensity measurements in Blue Hill Bay along the coastline of Maine. The data were set to NAD83 2011 UTM Zone 19 North in meters and NAVD88 (Geoid12B) elevations in meters. The data were classified as: 1 -Unclassified, 2 - Ground, 7 - Low Noise, 40 - Bathymetry, 42 - Derived Water Surface. OCM processed all classifications of points to the Digital Coast Data Access Viewer (DAV). Classes available on the DAV are: 1, 2, 7, 40, 42. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. The LAStools software scripts lasinfo and lasvalidate were run on the las files to check for errors. 2. An internal OCM script was run to check the number of points by classification and by flight ID and the gps and intensity ranges. 3. Internal OCM scripts were run on the las files to convert from orthometric (NAVD88) elevations to ellipsoid elevations using the Geoid 12B model, to convert from NAD83 2011 UTM Zone 19 North in meters to geographic coordinates, to assign the geokeys, to sort the data by gps time and zip the data to database and to http.
(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.
- 1.7. Data collection method(s)
- 3.1. Responsible Party for Data Management
- 4.1. Have resources for management of these data been identified?
- 4.2. Approximate percentage of the budget for these data devoted to data management
- 5.2. Quality control procedures employed
- 7.1. Do these data comply with the Data Access directive?
- 7.1.1. If data are not available or has limitations, has a Waiver been filed?
- 7.1.2. If there are limitations to data access, describe how data are protected
- 7.4. Approximate delay between data collection and dissemination
- 8.1. Actual or planned long-term data archive location
- 8.3. Approximate delay between data collection and submission to an archive facility
- 8.4. How will the data be protected from accidental or malicious modification or deletion prior to receipt by the archive?
(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.
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.
Data is available online for custom and bulk 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
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.