Data Management Plan
GUID: gov.noaa.nmfs.inport:38767 | 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
This dataset contains a unified backscatter GeoTiff with 1x1 meter cell size representing the 2014 Long Island Sound Benthic Habitat Priority Area of Interest off of Port Jefferson, NY. This backscatter dataset is a mosaic of surveys from the NOAA Ship S-222 Thomas Jefferson and its two inshore launch vessels, the NOAA Ship S-590 Rude, as well as surveys conducted by the University of Rhode Island and Stony Brook University in coordination with the NOAA Biogeography Branch and the Integrated OCean and Coastal Mapping Branch between 2001 and 2013. Backscatter data was collected using multibeam sonars and side scan sonars and mosaiced into a raster using ArcGIS 10.1 and Envi 5.0 software at the Biogeography Branch by a NOAA contractor.
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):
- 2012-05-01 00:00:00 - Data was collected aboard the NOAA Ship Thomas Jefferson between May 19th and July 30th, 2012. Multibeam data were acquired in .hsx format with three hull-mounted Reson 7125 MBES attached to the Thomas Jefferson and its two inshore hydro launch vessels, 3101 and 3102. Backscatter snippet collection was enabled and logged in .7k files. Line spacing for acquisition was three times the water depth, and data was retained out to 60 degrees from nadir. Heave, roll, pitch and heading correctors were collected using an Applanix POS/MV Model 320 V4 inertial measurement unit (IMU) and associated Trimble GPS antennas. Sound velocity profiles were acquired with a Seabird Electronics SeaCat SBE19P CTD profiler and processed using NOAA's Velocwin V8.85 software, then applied directly to the raw data. Positioning was obtained using Trimble Zephyr GPS receivers. Data was reduced to Mean Lower-Low Water (MLLW) using final approved tides from NOAA COOPS, based on National Water Level Observation Network (NWLON). | Source Produced: Raw Multibeam Data (Citation: Raw Multibeam Data)
- 2012-07-01 00:00:00 - Raw .hsx and .7k data were converted to .gsf and processed using Hypack MBmax software, resulting in a .gsf format dataset. SWMB data was cleaned of fliers, filtered and was reviewed by the Bigeography branch. | Source Produced: Raw Multibeam Data (Citation: Raw Multibeam Data)
- 2012-07-01 00:00:00 - The multibeam backscatter .gsf data were corrected for geometric and radiometric distortions using FMGT. In particular, the following corrections were applied where appropriate and when artifacts were evident: AVG Trend, TX Power and RX Gain, Area Correction, Spreading, Slant-Range and Extracted Beam Pattern. As no theoretical beam pattern for the Reson 7125 system exists, it was extracted for each vessel from a mapped area that was flat and had a relatively uniform (sandy) substrate. Individual lines were also truncated based on ping number and/or angle of incidence where appropriate. The final mosaics were exported as geotiffs in NAD 1983 zone 18N on a relative 0-255 linear color scale. The intensity results varied between each vessel as there were no ground validation samples that could be applied to acurately assess and calibrate the beam patterns. | Source Produced: Raw Multibeam Data (Citation: Raw Multibeam Data)
- 2012-07-01 00:00:00 - Side scan sonar surveys were conducted by the NOAA Ship Rude in 2001 and 2003 by the Atlantic Hydrographic Branch to map the shipping entrance into Bridgeport Harbor and detect hazards to navigation. This data was retrieved by the Biogeography Branch in summer of 2012 for the purpose of habitat classification, and was reprocessed using CARIS SIPS 7.1. The side scan data was then assessed for quality, and normalized to blend together with the Thomas Jefferson 2012 backscatter mosaic using ArcMap 10 and Envi 5.0 imagery enhancement software. | Source Produced: Raw Side Scan Sonar Data (Citation: Raw Side Scan Sonar Data)
- 2014-01-01 00:00:00 - Multibeam sonar surveys were conducted by the University of Rhode Island in coordination with the Biogeography Branch to collect more acoustic data within the Long Island Sound spatial prioritization area of interest. The URI provided the Biogeography Branch with three surveys from the Bridgeport Harbor. The surveys were then assessed for quality, normalized, and blended together with the Thomas Jefferson and Rude mosaic using ArcMap 10 and Envi 5.0 imagery enhancement software. | Source Produced: URI Bridgeport Side Scan Sonar Mosaics (Citation: URI Bridgeport Side Scan Sonar Mosaics)
- 2014-01-01 00:00:00 - Multibeam sonar surveys were conducted by the Stony Brook University School of Marine and Atmospheric Sciences in coordination with the State of New York and the Biogeography Branch to collect more acoustic data within the Long Island Sound spatial prioritization area of interest. Stony Brook also provided data to cover gaps from the NOAA Thomas Jefferson and Rude surveys, to make a complete backscatter mosaic. The surveys were then assessed for quality, normalized, and blended together with the Thomas Jefferson and Rude mosaic using ArcMap 10 and Envi 5.0 imagery enhancement software. | Source Produced: Raw Multibeam Data (Citation: Raw Multibeam Data)
(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)
- 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.2. Name of organization of facility providing data access
- 7.2.1. If data hosting service is needed, please indicate
- 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.
Please cite any use of this data.
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.