Ask the renderer's query port for heights through the queries gateway

The Cesium scene's height service moves into the Cesium adapter
(src/render/cesium/heights.js), where the Cesium query port answers its
height members through it; the files still bound to the Cesium scene
import it from there.

src/queries/heights.js becomes the height gateway over the renderer's
query port: heightsOf(viewer) answers now, clampNow, batch, clampBatch and
supported as before, a miss is null, a failed or destroyed query rejects,
and exclusions are draw set ids. The source scan that keeps height queries
in one place still holds: outside the renderer, only the gateway asks for
streamed heights. The bikeshare layer samples its station heights through
it.

Heights leaves the allow-list.
This commit is contained in:
Sameh Khamis committed 2026-11-07 04:13:18 -08:00
1 parent 3abb05ec4b
commit e34e923ddd
22 files changed
+665 -248

No files matched your search

+1 -1
View File
@@ -45,7 +45,7 @@ import {
import { createOutlineRungs } from './outlineRungs.js';
import { unavailablePlaceSearch } from '../search/placeSearch.js';
import { isPickedWorldPosition } from '../data/scenePick.js';
import { heightsFor } from '../queries/heights.js';
import { heightsFor } from '../render/cesium/heights.js';
// The application operations entry reaches locations.js, whose flights go
// through the camera and query ports and which cannot load the Cesium adapter
// itself; this listed module loads the factories a viewer with no renderer