Ask heights through the gateway at the flight sites, and load the camera factory from ground snapping

The camera ground guard, place and landmark flights and imported-file
flights read terrain and surface heights through heightsOf, the one place
the app's height queries go, rather than asking the query port themselves.

With the annotation resolver off the allow-list, ground snapping, which
the application operations entry also reaches and which stays listed,
loads the Cesium camera factory for a viewer with no renderer bound.

The height docs say what the Cesium renderer answers without depth
textures: no surface or tiles height, and terrain from the loaded tiles.
This commit is contained in:
Sameh Khamis committed 2026-11-07 04:19:56 -08:00
1 parent f509c688e8
commit 8c024f5ea7
6 files changed
+34 -22

No files matched your search

+4 -3
View File
@@ -12,9 +12,10 @@
* request error, a destroyed scene), so a caller can tell a failure from
* points that are merely uncovered.
*
* What the renderer cannot answer is a miss: the Cesium renderer answers no
* height, terrain included, without depth textures (its `sampleHeight`
* capability).
* What the renderer cannot answer is a miss: without depth textures (its
* `sampleHeight` capability) the Cesium renderer answers no `'surface'` or
* `'tiles'` height; `now()` still answers `'terrain'` from the globe's
* loaded tiles.
*
* `against` picks the surface: `'surface'` is what is drawn (tiles, the
* globe, and draw sets drawn as ground), `'terrain'` the terrain alone,