City Walk/WissenZum StadtspaziergangViewer
ImpressumDatenschutz
Leitfaden
  • So funktioniert der Stadtspaziergang
  • Woher die Daten kommen
  • Quellen nach Stadt
  • Wie der Viewer zu einer Angabe kommt
  • Der Weg der Daten
  • Bedienung
  • Glossar
Guide (English)
  • How the city walker works
  • Where the data comes from
  • Sources by city
  • How the viewer comes by what it shows
  • From download to browser
  • Using the viewer
  • Glossary
Entwicklung (English)
  • docs/ — the project knowledge base
  • Rendering — how the data becomes pixels
  • Data pipeline — the bakes, the build step and the artifact contracts
  • Architecture decision records
    • ADR 0001: Static where possible — no database, no accounts, nothing kept about a visitor
    • ADR 0002: Imperative three.js inside a React shell, not react-three-fiber
    • ADR 0005: Data stays in its provider's UTM zone, under one recenter offset and a rotated world group
    • ADR 0009: Light, shadows and post — soft PCF redrawn on demand, four concentric rings, a baked horizon for the far field, a fixed lamp pool
    • ADR 0010: The look — opaque clay on a painted ground, colours within one palette, detail drawn softly
    • ADR 0012: Sources — official data first, OSM and Wikidata for what it lacks, named stand-ins marked per city
    • ADR 0018: Headless tests run a lite profile and count frames; visuals are judged on a real GPU through snapshots
    • ADR 0021: docs/ is published as /wissen, and its diagrams are prerendered SVG
    • ADR 0024: The build bakes each city into a 3D Tiles tileset that streams around the camera
    • ADR 0027: WebGPURenderer and TSL node materials, one path, public API only
    • ADR 0030: The ground — a TIN of the native DGM, its static parts baked in, every part meeting it by one set of rules
    • ADR 0032: The camera is never below the ground or inside a building
    • ADR 0034: Picture styles are one post pass over the clay scene, reading the light and the world
    • ADR 0036: Buildings are LoD2; geometry beyond it only where a measurement and a name agree, and roofs that miss the scan are rebuilt in its form
    • ADR 0037: Cities, providers and the pipeline — fetch, bake, build; one deployment, a route per city
    • ADR 0040: Data layers are switches, off at start, drawn as glass; optional features start on first use
    • ADR 0041: Rails, trams and bridges — decks measured in the surface model, every line on a drivable profile solved by the build
    • ADR 0042: The twin answers on demand — facts and provenance ride in the tileset, text appears only when asked
    • ADR 0043: Crash and page reports go to an error tracker without an SDK, and the privacy page says what the code does
    • ADR 0044: Modell — the city in parallel projection, every pass reading the camera through a lens
    • ADR 0047: Every device gets a budget in true bytes, a phone's memory never grows, and a device that lost its GPU gets a lighter page
    • ADR 0048: A network failure is retried for a budget of the page's visible time, never decided at once
    • ADR 0054: A planner's design is loaded on the device, placed by its coordinates or by hand, and stands in for the buildings it covers
    • ADR 0055: What the twin knows is baked as files; walks are written ahead, their narration marked, every claim sourced
    • ADR 0056: Frag die Stadt runs on the visitor's own key, through one stateless function with a fixed prompt and fixed tools
    • ADR 0057: The Sprachführer speaks and listens with the browser's own voice, and the scene rests while it does
    • ADR 0059: One schema per file a bake hands over, checked by the build
    • ADR 0060: Glass fronts are read from street photos by an open image model, offline
    • ADR 0061: The scene runs in a worker; the page hosts it
  • Data → feature provenance
  • Transformation catalog
  • Portability — rendering any location, with whatever data it has
  • Writing a walk
  • Routines: the twin's scheduled agents
  • Implementation plans, backlog and audit history
  • What the data streams carry that the walker does not use yet
Contents
Leitfaden
  • So funktioniert der Stadtspaziergang
  • Woher die Daten kommen
  • Quellen nach Stadt
  • Wie der Viewer zu einer Angabe kommt
  • Der Weg der Daten
  • Bedienung
  • Glossar
