-
Notifications
You must be signed in to change notification settings - Fork 19
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
Connecting to OTB #18
Comments
IIRC OTB was removed from QGIS3? |
@pat-s, it was removed initially, but as of QGIS 3.8, it was added back in. Currently my QGIS installation is located in "C:/OSGEO4W" folder, and the Orfeo toolbox is located in "C:\OTB-7.0.0-Win64." |
Thanks for the heads up! AFAIR we removed the support for OTB back then when it was removed. Should be an easy one to add it back in if nothing major has changed meanwhile. |
@pat-s cool. Would the OTB folder need to "live" in a specific place and be named a certain way to be detected by RQGIS/RQGIS3? |
This would only work if OTB is part of the processing toolbox (as it was in QGIS 2) but I think I remember that they wanted to add other 3rd party providers as plugins. If this is the case I would rather refrain from adding an additional dependency since (R)QGIS3 is already hard to maintain. Instead I would simply use the command line interface of OTB which you could easily use via library("RQGIS3")
set_env()
algs = find_algorithms(name_only = TRUE)
# check if otb is among the 3rd party providers
unique(gsub(":.*", "", algs)) |
@jannes-m OTB does show up in the Processing Toolbox after following the instructions here (see image). However, it does not show up as a 3rd party provider for RQGIS3. It may be related to my setup though because I cannot get RQGIS to find it either even though it appears in the processing toolbar when QGIS2 is open.
|
The paper on RQGIS mentions the ability to connect with the Orfeo Toolbox.
qgis_session_info()
shows connections to qgis, gdal grass6, grass7, and saga, but not OTB. Is connecting to OTB currently supported?The text was updated successfully, but these errors were encountered: