-
Notifications
You must be signed in to change notification settings - Fork 79
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
Expose subwatershed delineation #349
Comments
Rich ended up implementing subwatershed delineation in natcap/pygeoprocessing#128, natcap/pygeoprocessing#140 for a separate project for the freshwater team. I'll edit this to allow subwatershed delineation to be exposed in DelineateIt. |
Let's get to this if we can, but if not it's OK to push off to the next release. |
The last time I looked into this, I remember feeling some uncertainty around which tool to build subwatershed delineation into -- RouteDEM or DelineateIt. Thinking about it a bit more, I think this belongs in RouteDEM because:
|
This is a placeholder issue for subwatershed delineation originally referenced in #147 . I'll fill in the issue details once I've finished working through the details of what this means with Stacie.
The text was updated successfully, but these errors were encountered: