-
Notifications
You must be signed in to change notification settings - Fork 3
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
cannot deal with SAGA installation from OSGEO4W #15
Comments
Thanks for this suggestion - I'll add the typical OSGEO4W path to SAGA's search path |
Careful with that though, as the SAGA binary won't be able to find many of the required dlls it needs to run, unless you also somehow set the environment variables correctly. Perhaps all you need to do is set PATH="%PATH%;%OSGEO4W_ROOT%\bin" for each saga_cmd session? That's where the supporting dlls seem to be, though can't guarantee that there aren't other files elsewhere. |
There is no support for the OSGEO4W version of SAGA - if you install the standalone version from the SAGA developers (binaries available for windows from sourceforge) then the |
Oh search_saga works....just need to leave of the () |
Either add the folder that contains the saga_cmd.exe, i.e., "C:/Program Files/saga-8.4.1_x64" to your user or system environment variable 'Path' and then Rsagacmd will know where it is located. Alternatively, you can do it manually every time you initiate the bridge to SAGA by:
|
Still relatively new to issue reporting, so apologies in advance if this post lacks details.
Unsure if this is related to what @ottadini mentioned as there isn't an error on dependencies. I really like the concept of this package and would really like to use it for a huge data pipeline as I am mostly familiar with working in R. |
Hello, thanks for yes. You are right that this is still the same issue. I always installed SAGA-GIS as a standalone software, probably because for a long time, the QGIS version was many versions behind. However, perhaps more people are using SAGA via OSGEO now. I'll try to look into it - the installation of SAGA through OSGEO is different and probably needs some environment variables setting first |
On Windows, a common means to install SAGA is through the OSGEO4W package installer, which is mostly an installer for QGIS. This package runs its binaries in a special environment managed through a bunch of batch files.
When saga_cmd.exe is run outside of the environment, it fails to find the required dependencies because PATH and other environment variables have not been correctly set. Is there any chance in Lytton that this env could be set through Rsagacmd's saga_env?
The workaround is to install a separate SAGA-GIS install.
The text was updated successfully, but these errors were encountered: