You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently 406 records with >= 5 salmon observations upstream, but only 37 of these are tagged as barriers - it would be better if this was available directly in the view.
Less important but also potentially useful would be including all species (particularly BT) in this summary, just for easier identification of CABD location / FWA stream matching issues.
The text was updated successfully, but these errors were encountered:
Also include the user barrier status, otherwise things get really confusing - Elk Falls (in Campbell River) has 10 upstream salmon observations since 1990 but is pinned as a barrier by user_barriers_definite_control.
Identifying records where the barrier status in the fix table overrides salmon observations upstream is straightforward with a query to the db, it could be added to the view... but usage is rather opaque - it is not possible to tell which records these are directly in the fix table.
Before completing this view, reworking of the falls/CABD fix tables would be helpful (and a cleanup is required anyway) - this can wait on fix to #530
Currently 406 records with >= 5 salmon observations upstream, but only 37 of these are tagged as barriers - it would be better if this was available directly in the view.
Less important but also potentially useful would be including all species (particularly
BT
) in this summary, just for easier identification of CABD location / FWA stream matching issues.The text was updated successfully, but these errors were encountered: