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
Relatively little scientific research or monitoring has occurred in the Pacific
Northwest or elsewhere on the biological effectiveness of restoration efforts in heavily
urbanized watersheds. With the overarching goal of improving ecological health of its
urban creeks, the City of Seattle is testing innovative approaches to stormwater
management. We report here on four years of pre-project monitoring data collected over
2006-2009 for one such technique: Natural Drainage Systems (NDS).
This low-impact development approach is designed to modify the quantity,
quality, and timing of stormwater delivery to creeks and other water bodies. Seattle
Public Utilities has proposed a large-scale NDS within the Pipers Creek basin of North
Seattle that will treat approximately 60% of the Venema Creek sub-basin. The focus of
NOAAs research effort has been to develop appropriate monitoring parameters and
collect baseline data to evaluate the effectiveness of this major restoration action. Our
selection of study parameters was guided by specific project goals and includes measures
of physical habitat, contaminant loading, and in-stream biota.
We found that the biological health of Pipers Creek is poor compared to forested
streams in the Puget Sound region, but comparable to other urban streams in the City of
Seattle. The fish community is dominated by cutthroat trout Oncorhynchus clarki; scores
for the benthic index of biological integrity (B-IBI) range from very poor to poor; and
diatom assemblages are composed of a relatively high proportion of species tolerant of
high nutrient levels, organic enrichment, and sedimentation.
Despite poor stream health, densities of cutthroat trout in three of our five study
reaches were higher than many urban streams and approaching densities of cutthroat
found in natural streams. This may be due to the migratory nature of cutthroat trout, as
about half these fish were detected migrating from our study area to lower Piper Creek or
Results from heavy metal sampling were inconsistent. Zinc concentrations in
soil, black fly larvae, and mayfly nymphs collected from Pipers Creek study reaches were
significantly higher than for forested streams. We did not detect any differences in
copper concentrations between urban and non-urban streams.
We hypothesize that in-stream biological health will improve relative to current
baseline conditions following Venema NDS implementation, with treated reaches
beginning to more closely resemble forested conditions. Based on statistical power
analyses, we recommend that post-project monitoring focus on rate and taxonomic
composition metrics rather than simple density measurements. Given the City of
Seattles considerable investment of restoration funds towards NDSs, it is critical that
post-project data be collected so as to explicitly test these hypotheses.
Fish (density, biomass, movement, growth, diet), benthic invertebrates, periphyton.
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.
Pipers Creek: Creek in Northwest Seattle that drains a 1,835 acre watershed into Puget Sound.
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):
Fish abundance estimates were obtained using the standard triple-pass depletion method (Carle & Strub 1978; Murphy & Willis 1996).
(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 projects 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.
- 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.
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.