Project references

Reference Notes and Documentation

Surface the notes, source posture, semantic-pack roadmap, viewer posture, and interoperability path so the twin can be reviewed as a real institutional product.

Reference surface

Territorial scope

Live

The current Ādaži area and municipal boundary are loaded from the active public payload.

Named streets

Live

Road counts and street-name coverage are derived from the current Ādaži geometry feed.

Built fabric

Live

Building counts and volumetric approximations are computed when the Ādaži twin payload is ready.

Inferred semantic seeds

Live

Civic, mobility, daily-economy, waste, and route seeds are recalculated for the active Ādaži workspace.

City brief

Ādaži, Latvia, Riga planning region.

Ādaži public-data base twin, lightweight logical twin, inferred semantic seeds, and a separate interoperability path.

The current Ādaži workspace starts from public territorial geometry, organizes it into a logical twin, exposes inferred semantic seeds honestly, and keeps data transport and interoperability as a separate architecture track for later growth.

Institutional document pack

Ādaži base twin brief (Institutional note): What is geometry, provenance, and baseline fact in the current city twin.

Semantic seed register (Domain note): What is already interpreted semantically from public data and what still needs formal enrichment.

Interoperability posture note (Architecture note): What exists today for transport and what still needs standards, cataloging, and exchange design.

Viewer surface register (Product note): What each viewer shows from the base twin, the logical twin, and the inferred semantic seeds.

WS2 pilot-detail alignment note (Compliance note): How the current product explains data lifecycle, seven-layer management, and semantic interoperability posture.

Semantic pack roadmap (Growth note): Which future packs can attach next without rebuilding the base and logical twin.

Current product posture

Base twin: active and visible.

Logical twin: active through layer definitions, bundles, counts, and viewer state.

Semantic seeds: visible, but still inferred from public data.

Interoperability: still pending as a formal exchange and federation layer.

Delivery and viewer posture

Jampack provides the application shell, module navigation, theme handling, and responsive app structure.

Next serves the digital twin routes while Express keeps the auth, API, and live viewers in the same product boundary.

Map, 3D, and immersive remain product-native viewers because they are the differentiating surfaces of the twin.

All three viewers start from the same active-city payload, but each one filters and stages it differently according to base, logical, and inferred semantic reading.

Future semantic packs should attach to the current base and logical twin without changing the shell.

Current source and derivation register

Source	Category	Scope	Status
OpenStreetMap / Overpass	Base geometry source	Roads, buildings, facilities, places, and green-blue geometries for Ādaži.	Feeds the public base twin.
Nominatim	Base administrative reference	Municipal lookup and territorial anchor for Ādaži.	Feeds scope and city reference.
OSRM public routing	Derived access seed	First route geometry and reach proof for the active Ādaži workspace.	Feeds a semantic access seed, not an authority route product.
Local classification logic	Semantic seed derivation	Civic, mobility, commerce, waste, and route interpretation from public inputs.	Feeds inferred semantic seeds only.
Twin Base payload	Logical twin output	Inventory, bundles, counts, viewer state, and scene-ready structures.	Feeds the current product surface, not yet the interoperability layer.

Current layer taxonomy

Layer	Type	Count	Source	Status	Reading
Municipal boundary	Base layer	Live	Nominatim + OpenStreetMap polygon reference	Active in the current Ādaži public base twin	Administrative scope and municipal footprint.
Road network	Base layer	Live	OpenStreetMap / Overpass highway geometry	Active in the current Ādaži public base twin	Ways, named streets, and the first access structure.
Built fabric	Base layer	Live	OpenStreetMap / Overpass building geometry	Active in the current Ādaži public base twin	Footprints and lightweight volumetric reading.
Green-blue systems	Base layer	Live	OpenStreetMap / Overpass leisure, landuse, natural, and water features	Active in the current Ādaži public base twin	Parks, woods, water, recreation, and landscape context.
Settlements and places	Base layer	Live	OpenStreetMap place points	Active in the current Ādaži public base twin	Named places and locality markers for territorial orientation.
Civic anchors	Inferred semantic seed	Live	Public OSM feature classification	Visible as inferred meaning, not authority-grade semantics	Town hall, schools, healthcare, library, and public-service anchors.
Mobility anchors	Inferred semantic seed	Live	Public OSM feature classification	Visible as inferred meaning, not operational transport data	Stops, parking, charging, and access-supporting points.
Daily economy	Inferred semantic seed	Live	Public OSM feature classification	Visible as inferred meaning, not commercial operations data	Shops and activity points that reveal everyday urban demand.
Waste and street seeds	Inferred semantic seed	Live	Public OSM feature classification	Seed only; not yet a formal waste semantic pack	Recycling and cleanliness points that bridge toward the first service layer.
Base route	Inferred semantic seed	1	OSRM public routing result	Derived access seed, not yet an authority routing product	Reference route toward a current Ādaži institutional anchor.

