refactor(maps): use the globe engine

MapSourceController (and MapStackController) take the page's globe
engine: a globe stack becomes engine.maps.setBaseImagery with the
controller's ready provider and credit, then setPhotorealTiles(null),
then setTerrain with the cached terrain; a 3D stack becomes
setPhotorealTiles with its tileset and credit; owned tilesets are
released through maps.releasePhotorealTiles before disposal. The
controller keeps its provider/terrain/tileset caches, construction and
tile-failure fallbacks, switch generations and error watch. The scene
builds its map stack controller with its engine; without an engine the
controller applies sources to the viewer as before. The photoreal-to-
globe sequence (imagery, credit, globe, tileset) is tested end to end on
the Cesium engine.
This commit is contained in:
German Khokhlov committed 2026-10-15 18:40:19 +04:00
1 parent 83c13f330d
commit 3e3aa0bd9f
4 files changed
+258 -7

No files matched your search

+2
View File
@@ -105,6 +105,8 @@ export async function createApplicationScene({
const mapStackController = new MapController(viewer, {
requestRender: governorRequestRender,
// Map sources reach the scene through the globe engine's maps.
engine,
...mapOptions,
googleTileset: tileset,
cesiumToken,