Data Management Plan
GUID: gov.noaa.nmfs.inport:39310 | 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
The work developed baseline information on fish and benthic communities within the Flower Garden Banks National Marine Sanctuary (FGBNMS). Surveys employed diving, technical diving, ROV, and hydroacoustics technologies for a comprehensive assessment of the fish and benthic habitat communities of the East and West Bank. The FGBNMS represents the northernmost tropical western Atlantic coral reef on the continental shelf and support the most highly developed offshore hard bank community in the region. The complexity of habitats supports a diverse assemblage of organisms including approximately 250 species of fish, 23 species of coral, and 80 species of algae in addition to large sponge communities. Understanding and monitoring these resources is critical to both sanctuary inventory and management activities. During the course of the sanctuary's management plan review process, the impact of fishing was identified as a priority issue, and the concept of a research only area was suggested. The purpose of this project was to provide baseline data for all benthic habitats and communities.
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-12-01 00:00:00 - A stratified random sampling design was employed to sample fish on the coral cap communities of the East and West Flower Garden Banks. The survey domain at each coral cap was designated as all areas shallower than 110 feet below sea level. Fine-scale (0.5 m) bathymetric data provided by the Flower Garden Banks National Marine Sanctuary was used to ascertain depths and slope. Survey sites were then randomly positioned in each stratum in ArcGIS (ESRI, 2006). A sample frame consisting of mutually-exclusive 50m X 50m grid cells was produced and overlaid on each coral cap to exhaustively cover all diveable areas (i.e less than 110ft). Each grid cell was considered a sample unit and units were divided into six strata. Strata were defined using benthic habitat, location and depth. High (dominated by plate and head corals) and low relief (dominated by Madracis and rubble) coral categories were determined using a benthic habitat map generated by visual interpretation of multibeam data. Units were divided into deep (>105 ft) and shallow (less than 105ft) groups based on the location of sampling unit centroids on multibeam bathymetric models. Location and high relief coral categories were divided by depth, low relief coral was not. Data were collected within 100m2 transects. Transects radiated from the centroid of each sample unit at a random bearing. Once in the field, the boat captain navigated to previously selected sites using a handheld GPS unit. On-site, divers were deployed and maintained contact with each other throughout the entire census. One diver was responsible for collecting data on the fish communities utilizing the belt-transect visual census technique over an area of 100m2 (25m length X 4m width). The belt-transect diver obtained a random compass heading for the transect prior to entering the water and recorded the compass bearing (0-360o) on the data sheet. Visibility at each site must be sufficient to allow for identification of fish at a minimum of 2m away. Once reasonable visibility was ascertained, the diver attached a tape measure to the substrate and allowed it to roll out for 25m while they collected data. As a rule, the habitat was not altered in any manner by lifting or moving structure, however, the observer did record fish seen in holes, under ledges and in the water column. To identify, enumerate, or locate new individuals, divers moved off the centerline of the transect as long as they stayed within the 4m transect width and did not look back along area already covered. The diver was allowed to look forward toward the end of the transect for the distance remaining (i.e. if the diver was at meter 15, he can look 10 meters distant, but if he was at meter 23, he could only look 2 meters ahead). On-site, no attempt to avoid structural features within a habitat such as a sand patch or an anchor was made as these features affect fish communities and are "real" features of the habitats. The only instance where the transect deviated from the designated path was to stay above 110 ft. Transect lasted 15 minutes regardless of habitat type or number of animals present. This allowed more mobile animals the opportunity to swim through the transect, and standardized the samples collected to allow for comparisons. (continued)
- 2011-12-01 00:00:00 - (continued from above) Data were collected on the following: 1) Logistic information - diver name, dive buddy, date, time of survey, site code, transect bearing. 2) Taxa presence - as the tape roles out at a relatively constant speed, the diver records all fish species to the lowest taxonomic level possible that come within 2m of either side of the transect. To decrease the total time spent writing, four letter codes are used that consist of the first two letters of the genus name followed by the first two letters of the species name. In the rare case that two species have the same four-letter code, alternate four-letter codes are used to distinguish between the species. These alternate codes contain the first two letters of the genus, the first letter of the species and then the first letter in the species name that differs from the other code. If the fish can only be identified to the family or genus level then this is all that is recorded. If the fish cannot be identified to the family level then no entry is necessary. 3) Abundance and size - the number of individuals per species is tallied in 5cm size class increments up to 35cm using visual estimation of fork length. If an individual is greater than 35cm, then an estimate of the actual fork length is recorded. 4) Photos - individuals too difficult to identify or unique in some manner may be photographed for later clarification. (end continuation)
(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.6. Type(s) of data
- 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?
(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.
Please contact the Flower Garden Banks NMSP Science Coordinator for additional information on data access (FGBScience.Coordinator@noaa.gov);
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.