-
Notifications
You must be signed in to change notification settings - Fork 1
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
pysheds
to whitebox
#266
pysheds
to whitebox
#266
Conversation
In
|
@cheginit I will stick with Did you want to rereview my calling of the wrapper? I know it seems extravagant to have the |
I packaged the wrapper that I wrote for whitebox as a python library called pywbt that doesn't have any dep, even |
@cheginit amazing thanks - all now good |
Description
Need because
pysheds
is GNU.pysheds
whitebox
tempfile
error according to suggestion inwhitebox
occasional error #268(note to self - on the cluster, current setup seems to weirdly work whenwhitebox
isverbose
but not when its not... no clue what that's about - for now probably just make it always verbose).Fixes #263
Fixes #212
Fixes #137
Fixes #141
Fixes #138
Fixes #268
whitebox
seems super powerful and the most sensible way to accommodate many changes to catchment delineation. In the long run it seems thatpyflwdir
could be removed and everything done onwhitebox
- one thing at a time though. (Adding an issue to discusswhitebox
#267 )