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

Compute catchments after resolving closed depressions #42

Open
benbovy opened this issue Nov 9, 2020 · 3 comments
Open

Compute catchments after resolving closed depressions #42

benbovy opened this issue Nov 9, 2020 · 3 comments

Comments

@benbovy
Copy link
Member

benbovy commented Nov 9, 2020

Currently catchment numbers are computed within the find_stack subroutine, which is called before LocalMinima in flow routing routines.

I think that in most cases we want catchment boundaries to rather correspond to the flow route paths obtained after resolving closed depressions.

@benbovy
Copy link
Member Author

benbovy commented Nov 9, 2020

Also, having integers (e.g., corresponding to the outlet node index) rather than random float numbers for the catchment ids would make more sense (and yield more stable results).

@benbovy
Copy link
Member Author

benbovy commented Nov 9, 2020

One benefit of using random numbers might be that one may easily distinguish adjacent catchments even when using continuous color maps, but arguably this should be addressed by using random, discrete color maps.

@LeoZijerveld
Copy link

Thanks for considering this. I would think that the benefits of using a meaningful number (i.e. corresponding to the outlet node) outweighs the plotting benefit you describe in your second comment.

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