Data Management Plan
GUID: gov.noaa.nmfs.inport:56775 | 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
This geodataabase provides an estimate to the spatial distribution of potential historical habitat for California Coastal Chinook Salmon, Central California Coast Coho Salmon, Northern California Steelhead and Central California Coast Steelhead.
Intrinsic potential measures the potential for development of favorable habitat characteristics as a function of the underlying geomorphic and hydrological attributes, as determined through a Digital Elevation Model (DEM) and mean annual precipitation grid. The model does not predict the actual distribution of "good'' habitat, but rather the potential for that habitat to occur, nor does the model predict abundance or productivity. Additionally, the model does not predict current conditions, but rather those patterns expected under pristine conditions as related through the input data. Thus, IP provides a tool for examining the historical distribution of habitat among and within watersheds, a proxy for population size and structure, and a useful template for examining the consequences of recent anthropogenic activity at landscape scales.
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:
- Calculating IP is a multi-step process that occurs both outside and inside a GIS. The first step creates a stream network from the Digital Elevation Model (DEM) and precipitation data that defines individual reaches and calculates values of gradient, valley floor width, and discharge for each. The second step creates suitability curves for these three variables based on life-history and habitat association of each species and life-stage. To construct a stream network, we implemented a model developed by Miller (2003 (Miller, D. 2003. Programs for DEM analysis)) that synthesizes grid-based data on topography derived from a 10 m resolution DEM and mean annual precipitation derived from the PRISM model (Daly et al., 1994). To run the model (Miller, 2003) (which is implemented outside of a GIS in a series of Fortran programs), we generated binary files of regional-scale elevation and precipitation grids. Beginning with these grids, we clipped the DEM and precipitation files to the watershed boundaries. The last input needed is a parameters file, and the only substantial change to the default inputs was to include regionally-specific equations relating precipitation to discharge. In the course of constructing the stream network, the model dynamically defines reaches on the order of 50-200 meters long, basing reach breaks on changes in gradient. In the resulting stream network, each reach is characterized by its gradient (averaged over the entire reach), valley width, and mean annual discharge (calculated at the downstream end of the reach).
(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?
- 5.2. Quality control procedures employed
- 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.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.
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.