Data Management Plan
GUID: gov.noaa.nmfs.inport:39201 | 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 fish and benthic composition database is the result of a multifaceted effort described below.The intent of this work is five fold: 1) To spatially characterize and monitor the distribution, abundance, and size of both reef fishes and macro-invertebrates (conch, lobster, Diadema); 2) To relate this information to in-situ data collected on associated benthic composition parameters; 3) To use this information to establish the knowledge base necessary for enacting management decisions in a spatial setting; 4) To establish the efficacy of those management decisions; and 5) To work with the National Coral Reef Monitoring Program to develop data collection standards and easily implemented methodologies for transference to other agencies and to work toward standardizing data collection throughout the US states and territories. Toward this end, the Center for Coastal Monitoring and Assessment's Biogeography Branch (BB) has been conducting research in Puerto Rico and the US Virgin Islands since 2000 and 2001, respectively. It is critical, with recent changes in management at both locations (e.g. implementation of MPAs) as well as proposed changes (e.g. zoning to manage multiple human uses) that action is taken now to accurately describe and characterize the fish/macro-invertebrate populations in these areas. It is also important that BB work closely with the individuals responsible for recommending and implementing these management strategies. Recognizing this, BB has been collaborating with partners at the University of Puerto Rico, National Park Service, US Geological Survey and the Virgin Islands Department of Planning and Natural Resources.To quantify patterns of spatial distribution and make meaningful interpretations, we must first have knowledge of the underlying variables determining species distribution. The basis for this work therefore, is the nearshore benthic habitats maps (less than 100 ft depth) created by NOAA's Biogeography Program in 2001 and NOS' bathymetry models. Using ArcView GIS software, the digitized habitat maps are stratified to select sampling stations. Sites are randomly selected within these strata to ensure coverage of the entire study region and not just a particular reef or seagrass area. At each site, fish, macro-invertebrates, and benthic composition information is then quantified following standardized protocols. By relating the data collected in the field back to the habitat maps and bathymetric models, BB is able to model and map species level and community level information. These protocols are standardized throughout the US Caribbean to enable quantification and comparison of reef fish abundance and distribution trends between locations. Armed with the knowledge of where "hot spots" of species richness and diversity are likely to occur in the seascape, the BB is in a unique position to answer questions about the efficacy of marine zoning strategies (e.g. placement of no fishing, anchoring, or snorkeling locations), and what locations are most suitable for establishing MPAs. Knowledge of the current status of fish/macro-invertebrate communities coupled with longer term monitoring will enable evaluation of management efficacy, thus it is essential to future management actions.
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):
- 2001-07-01 00:00:00 - Site selection begins by stratifying NOAA's nearshore benthic habitat maps into predetermined habitat strata. Utilizing ArcGIS, sites are then randomly selected within strata throughout the region. Using a handheld GPS unit, the boat captain navigates to previously selected sites. A weighted buoy is dropped to mark any site where "live boating" is necessary. Once in the field, the boat captain navigates to previously selected sites using a handheld GPS unit. On-site, divers are deployed and maintain contact with each other throughout the entire census. One diver is 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 obtains a random compass heading for the transect prior to entering the water and records 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 is ascertained, the diver attaches a tape measure to the substrate and allows it to roll out for 25m while they are collecting data.Although the habitat should not be altered in any manner by lifting or moving structure, the observer should record fish seen in holes, under ledges and in the water column. To identify, enumerate, or locate new individuals, divers may move off the centerline of the transect as long as they stay within the 4m transect width and do not look back along area already covered. The diver is allowed to look forward toward the end of the transect for the distance remaining (i.e. if the diver is at meter 15, he can look 10 meters distant, but if he is at meter 23, he can only look 2 meters ahead).On-site, no attempt to avoid structural features within a habitat such as a sand patch or an anchor should be made as these features affect fish communities and are "real" features of the habitats. The only two instance where the transect should deviate from the designated path is to stay above 110 ft. The transect should take 15 minutes regardless of habitat type or number of animals present. This allows more mobile animals the opportunity to swim through the transect, and standardizes the samples collected to allow for comparisons.Data are 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, letters are added to the species name until a difference occurs. 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. (continued...)
- 2001-07-01 00:00:00 - (continued from above) Data Caveats: Over time, some changes were made to the stratified random site selection process as follows: 1) Habitat strata initially consisted of hard bottom, sand, and seagrass. Sand and seagrass strata were subsequently combined into one soft bottom strata at all three locations (Puerto Rico, St. Croix, and St. John). This action was taken after the February 2002 mission to Puerto Rico. 2) During the first mission to St. John samples were also stratified by depth (less than or equal to 40 ft or greater than 40 ft). (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.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.