Troubles with the spatialResolution parameter
Currently, the spatial resolution parameter works well only if it is the same than the input resolution.
It was not taken in account in different steps, leading to errors in the last classification steps.
The two identified steps are mosaic (solved by commit 456c8bb6), and the validation step where an entry of OTB application is at the resolution required in the configuration file, and the second at the input resolution, leading to an error.
Several issues are identified:
- It is impossible to require a output map at a different resolution. Use Sentinel-2 with a spatial resolution of 20m to reproduce the issue.
- The case of non squared resolution is not handled.
Also, issue #211 (closed) shows that using a floating resolution is not possible.