Search Help Show/Hide Menu

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.

URL of higher-level DM Plan (if any) as submitted to DM Plan Repository:
Always left blank

1. General Description of Data to be Managed

1.1. Name of the Data, data collection Project, or data-producing Program:
NOAA NCCOS Assessment: Priority Areas Recommended for Shallow Coral Reef Management in the South Florida Coast from 2021-04-26 to 2021-05-21
1.2. Summary description of the data:

The National Oceanic and Atmospheric Administration (NOAA) National Centers for Coastal Ocean Science (NCCOS) developed a spatial framework, process, and online application (Buja and Christensen 2019) to identify mapping needs along the south Florida coast to support shallow coral reef management by NOAA's Coral Reef Conservation Program (CRCP). Eighteen participants from local federal, state, academic, and other institutions entered their priorities in an online participatory Geographic Information System (pGIS). Participants used virtual coins to denote their priorities in 10.4 km2 hexagonal grid cells overlaid on the study area. Grid cells with more coins were higher priorities than cells with fewer coins. Participants also reported why these locations were important, what data types were needed, and data collection methodologies using a pre-set list of options. Results were compiled, summarized, and mapped to identify high priority areas, reasons for those priorities, and information needs. Identifying these high priority areas provide a critical spatial framework for prioritizing mapping efforts in shallow coral reef ecosystems in south Florida.

Taken From: Item Identification | Abstract
Notes: Only a maximum of 4000 characters will be included.
1.3. Is this a one-time data collection, or an ongoing series of measurements?
One-time data collection
Taken From: Extents / Time Frames | Time Frame Type
Notes: Data collection is considered ongoing if a time frame of type "Continuous" exists.
1.4. Actual or planned temporal coverage of the data:
2021-04-26 to 2021-05-21
Taken From: Extents | Time Frame - Start, Time Frame - End
Notes: All time frames from all extent groups are included.
1.5. Actual or planned geographic coverage of the data:
W: -83.15, E: -79.96, N: 27.28, S: 24.37
Taken From: Extents | Geographic Area Bounds, Geographic Area Description
Notes: All geographic areas from all extent groups are included.
1.6. Type(s) of data:
(e.g., digital numeric data, imagery, photographs, video, audio, database, tabular data, etc.)
Map (digital)
1.7. Data collection method(s):
(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.)
No information found
1.8. If data are from a NOAA Observing System of Record, indicate name of system:
Always left blank due to field exemption
1.8.1. If data are from another observing system, please specify:
Always left blank due to field exemption

2. Point of Contact for this Data Management Plan (author or maintainer)

2.1. Name:
NCCOS Scientific Data Coordinator
Taken From: Support Roles (Metadata Contact) | Person
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.
2.2. Title:
Metadata Contact
Always listed as "Metadata Contact"
2.3. Affiliation or facility:
Taken From: Support Roles (Metadata Contact) | Organization
Notes: The name of the Organization of the most recent Support Role of type "Metadata Contact" is used. This field is required if applicable.
2.4. E-mail address:
NCCOS.data@noaa.gov
Notes: The email address is taken from the address listed for the Person assigned as the Metadata Contact in Support Roles.
2.5. Phone number:
No information found
Notes: The phone number is taken from the number listed for the Person assigned as the Metadata Contact in Support Roles. If the phone number is missing or incorrect, please contact your Librarian to update the Person record.

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.

3.1. Name:
NCCOS Scientific Data Coordinator
Taken From: Support Roles (Data Steward) | Person
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.
3.2. Position Title:
Data Steward
Always listed as "Data Steward"

4. Resources

Programs must identify resources within their own budget for managing the data they produce.

4.1. Have resources for management of these data been identified?
No
4.2. Approximate percentage of the budget for these data devoted to data management (specify percentage or "unknown"):
Unknown

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.

5.1. Processing workflow of the data from collection or acquisition to making it publicly accessible
(describe or provide URL of description):

