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

Lake Sockeye spawning - upstream of lake, max distance? #459

Open
2 tasks
smnorris opened this issue Feb 20, 2024 · 0 comments
Open
2 tasks

Lake Sockeye spawning - upstream of lake, max distance? #459

smnorris opened this issue Feb 20, 2024 · 0 comments

Comments

@smnorris
Copy link
Owner

smnorris commented Feb 20, 2024

Currently, for sockeye spawning upstream of rearing likes, the model in main is:

Suitable upstream segments were modeled as spawning habitat if they were directly connected to (rearing) lakes or to modeled Sockeye Salmon spawning segments (i.e., directly upstream of another spawning segment).

This constraint was mistake/mis-interpretion in the initial creation of the model.

As a preliminary fix for PSF, In branch psf, there is no constraint at all - any suitable stream upstream of a rearing lake is included as spawning habitat.

CWF (Nick L) provides this guidance for something in between:

So, I think using the maximum known upstream distance (so far it is 4.7 km) is appropriate for all Sockeye Salmon streams. This might mean that extra spawning habitat is identified in areas where fish rarely push past more suitable spawning habitat closer to spawning lakes, but even then there is some potential value in managing or reconnecting the additional habitat (e.g., it may be used in high abundance years). I am equally open to using a lower value if an analysis of maximum distances reveals outliers, but most observations are within X km of rearing lakes.

todo:

  • confirm max known upstream distance
  • make change in sockeye model
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