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

add discharge/channel width to crossings view #362

Closed
smnorris opened this issue Jul 18, 2023 · 7 comments
Closed

add discharge/channel width to crossings view #362

smnorris opened this issue Jul 18, 2023 · 7 comments

Comments

@smnorris
Copy link
Owner

From @NewGraphEnvironment

having width and mad in the crossing layer is really useful for our ability to screen sites when we are getting ready for the field and applying for permits

https://github.com/smnorris/bcfishpass/blob/dev/model/02_habitat_linear/sql/views/crossings_vw.sql

@NewGraphEnvironment
Copy link
Contributor

currently the data does not seem to be coming through into the streams layer either

@smnorris
Copy link
Owner Author

Definitely something off in the db:

hillcrestgeo=# select count(*) from bcfishpass.streams where channel_width is not null;
 count
-------
     0

@smnorris
Copy link
Owner Author

Might as well add all these:

upstream_area_ha
stream_order_parent
stream_order_max
map_upstream
channel_width
mad_m3s

@smnorris
Copy link
Owner Author

gradient might be good too but that can wait until a function for calculating it is added.
smnorris/fwapg#142

@NewGraphEnvironment
Copy link
Contributor

gradient is present in crossings and streams already. +1 Norris

@NewGraphEnvironment
Copy link
Contributor

hmm. or perhaps it is a carry over from the segments before they are broken?

@smnorris
Copy link
Owner Author

Good point, it is already in the crossings table.
But yes, it is taken from the adjacent stream segment as a shortcut in lieu of a gradient at point function.

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