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 predict reference conditions throughout the basin based on key reach-scale variables, which we empirically derived from a limited number of reference sites. Our typology predicts channel type based primarily on channel slope in confined reaches (floodplain width less than 4 times the bankful channel width) and on slope, drainage area, precipitation, and relative transport capacity in unconfined reaches (floodplain width greater than 4 times channel width). Channel types are cascade, step-pool, plane-bed, and pool-riffle in confined reaches, and braided, island-braided, meandering, and straight in unconfined reaches. Accuracy of channel type prediction in confined reaches is generally high compared to prediction accuracy in unconfined reaches. Lower accuracy in the unconfined reaches is largely due to vertical accuracy of the 10- m digital elevation model (DEM), which is insufficient to accurately estimate channel slope in low relief areas. However, lack of sediment supply information also limits our ability to predict floodplain channel type accurately. Therefore, we evaluate the effect of incorporating an estimate of relative transport capacity to help separate single thread channels (straight and meandering) from multi-thread channels (braided and island-braided) and increase prediction accuracy. Finally, we use existing ecoregion maps to show how channel type distributions vary among geologic regions, and suggest analysis options for mapping reference condition across large river basins.
We also attempted to develop a GIS data set that depicts pre-settlement riparian vegetation in the Columbia River Basin to guide stream restoration for endangered salmon. To do this, 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 included randomly sampled basin-wide data (drainage area 200,000 km2), as well as intensively reconstructed watershed-level data (3,000 km2). Our modeled output was too inaccurate to be useful.
GIS hydrography layer with multiple stream 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.)
Platform: Platform Not Applicable
Physical Collection / Fishing Gear: Not Applicable
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):
Multiple GIS processes to assign stream reach attributes; SVM model to classify stream reach types.
(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.
(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.
At this time, contact the Data Manager for information on obtaining access to this data set. In the near future, the NWFSC will strive to provide all non-sensitive data resources as a web service in order to meet the NOAA Data Access Policy Directive (https://nosc.noaa.gov/EDMC/PD.DA.php).
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.