Files
gods-eye-view/docs/INFRASTRUCTURE-LAYERS.md
T
Sameh Khamis e3865f462f Merge origin/main into the renderer-contract branch: the procedural fleet models drawn through the renderer's model sets
Aircraft, military, local ADS-B, vessel, transit and rail models come from
the fleet model set, loaded up front and drawn life size through the draw
port's models sets; no layer touches the viewer or Cesium outside
src/render/cesium/. The models capability gains glTF bytes (gltf), a
per-axis stretch (axisScale), a colour for tinted parts (maskColor) and a
cut below the origin (clip: 'belowOrigin'), with conformance checks.

Main's rail layer and Data Library are ported to the ports; the CCTV
footprint probe keeps the globe-terrain clamp through the query port.
2026-11-13 14:14:42 -08:00

5.7 KiB

Reusing infrastructure layers

gods-eye-view/infrastructure exports createInfrastructureLayers(services). It returns fresh datacenter and dam layers in that order, with the existing IDs, appearance, label budgets and bundled public datasets. Importing the module or calling the factory does not load data, create a viewer, or start the application. The asset URLs resolve relative to the module; Vite rewrites them for production base paths. This browser source export expects a Vite-compatible asset build.

Pass the application's existing functions:

import { createInfrastructureLayers } from 'gods-eye-view/infrastructure';

const layers = createInfrastructureLayers({
  overlayHost: { setEntries, setVisible, clearSource },
  registerEntityContext,
  selectEntityContext,
  clearSelectedEntityContextForLayer,
  removeEntityContextsForLayer,
  governorRequestRender,
});

// Register these layers with the existing data-layer manager and viewer.
Function Arguments / responsibility
overlayHost.setEntries (sourceId, entries, options); publish the existing infrastructure overlay records and paint budget
overlayHost.setVisible (sourceId, visible); toggle a source
overlayHost.clearSource (sourceId); remove that source's overlay entries
registerEntityContext (entity, metadata); register selectable feature metadata, including the owning layer and data source
selectEntityContext (entity); select that registered feature
clearSelectedEntityContextForLayer (layerId, { evicted }); clear selection only if owned by this layer; evicted when its feature left the data
removeEntityContextsForLayer (layerId, { retainIds }); remove records owned by the layer on destruction or failed setup, or those a new feature set no longer has
getSelectedEntityContext optional; () the selected record, so replaceFeatures keeps a selection the new set still has
governorRequestRender (reason); request a frame through the existing render scheduler

Each returned layer supports init(viewer), enable(viewer), disable(viewer), update(viewer), destroy(viewer), getStats(), getLodDiagnostics() and getAnalystRecords(). Use the same viewer for the instance's entire lifetime. Each viewer/context/overlay host permits one live instance per layer ID; destroy an old instance before replacing it. Separate applications may use identical IDs with separate hosts. Callbacks must be ready before enable and remain usable through destruction.

Disable retains the loaded dataset for reuse and clears selection and listeners. Concurrent enables share one load. Destroy is permanent, aborts pending fetches, discards late results, and clears the owned draw sets, context records, overlays, input handler and listeners. The layer never creates an application context store, overlay host, viewer, or render scheduler. The consumer must resolve one compatible Cesium installation shared with its viewer; it must not bundle separate copies.

The layers draw, size their stems and fly the camera through the renderer's ports. A viewer the application has bound a renderer to needs nothing more; a Cesium viewer with no renderer bound loads gods-eye-view/render/cesium/unbound once first; until then the layer reports an error naming it, as it does for a dataset it cannot load. A selected feature is the context record its draw item carries as meta; the layer no longer sets the viewer's selectedEntity. While the renderer's own double-click follow is on, a double-click follows a point or polygon through the camera port, looking at the centre of what it draws (stem included), framed as the default renderer framed an entity it began following, and zooms to a line, which has no stem to follow. Features keep their own simplestyle fill, fill-opacity, stroke, stroke-opacity, stroke-width, marker-color and marker-size, given as hex, rgb() or hsl() colours or by the CSS colour names the default renderer knows (it has no rebeccapurple, and spells lavenderblush lavendar_blush); a marker-symbol is stamped on the pin as the default renderer stamped it: a one-character string as bold upper-case text, any other value as the Maki icon of that id from the renderer's assets, the plain pin when the icon cannot be loaded. The assets are found as the renderer finds them from a page script: the CESIUM_BASE_URL global, else the folder Cesium.js is loaded from; a page bundling Cesium as modules sets CESIUM_BASE_URL for icon pins. Polygons with heights are drawn at them, outlined; points with heights stand their pin on the stem's tip. Edges follow rhumb lines.

gods-eye-view/infrastructure/geojson exports the lower-level createLocalGeoJsonLayer(options, services) and existing infrastructure overlay helpers. Its options also take loadFeatures({ signal }), a loader resolving to GeoJSON features in place of url, and featureColor(properties), a CSS colour per feature for its fill, stem, dot, pin and label accent. The layer it returns also has dropCachedFeatures(), so the next enable loads again, and replaceFeatures(viewer, features), which draws a new feature set in place of the current one: the current one stays drawn until the new one is built, and stays if that fails (the call then rejects). gods-eye-view/infrastructure/lod exports the existing LOD policy helpers. Consumers use the package exports, which do not import standalone application globals.

Dataset files and source/license notices remain under src/data/local_data/. Their input counts are 4,352 datacenter features and 704 dam features. A multipart geometry draws as several parts, each with its own stem; part and stem counts are different measurements from feature counts. This change does not refresh or relicense the datasets.