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.

URL of higher-level DM Plan (if any) as submitted to DM Plan Repository:
Always left blank

1. General Description of Data to be Managed

1.1. Name of the Data, data collection Project, or data-producing Program:
2017 NOAA/MCP Topobathy Lidar: Blue Hill Bay, ME - Riegl Sensor
1.2. Summary description of the data:

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 Riegl 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 Riegl VQ-820-Q LiDAR system along Blue Hill Bay on the coastline of Maine. These files contain topographic and bathymetric LiDAR elevations generated from data collected with the Riegl VQ-820-G LiDAR system along Blue Hill Bay on the coastline of Maine. Data were collected by Fugro for NOAA OCM. The Riegl VQ-820-G system is a 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 1 time the Secchi disk depth. Survey coverage is based on a delimiting polygon provided by NOAA OCM, which envelopes the area between the 0 m contour (NAVD88) down to approximated -10 meters. Riegl VQ-820-G data were processed on Riegl RiProcess software for: point cloud generation, boresight calibration, water surface classification and modeling, refraction correction; and exported with a minimal classification LAS format v1.4 for delivery. Additional classification was performed after delivery to extract ground and bathymetric points.

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 link to custom download the concurrently collected topographic and bathymetric data (collected with the SHOALS-1000T lidar system) is provided in the URL section of this metadata record.

Taken From: Item Identification | Abstract
Notes: Only a maximum of 4000 characters will be included.
Edit
1.3. Is this a one-time data collection, or an ongoing series of measurements?
One-time data collection
Taken From: Extents / Time Frames | Time Frame Type
Notes: Data collection is considered ongoing if a time frame of type "Continuous" exists.
Edit
1.4. Actual or planned temporal coverage of the data:
2017-06-29 to 2017-07-05
Taken From: Extents | Time Frame - Start, Time Frame - End
Notes: All time frames from all extent groups are included.
Edit
1.5. Actual or planned geographic coverage of the data:
W: -68.566, E: -68.432, N: 44.313, S: 44.194
Taken From: Extents | Geographic Area Bounds, Geographic Area Description
Notes: All geographic areas from all extent groups are included.
Edit
1.6. Type(s) of data:
(e.g., digital numeric data, imagery, photographs, video, audio, database, tabular data, etc.)
Point Cloud (Digital)
1.7. Data collection method(s):
(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.)
No information found
1.8. If data are from a NOAA Observing System of Record, indicate name of system:
Always left blank due to field exemption
1.8.1. If data are from another observing system, please specify:
Always left blank due to field exemption

2. Point of Contact for this Data Management Plan (author or maintainer)

2.1. Name:
NOAA Office for Coastal Management (NOAA/OCM)
Taken From: Support Roles (Metadata Contact) | Person
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.
Edit
2.2. Title:
Metadata Contact
Always listed as "Metadata Contact"
2.3. Affiliation or facility:
NOAA Office for Coastal Management (NOAA/OCM)
Taken From: Support Roles (Metadata Contact) | Organization
Notes: The name of the Organization of the most recent Support Role of type "Metadata Contact" is used. This field is required if applicable.
Edit
2.4. E-mail address:
coastal.info@noaa.gov
Notes: The email address is taken from the address listed for the Person assigned as the Metadata Contact in Support Roles.
2.5. Phone number:
(843) 740-1202
Notes: The phone number is taken from the number listed for the Person assigned as the Metadata Contact in Support Roles. If the phone number is missing or incorrect, please contact your Librarian to update the Person record.

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.

3.1. Name:
No information found
Taken From: Support Roles (Data Steward) | Person
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.
Edit
3.2. Position Title:
Data Steward
Always listed as "Data Steward"

4. Resources

Programs must identify resources within their own budget for managing the data they produce.

4.1. Have resources for management of these data been identified?
No information found
4.2. Approximate percentage of the budget for these data devoted to data management (specify percentage or "unknown"):
No information found

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.

5.1. Processing workflow of the data from collection or acquisition to making it publicly accessible
(describe or provide URL of description):

