2012-05-04

Salmon Population CrossWalk Focus Group

CRITFC, telecom/webinar

Attendees: Matt Denniston (Sitka Technologies), Henry Franzoni (CRITFC), Denise Kelsey (CRITFC), Anne Marshall (WDFW), Jacque Schei (USGS/PNAMP), Kathryn Thomas (USGS/PNAMP/notetaker), Van Hare (StreamNet)

AGENDA:

Introduction and Review Goals

Project – reminder of project purpose

Focus Group – assistance provided by the Focus Group

Application – simple pop/unit tool, review tool, attribute data

Future – possible uses and tools

Progress/or Not

PNAMP Webpage for Project

Report – handout with quick summary

Demo of Application

Tool Discussion

Suggested Changes Discussion

Our Questions for Features

Introduction & review goals

Purpose: In last 3 years we have been hearing that needed to know more about population names, CRITFC had started with some populations and had goal to develop more comprehensive information for the Basin, hoping that each managing entity will be able to compare reporting units and see how similar and different, want the tool to be the starting place for discussions on boundaries and names, regardless it will allow managers to understand population units to understand how their field collections correspond with others

Focus group

  • CRITFC looking for help design tool and suggest changes
  • Produce list of pop/unit attribute data that should accompany each pop/unit, what is the minimum to include?, agencies can add attributes to product later if they want
  • Want some help on converting spatial data from current form into Watershed Boundary Dataset (WBD) 6th level HUC subwatersheds

Application

  • Simple tool – will use a geographic basemap with HUCs overlain; each HUC is attributed with the different population management units name and attributes occurring in that HUC
  • Select a HUC of interest and receive a list of pop/units using the HUC or select a population and HUCs will display to show the boundary/area of the population.

Futures suggestions

  • Link application to StreamNet based on the selected HUC, species, pop/unit name to query their database for population data
  • The goal is to have any population of salmon or steelhead that anyone is managing
  • Collect salmon and steelhead monitoring locations and display by HUC and overlay this with pop/units
  • Would like to see this expanded to PNW

Discussion:

  • map services could be used to provide tabular data stored with StreamNet,
  • CBfish has a map that displays6th level HUC boundaries to see name of HUC and code – allows selection of ESU using TRT names (steelhead, Chinook) built on old HUC; Interior CRB is converting to 6th level HUC, has not found anyone in Lower Columbia converting; could be some leveraging with CBfish using web services;
  • there some discrepancies between HUC boundaries and TRT population boundaries, because the TRT data is in the old HUC boundaries and most of the basin is moving to a National Watershed Boundary Dataset.
  • How do users determine different population names? Each HUC will be attributed with all population names that occur in HUC, will not split a HUC if TRT has split but will describe in attribute fields for that HUC

PROGRESS OR NOT

  • PNAMP web page for project
  • Status report
  • Right now only have subbasin planning and hatchery review data in geodatabase
  • Working with ODFW & WDFW to convert spatial data and attribute some HUC
  • Have not heard from IDFG (Butterfield, Brown)
  • TRT
  • Interior data underconversion, Snake available
  • Lower Columbia no response on data
  • Still trying to contact tribes – a lot of tribal management units includedin subbasin planning data, which is already in the geodatabase.

Demo

  • Front page with Fish Icons
  • Basemap streaming in from ESRI – comes in rather grainy, could also use USGS topo
  • HSRG data – natural, integrated, segregated
  • Subbasin planning names with CBFWA Review – same as CBFWA names as used in DET
  • Source data from HSRG reports
  • Cannot distinguish between 1 pop with 2 names or 2 pops – currently have to look at attributes to differentiate, Once have all populations in then can look at whether 1 pop with 2 names
  • Want to develop review tool for comments and updates
  • will send data out for review and load info into crosswalk, when done in Nov all populations will be included, would like biologists review by November, hopefully annual updates including agreements on population names of use
  • If agencies agree that a population described in many different ways with names and attributes have the same boundaries and these agencies decide to give one name to the population, the data in the geodatabase can be switched from showing several name and the agency to one name and a list of agencies that agree on the population.

Discussion

  • SaSI – WDFW’s Salmonid Stock Inventory ( population names are in process of being aligned with recovery populations names for ESA-listed populations, want to report data on recovery units, data will be compiled into a recovery unit although biologistsmay still collect data for former SaSI units as well
  • query of online mapping may be best done by having user go to river then subcategories
  • currently bull trout and west coast cutthroat are not being considered but could be added in time
  • high priority data display is for ‘select HUC of interest and receive a list of pop/units using the HUC’, focus on data and way published, related table that could be grabbed and relate to their published service
  • core message is the crosswalk, would love to call service programmatically to exhibit multiple populations at once
  • hold workshops with biologist to vet data
  • Boundaries are administrative/management and may not equate to distribution (may be more HUCs in the boundary then presently have fish), if we have info for historic distribution can be included as attribute
  • CRITFC listed a few know needs and fixes for display and small webpage or map toolissues. Among the list, back buttons, size of pop-up windows, color label matching, direct links to data in the pop-ups, report page sizing, addition of other layers such as ESUs, etc.