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

Populate upstream habitat gain, species code, and priority in priorities sheet #43

Open
Mateo9569 opened this issue Jan 20, 2023 · 4 comments

Comments

@Mateo9569
Copy link
Collaborator

@NewGraphEnvironment as per this comment on a bulkley issue regarding this. Is the same still true for this report? Am I replacing co_rearing_km with st_rearing_km?

@NewGraphEnvironment
Copy link
Owner

ya - let's do it. 7.5% is a reasonable place for our cutoff. 5% seems perhaps on the up tight side.

@Mateo9569
Copy link
Collaborator Author

I ran script section for habitat gain with new bcfishpass object and st_rearing_km and there are 3 sites that have 0m of upstream habitat length modelled. These are 198215, 8530, and 198236. Am I going to estimate these three using GIS?

@NewGraphEnvironment
Copy link
Owner

Depends if they can be tied to the modelling with this or not (8530 definitely can). If they can, then we will ammend the csv, PR and I will run again later once bcfishpass is building from scratch again (should be soon). Otherwise we can use GIS but we should try to align the estimate with what the model will output

@Mateo9569
Copy link
Collaborator Author

They are all tied to modelled crossings yes. So I'm adding all 3 of those sites to Simon's csv? Maybe I'm not fully understanding this. Do these 3 sites have 0m of upstream habitat modelled because steelhead have never been observed in the streams? Or have these streams just not been modelled with bcfishpass yet?

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

2 participants