Guide (English)
  • How the city walker works
  • Where the data comes from
  • Sources by city
  • How the viewer comes by what it shows
  • From download to browser
  • Using the viewer
  • Glossary
Entwicklung (English)
  • docs/ — the project knowledge base
  • Rendering — how the data becomes pixels
  • Data pipeline — the bakes, the build step and the artifact contracts
  • Architecture decision records
    • ADR 0001: Static where possible — no database, no accounts, nothing kept about a visitor
    • ADR 0002: Imperative three.js inside a React shell, not react-three-fiber
    • ADR 0005: Data stays in its provider's UTM zone, under one recenter offset and a rotated world group
    • ADR 0009: Light, shadows and post — soft PCF redrawn on demand, four concentric rings, a baked horizon for the far field, a fixed lamp pool
    • ADR 0010: The look — opaque clay on a painted ground, colours within one palette, detail drawn softly
    • ADR 0012: Sources — official data first, OSM and Wikidata for what it lacks, named stand-ins marked per city
    • ADR 0018: Headless tests run a lite profile and count frames; visuals are judged on a real GPU through snapshots
    • ADR 0021: docs/ is published as /wissen, and its diagrams are prerendered SVG
    • ADR 0024: The build bakes each city into a 3D Tiles tileset that streams around the camera
    • ADR 0027: WebGPURenderer and TSL node materials, one path, public API only
    • ADR 0030: The ground — a TIN of the native DGM, its static parts baked in, every part meeting it by one set of rules
    • ADR 0032: The camera is never below the ground or inside a building
    • ADR 0034: Picture styles are one post pass over the clay scene, reading the light and the world
    • ADR 0036: Buildings are LoD2; geometry beyond it only where a measurement and a name agree, and roofs that miss the scan are rebuilt in its form
    • ADR 0037: Cities, providers and the pipeline — fetch, bake, build; one deployment, a route per city
    • ADR 0040: Data layers are switches, off at start, drawn as glass; optional features start on first use
    • ADR 0041: Rails, trams and bridges — decks measured in the surface model, every line on a drivable profile solved by the build
    • ADR 0042: The twin answers on demand — facts and provenance ride in the tileset, text appears only when asked
    • ADR 0043: Crash and page reports go to an error tracker without an SDK, and the privacy page says what the code does
    • ADR 0044: Modell — the city in parallel projection, every pass reading the camera through a lens
    • ADR 0047: Every device gets a budget in true bytes, a phone's memory never grows, and a device that lost its GPU gets a lighter page
    • ADR 0048: A network failure is retried for a budget of the page's visible time, never decided at once
    • ADR 0054: A planner's design is loaded on the device, placed by its coordinates or by hand, and stands in for the buildings it covers
    • ADR 0055: What the twin knows is baked as files; walks are written ahead, their narration marked, every claim sourced
    • ADR 0056: Frag die Stadt runs on the visitor's own key, through one stateless function with a fixed prompt and fixed tools
    • ADR 0057: The Sprachführer speaks and listens with the browser's own voice, and the scene rests while it does
    • ADR 0059: One schema per file a bake hands over, checked by the build
    • ADR 0060: Glass fronts are read from street photos by an open image model, offline
    • ADR 0061: The scene runs in a worker; the page hosts it
  • Data → feature provenance
  • Transformation catalog
  • Portability — rendering any location, with whatever data it has
  • Writing a walk
  • Routines: the twin's scheduled agents
  • Implementation plans, backlog and audit history
  • What the data streams carry that the walker does not use yet
Entwicklung (English)

ADR 0036: Buildings are LoD2; geometry beyond it only where a measurement and a name agree, and roofs that miss the scan are rebuilt in its form

  • Status: accepted
  • Date: 2026-09, rewritten 2026-10

Context