Viewer surface register

Surface	Base twin shown	Logical twin shown	Semantic seeds shown	Transport posture
Cockpit / Map	Boundary, roads, buildings, green-blue systems, places, and route geometry	Layer bundles, inventory counts, selected-object metadata, fidelity controls, and map state	Civic, mobility, commerce, waste, and route seeds when the corresponding bundle is enabled	Local payload only. No shared catalog or semantic exchange model yet.
Municipal / 3D	Simplified boundary, roads, buildings, green-blue context, and place references	LOD scene payloads, camera presets, bundle switching, and scene inventory	Civic, mobility, commerce, waste, and route seeds inside the spatial operations reading	Local scene payload only. Not yet brokered or standardized for exchange.
Public / Immersive	Recognisable streets, buildings, public realm, and orientation elements	Walkthrough state, tour stops, visible-layer bundles, and fidelity management	Only the simpler explanatory seeds needed for civic storytelling	Local walkthrough payload only. No external exchange layer yet.

Current semantic seed register

Seed	Current basis	Current meaning	Future enrichment
Civic anchors	Public facility classification	Public-service baseline	Authority service metadata, demand, quality, incidents
Mobility anchors	Public mobility point classification	Access and reach baseline	Traffic, restrictions, multimodal operations, service times
Daily economy	Public shop and activity classification	Daily urban demand and street-use hints	Intensity, service demand, waste generation, frontage logic
Waste and street seeds	Public waste-related points	First waste-service bridge	Collection logic, hotspots, service zones, actions
Base route	Public router result	Service-access proof	Authority routes, constraints, fleet logic

Interoperability and transport register

Topic	Current status	What exists now	Next step
Shared model	Not formalized	Internal JSON payload and viewer structures	Define the shared data model for the pilot
Catalog and discoverability	Not formalized	Human-readable docs and source register	Add DCAT-ready metadata and publication posture
Exchange format	Not formalized	Internal JSON only	Prepare NGSI-LD / JSON-LD / RDF transport path
Context and broker layer	Not active	No context broker in the current prototype	Evaluate a brokered layer when the pilot semantics are agreed
Federation path	Not active	Single-city local twin instance	Define reuse and exchange between pilot members

Future semantic pack roadmap

Pack	What it adds	Probable inputs
Municipal waste pack	Waste semantics, economics, service zones, and street-cleanliness logic	Authority operations, field observations, inferred demand, route logic
WEO pack	Water and environmental semantics on top of a new physical observation layer	Space or remote observation, environmental models, water semantics
SAMI pack	Additional operational or AI-driven city semantics	Partner domain models, derived intelligence, service workflows
EO / satellite pack	New physical observation layer before further semantics	Satellite imagery, remote sensing, raster-derived products

WS2 pilot-detail alignment register

Requirement	Manual expectation	Current platform posture
Rq2 data lifecycle	Describe tools, standards, components, and the data lifecycle from collection to use and sharing.	Theory and Docs separate collection, normalization, semantic interpretation, transport, and reuse.
Rq13 seven LDT layers	Each authority should control one LDT instance through management interfaces across all seven layers.	The product distinguishes source data, acquisition, knowledge logic, interoperability, services, orchestration, and visualisation even if not all are fully implemented yet.
Rq17 semantic interoperability	Ensure semantic interoperability of exchanged data through open standards such as NGSI-LD or LDES.	Semantic seeds are explicit, but transport remains local. The interoperability register keeps NGSI-LD, JSON-LD, RDF, LDES, and DCAT as future obligations, not fake current features.
Rc7 catalog and broker posture	Prefer DCAT cataloging and a context broker capable of JSON-LD, RDF, or NGSI-LD.	Documented as pending architecture. The product makes this visible instead of mixing it into the base twin.

Source