1. A concise explanation of the problem you’re experiencing.
We have some 3D tile datasets which extend below the surrounding default (Ion) terrain. For example a mining pit which has been dug deeper than at the time the default terrain data was captured.
We also have some 3D tile datasets which sit on top of the surrounding default terrain, but which show a negative camera height, e.g. -32.239458 (south), 115.77787 (east) shows a terrain height as -27m
In both these cases, if the camera is well above the ground height it operates as expected, but as you zoom in on the details it either reaches a point where it stops (i.e. you can’t descend any lower/closer, even though still well above the 3D tile data) and/or the rotation changes so instead of rotating around the mouse pointer location it changes to be an angular rotation around the camera’s own location.
I think this is a collision with the behaviour to prevent the cesium camera from descending below the terrian, but is there a workaround for these cases where it is valid to do that?
2. A minimal code example. If you’ve found a bug, this helps us reproduce and repair it.
I might be able to extract a minimal example, but currently entrenched in a lot of surrounding code and data, but hoping this is a known issue to discuss?
3. Context. Why do you need to do this? We might know a better way to accomplish your goal.
It is valid for some datasets to be below what Cesium considers to be the terrain surface, while still being above ground, e.g. open-cut mines
4. The Cesium version you’re using, your operating system and browser.
Cesium v1.50, Chrome on windows+osx
