Search Help Show/Hide Menu

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:
NOAA Point Shapefile- Benthic Habitat Classifications from Minibat ROV Underwater Video, US Virgin Islands, Project NF-04-06, 2004, UTM 20N WGS84
1.2. Summary description of the data:

This dataset contains a point shapefile with benthic habitat classifications of vertical relief, geomorphological structure, substrate, and biological cover for selected points along various Remotely Operated Vehicle (ROV) underwater video transects in the US Virgin Islands.NOAA's NOS/NCCOS/CCMA Biogeography Team, in collaboration with NOAA vessel Nancy Foster and territory, federal, and private sector partners, acquired Remotely Operated Vehicle (ROV) underwater video data in the US Virgin Islands from 2/18/04 to 3/5/04. Data was acquired with a towed Minibat and georeferenced and visually interpreted by CCMA employees. Data is in UTM zone 20, datum WGS84.

Taken From: Item Identification | Abstract
Notes: Only a maximum of 4000 characters will be included.
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.
1.4. Actual or planned temporal coverage of the data:
2004-02-18 to 2004-03-05
Taken From: Extents | Time Frame - Start, Time Frame - End
Notes: All time frames from all extent groups are included.
1.5. Actual or planned geographic coverage of the data:
W: -64.830345, E: -64.562601, N: 18.290169, S: 17.796352
Taken From: Extents | Geographic Area Bounds, Geographic Area Description
Notes: All geographic areas from all extent groups are included.
1.6. Type(s) of data:
(e.g., digital numeric data, imagery, photographs, video, audio, database, tabular data, etc.)
vector digital data
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:
NCCOS Scientific Data Coordinator
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.
2.2. Title:
Metadata Contact
Always listed as "Metadata Contact"
2.3. Affiliation or facility:
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.
2.4. E-mail address:
NCCOS.data@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:
No information found
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:
NCCOS Scientific Data Coordinator
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.
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:

  • 2004-03-01 00:00:00 - Video Acquisition:The NOAA ship Nancy Foster was used to collect underwater video of benthic habitats from February 22 to March 1, 2004. The seven transects collected traversed 30.5 km and provided approximately 10 hrs of video. Video was acquired using a downward pointing camera mounted on a towed underwater platform called the MiniBat. The MiniBat provided limited control of depth and was used to position the camera as close to 2 m off the bottom as possible. The camera height off the bottom ranged from 0.5 m to 10 m and averaged approximately 3 m. This range of differences translated into a range of camera field of views from approximately 0.5 m X 0.5 m to 10 m X 10 m with an average of 3 m X 3 m. Ship velocity and correspondingly camera velocity was approximately 1 m/s. All video was taken during daylight hours to guarantee sufficient ambient light levels for visual interpretation. Video was recorded onto MiniDV tapes as it was acquired. Time and GPS position as recorded by Trimble GPS units were fed into the video using a Horita GPT-50 real time video titler. Time, ship velocity, tow cable length, and shipboard GPS coordinates were recorded along with the video. This data was used to estimate the MiniBats geographic position using a layback method. The layback method adjusts the ship's GPS position by the distance of the Minibat's relative position to the ship which is estimated by the tow cable length. Similar studies using this layback method have estimated positional accuracy is within 50 m (CRED, 2001).
  • 2004-12-01 00:00:00 - Benthic Habitat InterpretationThe benthic habitat was characterized by visual interpretation of video images by two video interpreters. Video on the MiniDV tapes were displayed on a television using a digital video camera or miniDV cassette recorder. A transparent sheet demarcated with a 10 X 10 grid was fitted to the television screen to facilitate percent cover estimates. The video was paused every 10 seconds and the image was interpreted for three components of benthic habitat: structure, substrate and biological cover. Structure referred to the broad-scale habitat class within the entire field of view. Based on previous benthic habitat work in the area (Kendall et al., 2001) the structure designation was chosen from either 1) colonized pavement, 2) colonized pavement with sand channels, 3) sand, 4) scattered coral and rock in sand, or 5) other (with description). Substrate described the visible abiotic components of the benthic habitat. The four substrate classes, considered mutually exclusive and exhaustive were 1) consolidated material, 2) sand, 3) rubble (particles ~ 2-10 cm) and 4) cobble (particles < 10 cm). Substrate was measured to the nearest percent of the visible bottom. An estimate of rugosity was approximated by the vertical range of substrate in the field of view and was classified as either high (> 0.3 m) or low (<0.3 m).Biological cover referred to the biotic component of the seafloor and was divided among five mutually-exclusive categories differentiated by their size and shape. These were 1) sponge (Phylum Porifera), 2) soft coral (Subclass Octocorallia and subclass Ceriantipatharia), 3) hard coral (Subclass Hexacorallia), and 4) fleshy algae and 5) algae veneer. The sum of all cover categories provided an estimate of total colonization. If a biological cover component could not be unquestionably identified as one of the five cover categories it was only added to the total colonization estimate.Interpretation results were inputed into an Excel spreadsheet, with a single record for each sample point. These sample points and their associated benthic habitat attributes were then imported in ESRI ArcMap and converted into point shapefiles.
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)
  • 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.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:

Please cite any use of this data.

7.2. Name of organization of facility providing data access:
No information found
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.
7.2.1. If data hosting service is needed, please indicate:
No information found
Taken From: Data Management | If data hosting service is needed, please indicate
Notes: This field is required if a Distributor has not been specified.
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.
7.3. Data access methods or services offered:

Click on link from project page to NCEI archive and download zip file.;

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.
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.
8.2. Data storage facility prior to being sent to an archive facility (if any):
National Centers for Coastal Ocean Science - Silver Spring, MD
Taken From: Physical Location | Organization, City, State, Location Description
Notes: Physical Location Organization, City and State are required, or a Location Description is required.
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