Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:70316 | Published / External
This is an outdated version of the NOAA Data Management Plan template. InPort now supports a dedicated Data Management Plan Catalog Item type, which is up-to-date with the latest NOAA DMP template. The ability to generate Data Management Plans from Data Sets will be discontinued in a future release. Please see the Data Management Plan Help Guide to learn more.
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 goal of this research was to develop Gulf-wide cetacean and sea turtle spatial density models (SDMs) based on line-transect surveys conducted in the U.S. waters of the Gulf of Mexico. Surveys used to develop the SDMs for species occupying continental shelf and oceanic waters of the Gulf of Mexico were conducted during the Gulf of Mexico Marine Assessment Program for Protected Species (GoMMAPPS) project and comparable-prior-year surveys. Aerial survey data from seasonal surveys conducted during 2011/2012 and 2017/2018 (GoMMAPPS Surveys) were used to develop SDMs for cetacean and sea turtle species over the continental shelf. Data collected from vessel surveys, including the two-team surveys conducted during summer 2017, winter 2018, and summer/fall 2018 (GoMMAPPS Surveys) and 2003, 2004, and 2009 (that included only one survey team), were used to develop SDMs for cetaceans in oceanic waters. In addition, for Rice's whale, surveys conducted in 2018 and 2019 were also used in developing the SDMs specific for this species.
Habitat-based SDMs were developed using a generalized additive modeling (GAM) framework to determine the relationship between cetacean and sea turtle abundance and environmental variables. Samples for modeling were created by summarizing survey effort and environmental variables with a hexagon grid developed by the Environmental Protection Agency expanded to fit the entire Gulf of Mexico. The grid was created in a Lambert azimuthal equal area projection and the area of each hexagon is 40 km2. For all hexagons that contained survey effort segments, cetacean and sea turtle density was calculated using total number of animals observed, segment effort length and average sighting condition covariates in the hexagon, and the parameters estimated in distance sampling abundance models. A total of 19 SDMs were developed for individual or groups of species. For each modeled taxon, predictions were made for the period 2015-2019 on the hexagon grid, summarized into mean monthly densities for the 5-year period, and then resampled into traditional raster grids. Models were extrapolated beyond the U.S. waters of the Gulf of Mexico to provide insight into potential high density areas throughout the Gulf. However, extrapolations of this type should be interpreted with caution. This website contains the predictions as raster grids. The hexagon predictions are available as shapefiles in NCEI Accession 0256800. These models can be used by managers and federal agencies to assist with population assessments, environmental impact analyses, and conservation of these species.
As of October 2022, these are the latest available models for the Gulf of Mexico produced from NOAA Southeast Fisheries Science Center (SEFSC) surveys. The prior series of Gulf of Mexico models, produced by a collaboration between the Duke Marine Geospatial Ecology Lab (MGEL) and SEFSC and published as Roberts et al. 2016, are archived here. As of October 2022, SEFSC and MGEL consider the Roberts et al. 2016 models obsolete and recommend the GoMMAPPS models available here be used instead.
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):
(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.6. Type(s) of data
- 1.7. Data collection method(s)
- 5.1. Processing workflow of the data from collection or acquisition to making it publicly accessible
- 5.2. Quality control procedures employed
- 7.4. Approximate delay between data collection and dissemination
- 8.2. Data storage facility prior to being sent to an archive facility
- 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.
Download from provided links
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.