Data Management Plan
GUID: gov.noaa.nmfs.inport:65527 | 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
Spatial information on the arrangement of geological features, habitats and living marine resources on the seabed are often the foundation for decision-making in ecosystem management and ocean planning. Collecting information on the seabed depths and geomorphology is an expensive operation requiring airborne platforms like satellites, planes or drones, or small vessels to large research ships. Coordinating these data needs and data collection efforts will better leverage collective resources and meet shared goals. To help enable this coordination, in 2020 the National Oceanic and Atmospheric Administration (NOAA) National Centers for Coastal Ocean Science (NCCOS) developed a spatial framework, process, and online application to identify common data collection priorities for seafloor mapping, sampling, and visual surveys along shore and offshore of the Southeast United States (North Carolina, South Carolina, and Georgia).
Twenty-five representatives from federal and state agencies, academic institutions, and non-governmental conservation groups, designated seafloor mapping priorities using an online prioritization tool. Participants allocated virtual coins across 5 km x 5 km grid cells to denote their organization’s regions of seafloor mapping needs. Grid cells with more coins were higher priorities than cells with fewer coins. Participants also reported why these locations were important and what data types were needed. Results were analyzed and mapped using statistical techniques to identify significant relationships between priorities, reasons for those priorities and data needs. These data are the summarized results from this project and can also be viewed in an online web map (https://noaa.maps.arcgis.com/apps/webappviewer/index.html?id=04cdd2a68c4f427f893f2042f326dc80).
Several common areas of interest were identified in the spatially explicit analysis of the responses. Nearshore surfzone along Georgia, South Carolina, and North Carolina were highlighted by several agencies and organizations interested in sediment and sand resources as well as potential for rocky reef habitats. Inshore estuarine areas were highlighted by state agencies and conservation groups interested in monitoring change in managed areas like National Estuarine Reserves. On the outer continental shelf, areas near Blake Plateau off South Carolina and the continental shelf break off North Carolina were identified by federal agencies and conservation organizations as areas of sensitive habitats or historically significantly shipwrecks and maritime resources.
The seafloor mapping prioritization approach described in the Buckel et al. (2021) report associated with these data provides recommendations to organizations charged with mapping the seabed for navigation and commerce as well as resource assessments and management. Already, the priority areas identified in this exercise are being used by NOAA to focus planned seafloor mapping missions. Furthermore, the outcomes from this regional exercise contribute into a National Mapping Prioritization under the lead of NOAA to coordinate mapping activities across the entire US EEZ. Together, these quantitative seafloor mapping prioritization approaches will enable improved coordination and more efficient allocation of resources needed to conduct seafloor mapping providing data to support environmental stewardship, safe navigation and commerce.
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:
- There were four main steps in the Southeast US spatial prioritization process. The first step was to identify the technical advisory team, consisting of individuals from NOAA’s Integrated Ocean and Coastal Mapping Program, Office for Coast Survey, Office for Coastal Management, US Geological Survey, and University of South Florida. This advisory team invited 45 participants for the prioritization. Step two was to develop the spatial framework and an online application. To do this, the 365,709 square km region was divided into six subregions and 14,724 square 5x5 km grid cells. Existing relevant spatial datasets (e.g., bathymetry, protected area boundaries, etc.) were compiled to help participants understand information and data gaps and to identify areas they wanted to prioritize for future data collections. These spatial datasets were housed in the online application, which was developed using Esri’s Web AppBuilder. In step three, this online application was used by 25 participants to enter their priorities in each subregion of interest. Participants allocated virtual coins in the 5x5 km grid cells to denote their priorities. Grid cells with more coins were higher priorities than cells with fewer coins. Participants also reported why these locations were important and what data types were needed. Coin values were standardized across the subregions and used to identify spatial patterns across the Southeast US study region as a whole. The number of coins were standardized because each subregion had a different number of grid cells and participants. Standardized coin values were analyzed and mapped using statistical techniques, including hierarchical cluster analysis, to identify significant relationships between priorities, reasons for those priorities and data needs. This ESRI shapefile contains the 5x5 km grid cells used in this prioritization effort and associated the standardized coin values overall, as well as by justification, product, and organizational type. For a complete description of the process and analyses please see: Buckel et al. 2021. (Citation: Buckel, C.A., Taylor, J.C., Bollinger, M. 2021. Prioritizing Areas for Future Seafloor Mapping, Research, and Exploration for the Southeast U.S. Atlantic Coast. NOAA Technical Memorandum, NOS NCCOS 289. 71pp. doi:10.25923/qh2c-hs73)
(describe or provide URL of description):
For details of data quality control methods, see Lineage Sources. All users should independently analyze the datasets according to their own needs and standards to determine data usability.
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)
(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.
https://noaa.maps.arcgis.com/apps/webappviewer/index.html?id=04cdd2a68c4f427f893f2042f326dc80
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
Download from website
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
NCCOS IT Policy
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.