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 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

  • Status: accepted
  • Date: 2026-10

Context

Architects, landscape architects and planners want to see their designs in the city: walk past them, see their shadows at a given hour, draw them in Modell. Their formats differ, and their georeference is rarely dependable: glTF has no place at all, architectural models often stand on ±0 with the NHN height only in the title block, and exports that write the Land's coordinates into float32 vertices have rounded them. The page keeps nothing about a visitor (ADR 0001), a phone's memory must not grow (ADR 0047), and nothing the visitor does goes to a third party unannounced (ADR 0043).

Decision

  1. A design is a file read in the page, never uploaded: glTF, IFC, OBJ, Rhino .3dm, or a landscape plan as DXF, Shapefile, GeoPackage or LandXML. Nothing it names is fetched; the WebAssembly readers load only when their format is picked, from the site's own /wasm/. Its parts become one geometry about its anchor, moved there in doubles before float32.
  2. It is placed by its coordinates where they say something: UTM in the site's zone, an IFC's IfcMapConversion (its IfcSite roughly), a Rhino earth anchor. Its height is kept as NHN where the ground under it agrees, else it is set on the ground. A place more than 2 km beyond the site, or no place at all, puts it in front of the player, and the panel says why.
  3. It is read in metres unless the visitor sets a scale (a unit times a factor; a hint when it is under 4 m or over 3 km). A plan is not scaled: its CRS gives its unit. The Entwurf panel moves, turns, lifts and scales it and saves all of it as a small JSON file.
  4. It stands in for the buildings it covers. Each LoD2 object whose footprint its plan covers for at least half leaves its tile's index (CityLayer.setHidden) with all its parts, and comes back when the design moves or goes; collider, picks, shadows and minimap follow.
  5. Its site is cleared. One raster of the design's plan and lowest height (design-site.ts), read by the vertex stages: instanced sets fold away what stands in it; ground, water and the tracks near the floor are pressed under it. A plan's areas clear the site but take no house away.
  6. A plan is drawn in the city's own palette. Its areas become land-cover classes by their attributes, then their layer's name; trees are low-poly crowns, a building with a height a block, a TIN a planned ground. Lines are not drawn: in a plan they are edges.
  7. A design is drawn in a model-maker's white or its own colours, casts and takes shadows, is walked against, and is asked like any thing: the card says only what the file and its placement say.
  8. Its bytes come out of the tile cache, within a per-tier budget; past it the textures go first, then the design is refused with the numbers.

Consequences

  • The privacy page says that a design stays on the device. Sharing one by link would need storage for the visitor's content and is not offered.
  • One design at a time; a phone's memory does not grow with it.
  • A building hidden by a design and demolished meanwhile stays gone when the design leaves.

Alternatives

  • An upload to a store, so a design could be shared by link: a backend for the visitor's content, with questions of liability, deletion and confidentiality (competition entries are anonymous).
  • Hiding by a flag in the clay shader: no index rebuild, but the collider and the picks would still meet the hidden buildings.
  • A convex hull as the design's plan: an L-shaped design would take the house in its corner.
Previous
ADR 0048: A network failure is retried for a budget of the page's visible time, never decided at once
Next
ADR 0055: What the twin knows is baked as files; walks are written ahead, their narration marked, every claim sourced
Source on GitHub: docs/adr/0054-a-design-is-loaded-on-the-device.md
On this page
  • Context
  • Decision
  • Consequences
  • Alternatives