otb issueshttps://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues2023-11-28T09:00:57Zhttps://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2311Refactoring task for the modularization of OTB2023-11-28T09:00:57ZThibaut ROMAINRefactoring task for the modularization of OTB**New modular architecture**
![otb_9_archi](/uploads/219354ce907b36807efaf3a0e0dfac18/otb_9_archi.png)
**1. Simplify CMake options**
In OTB there is almost 40 cmake options when you call ccmake which is a bit confusing for the average...**New modular architecture**
![otb_9_archi](/uploads/219354ce907b36807efaf3a0e0dfac18/otb_9_archi.png)
**1. Simplify CMake options**
In OTB there is almost 40 cmake options when you call ccmake which is a bit confusing for the average user wanting to compile OTB for his project. A lot of option are about the dependencies of OTB, where you can mix system and superbuild dependencies, which can lead to eratic behaviors which the OTB team can't give a lot of time to debug.
- [x] Propose a simplified approach for the dependencies:
The user who wants to compile OTB will be given two options:
- Use all dependencies from the Superbuild which will be built before OTB
- Use all system dependencies, which will be listed in the cookbook for a one line simple installation
This approach permits to hide all USE_SYSTEM_DEPNAME flags which complicates the cmake process. The user will have to enable or disable the only flag `USE_SUPERBUILD_DEPS` which will activate/deactivate the flags USE_SYSTEM_XXX in the background
- [x] Review of all other cmake variables to determine which ones are mandatory, and which ones can be hidden/removed
- [x] Create OTB_BUILD_CORE, OTB_BUILD_LEARNING ... cmake targets to compile thematic modules
Instead of the current OTBGroup_XXX which is not thematic and can lead to misunderstandings for beginners, we propose to add options which will correspond to the future modules of OTB, which will be packaged with the same name.
**2. New source organisation**
The main idea is to reorganize the modules of OTB in coherent groups, which implies a reorganization of the source code.
Here is an example of a module (Core for example):
- Applications
- Functional_Tests : which will call one or a bunch of applications related to real treatments in production chains
- SubModule1... (For example IO)
- src
- include
- unit_tests
- SubModule2... (For example Common)
- src
- include
- unit_tests
- ...
With this organization, we have the applications related to this module, the tests calling those applications, and a list of submodules which contains filters/C++ classes grouped by theme. These filters are unit tested in each sub module.
To do this reorganization, the following guideline has been done:
- [x] Create a folder for each module (Learning, Stereo, SAR...)
- [x] Move src, include, tests and the related CMakeLists of each submodule to its related module
- [x] Connect CMAKE variables (OTB_BUILD_CORE etc) to the right module folder
- [x] Adapt the declared dependencies of each module in the CMakeLists
- [x] Reactivate the unit tests on the CI for each module
- [x] Reactivate the app tests ont the CI for each module
- [x] Package OTB Core and OTB Full with the current packaging method
- [x] Test the compilation of remote modules with otb core
- [x] move "to be deprecated" apps to a miscellaneous folder
**3. Test refactoring**
All the tests (TU + app) for each modules have been reactivated on the CI. Now it is important to see if all those tests are relevant.
- **Unit test + app tests**
A Lot of baselines and input has been added since the beginning of the project, but some tests have been deprecated. In order to make this refactoring relevant, we will follow this guideline :
- [x] Make a listing of currently used baselines/input files, to see what file is not needed anymore, and if some files are not too old to be relevant.
- [ ] See if there are any non relevant tests
- [ ] Determine which largeInput tests can be transformed into functional tests
- **Use cases for validation (fonctional tests)**
The current LargeInput tests are kind of outdated and not really relevant of real production chains.
The idea is to replace thoses tests with functional tests, containint one or a sequence of applications, which is the case in production chains.
We have to determine real use cases with production teams, to create those functional tests. They will be present in each thematic module.
While the unit test + app tests will be run on the CI, the new functional tests will be run on the HAL cluster
**4. New packaging**
The current packaging of OTB contains everything, all dependencies, all apps... Makeself is currently used to deliver a .run.
At the moment, there is an OTB Core package, and a full OTB package produced by the CI.
The idea is to use CPack which is integrated with cmake, to deliver packages of each OTB modules, that can install along the otb-core package.
For example, a user needs to do some machine learning with OTB, he should then install otb-core package which contains the core modules / apps of OTB and its dependencies, and then he will install otb-ML module, which will be installed in the same install tree.
This modularity permits each user to customize its installation, instead of having a big package while using 50% of it.9.0.0https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2287Missing feature in DEMHandler2023-11-28T09:00:59ZLuc HermitteMissing feature in DEMHandler**TL;DR:** Provide `DEMHandler::GetGeoidHeight()`
## Rationale
`DEMHandler::GetHeightAboveEllipsoid()` has a convoluted behaviour. Depending on what is visible it would return:
- either geoid offset + DEM offset
- or DEM offset -- alm...**TL;DR:** Provide `DEMHandler::GetGeoidHeight()`
## Rationale
`DEMHandler::GetHeightAboveEllipsoid()` has a convoluted behaviour. Depending on what is visible it would return:
- either geoid offset + DEM offset
- or DEM offset -- almost equivalent to `GetHeightAboveMSL()`
- or default height above ellipsoid
- or geoid offset
Sometimes we only need the geoid offset (it's the case of DiapOTB SARDEMProjection application).
We could make sure to have no DEM information configured, but then the application can not be chained into memory with another application that will need DEM information. Indeed `DEMHandler` is still mostly used as a global object (a singleton) (which is another known issue #2093), which makes it impossible to simultaneously have and not have DEM information.
Even if we don't chain such applications _in-memory_, we must not forget to clear DEM configuration if the applications are used through Python API and not isolated in different _subprocesses_. Indeed the memory would be shared between the various application object, and as such all the singletons...
As a workaround, SARDEMprojection detects `$OTB_GEOID_FILE` value to directly read geoid data from that file, and it falls back to `DEMHandler::GetHeightAboveEllipsoid()` if it's not possible. It's much too easy to use incorrectly.
That's why it'd be better to provide a dedicated `DEMHandler::GetGeoidHeight()` that would simplify applications such as SARDEMProjection, and that would avoid troubles regarding whether we configure DEM information or not in the global `DEMHandler`.https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2306BundleToPerfectSensor needs default mode for some PHR images2023-11-28T09:00:59ZYannick TANGUYBundleToPerfectSensor needs default mode for some PHR images### Description
The application BundleToPerfectSensor needs to be in _default mode_ when running on orthorectified PHR images.
If we don't set this mode, there are two messages :
- a warning : OTB does not recognize sensor -> use defa...### Description
The application BundleToPerfectSensor needs to be in _default mode_ when running on orthorectified PHR images.
If we don't set this mode, there are two messages :
- a warning : OTB does not recognize sensor -> use default mode
- the extents of PAN and XS images do not match
When we add the default mode, it works fine.
It had been reproduced with PHR extracts from OTB Workshop dataset, and also from official PHR products (using either the DIMAP or the orthorectified PAN and XS images from the DIMAP).
### Steps to reproduce
These commands were run to obtain a pansharpened orthorectified image : the second way to obtain it needs the default mode to be set.
```
#!/bin/sh
VER=$1
mkdir -p Workshop_Results/Tests_OTB_${VER}/step5_BDS_sensor
mkdir -p Workshop_Results/Tests_OTB_${VER}/step6_ortho
mkdir -p Workshop_Results/Tests_OTB_${VER}/step7_ortho
mkdir -p Workshop_Results/Tests_OTB_${VER}/step8_BDS_ortho
otbcli_BundleToPerfectSensor -inp WorkshopData/preprocessing/phr_pan_osr_mipy.tif -inxs WorkshopData/preprocessi
ng/phr_xs_osr_mipy.tif -out Workshop_Results/Tests_OTB_${VER}/step5_BDS_sensor/PXS_sensor.tif
otbcli_OrthoRectification -io.in Workshop_Results/Tests_OTB_${VER}/step5_BDS_sensor/PXS_sensor.tif -io.out Works
hop_Results/Tests_OTB_${VER}/step6_ortho/PXS_ortho_1.tif
otbcli_OrthoRectification -io.in WorkshopData/preprocessing/phr_pan_osr_mipy.tif -io.out Workshop_Results/Tests_
OTB_${VER}/step7_ortho/pan_ortho.tif
otbcli_OrthoRectification -io.in WorkshopData/preprocessing/phr_xs_osr_mipy.tif -io.out Workshop_Results/Tests_O
TB_${VER}/step7_ortho/xs_ortho.tif
otbcli_BundleToPerfectSensor -inp Workshop_Results/Tests_OTB_${VER}/step7_ortho/pan_ortho.tif -inxs Workshop_Res
ults/Tests_OTB_${VER}/step7_ortho/xs_ortho.tif -out Workshop_Results/Tests_OTB_${VER}/step8_BDS_ortho/PXS_ortho_
default_mode.tif -mode default
```
### Configuration information
OTB 8.1rc29.0.0https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2317GridBasedResampling y origin weird behaviour2023-11-28T09:00:59ZJonathan GuinetGridBasedResampling y origin weird behaviourWhen using GridBasedResampling an half pixel shift occurs between user specified value in command and output image, for example :
- user UL : [311000.0, 58818000.000] with spacing [0.5,-0.5] gives an output with origin at [310999.75, 58...When using GridBasedResampling an half pixel shift occurs between user specified value in command and output image, for example :
- user UL : [311000.0, 58818000.000] with spacing [0.5,-0.5] gives an output with origin at [310999.75, 58818000.25]
if we try to compensate that by shifting by an half spacing the input
- user UL : [311000.25, 58817999.75] with spacing [0.5,-0.5] gives an output with origin at [311000.00, 58818000.25]
- user UL : [311000.25, 58817999.74] with spacing [0.5,-0.5] gives an output with origin at [311000.00, 58817999.75]
only N*spacing + spacing/2 ULY seems to be reachable with a spacing set to 0.5
This problem doesn't occur with 5.0 spacing
OTB version : 8.1.0 (same problem with OTB 7.4)
[test_GridBased.tar.gz](/uploads/381e1c6c1487be81ee9d2afb94a225ac/test_GridBased.tar.gz)9.0.0https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2366no data management with otbcli_Superimpose2023-12-01T10:08:19ZemmaBno data management with otbcli_Superimposeotbcli_Superimpose doesn't seem to take into account (and then to ignore) no data values.
It considers them as usual values so they are used in the computation of new pixel values.
Would it be possible to add a parameter "no data value" ...otbcli_Superimpose doesn't seem to take into account (and then to ignore) no data values.
It considers them as usual values so they are used in the computation of new pixel values.
Would it be possible to add a parameter "no data value" ?
(otb version 7.4.0 in command line)https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2367vector files and other result files do not get saved when running OTB from QGIS2023-12-01T12:36:23ZJanOPedersenvector files and other result files do not get saved when running OTB from QGIS### Description
When running for instance the segmentation operation, everything seams to work until the result file and result layer is to be shown. Neither the shape file, nor result layer are produced.
### Steps to reproduce
0. QGI...### Description
When running for instance the segmentation operation, everything seams to work until the result file and result layer is to be shown. Neither the shape file, nor result layer are produced.
### Steps to reproduce
0. QGIS is already installed
1. Install OTB in QGIS
2. Run OTB -> Segmentation -> Segmentation
use default parameters and set the 'output vector file' to 'save as file' and provide a local folder and for instance the name 'segmentation.shp'
3. Press 'run'
4. The logs now show that the result has been saved to the specified file (segmentation.shp) in the specified folder, but the file does not exist.
5. the layer is not added either
### Configuration information
OS, OTB version or tag, information related to build (binaries, superbuild, system libs ...)
OS: Windows 11
OTB: 8.1.2
QGIS: 3.34https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2374AfterExecuteAndWriteOutputs() not called from python API2024-01-08T10:13:07ZRémi CressonAfterExecuteAndWriteOutputs() not called from python APIIt looks like `AfterExecuteAndWriteOutputs()` is not called in python.
OTB 9.0.0, Ubuntu 22.04
I test with various applications but the most easy is with Mosaic, setting `tmpdir` and `comp.feather` to `large`.
In CLI the tmp files are ...It looks like `AfterExecuteAndWriteOutputs()` is not called in python.
OTB 9.0.0, Ubuntu 22.04
I test with various applications but the most easy is with Mosaic, setting `tmpdir` and `comp.feather` to `large`.
In CLI the tmp files are deleted, in python they are not.https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2320Eager mode for ReadImageFilter2024-01-09T14:11:43ZRémi CressonEager mode for ReadImageFilterI was wondering if one could enable/disable a specific behavior of the processing workflow.
In particular I am wondering if the reading and the processing operations could be done in parallel in an OTB pipeline.
This could be an interest...I was wondering if one could enable/disable a specific behavior of the processing workflow.
In particular I am wondering if the reading and the processing operations could be done in parallel in an OTB pipeline.
This could be an interesting feature when accessing the input takes a while, e.g. when processing remote images (/vsicurl/http://.../image.tif). Indeed one region could be downloaded while another one is processed.
The typical processing flow in OTB is the following (we consider a simple pipeline composed of 1 reader --> 1 filter --> 1 writer):
1. Propagates the filter's requested output region to the reader. At the end of this step, the filter knows which region of the input it has to fetch.
2. Read the input data over this requested region
3. Process the requested region
4. Write the output
It's sequential.
What if we could run step 2 and 3 in parallel?
I am just wondering if that is somehow possible.
The only thing to do is for the reader, to not wait until the filter ask him the data, to go grab it. But this supposes that the reader knows in advance what the next requested region would be. I am wondering if somehow this is doable in the ITK framework?
I'll ask for toughs here, then I guess I will ask the ITK community...
Thanks,
Rémihttps://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2294The application RefineSensorModel is missing in version 8.0+2024-02-01T08:58:17Zhello-willyThe application RefineSensorModel is missing in version 8.0+# Refactoring the RefineSensorModel application
## Context
The application RefineSensorModel uses a set of tie points to adjust the parameters of a sensor model.
It uses an optimization algorithm (least-square) to fit the model to the...# Refactoring the RefineSensorModel application
## Context
The application RefineSensorModel uses a set of tie points to adjust the parameters of a sensor model.
It uses an optimization algorithm (least-square) to fit the model to the fit points.
The inputs of the application are
- a geom file containing the sensor model
- a text file containing the tie points
The outputs are
- a geom file containing the refined sensor model
- a text file containing output precision statistics
- a text file containing segments representing residues
Since OTB 8, this application is not available.
We want to reintroduce it, since it is of great interest.
## Details of the refactoring
To reintroduce RefineSensorModel, we need to address multiple issues
### OTB doesn't write geom files anymore
The new version of OTB can't produce a geom file as output of the application.
We propose to change the RefineSensorModel application to work at the product level.
Instead of reading and writing a geom file, it will read and write an image file.
Impact:
- The `ingeom` and `outgeom` parameters become `inImage` and `outImage`, and are of type "ParameterType_InputImage" instead of "ParameterType_InputFilename".
- Use the `SensorTransformFactory` to load the RPC or SAR model from the metadata of the input image.
### Hold the fit points
The fit points used to be stored in the SensorModelAdapter class.
This class was removed with OSSIM, so we need to store the fit points somewhere else.
The proposed class for this task is `SensorTransformBase`.
Impact:
- Add the attribute `m_TiePoints` and implement the function `AddTiePoint` to `SensorTransformBase`.
### Run the optimization
The optimization algorithm was provided by OSSIM.
So we need to implement the optimization algorithm and call it for each sensor model (SAR, RPC).
Impact:
- Implement the Least-Square Optimization algorithm ?
- Add an `Optimize` virtual function to `SensorTransformBase`.
- Implement an `Optimize` function in `RPCTransformBase` class that apply the optimization algorithm to the RPC model (RpcParam).
- Implement an `Optimize` function in `SARTransformBase` class that apply the optimization algorithm to the SAR model (SarParam).8.2.0https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2361ToJSON() method in otbGeometryMetadata returns a string that is not a valid json2024-02-05T17:04:54ZDamiano MissoniToJSON() method in otbGeometryMetadata returns a string that is not a valid jsonThe function does not return a valid json due to trailing comma after the last elements.
```cpp
// JSON export
std::string ToJSON(bool multiline=false) const;
inline static std::string doubleArrayToString(const double* array)
{
...The function does not return a valid json due to trailing comma after the last elements.
```cpp
// JSON export
std::string ToJSON(bool multiline=false) const;
inline static std::string doubleArrayToString(const double* array)
{
std::ostringstream oss;
oss << "[";
for (int loop = 0 ; loop < 20 ; loop++)
oss << " \"" << array[loop] << "\", ";
oss << "]";
return oss.str();
}
```https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2377QGIS adapters cause issues with SuperBuild2024-02-20T17:07:13ZLaurențiu NicolaQGIS adapters cause issues with SuperBuild### Description
1. building using SuperBuild without `OTB_WRAP_QGIS` fails at the configure step:
```
CMake Error at CMake/OTBModuleAPI.cmake:69 (message):
No such module: "OTBQGIS"
Call Stack (most recent call first):
CMake/OTBMod...### Description
1. building using SuperBuild without `OTB_WRAP_QGIS` fails at the configure step:
```
CMake Error at CMake/OTBModuleAPI.cmake:69 (message):
No such module: "OTBQGIS"
Call Stack (most recent call first):
CMake/OTBModuleAPI.cmake:44 (otb_module_load)
CMake/OTBModuleAPI.cmake:88 (_otb_module_config_recurse)
build/OTB/build/OTBConfig.cmake:99 (otb_module_config)
Utilities/Completion/CMakeLists.txt:21 (find_package)
```
2. building using SuperBuild with `OTB_WRAP_QGIS` works initially (perhaps?), but fails on a second build:
```
[ 87%] ./bin/otbQgisDescriptor OpticalCalibration lib/otb/applications ./share/otb/description/
[ 87%] ./bin/otbQgisDescriptor BundleToPerfectSensor lib/otb/applications ./share/otb/description/
[ 89%] ./bin/otbQgisDescriptor Pansharpening lib/otb/applications ./share/otb/description/
[ 89%] ./bin/otbQgisDescriptor ReadImageInfo lib/otb/applications ./share/otb/description/
[ 89%] ./bin/otbQgisDescriptor ExtractROI lib/otb/applications ./share/otb/description/
[ 89%] ./bin/otbQgisDescriptor DynamicConvert lib/otb/applications ./share/otb/description/
[ 89%] ./bin/otbQgisDescriptor CompareImages lib/otb/applications ./share/otb/description/
[ 89%] ./bin/otbQgisDescriptor ConcatenateImages lib/otb/applications ./share/otb/description/
[ 89%] ./bin/otbQgisDescriptor ManageNoData lib/otb/applications ./share/otb/description/
[ 89%] ./bin/otbQgisDescriptor Rasterization lib/otb/applications ./share/otb/description/
[ 90%] ./bin/otbQgisDescriptor VectorDataTransform lib/otb/applications ./share/otb/description/
[ 90%] ./bin/otbQgisDescriptor Mosaic lib/otb/applications ./share/otb/description/
[ 90%] ./bin/otbQgisDescriptor ResetMargin lib/otb/applications ./share/otb/description/
[ 90%] ./bin/otbQgisDescriptor VectorDataExtractROI lib/otb/applications ./share/otb/description/
/home/grayshade/Projects/otb/build/OTB/build/bin/otbQgisDescriptor: error while loading shared libraries: libtiff.so.6: cannot open shared object file: No such file or directory
[ 90%] ./bin/otbQgisDescriptor ConcatenateVectorData lib/otb/applications ./share/otb/description/
[ 90%] ./bin/otbQgisDescriptor VectorDataSetField lib/otb/applications ./share/otb/description/
[ 90%] ./bin/otbQgisDescriptor ZonalStatistics lib/otb/applications ./share/otb/description/
/home/grayshade/Projects/otb/build/OTB/build/bin/otbQgisDescriptor: error while loading shared libraries: libtiff.so.6: cannot open shared object file: No such file or directory
[ 91%] ./bin/otbQgisDescriptor OrthoRectification lib/otb/applications ./share/otb/description/
[ 91%] ./bin/otbQgisDescriptor RigidTransformResample lib/otb/applications ./share/otb/description/
/home/grayshade/Projects/otb/build/OTB/build/bin/otbQgisDescriptor: error while loading shared libraries: libtiff.so.6: cannot open shared object file: No such file or directory
[ 91%] ./bin/otbQgisDescriptor Superimpose lib/otb/applications ./share/otb/description/
gmake[5]: *** [Modules/Core/Wrappers/QGIS/src/CMakeFiles/generate_descriptors.dir/build.make:416: share/otb/description/OpticalCalibration.txt] Error 127
gmake[5]: *** Waiting for unfinished jobs....
gmake[5]: *** [Modules/Core/Wrappers/QGIS/src/CMakeFiles/generate_descriptors.dir/build.make:196: share/otb/description/BundleToPerfectSensor.txt] Error 127
gmake[5]: *** [Modules/Core/Wrappers/QGIS/src/CMakeFiles/generate_descriptors.dir/build.make:424: share/otb/description/Pansharpening.txt] Error 127
/home/grayshade/Projects/otb/build/OTB/build/bin/otbQgisDescriptor: error while loading shared libraries: libtiff.so.6: cannot open shared object file: No such file or directory
[ 91%] ./bin/otbQgisDescriptor ImageEnvelope lib/otb/applications ./share/otb/description/
[ 91%] ./bin/otbQgisDescriptor VectorDataReprojection lib/otb/applications ./share/otb/description/
[ 91%] ./bin/otbQgisDescriptor ColorMapping lib/otb/applications ./share/otb/description/
[ 91%] ./bin/otbQgisDescriptor MultiResolutionPyramid lib/otb/applications ./share/otb/description/
[ 91%] ./bin/otbQgisDescriptor Quicklook lib/otb/applications ./share/otb/description/
/home/grayshade/Projects/otb/build/OTB/build/bin/otbQgisDescriptor: error while loading shared libraries: libtiff.so.6: cannot open shared object file: No such file or directory
/home/grayshade/Projects/otb/build/OTB/build/bin/otbQgisDescriptor: error while loading shared libraries: libtiff.so.6: cannot open shared object file: No such file or directory
gmake[5]: *** [Modules/Core/Wrappers/QGIS/src/CMakeFiles/generate_descriptors.dir/build.make:280: share/otb/description/ExtractROI.txt] Error 127
/home/grayshade/Projects/otb/build/OTB/build/bin/otbQgisDescriptor: error while loading shared libraries: libtiff.so.6: cannot open shared object file: No such file or directory
/home/grayshade/Projects/otb/build/OTB/build/bin/otbQgisDescriptor: error while loading shared libraries: libtiff.so.6: cannot open shared object file: No such file or directory
/home/grayshade/Projects/otb/build/OTB/build/bin/otbQgisDescriptor: error while loading shared libraries: libtiff.so.6: cannot open shared object file: No such file or directory
[ 91%] ./bin/otbQgisDescriptor TileFusion lib/otb/applications ./share/otb/description/
[ 91%] ./bin/otbQgisDescriptor Synthetize lib/otb/applications ./share/otb/description/
[ 91%] ./bin/otbQgisDescriptor SplitImage lib/otb/applications ./share/otb/description/
[ 91%] ./bin/otbQgisDescriptor PixelValue lib/otb/applications ./share/otb/description/
/home/grayshade/Projects/otb/build/OTB/build/bin/otbQgisDescriptor: error while loading shared libraries: libtiff.so.6: cannot open shared object file: No such file or directory
/home/grayshade/Projects/otb/build/OTB/build/bin/otbQgisDescriptor: error while loading shared libraries: libtiff.so.6: cannot open shared object file: No such file or directory
/home/grayshade/Projects/otb/build/OTB/build/bin/otbQgisDescriptor: error while loading shared libraries: libtiff.so.6: cannot open shared object file: No such file or directory
gmake[5]: *** [Modules/Core/Wrappers/QGIS/src/CMakeFiles/generate_descriptors.dir/build.make:452: share/otb/description/ReadImageInfo.txt] Error 127
/home/grayshade/Projects/otb/build/OTB/build/bin/otbQgisDescriptor: error while loading shared libraries: libtiff.so.6: cannot open shared object file: No such file or directory
gmake[5]: *** [Modules/Core/Wrappers/QGIS/src/CMakeFiles/generate_descriptors.dir/build.make:228: share/otb/description/ConcatenateImages.txt] Error 127
gmake[5]: *** [Modules/Core/Wrappers/QGIS/src/CMakeFiles/generate_descriptors.dir/build.make:208: share/otb/description/CompareImages.txt] Error 127
gmake[5]: *** [Modules/Core/Wrappers/QGIS/src/CMakeFiles/generate_descriptors.dir/build.make:372: share/otb/description/ManageNoData.txt] Error 127
gmake[5]: *** [Modules/Core/Wrappers/QGIS/src/CMakeFiles/generate_descriptors.dir/build.make:448: share/otb/description/Rasterization.txt] Error 127
gmake[5]: *** [Modules/Core/Wrappers/QGIS/src/CMakeFiles/generate_descriptors.dir/build.make:268: share/otb/description/DynamicConvert.txt] Error 127
gmake[5]: *** [Modules/Core/Wrappers/QGIS/src/CMakeFiles/generate_descriptors.dir/build.make:392: share/otb/description/Mosaic.txt] Error 127
gmake[5]: *** [Modules/Core/Wrappers/QGIS/src/CMakeFiles/generate_descriptors.dir/build.make:456: share/otb/description/ResetMargin.txt] Error 127
gmake[5]: *** [Modules/Core/Wrappers/QGIS/src/CMakeFiles/generate_descriptors.dir/build.make:592: share/otb/description/VectorDataTransform.txt] Error 127
/home/grayshade/Projects/otb/build/OTB/build/bin/otbQgisDescriptor: error while loading shared libraries: libtiff.so.6: cannot open shared object file: No such file or directory
/home/grayshade/Projects/otb/build/OTB/build/bin/otbQgisDescriptor: error while loading shared libraries: libtiff.so.6: cannot open shared object file: No such file or directory
/home/grayshade/Projects/otb/build/OTB/build/bin/otbQgisDescriptor: error while loading shared libraries: libtiff.so.6: cannot open shared object file: No such file or directory
/home/grayshade/Projects/otb/build/OTB/build/bin/otbQgisDescriptor: error while loading shared libraries: libtiff.so.6: cannot open shared object file: No such file or directory
/home/grayshade/Projects/otb/build/OTB/build/bin/otbQgisDescriptor: error while loading shared libraries: libtiff.so.6: cannot open shared object file: No such file or directory
gmake[5]: *** [Modules/Core/Wrappers/QGIS/src/CMakeFiles/generate_descriptors.dir/build.make:608: share/otb/description/ZonalStatistics.txt] Error 127
gmake[5]: *** [Modules/Core/Wrappers/QGIS/src/CMakeFiles/generate_descriptors.dir/build.make:460: share/otb/description/RigidTransformResample.txt] Error 127
gmake[5]: *** [Modules/Core/Wrappers/QGIS/src/CMakeFiles/generate_descriptors.dir/build.make:420: share/otb/description/OrthoRectification.txt] Error 127
/home/grayshade/Projects/otb/build/OTB/build/bin/otbQgisDescriptor: error while loading shared libraries: libtiff.so.6: cannot open shared object file: No such file or directory
gmake[5]: *** [Modules/Core/Wrappers/QGIS/src/CMakeFiles/generate_descriptors.dir/build.make:232: share/otb/description/ConcatenateVectorData.txt] Error 127
gmake[5]: *** [Modules/Core/Wrappers/QGIS/src/CMakeFiles/generate_descriptors.dir/build.make:580: share/otb/description/VectorDataExtractROI.txt] Error 127
gmake[5]: *** [Modules/Core/Wrappers/QGIS/src/CMakeFiles/generate_descriptors.dir/build.make:588: share/otb/description/VectorDataSetField.txt] Error 127
/home/grayshade/Projects/otb/build/OTB/build/bin/otbQgisDescriptor: error while loading shared libraries: libtiff.so.6: cannot open shared object file: No such file or directory
/home/grayshade/Projects/otb/build/OTB/build/bin/otbQgisDescriptor: error while loading shared libraries: libtiff.so.6: cannot open shared object file: No such file or directory
gmake[5]: *** [Modules/Core/Wrappers/QGIS/src/CMakeFiles/generate_descriptors.dir/build.make:540: share/otb/description/Superimpose.txt] Error 127
/home/grayshade/Projects/otb/build/OTB/build/bin/otbQgisDescriptor: error while loading shared libraries: libtiff.so.6: cannot open shared object file: No such file or directory
gmake[5]: *** [Modules/Core/Wrappers/QGIS/src/CMakeFiles/generate_descriptors.dir/build.make:332: share/otb/description/ImageEnvelope.txt] Error 127
/home/grayshade/Projects/otb/build/OTB/build/bin/otbQgisDescriptor: error while loading shared libraries: libtiff.so.6: cannot open shared object file: No such file or directory
/home/grayshade/Projects/otb/build/OTB/build/bin/otbQgisDescriptor: error while loading shared libraries: libtiff.so.6: cannot open shared object file: No such file or directory
gmake[5]: *** [Modules/Core/Wrappers/QGIS/src/CMakeFiles/generate_descriptors.dir/build.make:204: share/otb/description/ColorMapping.txt] Error 127
/home/grayshade/Projects/otb/build/OTB/build/bin/otbQgisDescriptor: error while loading shared libraries: libtiff.so.6: cannot open shared object file: No such file or directory
/home/grayshade/Projects/otb/build/OTB/build/bin/otbQgisDescriptor: error while loading shared libraries: libtiff.so.6: cannot open shared object file: No such file or directory
gmake[5]: *** [Modules/Core/Wrappers/QGIS/src/CMakeFiles/generate_descriptors.dir/build.make:544: share/otb/description/Synthetize.txt] Error 127
/home/grayshade/Projects/otb/build/OTB/build/bin/otbQgisDescriptor: error while loading shared libraries: libtiff.so.6: cannot open shared object file: No such file or directory
/home/grayshade/Projects/otb/build/OTB/build/bin/otbQgisDescriptor: error while loading shared libraries: libtiff.so.6: cannot open shared object file: No such file or directory
gmake[5]: *** [Modules/Core/Wrappers/QGIS/src/CMakeFiles/generate_descriptors.dir/build.make:400: share/otb/description/MultiResolutionPyramid.txt] Error 127
gmake[5]: *** [Modules/Core/Wrappers/QGIS/src/CMakeFiles/generate_descriptors.dir/build.make:440: share/otb/description/Quicklook.txt] Error 127
gmake[5]: *** [Modules/Core/Wrappers/QGIS/src/CMakeFiles/generate_descriptors.dir/build.make:432: share/otb/description/PixelValue.txt] Error 127
gmake[5]: *** [Modules/Core/Wrappers/QGIS/src/CMakeFiles/generate_descriptors.dir/build.make:528: share/otb/description/SplitImage.txt] Error 127
gmake[5]: *** [Modules/Core/Wrappers/QGIS/src/CMakeFiles/generate_descriptors.dir/build.make:584: share/otb/description/VectorDataReprojection.txt] Error 127
/home/grayshade/Projects/otb/build/OTB/build/bin/otbQgisDescriptor: error while loading shared libraries: libtiff.so.6: cannot open shared object file: No such file or directory
gmake[5]: *** [Modules/Core/Wrappers/QGIS/src/CMakeFiles/generate_descriptors.dir/build.make:548: share/otb/description/TileFusion.txt] Error 127
gmake[4]: *** [CMakeFiles/Makefile2:11482: Modules/Core/Wrappers/QGIS/src/CMakeFiles/generate_descriptors.dir/all] Error 2
gmake[3]: *** [Makefile:156: all] Error 2
gmake[2]: *** [CMakeFiles/OTB.dir/build.make:87: OTB/src/OTB-stamp/OTB-build] Error 2
gmake[1]: *** [CMakeFiles/Makefile2:974: CMakeFiles/OTB.dir/all] Error 2
gmake: *** [Makefile:91: all] Error 2
```
I do have `libtiff` already built in the current directory:
```
TIFF/build/libtiff/libtiff.so
TIFF/build/libtiff/libtiff.so.6
TIFF/build/libtiff/libtiff.so.6.0.2
```
My workaround was to do something like below, but it isn't ideal, of course:
```
cmake --build . --parallel $(nproc); cp OTB/build/lib/libOTBSampling-9.0.so.1 ../superbuild_install/lib/libOTBSampling-9.0.so.1; cp OTB/build/lib/otb/applications/otbapp_SampleAugmentation.so ../superbuild_install/lib/otb/applications/otbapp_SampleAugmentation.so
```
### Steps to reproduce
```
$ mkdir build
$ cd build
$ ccmake ../SuperBuild # choose your favourite settings
$ cmake --build . --parallel $(nproc)
```
### Configuration information
Fedora 39, tested at c302db4eab9815ba94d83c29ce45aa4b0dc144b6
![image](/uploads/7be70d36a2fbbc1fd96cd1efe57489dc/image.png)https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2378Divide OTB modules in independent repositories2024-03-05T09:32:20ZTristan LaurentDivide OTB modules in independent repositories# Resume
The goal of this is to separate each modules located in https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/tree/develop/Modules in a separate repo (except Core). A link will be done from otb main repo and each module with the ...# Resume
The goal of this is to separate each modules located in https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/tree/develop/Modules in a separate repo (except Core). A link will be done from otb main repo and each module with the "submodule" git mechanism.
# Pro and cons
Separating modules have several advantages:
- Improve CI build time
- Improve unittest jobs and runs as only module related features are tested
- Issues will now be module-related
- Developers only download needed source code
The CI jobs may increase in complexity as we introduce dependencies with modules. Thus we need to trigger modules jobs from core.
# Plan
- [ ] According to @ytanguy , create a gitlab group to handle all modules in a separate repo. This will be easier for bug tracking and management
- [ ] Start with Miscellaneous module, use OTB modules https://www.orfeo-toolbox.org/CookBook-9.0/RemoteModules.html
- [ ] Create external git repo, link it as a submodule
- [ ] OTB core must download corresponding submodule if the cmake -DOTBGroup_Miscellaneous is turned on
- [ ] Compile it separately, you may use OTB core artifact
- [ ] Adapt CI to run corresponding build job and tests
- [ ] Adapt otb CI to start module job when there is a new dependency (i.e. OTB core)
- [ ] Adapt bug tracking for each project ?
- [ ] Add a Readme with compilation help, otb integration, and some exemples
- [ ] Repeat for Remote
- [ ] Repeat for FeatureExtraction
- [ ] Repeat for SAR
- [ ] Repeat for Segmentation
- [ ] Repeat for Hyperspectral
- [ ] Repeat for Learning
- [ ] Repeat for StereoProcessing10.0.0https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2307Spatial shifting (orthorectification Sentinel1) with 8.1.02024-03-06T10:08:43ZNicolas EkicierSpatial shifting (orthorectification Sentinel1) with 8.1.0### Description
I notice a spatial shifting in Orthorectification output in Sentinel1 images with 8.1.0 compared to 7.3.0., about 60m with the same parameters.
For your information, I call `otbcli_Orthorectification`.
### Configuratio...### Description
I notice a spatial shifting in Orthorectification output in Sentinel1 images with 8.1.0 compared to 7.3.0., about 60m with the same parameters.
For your information, I call `otbcli_Orthorectification`.
### Configuration information
Ubuntu 22.04.1
OTB version (9.0.0 / 8.1.0 / 7.3.0)8.1.1Thibaut ROMAINThibaut ROMAINhttps://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/1514Improvements for ApplicationEngine2024-03-06T14:05:30ZGuillaume PaseroImprovements for ApplicationEngine### What changes will be made and why they would make a better Orfeo ToolBox?
The OTB Application are now used very often, so it is important to keep the ApplicationEngine code clean. This RFC proposes small enhancements that will simpl...### What changes will be made and why they would make a better Orfeo ToolBox?
The OTB Application are now used very often, so it is important to keep the ApplicationEngine code clean. This RFC proposes small enhancements that will simplify the code base, and also new services available from the C++ ApplicationEngine API but also wrapped into the Python API.
#### High level description
The following are small improvement to the ApplicationEngine module:
* [x] __Handling of "UserValue" flag__: the optional boolean in 3rd argument of the functions SetParameterString/SetParameterInt/... is not very convenient. I think it is possible to get rid of it using a simple state flag "IsInPrivateDo" in the Application class. This flag would be set to ON during calls to DoInit(), DoUpdateParameters() and DoExecute(). During these calls, the values set on parameters are always "Automatic" values. Outside these calls, we can assume that the values set on parameters come from the user.
* [x] __Merging "UserValue" and "AutomaticValue" flags__: why do we have both ? I believe we could choose the convention : UserValue = not(AutomaticValue). The initial default value of a parameter would be considered "automatic". We could remove 1 of these 2 flags, there are already enough in the Parameter class.
* [ ] __Handling of the m_Active flag__: this flag should be handled mostly by the Parameters themselves in the ApplicationEngine module. For instance the call to EnableParameter() in otb::Wrapper::CommandLineLauncher::LoadParameters() should not be here, but rather in each "param->SetValue(string)". In a similar way, in otb::Wrapper::Application::SetParameterUserValue(), the call to EnableParameter() should not be here (in addition, it will always switch ON an EmptyParameter). The benefit is also to guarantee the same behaviour on CLI / GUI /Python.
* [x] __Refactor the ParameterType_Empty__: there are a lot of special cases for this parameter because its value (a boolean flag) and its Active flag are actually the same. For instance, in the current state of ApplicationEngine, it is impossible to have an Empty parameter with Role_Output. This parameter should have its value stored in a specific flag, proper functions Application::Set/GetParameterBool(), and maybe easy conversions to/from string and integer values. Maybe a specific ParameterType_Boolean can be added...
* [ ] __String getters and setters for all parameters__: it would be nice if all the parameters could be set using a common Application::SetParameterString(), or SetParameterStringList(). Same remark for getters. It would remove some long sections of if/elseif/elseif/... in the CommandLineLauncher but also in the Input/OutputXML parameters.
* [x] __Move m_IsChecked to QtWrappers__: in the Parameter base class, the flag m_IsChecked is only used by QtWrapper, so it should be moved outside ApplicationEngine.
* [ ] __Improve architecture of Parameters__: there is also room for improvement in the architecture of Parameters. There is a lot of code that is duplicated between similar parameter types, we should consider a better class architecture to gather common features between parameters with similar behaviour.
* [x] __Remove enum m_DefaultValueMode__: in the Parameter base class, the enum m_DefaultValueMode is never used in OTB. We could check if other external projects use it. We could get rid of it.
If you see other potential improvements to the core of this module, feel free to give your idea.
The following are a list of new services for ApplicationEngine framework:
* [x] __Streaming and output information__: this is a set of service that let you have insights on what output the
application will generate, and what pieces of the input you need to generate a piece of the output.
* [x] __Get the output information__: given a parameter key corresponding to an OutputImageParameter, retrieve the output size, spacing, origin, projection, geom file and so on
* [x] __Get the requested input regions__: given a parameter key corresponding to an OutputImageParameter, and a region corresponding to a piece of this output, get for each InputImageParameter the region required to produce that piece of output. The application could also return the estimated amount of RAM needed to compute that piece.
* [x] __Attach metadata to numpy array interface__: the numpy array interface to application is useless in many cases because it only allows to pass the pixel buffer, and no metadata. Many OTB filters need additional metadata (such as origin, spacing, size, projection and geom file) to be able to process the data.
* [x] __Get rid of ComplexParameterInput/OutputImage__: there is no reason to have a separate complex image parameter. This makes most application incompatible with complex images (such as ExtractROI for instance). It would be better to be able to detect complex images with InputImageParameter, and to add new output types for OutputImageParameter (cint, cfloat, ...). Check Request_for_changes-125:_Merge_Complex_and_standard_Image_Parameter
* [x] __Set/get all parameters at once through a dictionnary in Pyton API__: this is a small helper for large application with many parameters to set.
* [x] __Get proper logging / progress reporting in Python__: self explanatory.
* [x] __Register/free filter resources__: provide a way to register filters and free them at the end of the application processing to avoid retaining memory. Check improvements to fix bug #1475
* [ ] __Interface with OGR Python wrappers__: GDAL/OGR provides Python wrappers for vector data. It would be useful to import them in OTB Applications (into ParameterType_VectorData). Solution for vectors defined as ParameterType_InputFilename ?
* [x] __Stop button for Graphic Interface__: Be able to stop a running application.
* [ ] __Document new features in CookBook__: new recipe ?
#### Risks and benefits
The main risk is to break existing applications, so we need to focus on compatibility. In the end, the ApplicationEngine will have a cleaner code base and new useful features.
#### Alternatives for implementations
### Who will be developing the proposed changes?
Work can be split, different contributors expected.https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/1640[DOC] Document alternate Application API Python syntax2024-03-06T14:17:38ZManuel Grizonnet[DOC] Document alternate Application API Python syntax### Target documentation ressources
bandmath.IN = image.tif
bandmath.EXP = "im1b1"
This type of syntax should be described in the otb app section of the Cookbook (explain why upper case parameter is mandatory for instance).
### Chang...### Target documentation ressources
bandmath.IN = image.tif
bandmath.EXP = "im1b1"
This type of syntax should be described in the otb app section of the Cookbook (explain why upper case parameter is mandatory for instance).
### Change requested
Describe precisely the changes that are required.https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/1671Remove hard-coded muParser expression library-wise2024-03-20T14:05:37ZJulien MichelRemove hard-coded muParser expression library-wise### What changes will be made and why they would make a better Orfeo ToolBox?
#### High level description
Some filters and classes use the `muParser` based filters with hard-coded expressions. This is bad for at least 2 reasons:
* `muP...### What changes will be made and why they would make a better Orfeo ToolBox?
#### High level description
Some filters and classes use the `muParser` based filters with hard-coded expressions. This is bad for at least 2 reasons:
* `muParser` based filters are not as fast as their functor based counter-parts
* `muParser` is an optional dependency. Using it heavily results in many applications and filters disabled if `muParser` is disabled (see #1670 for instance)
#### Risks and benefits
Only risk might be small changing with floating point baselines.
Benefit is a faster OTB less dependent on muParser.
#### Alternatives for implementations
We need to spot places where `muParser` is mis-used:
```
$ grep -R -l BandMath Modules/ | grep -v BandMath | grep -v Parser
Modules/Applications/AppProjection/app/otbGridBasedImageResampling.cxx
Modules/Applications/AppImageUtils/app/otbCompareImages.cxx
Modules/Applications/AppStereo/app/otbStereoFramework.cxx
Modules/Applications/AppStereo/app/otbBlockMatching.cxx
```
### Who will be developing the proposed changes?
TDB.https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2381PLEIADES Orthorectification failed since version 82024-03-20T14:24:20ZdemagistPLEIADES Orthorectification failed since version 8### Description
Since release 8 of OTB I am not able anymore to apply Orthorectification on a Pleiades image I use during a lesson.
The same command line works fine with version 7.4.2 and fails since versions 8.
### Steps to reproduce
...### Description
Since release 8 of OTB I am not able anymore to apply Orthorectification on a Pleiades image I use during a lesson.
The same command line works fine with version 7.4.2 and fails since versions 8.
### Steps to reproduce
The following command produce a good result with release 7.4.2 (linux or windows) :
otbcli_OrthoRectification -io.in "./IMG_PHR1B_MS_004/IMG_PHR1B_MS_201807291333495_SEN_3210573101-004_R1C1.TIF?&skipcarto=true" -map utm -map.utm.zone 23 -interpolator nn -opt.ram 1024 -opt.gridspacing 4 -elev.dem ./SRTM1 -io.out ./test_ORTHO+DEM.tif
Since release 8, it does not work anymore.
I tested the latest 9.0.0 release using a docker image :
docker run -it -v .:/Data orfeotoolbox/otb:9.0.0 otbcli_OrthoRectification -io.in "/Data/IMG_PHR1B_MS_004/DIM_PHR1B_MS_201807291333495_SEN_3210573101-004.XML?&skipcarto=true" -map utm -map.utm.zone 23 -interpolator nn -opt.ram 1024 -opt.gridspacing 4 -elev.dem /Data/SRTM1 -io.out /Data/test_ORTHO+DEM.tif
and got the following error :
(FATAL) OrthoRectification: itk::ERROR: ImageToGenericRSOutputParameters(0x788a50): No information in the metadata, please set an image with non empty metadata
Same problem using the DIMAP xml file as input file :
docker run -it -v .:/Data orfeotoolbox/otb:9.0.0 otbcli_OrthoRectification -io.in "/Data/IMG_PHR1B_MS_004/DIM_PHR1B_MS_201807291333495_SEN_3210573101-004.XML?&skipcarto=true" -map utm -map.utm.zone 23 -interpolator nn -opt.ram 1024 -opt.gridspacing 4 -elev.dem /Data/SRTM1 -io.out /Data/test_ORTHO+DEM.tif
2024-03-06 16:27:10 (INFO) OrthoRectification: Elevation management: setting default height above ellipsoid to 0 meters
2024-03-06 16:27:10 (INFO): Loading metadata from official product
2024-03-06 16:27:10 (FATAL) OrthoRectification: itk::ERROR: ImageToGenericRSOutputParameters(0x788a50): No information in the metadata, please set an image with non empty metadata
### Configuration information
see above in descriptionhttps://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2380Separate Miscellaneous in separate repository2024-03-20T15:59:44ZTristan LaurentSeparate Miscellaneous in separate repositoryTo compilate project, we can use OTB modules https://www.orfeo-toolbox.org/CookBook-9.0/RemoteModules.html
- [x] Create external git repo, link it as a submodule
- [x] OTB core must download corresponding submodule if the cmake -DOTBGrou...To compilate project, we can use OTB modules https://www.orfeo-toolbox.org/CookBook-9.0/RemoteModules.html
- [x] Create external git repo, link it as a submodule
- [x] OTB core must download corresponding submodule if the cmake -DOTBGroup_Miscellaneous is turned on
- [x] Compile it separately, you may use OTB core artifact
- [x] Verify that package is correctly built during cpack
- [ ] Adapt CI to run corresponding build job and tests
- [ ] Adapt otb CI to start module job when there is a new dependency (i.e. OTB core)
- [ ] Adapt bug tracking for each project ?
- [ ] Add a Readme with compilation help, otb integration, and some exemples10.0.0Tristan LaurentTristan Laurenthttps://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2384SuperBuild LibKML URL is out of date2024-03-21T11:29:08ZLaurențiu NicolaSuperBuild LibKML URL is out of dateIt's https://deb.debian.org/debian/pool/main/libk/libkml/libkml_1.3.0~r864+dfsg.orig.tar.gz, but should be http://deb.debian.org/debian/pool/main/libk/libkml/libkml_1.3.0.orig.tar.gz or something like that.It's https://deb.debian.org/debian/pool/main/libk/libkml/libkml_1.3.0~r864+dfsg.orig.tar.gz, but should be http://deb.debian.org/debian/pool/main/libk/libkml/libkml_1.3.0.orig.tar.gz or something like that.https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2365QGIS Plugin being removed from core2024-03-25T13:21:26ZJulien CabiecesQGIS Plugin being removed from core### Remove OTB QGIS Plugin from core
#### High level description
OTB provider plugin is currently being part of the QGIS core, and some [discussions](https://lists.osgeo.org/pipermail/qgis-developer/2023-November/066221.html) has been ...### Remove OTB QGIS Plugin from core
#### High level description
OTB provider plugin is currently being part of the QGIS core, and some [discussions](https://lists.osgeo.org/pipermail/qgis-developer/2023-November/066221.html) has been raised to remove it so it becomes a fully 3rd party plugin, maintained by the OTB community.
I have both contributed to QGIS and OTB and I'm in favor of this proposal.
#### Risks and benefits
I think it would ease development of the plugin and would lower the pain of managing compatibility between QGIS and OTB.
#### Alternatives for implementations
That would require to move the OTB QGIS Plugin to the [QGIS Plugin platform](https://plugins.qgis.org/) or even embed it in the OTB installer.
### Who will be developing the proposed changes?
At the moment, no one is clearly identified to make the modifications.
OTB is a great tool and we would like to see it still integrated into QGIS.
If you have any questions or concerns, please let us know.
CC @ytanguy