Data Management Plan
GUID: gov.noaa.nmfs.inport:54258 | 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 data set contains sensitive biological resource data for marine, estuarine, diadromous, freshwater, and federally and/or state endangered, threatened, or rare fish species in Northwest Peninsular Florida. Vector polygons in this data set represent fish distributions, spawning and nursery areas, concentration areas, migration areas, and harvest areas. Species-specific abundance, seasonality, status, life history, and source information are stored in associated data tables (described below) designed to be used in conjunction with this spatial data layer. This data set is a portion of the ESI data for Northwest Peninsular Florida. As a whole, the ESI data characterize the marine and coastal environments and wildlife by their sensitivity to spilled oil, and include information for three main components: shoreline habitats, sensitive biological resources, and human-use resources.
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.
4. Resources
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):
Process Steps:
- 2016-12-01 00:00:00 - Emphasis was put on mapping the juvenile life stage for fish due to their comparatively high risk to an oiling event compared with adults. Adults, larvae, eggs, and spawning areas were mapped for a handful of species with high importance to the region based on a review with biological experts from the Florida Fish and Wildlife Conservation Commission (FWC) Fish and Wildlife Research Institute (FWRI) and the University of Florida. The primary source for juvenile presence and seasonality information in nearshore and inshore habitats was the Fisheries Independent Monitoring (FIM) Stratified Random Sampling data set from the FWRI. The FIM Stratified Random Sampling data set is a conglomeration of juvenile fish surveys and includes species names, survey locations, and a catch per unit effort (CPUE), among other data. Juvenile fish species mapped based on this data set received qualitative concentration values (CONC) based on the results of a K-means test. This K-means test was run to create 3 distinct density categories (HIGH, MED, and LOW) for each species based on CPUE. These concentration categories were calculated separately for Tampa Bay, for surveys where CPUE = number of animals per 100 square meters, and for surveys where CPUE = number of animals per set. The primary source for juvenile presence and seasonality in Tampa Bay was a derived data set based on the FIM Stratified Random Sampling data set. To come up with this derived data set, statistical and spatial analyses were run on raw FIM data to determine patterns of community structure and to develop a spatial model for the changes in nekton community throughout the year in Tampa Bay (Santi and Whaley, 2017). Data mapped using sources other than the FIM Stratified Random Sampling data set were given concentration values based on various input sources. Ranging from lowest to highest, these values are: Rare, Low, Present, Common, Abundant, and Very High or Highly Abundant. Other sources of information came from NOAA, the Gulf States Marine Fisheries Commission, the United States Geological Survey, the University of Florida, SEDAR (Southeast Data, Assessment, and Review), the International Union for Conservation of Nature (IUCN) Red List of Threatened Species, fishbase.org, and Mote Marine Laboratory. Critical habitat, essential fish habitat, and some FIM survey data came in the form of vector digital data and were clipped to the AOI. SEAMAP trawl, reef fish, and plankton survey data as well as some FIM survey data, commercial fisheries landings data from the FWRI, and hogfish survey data from the FWRI were received as spreadsheets with geographic coordinates that were later transformed into a GIS format. Information received as written reports and/or written information on websites (eg. IUCN Red List and fishbase.org) was translated to a GIS format with the aid of bathymetric contours from NOAA and consultation with biological experts. See the Lineage section for additional information on the type of source data for this data layer. The ESI, biology, and human-use data are compiled into the standard ESI digital data format. A second set of interviews with participating resource experts are conducted to review the compiled data. If necessary, edits to the FISH data layer are made based on the recommendations of the resource experts and digital data are created.
(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.
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?
(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.
None
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.
Data can be accessed by downloading the zipped ArcGIS geodatabase from the Download URL (see Distribution Information). Questions can be directed to the ESI Program Manager (Point Of Contact).
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.