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 GeoTiff with 3x3 meter cell size representing the rugosity of several deep coral priority areas off the Atlantic Coast of Florida, derived from data collected in October 2010. NOAA's NOS/NCCOS/CCMA Biogeography Branch, in collaboration with NOAA vessel Ron Brown, as well as federal, university, and private sector partners, acquired multibeam bathymetry data off the Atlantic Coast of Florida from 10/26/2010 to 10/27/2010. Data was acquired with a hull-mounted Kongsberg EM 710 multibeam echosounder (70 kHz). It was processed by a NOAA contractor using CARIS HIPS software. Attitude and sound velocity correctors applied to the data. Verified tides were not applied to the data, leaving the depth values referenced to the ellipsoid. The imagery is projected in the UTM Zone 17 north, NAD83 datum. The processed CARIS data was used to generate a CARIS BASE surface based on swath angle. The CARIS Export option "BASE Surface to Image" was then used to create a GeoTiff of the priority areas. Rugosity was derived from this surface using NOAAs Benthic Terrain Modeler extension.
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):
- 2011-01-01 00:00:00 - For this project, data was collected aboard the Lost Coast Explorer from 10/26/2010 to 10/27/2010. Multibeam data were acquired in .all format with a hull-mounted Kongsberg EM 710 multibeam echosounder (70 kHz). Backscatter snippet collection was enabled. 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. | Source Produced: HDCS Processed Multibeam Data (Citation: Raw Multibeam Data)
- 2011-01-01 00:00:00 - Raw .all data were converted and processed using CARIS HIPS and Sips 7.0 software, resulting in a CARIS HDCS format dataset with all correctors applied. Attitude and SWMB data was cleaned of fliers, and SWMB data was reviewed in subset mode by a NOAA contractor. | Source Produced: HDCS Processed Multibeam Data (Citation: HDCS Processed Multibeam Data)
- 2011-01-01 00:00:00 - After being submitted to CCMA by the contractor, CARIS HIPS and Sips 7.0 was used to generate a CARIS BASE surface (similar to a DTM), based on weighted swath angle, from the processed HDCS data. Then CARIS export tool "BASE Surface to Image" was used to export a GeoTiff in NAD83 UTM zone 17N. | Source Produced: CARIS BASE Surface (Citation: HDCS Processed Multibeam Data)
- 2011-01-01 00:00:00 - An ESRI grid of source bathymetry was input into the Rugosity Builder Tool, a component of the ArcGIS Benthic Terrain Modeler (BTM). The BTM tool, a collection of ArcGIS terrain visualization tools developed by the Oregon State University (OSU) Department of Geosciences and the National Oceanic and Atmospheric Administration (NOAA) Coastal Services Center, calculated the rugosity of that bathymetric grid based on an algorithm developed by Jeff Jenness. A short summary of the process, quoted directly from the BTM's documentation, is as follows: "...rugosity derivation relies, in part, on a neighborhood analysis using a 3 grid cell by 3 grid cell neighborhood. An algorithm is passed through the Raster Map Algebra Operation object within Spatial Analyst that calculates the planar distance between the center point of the center cell and of each of the eight surrounding cells in the neighborhood. Next, using the Pythagorean Theorem, the surface distance is calculated for each planar distance using the difference in elevation between the cells. The result of this function is sixteen separate grid data sets with each cell value equal to this surface distance. The next step in the process is to calculate the area formed by three adjacent sides. The result is eight triangular surface area grids. These grid datasets are combined to obtain a surface area data set for the input bathymetric data set. The final step in the process is to create a data set that represents the ratio of surface area to planar area. This final data set represents rugosity for the study area." More information on the specific algorithms used, and contact points for questions, can be found in the BTM's documentation. Rugosity values near 1 represent flat smooth terrain, while higher values reflect increasing rugosity or terrain roughness. For rugosity grid interpretation, is recommended that the grid be reclassified according to standard deviation divisions. (Citation: LCE 2010 Bathymetry Geotiff)
(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.