Process Steps:

  • An advisory group was established which included individuals from NOAA CRCP and NOAA Fisheries. This advisory team customized the pGIS process specifically to meet the needs of CRCP and local coral reef manager priorities. In the online pGIS, the study area was divided into 1761 hexagonal grid cells 10.4 km2 in size. Existing relevant spatial datasets (e.g., bathymetry, Sanctuary Protection Areas, etc.) were provided as a digital atlas to help participants understand information and data gaps within the project area and to identify locations they wanted to prioritize for future data collections. The pGIS was used by 18 participants to convey their recommendations. Each participant was provided with 530 virtual coins to place into grid cells that they wished to prioritize. They were instructed to place more coins in grid cells that were higher priorities. A maximum of 53 coins could be placed into an individual grid cell by each respondent. Respondents also reported why these locations were important by selecting a minimum of one, and a maximum of two, management uses from the following list: endangered species management (e.g.,), habitat restoration, monitoring, coastal vulnerability planning, watershed management, fisheries management, consultations and permitting, emergency response, and spatial protection and management. Respondents also reported what data types were needed in priority cells. A minimum of one, to a maximum of two choices were selected from the following list: habitat map/characterization, shoreline characterization, ground truthing (e.g. photos and videos collected using ROVs or AUVs), elevation (e.g. bathymetry and topography), backscatter and intensity (e.g. surfaces used to delineate between hard and soft substrate), 2D map product (e.g. static images used to visualize bottom type, presence/absence of taxa), georectified photomosaics (e.g. 3D products created from structure for motion), and water column (e.g. for fish biomass detection). Respondents also reported what method of data collection was desired in each priority cell. Only one response was required and were selected from the following list: satellite, lidar, multibeam echosounder, split beam echosounder, side-scan sonar, photogrammetry, drop-camera, and uncrewed systems. Coin values were summarized and mapped to identify high priority areas, reasons for those priorities, and information needs. This ESRI shapefile contains the 10.4 km2 grid cells used in this prioritization and their associated coin values overall, as well as by management use, data product, and mapping methodology. Other summary values include the number of participants, number of participating groups, number of management uses, and number of data products. Also included is a ranking of each grid cell based on the total number of coins, management uses, and agencies allocating coins in the respective cell. For a complete description of the process and analysis see: Kraus et al., 2022. (Citation: Kraus, J., C. Buckel, B. Williams, C. Ames, F. Pagan, E. Towle, D. Dorfman. 2022. Agency Priorities for Mapping South Florida's Coral Reef Ecosystems. NOAA Technical Memorandum NOS NCCOS 304. Silver Spring, MD. https://doi.org/10.25923/qc9e-gt19)
5.1.1. If data at different stages of the workflow, or products derived from these data, are subject to a separate data management plan, provide reference to other plan:
Always left blank
5.2. Quality control procedures employed
(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.

6.1. Does metadata comply with EDMC Data Documentation directive?
No
Notes: All required DMP fields must be populated and valid to comply with the directive.
6.1.1. If metadata are non-existent or non-compliant, please explain:

Missing/invalid information:

  • 1.7. Data collection method(s)
Notes: Required DMP fields that are not populated or invalid are listed here.
6.2. Name of organization or facility providing metadata hosting:
NMFS Office of Science and Technology
Always listed as "NMFS Office of Science and Technology"
6.2.1. If service is needed for metadata hosting, please indicate:
Always left blank
6.3. URL of metadata folder or data catalog, if known:
Always listed as the URL to the InPort Data Set record
6.4. Process for producing and maintaining metadata
(describe or provide URL of description):
Metadata produced and maintained in accordance with the NOAA Data Documentation Procedural Directive: https://nosc.noaa.gov/EDMC/DAARWG/docs/EDMC_PD-Data_Documentation_v1.pdf
Always listed with the above statement

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.

7.1. Do these data comply with the Data Access directive?
Yes
7.1.1. If the data are not to be made available to the public at all, or with limitations, has a Waiver (Appendix A of Data Access directive) been filed?
No
7.1.2. If there are limitations to public data access, describe how data are protected from unauthorized access or disclosure:

None

7.2. Name of organization of facility providing data access:
Zenodo
Taken From: Support Roles (Distributor) | Organization
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.
7.2.1. If data hosting service is needed, please indicate:
Taken From: Data Management | If data hosting service is needed, please indicate
Notes: This field is required if a Distributor has not been specified.
7.2.2. URL of data access service, if known:
Taken From: Distribution Info | Download URL
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
7.3. Data access methods or services offered:

Download from website

7.4. Approximate delay between data collection and dissemination:
Six months
7.4.1. If delay is longer than latency of automated processing, indicate under what authority data access is delayed:

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.

8.1. Actual or planned long-term data archive location:
(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)
OTHER
8.1.1. If World Data Center or Other, specify:
Information for this field exists in the InPort item but will not be included, since the answer to 8.1 is not one of the relevant values.
Taken From: Data Management | Actual or planned long-term data archive location
Notes: This field is required if archive location is World Data Center or Other.
8.1.2. If To Be Determined, Unable to Archive or No Archiving Intended, explain:
Information for this field exists in the InPort item but will not be included, since the answer to 8.1 is not one of the relevant values.
Taken From: Data Management | If To Be Determined, Unable to Archive or No Archiving Intended, explain
Notes: This field is required if archive location is To Be Determined, Unable to Archive, or No Archiving Intended.
8.2. Data storage facility prior to being sent to an archive facility (if any):
National Centers for Coastal Ocean Science - Silver Spring, MD
Taken From: Physical Location | Organization, City, State, Location Description
Notes: Physical Location Organization, City and State are required, or a Location Description is required.
8.3. Approximate delay between data collection and submission to an archive facility:
Six months
8.4. How will the data be protected from accidental or malicious modification or deletion prior to receipt by the archive?
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.

Always left blank