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
High resolution sonar data were collected over ultra-shallow areas of the San Francisco Bay estuary system. Bathymetric and acoustic backscatter data were collected simultaneously in 10 survey blocks. All of these blocks were surveyed with 100% cover of backscatter imagery. These data were collected as source material for planned benthic habitat mapping. An earlier project had been completed to map the very-shallow subtidal and intertidal areas using optical methods. Interferometric sidescan backscatter data were acquired using a 468 kHz Bathyswath sonar system aboard the RV MacGinitie and RV Kelpfly. Both of these platforms were well suited to acquire data in the very shallow subtidal areas of the bay.
Original contact information:
Contact Name: Jen Eckerle
Contact Org: Ocean Protection Council (OPC)
Title: Deputy Director, Ocean Protection Council
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.
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):
- 2014-01-01 00:00:00 - Interferometric side-scan backscatter data collection. Prior to data collection, a series of planned survey lines were created using the survey navigation and planning software HYPACK (Hypack, Inc). An Applanix Position and Orientation System, Marine Vessel (POS MV 320 v4) system was used on the RV MacGinitie and a Wavemaster on the RV Kelpfly to provide position and attitude data during data collection and accounted for vessel motion such as heave, pitch, and roll (position accuracy 2m, pitch, roll and heading accuracy +/-0.02 degrees, heave accuracy +/-5% or 5cm). KGPS altitude data were used to account for tide cycle fluctuations and sound velocity profiles were collected with YSI Castaway CTDs. Data acquisition, post-processing, and final products derived from bathymetry data were handled by the Seafloor Mapping Lab at CSUMB and submitted to Fugro Pelagos for inclusion in the San Francisco Bay Habitat Mapping project. Delivered formats consist of gray-scale Geotiffs for each block.
- 2016-04-15 00:00:00 - Backscatter data processing. Raw (.sxr) format Bathyswath data were post-processed in Bathyswath Swath Processor 126.96.36.199 (ITER), during which they were corrected for sound velocity and installation calibration offsets, and IAPPK Smoothed Best Estimate of Trajectory (SBET) data were applied, producing processed (.sxp) Bathyswath files. Processing and mosaicking of Bathyswath backscatter sxp data were completed using SonarWiz v6.04.001 (Chesapeake Technology, Inc). Within SonarWiz, the backscatter intensity was corrected using Empirical Gain Normalization and the position of each acoustic sample was geometrically corrected for slant-range and georeferenced to UTM Zone 10N, NAD83 (2011). After gain normalization, the backscatter data were mosaicked into 0.5m and 1m resolution images and exported in GeoTiff format. More detailed information on data processing can be found in the project Data Acquisition and Processing Report NCNP0000-14-01192_DAPR.pdf
(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.3. Data access methods or services offered
- 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.
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
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.