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 0041: Rails, trams and bridges — decks measured in the surface model, every line on a drivable profile solved by the build

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

Context

The bare-earth DGM removes bridge decks by definition and rounds every embankment and cutting. The official vector data has no bridge types and LoD2 draws bridges as flat 1 m slabs. A track lifted onto whatever deck lay under a point jumped between levels; a track laid on the DGM bumped and dipped, and the terrain's triangles rose through the rails.

Decision

  1. Bridges are the rail layer's alone. The building mesh leaves out LoD2's traffic structures. A deck's height is the roadway DOM1 measures along its axis, held near the DGM ramp, grade-limited and never sagging; its depth comes from the fairway clearance.
  2. What stands above a deck is measured, typed by Wikidata. Ribs are the highest surface above the deck where it stands high enough for long enough, kept only where the bridge's class (arch, truss, suspension, cable-stayed) stands above it. An arch rib becomes a steel arch; any other rib a simple open frame in pale matte steel — the silhouette, not the members. Wikidata's class overrides OSM's bridge:structure.
  3. Everything across a deck is measured from its centreline, and a bridge line takes the footprint it runs on.
  4. A line's level is solved along the whole line (lib/city/levels.ts): ground, a deck, a span over a gap the DGM leaves, or a cut through fill, chosen as the path the line can drive within its grade (rail 4 %, tram 8 %, a funicular 100 %: its track climbs its slope), with the line's context across tiles — a funicular's only across funiculars. A cut under a drawn deck opens a passage in the terrain.
  5. A line lies on a profile within its grade and vertical-curve radius (rail 2 000 m, tram 500 m, funicular 100 m), fitted by the build step and published with the levels (lv, lz). The layers draw a baked line on its profile, never on the ground.
  6. The ground is laid under the bed: the terrain bake shapes the DGM to the profile under each bed and grades the sides at 1 : 1.5; under a deck it only lowers. The ballast drapes on the beds.
  7. Platforms keep their edge distance from the tracks, and a flat LoD2 top just over a track is lowered to its bed.
  8. A monorail is a beam, not a track: the bake lays its underside on the upper hull of the ground plus a car's clearance along the whole way (straight over a hollow, bent over a crest), and the rail layer stands it on supports. It takes no level, no profile and no bed.

Consequences

  • The Blaues Wunder and the Waldschlößchenbrücke read as themselves with no per-bridge code; any bridge with steel above its deck gets its ribs.
  • A new line layer takes its levels and profile the same way (lineLevelsAt); scripts/line-levels.test.ts holds the jumps to a budget.
  • A standing train or a crown over a deck can still lift the measured deck (bounded); stay cables are too thin for a 1 m raster.

Alternatives

  • Bridge types from OSM or the DLM: OSM's tag is patchy and sometimes wrong; the DLM's codes are not captured.
  • Drawing the members as measured, in dark steel: busier and darker than any building.
  • Lifting a line by its source's layer tag, or by a median filter: the DLM has none, OSM's is relative and patchy; a median shifts every real ramp and cannot tell a gap from a fill.
  • Smoothing or draping at runtime: piece ends disagree across seams and the ground still rises over the rails.
  • Lifting the rails by a margin: they float wherever the ground is lower.
Previous
ADR 0040: Data layers are switches, off at start, drawn as glass; optional features start on first use
Next
ADR 0042: The twin answers on demand — facts and provenance ride in the tileset, text appears only when asked
Source on GitHub: docs/adr/0041-line-levels-along-the-whole-line.md
On this page
  • Context
  • Decision
  • Consequences
  • Alternatives