Ādaži digital twinInstitutional cockpitCurrent baseline, visible systems, and next institutional move.
Twin Base StudioPolisplexity / ĀdažiTwin Base StudioRiga planning region, Latvia
Workspace
Cockpitlive
Municipal
Public
Guidance
Theory
Docs
Cockpit controls

Use the inner rail to switch between base-only reading and inferred-seed reading, focus the map by bundle, and inspect whether a selected element belongs to the base twin or to an inferred semantic seed.

Map fidelity
Bring in more city detail

Low keeps only the clearest territorial baseline. High brings back more geometry and more inferred seed context.

Light58%Dense
Surface status
ViewerLoading
Visible systems0
Rendered0
Discovered0
Logical twin posture
This rail is not the base twin itself

Bundles, counts, selection logic, fidelity, and viewer state belong to the logical twin layer that makes the baseline manageable across map, 3D, and immersive surfaces.

Mouse controls
Move the twin naturally

Left drag rotates. Wheel zooms. Right drag pans. Click any object to inspect it.

Surface actions
Next semantic packs
Future packs attach here

Waste, WEO, SAMI, EO, or authority data should arrive as new semantic packs, not by rewriting the base layers.

Transport status
Current twin transport is local only

The current module uses an internal payload. Shared exchange standards such as NGSI-LD, JSON-LD, RDF, LDES, DCAT, or brokered federation still belong to the next architecture step.

Current selection
No live selection yet

Choose a road, building, route, or anchor inside the viewer to inspect whether it belongs to the base twin or to an inferred semantic seed.

Inner rail: logical-twin controls for presets, fidelity, base-vs-seed visibility, and layer toggles.
Institutional command surface

Twin Development Cockpit

Review what already belongs to the base twin, what the logical twin adds, what is only an inferred semantic seed, and what still remains outside the current transport layer.

Preparing live viewer
Institutional command surface

Twin Development Cockpit

Review what already belongs to the base twin, what the logical twin adds, what is only an inferred semantic seed, and what still remains outside the current transport layer.

LoadingMAP
Preparing the live MAP surface

Loading city data, counts, and viewer state so the module opens as a single coherent surface.

What the current cockpit already proves

The current cockpit separates public baseline geometry, lightweight logical-twin management, inferred semantic seeds, and still-pending transport/interoperability work instead of mixing them into one surface.

Next institutional move
Confirm the base geometry with the authority first.
Decide which inferred seed becomes the first formal semantic pack.
Add operational municipal data only after the base, logical, and seed story is accepted.
Current public source posture
OpenStreetMap / Overpass for public geometry, facilities, mobility points, green-blue systems, and candidate waste points.
Nominatim for the municipal reference and territorial anchor.
OSRM public routing as the first cheap access seed.
Twin derivations for grouped systems, counts, seed registers, and stage-ready inventory. These belong to the logical twin, not to the base geometry.