Public, municipal and provider sources enter through bounded workflows.
City-controlled infrastructure
OPEN LOCAL
DIGITAL TWIN.
A self-hosted runtime for turning governed city evidence into spatial queries, specialist model outputs, reusable workflows and inspectable 2D, 3D and Civic XR experiences.
PUBLIC VERSIONv0.2.0 RCApache 2.0
CANONICAL CITYPostgreSQL
+ PostGISidentity · context · geometry · provenance
+ PostGISidentity · context · geometry · provenance
DATA FACTORY / INTAKELocal, remote, offline, cloud and HPC sources.
Every intake keeps its origin and consolidation rules.
DEPLOYLocal · server · VPS · cloud
QUERYTwinQL · CQL2 · guarded SQL
VIEWMapLibre · Cesium · Civic XR
AUTHORITYSource ≠ model ≠ city decision
2.0CITY SERVICES / BOUNDED WORKFLOWS
Begin with the decision
FROM A
CITY QUESTION
TO A SERVICE.
OLDT is not tied to one dashboard or sector. A deployment starts with a workflow owner, governed evidence, a returned result and an explicit validation boundary.
S–01Planning + digital constructionPROPOSAL PATH+
Connect planning cases, parcels, GIS constraints and BIM/IFC evidence into an inspectable review artifact. Tallinn is part of a submitted TR-LDT proposal; it is not presented as an awarded deployment.
- Planning case
- GIS constraints
- BIM / IFC evidence
- Review artifact
S–02Resilience + reconstructionPROPOSAL / RESEARCH+
Relate hazard evidence, built environment, shelters, access routes and critical services. Gaziantep is part of the submitted TR-LDT proposal; Kharkiv remains a strategic research route.
- Hazard evidence
- Built environment
- Access + shelters
- Preparedness service
S–03Mobility, climate + public assetsCROSS-SECTOR PATH+
Reuse one governed evidence base across movement, evacuation, heat, air quality, flood, heritage and infrastructure analysis while keeping model method, version and uncertainty attached.
- Networks + sensors
- Models + simulation
- Indicators
- Operations + scenarios
S–04Readiness + continuityDELIVERY GATE+
Qualify the workflow owner, data authority, hosting, security, procurement, financing and continuity route before claiming deployment readiness.
- Workflow owner
- Data authority
- Hosting + security
- Funding + continuity
3.0PRODUCT ARCHITECTURE
A governed urban record
ONE CITY
RUNTIME.
CLEAR BOUNDARIES.
Source evidence, consolidated entities, inferred semantics, provider results, model outputs and city-authoritative decisions remain distinct and traceable.
Architecture index ↗CANONICAL STORECITY
RECORDPostgreSQL + PostGIS
RECORDPostgreSQL + PostGIS
Stable identity, relations, cohorts, areas and scenario worlds.
TwinQL, CQL2, SQL and provider-neutral output contracts.
Selections, passports, manifests, APIs and viewer artifacts.
A–01Canonical city storePostgreSQL / PostGIS
A–02Governed intakesource / authority
A–03Query + evidenceTwinQL / CQL2 / SQL
A–04Models + scenariosversion / confidence
A–05Standards + APIsexchange / reuse
A–06Operator surfaces2D / 3D / XR
4.0INTEGRATION SURFACE
The representation changes; the evidence does not
ONE RECORD.
MANY
SURFACES.
A specialist service declares what it consumes, what it returns, which method and version it used, and where its authority ends.
GIS · BIM · sensors · catalogues · satellite · providers
spatial query · model · simulation · indicator
grid · vector · trajectory · scenario · alert
cockpit · MapLibre · Cesium · Civic XR · Canvas
OUTPUT CONTRACTmethod
version
provenance
validation
version
provenance
validation
DCATNGSI-LDOGC API FEATURESGEOJSONCITYJSONMODEL OUTPUTS
5.0EU LDT TOOLBOX / LAB COMPATIBILITY
Compatibility, not certification
12 TOOLS.
ONE
LAB.
The complete toolbox bundle was installed in a local compatibility environment. Nine tools have an accepted OLDT scenario path; Integrated Environment was evaluated as a launcher, while Participate and Federated Learning remain future direct integrations.
Official EU repository ↗01Data Modellerscenario path
02Data Space Readyscenario path
03AI Notebookscenario path
04Innovation Plannerscenario path
05Integrated Environmentlauncher evaluated
06Federated Learningfuture direct integration
07Use Casesscenario path
08Data Platformscenario path
09Participatefuture direct integration
10Identityscenario path
11Marketplacescenario path
12Play + Visualisescenario path
Accepted scenario pathLauncher evaluatedFuture direct integration
6.0PRODUCT RESOURCES
Public by inspection
INSPECT
BEFORE
DEPLOYING.
The public release is suitable for installation, source review, interoperability work and bounded partner testing. Municipal production use requires local hardening, governance, security, capacity planning and authority acceptance.
RELEASE BOUNDARYTechnical release candidate ≠ production acceptance.
Use the public release to inspect, install and test. Define authority, privacy, hosting, security, validation and continuity before municipal deployment.
7.0START A CITY WORKFLOW
The first output is a fit brief
START WITH
ONE REAL
WORKFLOW.
The first conversation should resolve what must improve, who owns the decision, which evidence exists and what the returned result must make possible.
- 01WorkflowDECISION
What should become faster, safer or better informed?
- 02OwnerAUTHORITY
Which municipal team uses and validates the result?
- 03EvidenceSOURCES
What data and systems exist, and who controls them?
- 04ModuleSERVICE
What must be ingested, computed and returned?
- 05BoundaryCONTROL
Hosting, privacy, security and publication rules.
- 06DeliveryROUTE
Resources, procurement, adoption and continuity.