Process Steps:

  • The airborne raw files from the VQ-820-G sensor are downloaded into RIEGL LMS RiProcess version 1.8.3. The system collects bathymetric LiDAR data at 520 kHz Pulse Repetition Rate for an approximated point density of 8.5 pts/m2 at 400 m altitude (AGL) and 100 kts (speed over ground). 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). The RiProcess process also produced the automated and semi-automated clasification of water surface points to generate a water surface model for refraction correction of all lidar points underwater. Point clouds data was exported to LAS format were additional QC reviews were performed in external tools (Terrascan), including positioning adjustments to overlapping line data. 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 a basic classification produced during the refraction correction process: Emerged and topographic points (1), Noise (7), Submerged Underwater points (40), Derived water surface (42). However, other than this necessary processing classification, the dataset has not been further classified or edited.
  • 2018-02-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. Ecognition was used to generate a water mask for extracting bathymetric points and identifying water surface and other non-bottom bathymetric points. 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), and class 40 (bathymetric point). Class 40 represents seafloor points. Class 1 on land includes all non-ground points (e.g., vegetation, buildings, powerlines). Class 1 in the water includes all non-bathymetric points (e.g., water surface, water column, floating submerged aquatic vegetation, and docks/piers).
  • 2018-05-09 00:00:00 - The NOAA Office for Coastal Management (OCM) received 287 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. OCM processed all classifications of points to the Digital Coast Data Access Viewer (DAV). Classes available on the DAV are: 1, 2, 7, 40. 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.
5.1.1. If data at different stages of the workflow, or products derived from these data, are subject to a separate data management plan, provide reference to other plan:
Always left blank
5.2. Quality control procedures employed
(describe or provide URL of description):
No information found

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.

6.1. Does metadata comply with EDMC Data Documentation directive?
No
Notes: All required DMP fields must be populated and valid to comply with the directive.
6.1.1. If metadata are non-existent or non-compliant, please explain:

Missing/invalid information:

  • 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?
Notes: Required DMP fields that are not populated or invalid are listed here.
6.2. Name of organization or facility providing metadata hosting:
NMFS Office of Science and Technology
Always listed as "NMFS Office of Science and Technology"
6.2.1. If service is needed for metadata hosting, please indicate:
Always left blank
6.3. URL of metadata folder or data catalog, if known:
Always listed as the URL to the InPort Data Set record
6.4. Process for producing and maintaining metadata
(describe or provide URL of description):
Metadata produced and maintained in accordance with the NOAA Data Documentation Procedural Directive: https://nosc.noaa.gov/EDMC/DAARWG/docs/EDMC_PD-Data_Documentation_v1.pdf
Always listed with the above statement

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.

7.1. Do these data comply with the Data Access directive?
No information found
7.1.1. If the data are not to be made available to the public at all, or with limitations, has a Waiver (Appendix A of Data Access directive) been filed?
No information found
7.1.2. If there are limitations to public data access, describe how data are protected from unauthorized access or disclosure:

None

7.2. Name of organization of facility providing data access:
NOAA Office for Coastal Management (NOAA/OCM)
Taken From: Support Roles (Distributor) | Organization
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.
Edit
7.2.1. If data hosting service is needed, please indicate:
Taken From: Data Management | If data hosting service is needed, please indicate
Notes: This field is required if a Distributor has not been specified.
Edit
7.2.2. URL of data access service, if known:
Taken From: Distribution Info | Download URL
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
Edit
7.3. Data access methods or services offered:

Data is available online for custom and bulk downloads.

7.4. Approximate delay between data collection and dissemination:
No information found
7.4.1. If delay is longer than latency of automated processing, indicate under what authority data access is delayed:

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.

8.1. Actual or planned long-term data archive location:
(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)
No information found
8.1.1. If World Data Center or Other, specify:
Taken From: Data Management | Actual or planned long-term data archive location
Notes: This field is required if archive location is World Data Center or Other.
Edit
8.1.2. If To Be Determined, Unable to Archive or No Archiving Intended, explain:
Taken From: Data Management | If To Be Determined, Unable to Archive or No Archiving Intended, explain
Notes: This field is required if archive location is To Be Determined, Unable to Archive, or No Archiving Intended.
Edit
8.2. Data storage facility prior to being sent to an archive facility (if any):
Office for Coastal Management - Charleston, SC
Taken From: Physical Location | Organization, City, State, Location Description
Notes: Physical Location Organization, City and State are required, or a Location Description is required.
Edit
8.3. Approximate delay between data collection and submission to an archive facility:
No information found
8.4. How will the data be protected from accidental or malicious modification or deletion prior to receipt by the archive?
Discuss data back-up, disaster recovery/contingency planning, and off-site data storage relevant to the data collection
No information found

9. Additional Line Office or Staff Office Questions

Line and Staff Offices may extend this template by inserting additional questions in this section.

Always left blank