Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:56126 | 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
We used a well-established Generalized Additive Modeling framework to develop cetacean SDMs based on 20 California Cooperative Oceanic Fisheries Investigations (CalCOFI) shipboard surveys conducted during winter and spring between 2005 and 2015. Models were fit for short-beaked common dolphin (Delphinus delphis delphis), Dall’s porpoise (Phocoenoides dalli), and humpback whale (Megaptera novaeangliae). Model performance was evaluated based on a variety of established metrics, including the percentage of explained deviance, ratios of observed to predicted density, and visual inspection of predicted and observed distributions. Final models were used to produce spatial grids of average species density and spatially-explicit measures of uncertainty. Results provide the first fine scale (10 km) density predictions for these species during the cool seasons and reveal distribution patterns that are markedly different from summer/fall, thus providing novel insights into species ecology and quantitative data for the seasonal assessment of potential anthropogenic impacts.
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.
W: -125.055684, E: -117.122588, N: 38.065782, S: 30.070776
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:
- 2015-05-01 00:00:00 - The NMSDD compliant grid layer, which required each cell to be 10² km, was produced using the ArcGIS Fishnet tool. The grid data layer was generated using the World Plate Carree projection so that each grid cell would line up with the points generated from any HBDM output. The gridded data layer was created to cover the entire study area. All fields required for the NMSDD were added.
- 2015-05-15 00:00:00 - The following fields were populated using ArcGIS ModelBuilder with inputs provided by subject matter experts (SME): SPECIES, SPECIES_2,STUDY, STRATUM, MODEL_TYPE, SEASON, AREA_SQKM, ABUNDANCE. The AREA_SQKM field was populated by calculating square kilometers using the ArcGIS geometry calculator.Areas were calculated using the World Cylindrical Equal Area projection. The ABUNDANCE field was populated by running a field calculation that multiplied the DENSITY and AREA_SQKM fields.
- 2015-05-20 00:00:00 - Habitat-based Density Model Data: Original data in csv format produced from habitat-based density models (HBDM) were converted to a point shapefile using ArcGIS. A spatial join between the points generated from the HBDM csv output and the NMSDD grid data was created in ArcGIS in order to populate the appropriate NMSDD attribute fieds with the HBDM information. The following fields were calculated from the HBDM information: DENSITY, UNCERTAINTY, AREA_SQKM2, ABUNDANCE2. The UNCERTAINTY field represents the coefficient of variation (CV) value. The AREA_SQKM2 and ABUNDANCE2 fields are for Navy internal purposes only and are used to compare the HBDM and NMSDD grid areas since there could be slight variations due to spatial projections.
- 2015-05-31 00:00:00 - Data Layer was projected to the WGS84 Global Coordinate System (GCS). Data geometry was validated by running ArcGIS topology checks and the check/repair geometry tool. Attribute values were validated by running a python script to ensure all fields were correctly populated.
- 2019-04-16 00:00:00 - For distributing data to the public via the CetSound project, we performed the following: - Made a single shapefile for each species, instead of separate shapefiles for winter and spring - Calculated STUDY column to "Becker, et al. 2017" - Calculated SEASON column to "Winter/Spring". While this does not meet Navy standards (Fall, Winter, Spring, Summer), we felt it was important to note the extended season that the data apply to because we are using a single shapefile. - Removed Navy-specific fields AREA_SQKM2 and ABUNDANCE2 - Removed Shape_Area and Shape_Leng fields - Updated metadata with input from SME
(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.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.
Moss Landing, CA
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.