LoD2 is the building model: footprints from the cadastre, roofs fitted to a laser scan as the nearest catalogue type. It leaves out slim structures (chimneys, masts, towers), lags new buildings by a year or more, and draws complex buildings it cannot fit as a few non-planar polygons — a hotel of flat roofs as a crumpled tent, a new block as a 3 m placeholder. The surface model DOM1 sees everything that stands, but most of what it adds is trees, pylons and the cranes of the flight day.

Decision

  1. New volumes need a measurement and a name. DOM1 measures, OSM or Wikidata names: a column (chimney, tower, mast, water tower) where OSM maps one and the scan rises there; a missing building where OSM maps an outline LoD2 barely covers and the scan fills it; a roof on posts where OSM maps a roof and DOM1 shows a level surface. The shape is simple and measured, never a modelled likeness. A tower LoD2 already draws is not added again.
  2. A landmark's roof relief (a Wikidata item matched to LoD2 objects) is the one gap drawn without its own outline: the measured height field above its highest LoD2 roof, where the excess is large.
  3. A LoD2 roof that misses DOM1 is rebuilt inside its own footprint (pipeline/bake/roofs.py), only where the rebuild fits the scan clearly better and the footprint is not out of date. A LoD2 roof whose form the scan confirms is kept, even when its level is off. The rebuild follows the scan's form — measured faces where it slopes, flat levels elsewhere, walls where parts meet — under the object's own id, so its row, tint, picking and demolish stay.
  4. Rebuilt parts are architectural, not raster-shaped: no part narrower than a few metres, outlines straight rather than on the 1 m grid, running along the footprint's walls and meeting at corners, steep flanks drawn as faces.
  5. A face is drawn in a form roofs are built in, or not at all: first as the flanks of a pitched roof — one plane a wing, however its dormers break the scan, and a section of its own only for each house of a row or bend of a wing, rising from an eave, level along it, a lower roof beside it meeting it at a wall along the eave, opposite flanks meeting at a level ridge, every ridge, hip and valley where its two planes cross, dormers left to their own step — where its feet lie along the eaves; else as planes turned the ways one roof's flanks turn, or as one profile extruded along an axis (a barrel, a shed's curve). The scan's own surface — a dome, a hall's ribbed vaults — only on a landmark, where Wikidata vouches that the building is that unusual. A face the scan shows in no such form goes back to flat levels.
  6. Where the scan predates a building OSM maps, the mapped height stands, guarded by OSM's date and the outline's coverage.
  7. Every rule is general. No list of buildings, no per-building fix.

Consequences

  • Free-form complexes and new buildings read as what they are; a city gets its chimneys and towers from fetch → bake → build.
  • What OSM does not map is not drawn, even where the scan shows it.
  • A new LoD2 edition or scan means re-running roofs and then skyview.

Alternatives

  • Every gap from the surface model alone: cranes, pylons and crowns become towers.
  • Hand-modelled landmarks or models from 3D warehouses: not repeatable, licensed per model, and a detailed look the clay cannot absorb.
  • Re-triangulating LoD2's non-planar polygons: they describe a tent.
  • Rebuilding every tdcFreeFormRoof: most fit the scan; the gate measures the fault instead of trusting the label.
  • Stepped flat blocks or 1 m cells: contour terraces on every dome and vault, or a mesh 70 % larger.
  • LoD1 from the scan everywhere: throws away the 98 % of roofs LoD2 gets right.
  • The scan's surface, smoothed, on every face: tiles, dormers and the edges' blur read as a crumpled blanket over ordinary pitched roofs (An der Frauenkirche 5).
  • Planes grown from the scan as the first form: on a street of town houses every dormer breaks a plane, and the face fell apart into slivers and blobs (the block at Schloßstraße and Sporergasse).
Previous
ADR 0034: Picture styles are one post pass over the clay scene, reading the light and the world
Next
ADR 0037: Cities, providers and the pipeline — fetch, bake, build; one deployment, a route per city
Source on GitHub: docs/adr/0036-lod2-roofs-that-miss-the-scan-are-rebuilt.md
On this page
  • Context
  • Decision
  • Consequences
  • Alternatives