3D initial heigth / collision avoid

[consta-v]

As discussed with @davidoesch here a customer feedback to consider for the collision avoidance definition for the new 3D viewer:

It looks like the viewer does not to "like" being started with cameras near the ground (this would be great for our purposes) and increases the elevation parameter automatically. For example, when started with "https://map.geo.admin.ch/?topic=ech&bgLayer=ch.swisstopo.pixelkarte-farbe&lon=7.38394&lat=46.96701&elevation=500&heading=62.992&pitch=-4", the rendering is performed as wanted, but the elevation is quickly changed to 566. Is there any possibility to disallow this initial initial behaviour?

It is clear to me that terrain-collision-avoidance leads to some increase in the camera-elevation when needed. My observation is that the lowest-allowed elevation rel. to the terrain is quite high, much higher at initialization (~70m larger in the example I sent; see link above) than it is during navigation. And note that the initial rendering is fully performed at the specified height of 500m; the mentioned height-correcting behaviour takes place only a few seconds after this successful rendering. Please, test it with the example-link I sent. In this example, there is clearly no collision at the specified height (successful rendering), but the camera-height is then automatically increased by 66m (to over 70m above the ground). Furthermore, after this correction takes place, it is possible to use mouse navigation to lower the camera to the specified height (and even to a few meters below the specified height).

Thanks for considering this wish, and thanks again for this great project.

Customer feedback ID : 2022020920013845

[davidoesch]

wichtig in 3d vor allem wenn mit dem geol viewer function parity gesucht wird