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
Hello,
Thanks for all the work getting SAGA to work with QGIS! It sounds tike it can be tricky at times but there are a lot of SAGA algorithms I have trouble finding alternatives for in QGIS. Therefor I have a lot of them in my graphical models. In QGIS version 3.30 with SAGA having been removed this means that those models are now broken.
Would it be possible to make the Next Gen plugin algorithms automatically be used in their place?
It seems that maybe the only difference is that the call to the algorithm is sagang:algo rather than saga:algo. While this distinction made sense in pre 3.30 versions when there could be 2 versions of the SAGA plugin now it seems unnecessary.
I have been able to get my models to work by opening the .model3 file in a text editor and simply finding and replacing saga: with sagang: but I imagine many users will be less adventurous than me.
Thanks again.
The text was updated successfully, but these errors were encountered:
Hello,
Thanks for all the work getting SAGA to work with QGIS! It sounds tike it can be tricky at times but there are a lot of SAGA algorithms I have trouble finding alternatives for in QGIS. Therefor I have a lot of them in my graphical models. In QGIS version 3.30 with SAGA having been removed this means that those models are now broken.
Would it be possible to make the Next Gen plugin algorithms automatically be used in their place?
It seems that maybe the only difference is that the call to the algorithm is sagang:algo rather than saga:algo. While this distinction made sense in pre 3.30 versions when there could be 2 versions of the SAGA plugin now it seems unnecessary.
I have been able to get my models to work by opening the .model3 file in a text editor and simply finding and replacing saga: with sagang: but I imagine many users will be less adventurous than me.
Thanks again.
The text was updated successfully, but these errors were encountered: