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

Implement "Chimaps in a few lines of code" #73

Open
1 of 8 tasks
wkearn opened this issue Nov 6, 2024 · 0 comments
Open
1 of 8 tasks

Implement "Chimaps in a few lines of code" #73

wkearn opened this issue Nov 6, 2024 · 0 comments

Comments

@wkearn
Copy link
Contributor

wkearn commented Nov 6, 2024

This series of articles on the blog presents how to construct chimaps with TopoToolbox v2. I think turning these blog posts into Jupyter notebooks would be a useful way to organize some of our next steps with pytopotoolbox as well as giving some more structure to the documentation.

I will go through these posts more closely to identify more concrete tasks and open the appropriate issues. I think we can do many of the steps already, namely creating FlowObjects and StreamObjects. There are a few preprocessing steps that I don't think we have Python solutions to yet, and we can also take this opportunity to improve the visualization interface of pytopotoolbox. The chi transform itself or at least the integration along the stream network can probably be implemented in libtopotoolbox.

Update:

I more or less copy-and-pasted the blog posts into a Jupyter Notebook. I will push that up as a draft PR so we can look at it, but these are the things that I think we need to implement to be able to run the entire example:

wkearn added a commit to wkearn/pytopotoolbox that referenced this issue Nov 6, 2024
This directly copies most of the content from
https://topotoolbox.wordpress.com/2017/08/18/chimaps-in-a-few-lines-of-code-final/
with some modifications for the functionality that currently exists in
pytopotoolbox. This is not expected to work completely (see TopoToolbox#73 for
details).

It does depend on the Mendocino data, which should be added to
the DEMs repository if we want to use it.
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

1 participant