Elevation management tricky bugs

Description

Discussing with @ytanguy , I open a bug happening in cars 3D software.

We are using several OTB applications and it occurs that there are tricky behaviors when using elevation management API.

When using only one time or with the same dem, geoid or default_alt, the problem doesn't appear

But using several apps (different or not) with elevation interface seems to not reproduce the same results.

It appears that the first setting is not reset and we cannot put another one in next apps which takes.

This behavior is difficult to detect. For instance, the default_alt is not changing the result if elev.dem is set before. The default_alt is not stable when already used in another app, ...

Is there a way to reset the elevation management information between two apps usage ?

Thanks by advance. First Bug in OTB so don't hesitate to react, change this content if not clear. Emmanuel

Steps to reproduce

Take an OTB application with elevation management (Example ImageEnvelop) and launch it two times with two dem different and check values with Python interface in the same code.

Take two OTB application with elevation management (Example ImageEnvelop and ConvertSensorToGeoPoint) and see standalone results and when the two apps are sequenced in the same python file.

Reproducibility: always

Configuration information

Ubuntu, Centos, OTB 7.x (7.2), installation from binary version.