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

+6
View File
@@ -48,6 +48,12 @@
import * as Cesium from 'cesium';
import { heightsFor } from '../render/cesium/heights.js';
// The application operations entry reaches the annotation resolver and
// locations.js, whose flights and heights go through the camera and query
// ports and which cannot load the Cesium adapter themselves; this listed
// module, on the same entry, loads the factories a viewer with no renderer
// bound gets them from.
import '../render/cesium/camera.js';
/** Taxi threshold: a cached snap answers directly for moves up to this far from
* the sampled spot (m). Past it the value is demoted to a held last-known and a