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
Nutrient data were obtained from the Bio-ORACLE project and represent a long-term composite of data from 2000 to 2014. The map layer represents mean phosphate concentration (micromoles per liter) in surface waters of the U.S. Exclusive Economic Zone. Additional data available for download here provide six nutrient concentrations at three different depths within the water column (surface, mean depth, and maximum depth). Data have a common spatial resolution of 5 arc minutes and were assessed using a cross‐validation framework against in situ quality‐controlled data.
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):
- 2020-01-01 00:00:00 - 1) Data sets were derived from Bio‐ORACLE (ocean rasters for analysis of climate and environment) global data set. 2) Phosphate concentrations (micromoles per litre) are reported as six statistical measures including Lt. Max, Lt. Min, Min, Max, mean, and range over three depths (surface, mean, maximum). *Lt. (long-term) for average of the minimum and maximum records per year (e.g., temperature of the warmest month, on average). For the Marine Cadastre National Viewer, only the mean surface depth concentration is displayed as an example. 3) The Bio-ORACLE “Present data set” (2000 - 2014) was downloaded as Tiff Raster files (.tif) using Bio-ORACLE’s download manager. 4) This surface and benthic layers, for each of the three nutrients were then entered as a geodatabase into ArcGIS 10.7. Each .tif file was then clipped to the United States Exclusive Economic Zone (EEZ) using the marinecadastre.gov EEZ shapefile. 5) Data were then given a continuous color schema to avoid issues with color-blind audiences (e.g. red to green) over the range of data values for each statistical measure. The lighter shade of a color represents areas with lower phosphate concentrations relative to the darker shades where higher phosphate values occur. 6) Surface, mean, and maximum concentration values were QA/QC’ed for any elements lacking in the data description or attributes, illogical values, spatial accuracy, and overall consistency across the data within the US EEZ. 7) Each data layer was then projected to WGS 1984 Web Mercator Auxiliary Sphere (EPSG: 3857) projection 8) Permission to use this data was received from the authors prior to use in marinecadastre.gov. Comparisons were also made to the ESRI Ecological Marine Unit (EMU) nutrient data where spatial overlap occurred, to ensure likeness in data over geographical space. 9) The Bio-ORACLE data are modeled and have been statistically downscaled and therefore have inherit biases associated with these types of analyses occur. However, methodology implemented here create a more spatially resolved data set for nutrients in US waters than any other known by the authors. However, these data lack high temporal resolution. 10) While the Bio-Oracle Nutrient data may have higher horizontal spatial resolution, the Esri EMU data has higher number of depth levels (102 depth levels). There are pros and cons of both data sets and users are recommended to compare the data sets before deciding which is best for their own analyses. 11) The pros to the ESRI EMU nutrient data is data are present over 102 depth levels, and can be used to statistically differentiate different portions of the water column. The cons lie its course spatial resolution, no temporal component, and no nearshore values (as of 2020). Sayre et al. (2019) (https://www.tandfonline.com/doi/full/10.1080/1755876X.2018.1529714 ) are working towards coastal EMUs, which will increase the spatial coverage of the EMU data. It is recommended that users view the pros and cons of applying the various data sets (Bio-ORACLE vs. EMU) to their own analyses. More information about methodology used can be found in these resources: Assis, J., Tyberghein, L., Bosh, S., Verbruggen, H., Serrão, E. A., & De Clerck, O. (2017). Bio-ORACLE v2.0: Extending marine data layers for bioclimatic modelling. Global Ecology and Biogeography. Tyberghein L, Verbruggen H, Pauly K, Troupin C, Mineur F, De Clerck O (2012) Bio-ORACLE: A global environmental dataset for marine species distribution modelling. Global Ecology and Biogeography, 21, 272–281.
(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.3. Is this a one-time data collection, or an ongoing series of measurements?
- 1.4. Actual or planned temporal coverage of the data
- 1.7. Data collection method(s)
- 2.1. Point of Contact Name
- 2.4. Point of Contact Email
- 3.1. Responsible Party for Data Management
- 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.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.
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.