[Bug] TileMesh min and max elevation with multiple elevation layers

[jailln]

Min and max elevation values of a TileMesh node are wrong when there multiple elevation layers are added to the view

Context

TileMesh has an OBB which z min and max values are reset each time a new ElevationLayer is added to the view with the new ElevationLayer values (while it should consider all the elevation layers min and max values). Also, when removing one ElevationLayer from the view, the bbox min and max z values are set to 0,0 while they should be computed from the remaining ElevationLayers.

Possible Cause/Fix/Solution

We need to:

• Assess where this obb z min and max are used
• Properly set its values when there is multiple elevation layers (take the min and max of all elevation layers)
• Re-compute the min and max z values when there is multiple elevation layers instead of resetting them to [0,0]