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

FlowAccumulationFullWorkflow gracefully exits without writing all 3 results #401

Open
geotom opened this issue Apr 19, 2024 · 0 comments
Open

Comments

@geotom
Copy link

geotom commented Apr 19, 2024

Hi,

I think the problem we have in our current automated processing using the FlowAccumulationFullWorkflow tool is related to a large DEM input (20527x9187 Pixel) and limited memory available on a docker host (Processing runs within a Python container).

Our observation: The FlowAccumulationFullWorkflow step exists gracefully after line 631 (Whitebox Version 2.3.1)

(It still writes the DEM file but then no further output)

Input to that tool is the

  • mentioned DEM with 20527x9187 Pixel
  • output type (cells)
  • no log format
  • no clipping
  • no ESRI pointer

I found the following threads already touching the same topic of large DEMs

I wonder if there were changes made to Whitebox improving this situation. I also think it would be good to not fail gracefully in Whitebox to give a t least some feedback to the user why the tool exists before finishing.

I would be especially interested what solutions others found to address the problem with too large DEM inputs.
I also wonder if using a chunked approach works with this tool as it does both, flow direction and accumulation at the same moment.

In case our issue is really the lack of memory, then maybe a best approach (like chunking) could be directly integrated into Whitebox?

Thanks for looking into this!

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