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
Not sure if anybody encountered this issue with the SAGA installation in QGIS:
After installing SAGA 9.2 using OSGeo4W in windows and activating the Processing SAGA NextGen Provider plugin in QGIS (3.32.2-Lima) the SAGA tools do not show up in the processing toolbox.
I have tried installing an earlier version of SAGA (v 7) and they do show up but I get an error upon executing (in this case Natural Neighbour), indicating I need SAGA >= 9.1.
I noticed that the folder name for the SAGA installation (under C:\Program Files\QGIS 3.32.2\apps) is 'saga' for the version 7, and 'saga9' for the version 9.2 installation.
Changing the name of the folder from 'saga9' to 'saga' and reinstalling the plugin makes the SAGA package visible in the Processing Toolbox.
The text was updated successfully, but these errors were encountered:
cpWWS
changed the title
SAGA NextGen Provider QGIS plugin -> SAGA not visible in processing toolbox
SAGA NextGen Provider QGIS plugin -> SAGA not visible in processing toolbox - RESOLVED
Jan 8, 2024
Not sure if anybody encountered this issue with the SAGA installation in QGIS:
After installing SAGA 9.2 using OSGeo4W in windows and activating the Processing SAGA NextGen Provider plugin in QGIS (3.32.2-Lima) the SAGA tools do not show up in the processing toolbox.
I have tried installing an earlier version of SAGA (v 7) and they do show up but I get an error upon executing (in this case Natural Neighbour), indicating I need SAGA >= 9.1.
I noticed that the folder name for the SAGA installation (under C:\Program Files\QGIS 3.32.2\apps) is 'saga' for the version 7, and 'saga9' for the version 9.2 installation.
Changing the name of the folder from 'saga9' to 'saga' and reinstalling the plugin makes the SAGA package visible in the Processing Toolbox.
The text was updated successfully, but these errors were encountered: