1 / 29

Considerations for Regional Data Collection, Sharing and Exchange

White Paper:. Considerations for Regional Data Collection, Sharing and Exchange. Bruce Schmidt StreamNet Program Manager Pacific States Marine Fisheries Commission Presentation to Northwest Power and Conservation Council July14, 2009. www.streamnet.org.

corina
Download Presentation

Considerations for Regional Data Collection, Sharing and Exchange

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. White Paper: Considerations for Regional Data Collection, Sharing and Exchange Bruce Schmidt StreamNet Program Manager Pacific States Marine Fisheries Commission Presentation to Northwest Power and Conservation Council July14, 2009 www.streamnet.org

  2. There’s been talk of a regional data delivery system… 2002 Council Contract with SAIC 2000 BiOp RPA 198 So why isn’t there one? NOAA Guidance 2008 BiOp RPA 72 2006 Col. Basin Data Center CBCIS / NED Fish and Wildlife Program

  3. Many Programs Cross Jurisdictions Coordinated Monitoring, PNAMP ESA Recovery Planning Population Assessments (VSP) Need for Shared Data High Level Indicators, SOTR Inter-jurisdictional Management Co- management BiOp Compliance, Listing Decisions Legal: Remand, US v OR, PST, etc.

  4. Current data delivery status: • Existing database projects – Focused • StreamNet • Pacific Northwest Water Quality Data Exchange • Fish Passage Center • PTAGIS, RMIS, PACFIN, RECFIN • IBIS (wildlife data) • Proposals – Comprehensive, but not built • SAIC / CBCIS • 2000 BiOp RPA 198 • Columbia Basin Data Center • Efforts started – Not complete • NED / PNAMP (NED Portal, ISTM) • Columbia Basin Center of Knowledge (Canadian & US data)

  5. Existing database projects Output Tool SOTR Population models Population Assessments Subbasin planning Planning HLIs Management Public, etc. Regional Data Access DB Project ? ? ? ? db db db Data sources: Agencies / Tribes / Projects

  6. Smooth, organized v. current inefficient approach Database Project Agency Database Data sources: field offices, research projects, etc.

  7. Most efficient – start with existing projects: Output Tool Regional Data Access Pacific Northwest Water Quality Data Exchange Hab. db Fish db Water dd … db db db db db db db Multiple types of data from multiple sources

  8. Improve from there: Output Tool Regional Data Access dd db db … Water Habitat Habitat Fish db db db db db db db db db db db db Multiple types of data from multiple sources, standardized by data type

  9. The essential driver of a comprehensive data delivery system: Output Tool Regional Data Access Data flow can be automated dd db db … Water Habitat Habitat Fish db db db db db db db db db db db db Multiple types of data from multiple sources, standardized by data type

  10. Automation is the key! • Efficiency, Speed • Accuracy • Automatic data updates • Canned products • Translation to regional format • Essential for any database technology

  11. Continue to evolve: Output Tool Regional Data Access standards Standards Standards … Water Habitat Fish db db db db db db db db db db db db Multiple types of data from multiple sources, standardized by data type

  12. The ultimate endpoint?? … Water Habitat Fish db db db db db db db db db db db db Multiple types of data from multiple sources, standardized by data type

  13. How does the Data Sharing Guide help? • Organize discussions • Consider ALL components • Provide a blueprint • Identify needed support Assure that when a system is built, the data are there to deliver!

  14. The Data Sharing Guide addresses data flow from field to highest reporting need Non prescriptive Any data type Any agency Non-technical Primary focus is on infrastructure and processes to assure data accessibility

  15. Previous Proposals Vendors pitched their output tool… but not getting data to the tool

  16. What’s needed? 1. Uninterrupted data flow, source to output

  17. Data Flow Steps in data flow Regional data application GOAL Data interoperability Post data on the Web Post metadata on the Web Describe full data set(metadata) Regional standards Agency data QA / QC Agency database system Local use of data Describe the data (metadata) Quality Assurance / Quality Control Input to electronic form Field data creation (local office/project)

  18. Data Flow Steps in data flow Regional data application GOAL Data interoperability Post data on the Web Post metadata on the Web Describe full data set(metadata) Regional standards Agency data QA / QC Agency database system Local use of data Describe the data (metadata) Quality Assurance / Quality Control Input to electronic form Field data creation (local office/project)

  19. Data Flow Steps in data flow Regional data application GOAL Any missed step can prevent data flow! Data interoperability Post data on the Web Post metadata on the Web Significant effort to bridge the gaps! Describe full data set(metadata) Regional standards Agency data QA / QC Agency database system Local use of data Describe the data (metadata) Quality Assurance / Quality Control Input to electronic form Field data creation (local office/project)

  20. What’s needed? 1. Uninterrupted data flow, source to output 2. Data validated by agency

  21. What’s needed? 1. Uninterrupted data flow, source to output 2. Data validated by agency 3. Descriptive information (metadata)

  22. What’s needed? 1. Uninterrupted data flow, source to output 2. Data validated by agency 3. Descriptive information (metadata) 4. Data and metadata on the Internet

  23. What’s needed? 1. Uninterrupted data flow, source to output 2. Data validated by agency 3. Descriptive information (metadata) 4. Data and metadata on the Internet XML SQL Database Spreadsheet ASCII Word Processing PDF

  24. What’s needed? 1. Uninterrupted data flow, source to output 2. Data validated by agency 3. Descriptive information (metadata) 4. Data and metadata on the Internet 5. Data able to roll together Ideal: standard data collection, definition, codes Minimum: Data translate to a standard

  25. All of this is needed for seamless data delivery to ANY regional tool We can implement these steps before deciding on a data sharing tool

  26. Sampling Crews Sampling Agencies Negotiate key issues Metrics Methods Data disposition Contract language Support data automation Technical assistance System development Data tasks for agencies Post data & metadata Feed regional data tools Set priorities Policies to remove obstacles to data sharing Agency support Create the data Data Entry QA Describe the data Maintain the data Establish procedures Set standards, codes Agency data systems Post data / metadata Biological & data mgt. responsibilities Roles Database Projects Funding Entities Policy Makers Regional Data Users

  27. So, why don’t we have a regional data delivery system? • Infrastructure to automate data flow is not in place • Focus was on the data delivery tool • Didn’t address all roles

  28. We think the Data Sharing Guide will help to: • inform development of a regional data system • avoid skipping essential components • Get us started

  29. Questions? www.streamnet.org Funded by: Through: Fish and Wildlife Program Administered by:

More Related