Data Management Plan
GUID: gov.noaa.nmfs.inport:20561 | 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
Basin-wide analysis of potential to improve tributary habitats in the Columbia River basin through restoration of habitat-forming processes.
Identification of geomorphological target conditions for river restoration is typically based on locally measured reference conditions, yet few reference sites remain in much of the 630,000 km2 Columbia River Basin, USA. Therefore, we predicted reference conditions throughout the basin based on key reach-scale variables, which we empirically derived from a limited number of reference sites. We developed a GIS data set that depicts pre-settlement riparian vegetation in the Columbia River Basin to guide stream restoration for endangered salmon. However, the modeled riparian species composition was quite inaccurate, so we are not distributing these model results.
Methods: We first created a data layer of historic riparian vegetation information from survey notes that were taken mid-19th to early 20th century during the Public Land Survey System (PLSS) conducted by General Land Office (GLO). Our reconstructed riparian vegetation data include randomly sampled basin-wide data (drainage area 200,000 km2), as well as intensively reconstructed watershed-level data (3,000 km2). Second, based on the reconstructed riparian vegetation points, which are arrayed along a 1-mile (1600 m) grid, we are developing statistical models to estimate potential historic riparian vegetation types (conifer, hardwood, willow-shrub, grass, sage) as well as the probability of occurrence of individual species at stream reach level (~ 200 m) in the basin. We examined environmental variables, such as mean annual precipitation, average minimum and maximum temperature, channel gradient, channel bankful width, floodplain width, and fine sediment supply potential, against five vegetation types and found that precipitation and temperature discriminate vegetation groups. We also developed vegetation response curves against each variable, using kernel density estimates to describe the probability of each vegetation type occurring across the range of each environmental variable.
GIS hydrography layer with riparian attributes.
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.
Columbia River Basin: The Columbia River Basin is the fourth largest watershed in the United States - it includes area in 7 states (Oregon, Washington, Idaho, Montana, Nevada, Wyoming, and Utah) and one Canadian province.
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):
Lineage Statement:
Multiple GIS processes to assign riparian specie composition
(describe or provide URL of description):
These data were collected and processed in accordance with established protocols and best practices under the direction of the project’s Principal Investigator. Contact the dataset Data Manager in section 3 for full QA/QC methodology.
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.
NA
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://www.webapps.nwfsc.noaa.gov/server/rest/services/Hosted/Columbia_GLO_riparian/FeatureServer
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
Model results were low accuracy, so we are not distributing these model results
No Delay
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
The Northwest Fisheries Science Center facilitates backup and recovery of all data and IT components which are managed by IT Operations through the capture of static (point-in-time) backup data to physical media. Once data is captured to physical media (every 1-3 days), a duplicate is made and routinely (weekly) transported to an offsite archive facility where it is maintained throughout the data's applicable life-cycle.
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.