You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hopefully I can get your valuable input in this matter.
We have a hydrological analysis project where we have to employ SAGA-GIS for many different reasons. However, the channel network in SAGA has a bottle neck somewhere and it takes extremely long time for some DEMs, especially larger DEMs.
I am trying to work around by creating the flow accumulation using SAGA and then use the flow accumulation from saga to extract channel networks using Whitebox tools. The results look similar with some differences as saga output seems to have some parallel streams.
Could you please comment on the reasons for that and is there a procedure to follow to create somehow identical results?
To clarify, the flow accumulation was created using MFD. However, I was wondering if channel networks can be extracted from an MFD-based flow accumulation.
Hi Dr. Lindsay.
Hopefully I can get your valuable input in this matter.
We have a hydrological analysis project where we have to employ SAGA-GIS for many different reasons. However, the channel network in SAGA has a bottle neck somewhere and it takes extremely long time for some DEMs, especially larger DEMs.
I am trying to work around by creating the flow accumulation using SAGA and then use the flow accumulation from saga to extract channel networks using Whitebox tools. The results look similar with some differences as saga output seems to have some parallel streams.
Could you please comment on the reasons for that and is there a procedure to follow to create somehow identical results?
To clarify, the flow accumulation was created using MFD. However, I was wondering if channel networks can be extracted from an MFD-based flow accumulation.
https://github.com/UoA-eResearch/saga-gis/blob/master/saga-gis/src/modules/terrain_analysis/ta_channels/ChannelNetwork.cpp
The text was updated successfully, but these errors were encountered: