Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bcfishpass.falls_upstr_anadromous_vw - include current CABD barrier status #541

Open
smnorris opened this issue Jul 10, 2024 · 2 comments
Open

Comments

@smnorris
Copy link
Owner

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.

@smnorris
Copy link
Owner Author

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.

@smnorris
Copy link
Owner Author

smnorris commented Jul 11, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant