otb issueshttps://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues2022-04-12T05:45:56Zhttps://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2261Cannot get the output statistics of ComputeImagesStatistics2022-04-12T05:45:56ZNicolas NarçonCannot get the output statistics of ComputeImagesStatisticsCurrently, the application ComputeImagesStatistics only prints the mean and standard deviation and can optionally save the result inside an XML.
I would like to be able to get the result in Python, as it is possible in ReadImageInfo, so...Currently, the application ComputeImagesStatistics only prints the mean and standard deviation and can optionally save the result inside an XML.
I would like to be able to get the result in Python, as it is possible in ReadImageInfo, something such as:
```python
stats = otbApplication.Registry.CreateApplication('ComputeImagesStatistics')
stats.SetParameterStringList('il', ['image.tif'])
stats.Execute()
mean = stats.GetParameterFloat('mean')
```8.0.0https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2260Problem for TSX metadata in V8 (parseGeom)2022-04-12T05:45:55ZGaëlle USSEGLIOProblem for TSX metadata in V8 (parseGeom)### Description
DEM projection can raise a seg fault for TSX inputs. A Seg Fault is raised if metadata comes from a geom file (OTB = 7.4)
Hera a [patch](/uploads/eda60d4fa2481c7ef6d6866529428cb1/tsx_metadata.patch) to solve this issue ...### Description
DEM projection can raise a seg fault for TSX inputs. A Seg Fault is raised if metadata comes from a geom file (OTB = 7.4)
Hera a [patch](/uploads/eda60d4fa2481c7ef6d6866529428cb1/tsx_metadata.patch) to solve this issue in 7.4. FYI, I tried to remain compliant with OTB < 7.4 (different keys in geom) but I did not check it.
### Configuration information
OS centos 7.9 (HAL), OTB release-8.08.0.0https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2258Problem for CSK metadata in V82022-03-15T07:08:47ZGaëlle USSEGLIOProblem for CSK metadata in V8### Description
I have noticed a few problems using CSK metadata:
* CSK metadata interface always set HDF5:*filename*://SBI//S01 as image. It does not work if an extraction was made from a CSK product.
* Missing metadata in `parseGDAL` ...### Description
I have noticed a few problems using CSK metadata:
* CSK metadata interface always set HDF5:*filename*://SBI//S01 as image. It does not work if an extraction was made from a CSK product.
* Missing metadata in `parseGDAL` function such as NumberOfColums or GCPTimes
* Missing metadata in `parseGeom`
Here a [patch](/uploads/9a5ca82f7b5266d7734f2cc4252c98e5/csk_metadata.patch).
Let me know if there is a problem.
### Configuration information
OS centos 7.9 (HAL), OTB release-8.08.0.0https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2257Problem nb lines/columns in SARBurstExtraction2022-03-15T07:08:59ZGaëlle USSEGLIOProblem nb lines/columns in SARBurstExtraction### Description
A little confusion between *NumberOfLines* and *NumberOfColumns* in `SARBurstExtraction` : [patch](/uploads/9090f64ea919491b5383625c66fe7d66/burst_extraction_correction.patch)
### Configuration information
OS centos 7....### Description
A little confusion between *NumberOfLines* and *NumberOfColumns* in `SARBurstExtraction` : [patch](/uploads/9090f64ea919491b5383625c66fe7d66/burst_extraction_correction.patch)
### Configuration information
OS centos 7.9 (HAL), OTB release-8.08.0.0https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2256Problem with right_looking_flag on S1 products2022-03-15T07:09:12ZGaëlle USSEGLIOProblem with right_looking_flag on S1 products### Description
Rigth looking flag is always true for S1 products. Old metadata (from v7.4/geom) do not contain a key to specify this flag (such as [support_data.look_side](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/blob/releas...### Description
Rigth looking flag is always true for S1 products. Old metadata (from v7.4/geom) do not contain a key to specify this flag (such as [support_data.look_side](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/blob/release-8.0/Modules/Core/Metadata/src/otbSarImageMetadataInterface.cxx#L300)). Without this key, the flag is set, by default to false.
IMO, we can set this flag to true in `Sentinel1ImageMetadataInterface` : [patch](/uploads/eeeef091657813fb0fc30610410f9434/rightlookingflag_s1_from_geom.patch)
### Configuration information
OS centos 7.9 (HAL), OTB release-8.08.0.0https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2255Wrong projection in range for S1 IW products2022-03-15T07:09:24ZGaëlle USSEGLIOWrong projection in range for S1 IW products### Description
I have noticed huge differences between v7.4 and v8 projection using `WorldToLineSampleYZ` function from `SarSensorModel`.
A bug is present on [nearRangeTime value](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/bl...### Description
I have noticed huge differences between v7.4 and v8 projection using `WorldToLineSampleYZ` function from `SarSensorModel`.
A bug is present on [nearRangeTime value](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/blob/release-8.0/Modules/Core/Metadata/src/otbSARMetadata.cxx#L194). If the input image has *AzimuthBandwidth*, *RangeBandwidth* or *AzimuthSteeringRate* as metadata, *nearRangeTime* value is wrong.
Here a [patch](/uploads/06c3493ae0e294b8a64277ef418ccfdd/nearRangeTime_correction.patch) to correct this bug. Projection on range dimension seems to be OK with this patch.
### Configuration information
OS centos 7.9 (HAL), OTB release-8.08.0.0https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2241Segfault when using several images with no projection In Monteverdi2022-01-04T19:38:51ZCédric TraizetSegfault when using several images with no projection In Monteverdi### Description
Monteverdi crash when trying to open two images with no projection
### Steps to reproduce
```
monteverdi '/mnt/datas/OTB2/otb/Data/Input/StereoMoving.png' '/mnt/datas/OTB2/otb/Data/Input/StereoFixed.png'
```
### Conf...### Description
Monteverdi crash when trying to open two images with no projection
### Steps to reproduce
```
monteverdi '/mnt/datas/OTB2/otb/Data/Input/StereoMoving.png' '/mnt/datas/OTB2/otb/Data/Input/StereoFixed.png'
```
### Configuration information
develop and release-8.0 branches.8.0.0Cédric TraizetCédric Traizethttps://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2240DOC: Improve documentation on how to recompile python bindings2022-02-07T08:32:43ZThibaut ROMAINDOC: Improve documentation on how to recompile python bindingsIn the cookbook, the users don't have the information about the system requirements to rebuild the python bindingsIn the cookbook, the users don't have the information about the system requirements to rebuild the python bindings8.0.0Cédric TraizetCédric Traizethttps://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2239Link otb 8.0 with boost2022-03-08T07:15:13ZCédric TraizetLink otb 8.0 with boostSome users are unable to compile eternal code and standalone remote modules against OTB 8.0 without calling find-package Boost first.
I failed to reproduce this bug using the binary package for now
The user was using a compiled versio...Some users are unable to compile eternal code and standalone remote modules against OTB 8.0 without calling find-package Boost first.
I failed to reproduce this bug using the binary package for now
The user was using a compiled version using system libraries in a docker8.0.0Thibaut ROMAINThibaut ROMAINhttps://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2238Need to document how to build a remote module against binary packages2022-02-07T08:32:42ZYannick TANGUYNeed to document how to build a remote module against binary packages### Target documentation resources
CookBook should add a section (or paragraph here : https://www.orfeo-toolbox.org/CookBook-8.0/RemoteModules.html#installation-and-usage)
### Change requested
I've compiled my remote module againt an ...### Target documentation resources
CookBook should add a section (or paragraph here : https://www.orfeo-toolbox.org/CookBook-8.0/RemoteModules.html#installation-and-usage)
### Change requested
I've compiled my remote module againt an installed OTB, I've a "symbol not found" error when I launched the application.
This is due to a very tricky bug, discussed here : https://gitlab.orfeo-toolbox.org/s1-tiling/s1tilingsupportapplications/-/issues/4#note_93605
When I add this flag, it works fine :
`cmake ../../fast-lsd/ -DOTB_BUILD_MODULE_AS_STANDALONE=True -DCMAKE_CXX_FLAGS=-D_GLIBCXX_USE_CXX11_ABI=0`
This workaround should be documented.8.0.0https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2237Implement a GetSize() function for the ImageMetadata class2022-01-04T19:38:50ZJulien OsmanImplement a GetSize() function for the ImageMetadata class### Description
With OTB 7.4, I use `keywordlist.GetSize()`. It is not possible with OTB 8.0 and ImageMetadata since it doens't have such a function.### Description
With OTB 7.4, I use `keywordlist.GetSize()`. It is not possible with OTB 8.0 and ImageMetadata since it doens't have such a function.8.0.0Julien OsmanJulien Osmanhttps://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2235Release 8.0.02022-04-12T05:45:56ZJulien OsmanRelease 8.0.0[[_TOC_]]
We are ready to release OTB version 8.0.0. The following steps need to be done:
## Blocking issues/MR
* [x] !865: Update the version of several OTB dependencies in the Superbuild
* [x] !868: Use std::chrono and the date libr...[[_TOC_]]
We are ready to release OTB version 8.0.0. The following steps need to be done:
## Blocking issues/MR
* [x] !865: Update the version of several OTB dependencies in the Superbuild
* [x] !868: Use std::chrono and the date library instead of boost date time as internal types
* [x] !870: Provide access to the metadata from the python API
* [x] !874: Fix segfault in Monteverdi
* [ ] !876
* [ ] !883
## Release Candidate 1
### 1. Branches
* [X] Feature freeze: [create the new release branch](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#create-release-branch)
* [X] Make sure the version number in `CMakeLists.txt` is 8.0.0
### 2. Housekeeping
* [x] In this story, make a list of blocking issues for the release (if any)
* [x] Update release notes (walk the GitLab MR merged history and log all improvements)
* [x] Update the date in RELEASE_NOTES.txt
* [x] Check [SonarQube](https://sonar.orfeo-toolbox.org/dashboard?id=orfeotoolbox-otb)
* [x] Run Debian [spelling](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#spelling-check) checker
* [x] Run shellcheck script from [OTB-Devutils/Scripts/](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb-devutils/blob/master/Scripts/run_shellcheck.sh)
* [x] [Update translation](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#translation-for-monteverdi-mapla) for Monteverdi and Mapla
* [x] [Sanity check the binary packages](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#standalone-packages-sanity-check)
* [x] Windows
* [x] Linux
* [x] Mac
* [x] Test QGIS on qgis docker image
### 3. Actual release
Once all blocking issues are closed, and the previous steps are done:
* [x] [Tag the release candidate](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#release-tag)
* [x] Update GIT_TAG for all official remote modules (if needed)
### 4. Publish and plan next release
* [x] [Prepare and upload source packages](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#prepare-and-upload-source-packages)
* [x] [Promote staging packages](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#promote-staging-packages)
* [x] [Update documentation](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#update-documentation)
* [x] Cookbook
* [x] Doxygen
* [x] [Update the SuperBuild archive](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#superbuild-archive)
* [x] Release Candidate announcement on the forum
## Release Candidate 2
### 1. Branches
* [X] Feature freeze: [create the new release branch](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#create-release-branch)
* [X] Make sure the version number in `CMakeLists.txt` is 8.0.0
### 2. Housekeeping
* [x] In this story, make a list of blocking issues for the release (if any)
* [x] Update release notes (walk the GitLab MR merged history and log all improvements)
* [x] Update the date in RELEASE_NOTES.txt
* [ ] Check [SonarQube](https://sonar.orfeo-toolbox.org/dashboard?id=orfeotoolbox-otb)
* [x] Run Debian [spelling](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#spelling-check) checker
* [x] Run shellcheck script from [OTB-Devutils/Scripts/](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb-devutils/blob/master/Scripts/run_shellcheck.sh)
* [x] [Update translation](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#translation-for-monteverdi-mapla) for Monteverdi and Mapla
* [x] [Sanity check the binary packages](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#standalone-packages-sanity-check)
* [x] Windows
* [x] Linux
* [x] Mac
* [x] Test QGIS on qgis docker image
### 3. Actual release
Once all blocking issues are closed, and the previous steps are done:
* [x] [Tag the release candidate](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#release-tag)
* [x] Update GIT_TAG for all official remote modules (if needed)
### 4. Publish and plan next release
* [x] [Prepare and upload source packages](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#prepare-and-upload-source-packages)
* [x] [Promote staging packages](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#promote-staging-packages)
* [x] [Update documentation](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#update-documentation)
* [x] Cookbook
* [x] Doxygen
* [x] [Update the SuperBuild archive](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#superbuild-archive)
* [x] Release Candidate announcement on the forum
## Release Candidate 3
### 1. Branches
* [x] Feature freeze: [create the new release branch](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#create-release-branch)
* [x] Make sure the version number in `CMakeLists.txt` is 8.0.0
### 2. Housekeeping
* [x] In this story, make a list of blocking issues for the release (if any)
* [x] Update release notes (walk the GitLab MR merged history and log all improvements)
* [x] Update the date in RELEASE_NOTES.txt
* [ ] Check [SonarQube](https://sonar.orfeo-toolbox.org/dashboard?id=orfeotoolbox-otb)
* [ ] Run Debian [spelling](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#spelling-check) checker
* [ ] Run shellcheck script from [OTB-Devutils/Scripts/](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb-devutils/blob/master/Scripts/run_shellcheck.sh)
* [x] [Update translation](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#translation-for-monteverdi-mapla) for Monteverdi and Mapla
* [ ] [Sanity check the binary packages](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#standalone-packages-sanity-check)
* [x] Windows
* [x] Linux
* [x] Mac
* [x] Test QGIS on qgis docker image
### 3. Actual release
Once all blocking issues are closed, and the previous steps are done:
* [x] [Tag the release candidate](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#release-tag)
* [x] Update GIT_TAG for all official remote modules (if needed)
### 4. Publish and plan next release
* [x] [Prepare and upload source packages](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#prepare-and-upload-source-packages)
* [x] [Promote staging packages](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#promote-staging-packages)
* [x] [Update documentation](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#update-documentation)
* [x] Cookbook
* [x] Doxygen
* [x] [Update the SuperBuild archive](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#superbuild-archive)
* [x] Release Candidate announcement on the forum
## Release
### 1. Branches
* [x] Make sure the version number in `CMakeLists.txt` is 8.0.0
### 2. Housekeeping
* [x] In this story, make a list of blocking issues for the release (if any)
* [ ] Fix compilation warnings on CI
* [x] Update release notes (walk the GitLab MR merged history and log all improvements)
* [x] Update the date in RELEASE_NOTES.txt
* [ ] Check [SonarQube](https://sonar.orfeo-toolbox.org/dashboard?id=orfeotoolbox-otb)
* [x] Run Debian [spelling](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#spelling-check) checker
* [ ] Run shellcheck script from [OTB-Devutils/Scripts/](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb-devutils/blob/master/Scripts/run_shellcheck.sh)
* [x] [Update translation](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#translation-for-monteverdi-mapla) for Monteverdi and Mapla
* [ ] [Sanity check the binary packages](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#standalone-packages-sanity-check)
* [ ] Windows
* [x] Linux
* [ ] Mac
* [ ] Test QGIS on qgis docker image
### 3. Actual release
Once all blocking issues are closed, and the previous steps are done:
* [x] [Tag the release](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#release-tag)
* [x] Merge the release into develop
* [x] Merge the release into master
* [x] Update GIT_TAG for all official remote modules (if needed)
### 4. Publish and plan next release
* [x] [Prepare and upload source packages](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#prepare-and-upload-source-packages)
* [x] [Promote staging packages](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#promote-staging-packages)
* [x] [Update documentation](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#update-documentation)
* [x] Cookbook
* [x] Doxygen
* [x] WordPress page "Home" and "Download" pages
* [x] Upload OTB source archive to [Zenodo](https://zenodo.org/) to create a unique Digital Object Identifier (DOI)
* [ ] [Update the SuperBuild archive](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/wikis/Help-for-release-actions#superbuild-archive)
* [x] Release announcement
* [x] On the [forum](https://forum.orfeo-toolbox.org/)
* [x] On the [blog](https://www.orfeo-toolbox.org/blog/)
* [x] On [Twitter](https://twitter.com/orfeotoolbox)
* [x] Forward announcement to news_item@osgeo.org ([OSGeo news](https://www.osgeo.org/foundation-news/))
* [x] Remove public branches related to MR or bugfix merged before the release8.0.0https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2233OTB plugin integration in QGIS >= 3.222022-02-07T08:32:43ZYannick TANGUYOTB plugin integration in QGIS >= 3.22### Target documentation resources
CookBook shall be updated to document recent QGIS changes in OTB plugin integration : https://www.orfeo-toolbox.org/CookBook/QGISInterface.html
### Change requested
QGIS 3.22 does not activate any mor...### Target documentation resources
CookBook shall be updated to document recent QGIS changes in OTB plugin integration : https://www.orfeo-toolbox.org/CookBook/QGISInterface.html
### Change requested
QGIS 3.22 does not activate any more OTB plugins (and some others) by default. As OTB plugin is an official plugin, it only needs to be activated (in the Plugins>Manage plugins menu) and then configured (as it used to be, in the Settings>Options menu).
This is a small change but users need to know how to reactivate OTB plugin.
Tests have been done on Ubuntu 20.04 / QGIS 3.22 RC / OTB 8.0a1 and it works fine.8.0.0https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/22328.0.0-alpha2 fails to build without Python2021-11-08T09:17:16ZBas Couwenberg8.0.0-alpha2 fails to build without PythonOTB 8.0.0-alpha2 fails to build without Python.
The issue is fixed by only looking for Python when `OTB_WRAP_PYTHON` is enabled:
[python.patch](/uploads/7639a2c054f6f182dd2ed6a957d572cd/python.patch)OTB 8.0.0-alpha2 fails to build without Python.
The issue is fixed by only looking for Python when `OTB_WRAP_PYTHON` is enabled:
[python.patch](/uploads/7639a2c054f6f182dd2ed6a957d572cd/python.patch)8.0.0https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2228Write no data as output in applications2021-11-05T10:49:26ZCédric TraizetWrite no data as output in applicationsSome applications still uses the itk::MetadataDictionary to store nodata information. While this work during the application, the metadata is not written in the output image at then end of the pipeline. For example this is the case with ...Some applications still uses the itk::MetadataDictionary to store nodata information. While this work during the application, the metadata is not written in the output image at then end of the pipeline. For example this is the case with the `Orthorectification` application.
Instead, the metadata `MDNum::NoData` should be used consistently inside the library8.0.0https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2226Wrap image metadata in SWIG2022-01-04T19:38:50ZCédric TraizetWrap image metadata in SWIG`ImageMetadata` sgould be wrapped in SWIG so metadata dictionaries can be accessed from Python. This would allow metadata manipulations in Python pipelines.
The whole ImageMetadata API should be exported, along with the metadata key enu...`ImageMetadata` sgould be wrapped in SWIG so metadata dictionaries can be accessed from Python. This would allow metadata manipulations in Python pipelines.
The whole ImageMetadata API should be exported, along with the metadata key enums. In addition, some metadata classes should be wrapped so they can be manipulated from Python (e.g. RPCParam, TimePoint, Duration).
Maybe we could use SWIG typemaps to wrap some of the exported types directly to Python types.8.0.0Julien OsmanJulien Osmanhttps://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2221Clean of elevation management geoid parameter2022-02-07T08:32:42ZaurelieemilienClean of elevation management geoid parameter### Description
This issue is a follow up of #2198
In the context of the [cars software](https://github.com/CNES/CARS), we are having troubles to unset the geoid parameter used in the otb applications.
CARS implements two homemade app...### Description
This issue is a follow up of #2198
In the context of the [cars software](https://github.com/CNES/CARS), we are having troubles to unset the geoid parameter used in the otb applications.
CARS implements two homemade applications that use the elevation management:
* [otbDEMReader](https://github.com/CNES/cars/blob/master/otb_remote_module/app/otbDEMReader.cxx) used in a CARS API function called [read_lowres_dem](https://github.com/CNES/cars/blob/master/cars/externals/otb_pipelines.py#L338)
* [otbConvertSensorToGeoPointFast](https://github.com/CNES/cars/blob/master/otb_remote_module/app/otbConvertSensorToGeoPointFast.cxx) used for example in the CARS API function [get_time_ground_direction](https://github.com/CNES/cars/blob/master/cars/core/projection.py#L574)
If several calls of the CARS API function are done in the same run session, the geoid parameter setting is not cleared between each otb application creation and execution. It seems that once `m_GeoidFile` is defined it is not unset when using [`DEMHandler::ClearDEM`](https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/blob/release-7.3/Modules/Adapters/OSSIMAdapters/src/otbDEMHandler.cxx#L111).
It might concerned usual otb application too but I couldn't print the geoid file path used by them (CARS also uses the `StereoRectificationGridGenerator` application).
### Steps to reproduce
Two consecutive calls of the application using the elevation management (I only tried with the CARS API function described above), one with the geoid file set and one without. The `m_GeoidFile` should be both time set to the first geoid file.
### Configuration information
Ubuntu, Centos, OTB 7.x (7.2), installation from binary version.8.0.0Cédric TraizetCédric Traizethttps://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2215Refactor the Superimpose PHR mode2021-09-06T18:54:59ZCédric TraizetRefactor the Superimpose PHR modeThe PHR mode of the `Superimpose` and `BundleToPerfectSensor` uses Ossim date utilities and keywordlist metadata. As part of the Ossim removal refactoring, it should be modified to use the new date and metadata classes. This include:
* ...The PHR mode of the `Superimpose` and `BundleToPerfectSensor` uses Ossim date utilities and keywordlist metadata. As part of the Ossim removal refactoring, it should be modified to use the new date and metadata classes. This include:
* Reading additional metadata (Sensor model characteristics section) of the dimap product
* Using these metadata in PleiadesPToXSAffineTransformCalculator
* Using otb::Metadata::TimePoint and otb::Metadata::Duration to manage date objects8.0.0Cédric TraizetCédric Traizethttps://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2214Implement the SARParam::ToJSON function2021-10-07T07:26:35ZJulien OsmanImplement the SARParam::ToJSON functionThe SARParam::ToJSON function still needs to be implemented.
We also need to implement a function to read from a JSON file (SARParam::FromJSON ?)The SARParam::ToJSON function still needs to be implemented.
We also need to implement a function to read from a JSON file (SARParam::FromJSON ?)8.0.0https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/2200Cannot set RAM parameter with SetParameters() function2021-07-06T13:47:50ZNicolas NarçonCannot set RAM parameter with SetParameters() functionIn Python, I want to set the RAM parameter (available memory for processing), using `SetParameters()` but it fails.
Small piece of code for reproducing the error :
```python
import otbApplication
app = otbApplication.Registry.CreateApp...In Python, I want to set the RAM parameter (available memory for processing), using `SetParameters()` but it fails.
Small piece of code for reproducing the error :
```python
import otbApplication
app = otbApplication.Registry.CreateApplication('BandMath')
app.SetParameters({'il': ['any_image.tif'], 'exp': 'im1b1', 'out': 'output.tif', 'ram': 512})
```
Error raised :
> NotImplementedError: Wrong number or type of arguments for overloaded function 'Application_SetParameterString'.
>
> Possible C/C++ prototypes are:
>
> Application::SetParameterString(std::string,std::string,bool)
>
> Application::SetParameterString(std::string,std::string)
It seems to fail in the `SetParameterValue()` function. Indeed, when looking at the code of `SetParameterValue` inside **otbApplication.py**, ParameterType_RAM is handled as a string whereas it should be handled as an int.
### Configuration information
OTB version 7.28.0.0