1 / 37

FCRPS BiOp RME Data Management Pilot Project: Protocol Manager

FCRPS BiOp RME Data Management Pilot Project: Protocol Manager Mike Beaty, USBR PN-Region GIS & Remote Sensing Manager Northwest Environmental Data Network (NED) Executive Meeting Portland, OR December 7, 2005. I. Introduction. What is Protocol Manager? Relational Database Application

colette-garner
Download Presentation

FCRPS BiOp RME Data Management Pilot Project: Protocol Manager

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. FCRPS BiOp RME Data Management Pilot Project: Protocol Manager Mike Beaty, USBR PN-Region GIS & Remote Sensing Manager Northwest Environmental Data Network (NED) Executive Meeting Portland, OR December 7, 2005

  2. I. Introduction • What is Protocol Manager? • Relational Database Application • Dynamic Data Dictionary • Data Management Tool

  3. I. Introduction • B. What does Protocol Manager do? • Supports Biological Monitoring Programs and Projects • Fully Documents Data Elements and their Properties • Stores Protocol and Method Reference Documents

  4. I. Introduction • C. Why use Protocol Manager? • Foster Coordination and Collaboration • Improve Data Quality & Consistency • Enforce Data Standards • Provide Data Transparency • Facilitate Data Exchange and Usage • Compare, Improve, and Develop Protocols

  5. I. Introduction • D. What can NED do for Protocol Manager? • Support Pacific Northwest Aquatics Monitoring Partnership (PNAMP) Workgroup Functions • Data Analysis • Content Management • Protocol Standards

  6. I. Introduction • D. What can NED do for Protocol Manager? • Partner with USGS National Biological Information Infrastructure (NBII) Protocol Library and Monitoring Locator National Project • FormRegional Consortium Node • Leverage NBII Information Technology (IT) Resources • Utilize National and International Scientific Expertise

  7. II. Pilot Overview • Brief History • Research, Monitoring & Evaluation (RME) Data Management Work Plan, May 2003 • John Day Pilot, October 2003 • Data Analyst • Data Dictionary

  8. II. Pilot Overview • Brief History • 3. Coordinate with Wenatchee Regional Technical Team (RTT) Pilot • a. Upper Columbia Monitoring Strategy, Hillman, February 2004 • 4. Publish John Day (& U.Columbia) Data Dictionary, June 2004

  9. II. Pilot Overview • Brief History • 5. Host Database Design Process, June 2004 • a. ArcHydro Geospatial Data Model concepts and relationships applied to monitoring data • b. NPS FEAT Protocol Manager DB application replaces static data dictionary

  10. II. Pilot Overview • Brief History • 6. NOAAF Status Trend Monitoring (STM) Database initiated, September 2004 • a. Wenatchee 2004 physical and biological data loading completed, August 2005 • b. EMAP (ODEQ & Wenatchee) & PIBO 2004 loading in progress at NWFSC

  11. II. Pilot Overview • Brief History • 7. National Biological Monitoring Protocol Library and Monitoring Locator Project initiated, November 2005. • USGS NBII, National Park Service (NPS), & International Association of Fish and Wildlife Agencies (IAFWA) • USGS NBII: $500K & Technical Resources

  12. II. Pilot Overview • Brief History • 8. Current Status • Version 0.7 (.Net) • January 2006 release • NPS NIFC cost share through contractor • Documentation • Desktop Installations • Multiple versions require coordination • U.S. Government owns software code (public)

  13. II. Pilot Overview • Brief History • 9. Next Steps • Grow Protocol Manager Project Partnership • NED/PNAMP • USGS NBII • Develop Version 2.0 • Fully Functional Suite of Features • Plan Web Enabled Application • Centralized Relational Database Management System Host & Services Oriented Architecture

  14. II. Pilot Overview B. Resources (USBR PN-Region GIS) 1. October 2003 – December 2005 2. 2+ Staff Years utilized a. GIS/RS support: 33 % b. Data analysis: 67% i. Protocol Manager application dev: 5%

  15. II. Pilot Overview B. USBR Resources to Date 3. Contracting: $133K a. Data Analysis & Dictionary: $90K b. Protocol Manager Development: $43K 4. Total Cost: $325K a. Data Analysis: $250K b. Protocol Manager Development: $75K

  16. II. Pilot Overview • C. Key Findings • 1. Protocols are integral to monitoring data • a. Protocols = Metadata • b. Metadata = Data • c. Protocols = Data

  17. II. Pilot Overview • C. Key Findings • 2. Protocols are defined by their data management functions • a. Prescribe data elements • b. Describe methods and procedures • i. Collect field data • ii. Process summary values • iii. Validate values

  18. II. Pilot Overview C. Key Findings 3. “Data management systems must be designed from an end-to-end perspective (from data collection through data entry to database management, report generation and data sharing).” –Data Management for Field Collection, June 2004, Welches, OR Data Management Workshop

  19. Empirical Method Road Map Pose Scientific Questions Display results Collect and Analyze data Design Experiments and monitoring protocols AFG GIS Data needs Data Dictionary (monitoring indicators and protocols) GDB Needs Analysis III. Monitoring Data Processes A. Analytical Framework Empirical Method

  20. III. Monitoring Data Processes B. Field Data Processing Flow Subject Matter Expert Data Analyst Data Steward Prep for field Record data Update repository Analyze indicators Collect data Capture data Transfer data Field Worker Researcher Coordinator

  21. III. Monitoring Data Processes C. Interaction between Tabular Data and ArcHydro Geodatabase Raw Data Foreign Keys Generated Data ArcHydro Analysis Protocols Feature ID

  22. Field forms Field forms Output files Protocol Metadata Records Protocol Metadata Records Metadata Records (Protocols) Protocol Manager Monitoring Program Revise Protocols/ Methods Document Protocols/ Methods Evaluate Protocols/ Methods Protocol Data Collection Methods Data Validation Methods Data Summary Methods Data Analysis Status Trend Monitoring Database Field Forms Field Data Tables Repository Database

  23. IV. Protocol Manager Contents • Monitoring Programs & Protocols • Terms • Relationships of Terms • Protocol Manager • Comparing Protocols & Methods

  24. Monitoring Programs & Protocols Monitoring Program Protocols Specified EMAP EMAP (2001) PNAMP (w/ OWEB for Bank Stability) EMAP (2001) PIBO PIBO (2002) PIBO (2003) PIBO (2004) John Day AFG EMAP (2001) PIBO (‘02-’04) plus other protocolsin development or undocumented Upper Columbia Monitoring Strategy EMAP (2001) OPSW (1999) WFC (1998) WDFW (2000) WFPB (1983) Zaroban (2000) Schuett-Hames (1999) BURPTAC (1999) Hawkins et al. (1993) Overton et al. (2000) Platts et al. (1983) Strange (1996) Parmenter et al. (2003) Dolloff et al. (1996) Reynolds et al. (1996) Reeves et al. (2001) Van Deventer and Platts (1989) Borgerson et al. (1992) Anderson and Neumann (1996) Mosey and Murphy (1996) and more…

  25. Terms Subject Area Habitat / Physical Biological Classification Indicator Group Ecoregion Water Quality Adults Physiography Habitat Access Redds Geology Habitat Quality Parr / Juveniles Geomorphic Features Channel Condition Smolts Valley Characteristics Riparian Condition Macro Invertebrates Channel Characteristics Flows & Hydrology Watershed Condition

  26. Terms Subject Area Indicator Group Indicator Escapement/number Age structure Size Sex ratio Origin (hatchery or wild) Genetics Fecundity Biological Adults Protocol Method Attribute Redds Number Distribution Abundance/distribution Size parr Parr / Juveniles Number smolts Size smolts Genetics smolts Smolts Transport Composition Macro invertebrates

  27. Relationships of Terms Protocol Collection Method Indicator Attribute Name Attribute Name Indicator Group Attribute Name Indicator Summary Method Summary Value Indicator Collection Method Attribute Name

  28. Relationship of Terms EMAP, 2001 Dominate Substrate Dominant Substrate (EMAP, 2001) Fields from data collections Distance Left Bank DIST_LB Bankfull Depth BF_DEPTH Size Class Code SIZE_CLS Embeddedness EMBED Substrate Flag FLAG_SUB Transect TRANSECT Collection Attributes Transect Position TRANSDIR Comments COMMENTS Habitat Event ID HAB_EVENT Links to Site info: Site ID, Date, Stream ID, Visit No., Team ID, Location, etc. Large Wood Debris

  29. Protocol Manager Protocol Short Name: EMAP, 2003 Name:EMAP West Surface Water Wadeable Streams Contact:Phil Kaufman Doc Ref:Peck, et al., 2003, EMAP West Surface Water Wadeable Streams, EPA, Corvallis,OR - Library Protocols - EMAP Surface Waters – Wadeable Streams, 2003 Bank Measurements Large Woody Debris Bank Measurements + Procedure Procedure + Large Woody Debris Attribute Attribute Torrent Evidence + Procedure Procedure Attribute Attribute Procedure Procedure Attribute Attribute Procedure Procedure Attribute Attribute Methods Torrent Evidence Stream Flow - NBO Procedure Procedure Attribute Attribute Procedure Procedure Attribute Attribute Procedure Procedure Attribute Attribute Procedure Procedure Attribute Attribute

  30. Comparing Protocols & Methods Large Woody Debris EMAP, 2001 Merritt, 2004 Large Woody Debris (EMAP, 2001) Field Name Attribute Name Large Woody Debris (Merritt, 2004) Bankfull Diameter 0.1-0.3m Length 1.5-5m WETSDSL Field Name Attribute Name Bankfull Diameter 0.3-0.6cmLength 1.5-5m WETMDSL Bankfull Diameter 0.6-0.8mLength 1.5-5m WETLDSL Bankfull Diameter 10-15cm Length 1-3m 10_SHT Bankfull Diameter >0.8m Length 1.5-5m WETXDSL Bankfull Diameter 10-15cmLength >3-6m 10_MED Bankfull Diameter 0.1-0.3m Length 5-15m WETSDML Bankfull Diameter 10-15cmLength >6m 10_LON Bankfull Diameter 0.3-0.6cmLength 5-15m WETMDML Bankfull Diameter >15-30cm Length 1-3m 15_SHT Bankfull Diameter 0.6-0.8mLength 5-15m WETLDML Bankfull Diameter >15-30cmLength >3-6m 15_MED Bankfull Diameter >0.8m Length 5-15m WETXDML Bankfull Diameter >15-30cmLength >6m 15_LON Bankfull Diameter 0.1-0.3m Length >15m WETSDLL Bankfull Diameter >30cm Length 1-3m 30_SHT Bankfull Diameter 0.3-0.6cmLength >15m WETMDLL Bankfull Diameter >30cmLength >3-6m 30_MED Bankfull Diameter >30cmLength >6m 30_LON Bankfull Diameter 0.6-0.8mLength >15m WETLDLL Bankfull Diameter >0.8m Length >15m WETXDLL Above Bankfull Diameter 0.1-0.3m Length 1.5-5m DRYSDSL Above Bankfull Diameter 0.3-0.6cmLength 1.5-5m DRYMDSL Above Bankfull Diameter 0.6-0.8mLength 1.5-5m DRYLDSL BURPTAC, 1999 Above Bankfull Diameter >0.8m Length 1.5-5m DRYXDSL Above Bankfull Diameter 0.1-0.3m Length 5-15m DRYSDML Large Woody Debris (BURPTAC, 1999) Above Bankfull Diameter 0.3-0.6cmLength 5-15m DRYMDML Above Bankfull Diameter 0.6-0.8mLength 5-15m DRYLDML Above Bankfull Diameter >0.8m Length 5-15m DRYXDML Field Name Attribute Name Above Bankfull Diameter 0.1-0.3m Length >15m DRYSDLL Bankfull Diameter >10cm Length >1m LOD Above Bankfull Diameter 0.3-0.6cmLength >15m DRYMDLL Above Bankfull Diameter 0.6-0.8mLength >15m DRYLDLL Above Bankfull Diameter >0.8m Length >15m DRYXDLL

  31. IV. Protocol Manager Screens

More Related