About the project

The diagram is titled “DT-aCoGo Data Space building blocks.”

It shows how different types of public and private data sources flow into the DT-aCoGo Data Space and then connect to an application ecosystem.

1. Data Sources: Public & Private (left side, blue header)

Two categories of yellow blocks:

• Contextual Data:
  • Water data
  • Traffic data
  • Utility data
  • BIM data
• Generic Data:
  • Climate data
  • Mobility data
  • Satellite data
  • Master registrations

2. DT-aCoGo Data Space (middle, blue header)

Contains several dark-blue and grey blocks:

• Open Urban Platform
• Trustbroker Connector-as-a-Service
• Landingzone NLDT-testbed (grey)
• OUP “City” hubs (blue circle)
• Product & Data Exchange

A note at the bottom says: “Recipes for automated and enforceable data preparation and contracts.”

3. Application Ecosystem (right side, blue header)

A list in a white box describes an appstore-like marketplace for:

• Data
• Tooling
• Services
• Models
• Recipes
• Etc.

4. Visual Notations

• Yellow boxes = different types of contextual or generic data.
• Dark blue boxes = key building blocks of the DT-aCoGo Data Space.
• Grey and circular boxes = supporting testbed and city hubs.
• Blue arrows show data flow:
  • From data sources into the DT-aCoGo Data Space.
  • From the DT-aCoGo Data Space into the Application Ecosystem.

The diagram is titled “DT-aCoGo: Workpackages.”

It shows the five main work packages (WPs) of the project, organized in colored boxes.

WP 1: Pilot Coordination (top, pink box)

Overall coordination of the pilot activities.

WP 2: Hub Set Up (left, light green box)

• 2.1 OUP “hubs” ready in pilot sites for use case deployment. Connecting stakeholders, data sources, viewers, etc.
  Output: data requirement inventory.
• 2.2 Timelapse viewing slider for 2D, 3D, and Unreal viewing installed.
• Checks and guidance by Governance & Ethical board.

WP 3: Model Usage (center, blue-grey box)

• 3.1 Interoperability between OUP and sectoral models realized.
  Inventory of data model requirements for usage in Replicable Recipe Format.
• 3.2 Timelapse viewing slider for 2D, 3D, and Unreal viewing validated.

WP 4: Recipe & Model2Model Trials (right, yellow box)

• 4.1 and 4.2 Replicable Recipe Template designed, trialed, and validated.
• 4.3 Report on:
  • Replicability
  • Human–machine readable functionalities
  • Usability within “Data Space blueprint” building blocks

WP 5: Communication & Dissemination (bottom, green box)

Sharing results through Community of Practice (CoP) and Cookbook.

Visual Notations

•  Pink box (top): Coordination task.
• Green, grey-blue, and yellow boxes (middle): Technical and functional work packages.
• Green box (bottom): Communication and dissemination.
• Sequential numbering (WP1–WP5): Work packages are meant to be executed in coordination but represent distinct areas of responsibility.

The diagram is a flowchart titled “Dataflow”. It shows how different spatial and environmental datasets flow into models for analyzing future urban conditions, such as rain effects, road closures, mobility, and heat stress.

Input datasets (left side):

These datasets are represented as separate boxes feeding into the central model.

• Buildings
• Terrain
• Trees
• BGT in 3D (Base Registrations for Large-Scale Topography)
• Roads
• Water & sewer system
• Other spatial data

Central model (top center):

• “(N&S) Current situation – Existing 3D City model – OUP”
  This represents the current urban digital twin model.

Pathways from the current situation:

• Leads into “New situation in 2040 – OUP” (a future scenario).
• Leads directly to “Heat stress? – Tygron”.
• Connects to the rain prediction and mobility analysis chain.

Future changes (left middle):

These feed into the “New situation in 2040 – OUP”.

• How to clear the area where you’re going to build?” → manual delete in current situation.
• BIM models in IFC, clearlyBIM or ESRI → imported as 3D tiles.
• New water & sewer system.
• New road network.
• New trees, BGT, etc.

Rain and mobility analysis chain (center):

• Predictive rain model (current + 2040) – Velen & Schuurmans
  • Output registered as OSC API features + vector tiles dataset in OUP.
• Closed roads analyses (e.g., >10 cm water on road) – Dat.mobility
  • Registered as OSC API features + vector tiles dataset in OUP.
• Mobility model effect of water on roads/traffic – Dat.mobility
  • Registered as OSC API features + vector tiles dataset in OUP.
• Unreachable destinations

Final integration (bottom center):

• Digital Twin with blocked roads after rain event – Unreal Viewer
  This combines unreachable destinations and other mobility outputs.

Connections to OUP Digital Twin (right side):

Multiple arrows show that Heat stress (Tygron), new situation in 2040, and the blocked road digital twin all connect into the OUP Digital Twin for visualization and integration.

Notes in diagram:

• “Creating new transformations in ESRI and/or FME from the OUP is out of scope.” (in red)
• “Use FME to fully automatically flow the input and the output of the models in orchestration.” (in green)

The diagram is titled “Data Space for Smart Communities.”

It shows how different types of data sources connect through federation, platforms, and catalogues, ending in shared European data spaces.

Data Sources (left side)

A green box labeled “Data sources – Public & Private.”

Below, two categories of data are shown in yellow:

• Contextual Data
  • Geo data
  • Mobility data
  • BIM planning and design data
  • Provider data
  • 3D city model
  • IoT platform data (examples: weather stations, sewage systems, slow traffic)
  • Asset management data
• Generic Data
  • Master registrations
  • Mobility data
  • Weather & water data models
  • Satellite data

Federation Layer (center top)

A turquoise box labeled “Federation layer.”

Connected to:

• Open Urban Platform
• DMI Products & Data Exchange
• Authorisation Policies store
• European SSCC Data Space

Open Urban Platform (center area)

A blue box with linked yellow modules:

• Open APIs (MIM1)
• Data transformation: Harmonise, integrate & distribute
• Catalogues (MIM2)
• DT-generator (MIM7)
• OUP Data & Application Marketplace (MIM4)
• OUP “City” hubs
• Landing zone NLDT testbed

DMI Products & Data Exchange (next to Open Urban Platform)

A blue box with yellow modules:

• D&P Catalogue
• Identification, Authentication, Authorisation
• Review: Data sharing rule book
• Logging
• Trust engine, etc. (MIM3)

Connected Registries & Catalogues (right side)

• Universal Trust Data Registry (blue, linked via MIM6)
• Federated Services Catalogue (blue, linked to Governance Schema)
• Governance Schema Data Cooperation (blue, with MIM8)

Notes at Bottom

A text note says: “Recipes for automated data preparation and enforceable contracts (human–machine readable).”

Visual Notations

• Yellow boxes = specific datasets, functions, or catalogues.
• Blue boxes = platforms, registries, or higher-level services.
• Red ovals labeled MIM1–MIM8 = standardised interoperability modules (Minimum Interoperability Mechanisms).
• Arrows show data flow between sources, platforms, catalogues, and registries.