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 0010: The look — opaque clay on a painted ground, colours within one palette, detail drawn softly

  • Status: accepted
  • Date: 2026-06, rewritten 2026-10; the glass veto lifted 2026-11

Context

The default picture is the product: a pastel, archviz city of clay on paper. Earlier building styles (raw LoD colours, transmissive "ghost" glass) doubled every shader or rendered the scene twice. A procedural window grid read as an office block over historic silhouettes; raw OSM colours put a signal-red facade into a pastel city. Detail has to come from data, read the same on every house, and stay calm.

Decision

  1. One building material: opaque clay with a per-building tint and the facade terms of the clay shader. No transmission, no textures, no second building style. Other looks are picture styles over the frame (ADR 0034).
  2. Colour comes from data and stays in the palette. Roofs from the orthophoto under each roof, lifted by a hue-preserving vibrance; walls from OSM colour, else material family, else use. A mapped colour keeps its hue with capped saturation and held lightness. Glass and metal are object flags with a subtle response, not a texture.
  3. The ground is painted at runtime from one palette (lib/city/landcover.ts): the bake writes class ids only, so a colour change is a code change, not a re-bake.
  4. Windows are drawn by the clay's fragment shader on every house — a recess with a sill, its back a muted pane that mirrors a little sky at a grazing view. Their rhythm per building is measured where open street photos saw it (Panoramax, Mapillary — never Google Street View), else a neighbour's, else its type's. None on party walls, over doors or a measured shopfront; a monumental facade gets no town-house windows (listed palaces a kind of their own, churches none). No window row below the ground in front of the wall. Within 250 m the openings are cut and real niches stand behind them, laid on the shader's own grid, so drawn and real windows are one window; a house turns as a whole, never a wall in part.
  5. Facade parts are soft, abstract geometry: plinths, cornices, doors from OSM entrances, dormers, shop fascias — rounded profiles, never hard bevels, relief lit from above and never darker than the wall. Landmarks get none of the generic parts.
  6. Glass where it helps the facade read: a shop window is an opening cut into its wall, reveals in the wall's clay and glass at its back, as a window is a recess (a real one at every distance, as wide as the measured bay). Panes and glass walls mirror the street's skyline and the sky above it, read from the baked horizon — a stand-in house below the skyline, never a second render of the scene. A glass wall shows its frame — mullions and a transom a storey — the one grid on a facade.
  7. Night: walls do not glow; every unlit or additive layer is dimmed by the one night factor.
  8. Water is matte (a sun path, glints, gentle waves); fountains keep their sky mirror. After dark the river mirrors the lamps by the water, as points of light on the waves, never the scene.

Consequences

  • One shader budget, spent on post and shadows, not on a second scene.
  • A new building attribute is a row in the object table that tints within the palette, never a texture.
  • A new facade term must fit the clay's varyings (ADR 0027) and read the flat facet normal.

Alternatives

  • Ghost (transmission) or raw LoD styles: a style that halves the frame rate is a trap.
  • A uniform window grid or a window texture over every facade: read as an office block over historic silhouettes.
  • No glass at all (until 2026-11): windows seen obliquely read as flat paint; a pane's grazing sky is what tells their depth.
  • Geometry niches baked into the mesh: plump at the mesh's precision and only on measured walls; a street with every thirtieth house windowed was rejected. Niches at runtime on the shader's grid (2026-11) have neither fault.
  • Niches cut on every tile: a discard costs the clay its early depth test, so only the tiles near the eye build it.
  • Blending roofs toward terracotta: destroyed the real copper greens.
  • Raw OSM colours: pure hues in a pastel city.
  • A palette lookup per fragment: class ids cannot be mipmapped.
Previous
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
Next
ADR 0012: Sources — official data first, OSM and Wikidata for what it lacks, named stand-ins marked per city
Source on GitHub: docs/adr/0010-opaque-clay-buildings-only.md
On this page
  • Context
  • Decision
  • Consequences
  • Alternatives