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
  • 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
    • Completed plans — condensed records
    • Plan 086 [rewrite]: The rewrite series — faster on the device, fewer bytes on the wire, less to hold in the head
    • Plan 017: Any German city — the open half: a second Land, NAS input, OSM land cover, a site check
    • Plan 019: The GPU checklist — look at everything built headless, on real GPUs and phones
    • Plan 021: /wissen on Astro Starlight instead of a hand-built Next route
    • Plan 047 (spike): "Problem melden" — the crash report with somewhere to go
    • Plan 048 (spike): Share a view as a link, and commit the reference views the GPU checks need
    • Plan 050: Landmarks and what LoD2 leaves out — measured in DOM1, named by OSM and Wikidata
    • Plan 051: Stand-ins where a Land publishes less, and looks derived from each city's data
    • Plan 052: A queryable twin — identity, semantics and provenance, asked on demand
    • Plan 053: Time and live sources — the twin's fourth dimension
    • Plan 054: Scenarios — what-if studies drawn in the scene's own hand
    • Plan 069: Find what holds the load at 52 %, then take it off the tile path
    • Plan 070: Each tile holds a fraction of the raster memory it holds today
    • Plan 071: A phone renders a lean scene, a desktop a lighter one
    • Plan 074: Bake the static dressing, load the optional features on demand, one store for the HUD
    • 076 — Streaming without holes: the ground first, a plate under everything, coarse buildings and trees from the start
    • Plan 077: One rasters module — a tile's rasters loaded, shared and weighed behind one interface, their files named by the artifact table
    • 078 — One scene environment the dressings bind at birth
    • Plan 079: A page that lost its GPU comes back where it stood, through one recovery session
    • 080 — One row per inquiry kind: the twin's per-kind dispatch in one place
    • 082 — One answer turn, and a code for every way it ends
    • 084 — One session for an answer's lifetime: reading aloud, dictation and the scene's waits in one module
    • 085 — Window niches and shop windows: performance and follow-ups
    • Plan 087 [rewrite]: Plates compared on a real GPU, and one ledger every plan of the series writes its figures into
    • Plan 088 [rewrite]: The tileset is a published product, named by a lock file; the web build bakes nothing and data/ leaves git
    • Plan 089 [rewrite]: The bakes are type-checked in CI against a baseline that only shrinks
    • Plan 090 [rewrite]: A tile's dressing arrives in the layout the GPU draws from
    • Plan 091 [rewrite]: A tile's rasters arrive as the GPU reads them — plain arrays for ids, blocks for soft fields, a few files and bindings
    • Plan 092 [rewrite]: The bakes work on site-wide typed tables, cut tiles last, and no step rewrites another's file
    • Plan 093 [rewrite]: The stream's tile is smaller than the bake's — a quadtree whose levels replace the raster twins, built only if a phone still asks for it
    • Plan 094 [rewrite]: The clay's limits are counted by a test, and every pipeline the scene draws with is known at boot
    • Plan 095 [rewrite]: The viewer is a package with one entrance, a coordinate's frame is its type, and bootApp is owners
    • Plan 096 [rewrite]: Every bake heuristic that guesses has a reference set and a score a bake PR must hold
  • 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
  • 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
    • Completed plans — condensed records
    • Plan 086 [rewrite]: The rewrite series — faster on the device, fewer bytes on the wire, less to hold in the head
    • Plan 017: Any German city — the open half: a second Land, NAS input, OSM land cover, a site check
    • Plan 019: The GPU checklist — look at everything built headless, on real GPUs and phones
    • Plan 021: /wissen on Astro Starlight instead of a hand-built Next route
    • Plan 047 (spike): "Problem melden" — the crash report with somewhere to go
    • Plan 048 (spike): Share a view as a link, and commit the reference views the GPU checks need
    • Plan 050: Landmarks and what LoD2 leaves out — measured in DOM1, named by OSM and Wikidata
    • Plan 051: Stand-ins where a Land publishes less, and looks derived from each city's data
    • Plan 052: A queryable twin — identity, semantics and provenance, asked on demand
    • Plan 053: Time and live sources — the twin's fourth dimension
    • Plan 054: Scenarios — what-if studies drawn in the scene's own hand
    • Plan 069: Find what holds the load at 52 %, then take it off the tile path
    • Plan 070: Each tile holds a fraction of the raster memory it holds today
    • Plan 071: A phone renders a lean scene, a desktop a lighter one
    • Plan 074: Bake the static dressing, load the optional features on demand, one store for the HUD
    • 076 — Streaming without holes: the ground first, a plate under everything, coarse buildings and trees from the start
    • Plan 077: One rasters module — a tile's rasters loaded, shared and weighed behind one interface, their files named by the artifact table
    • 078 — One scene environment the dressings bind at birth
    • Plan 079: A page that lost its GPU comes back where it stood, through one recovery session
    • 080 — One row per inquiry kind: the twin's per-kind dispatch in one place
    • 082 — One answer turn, and a code for every way it ends
    • 084 — One session for an answer's lifetime: reading aloud, dictation and the scene's waits in one module
    • 085 — Window niches and shop windows: performance and follow-ups
    • Plan 087 [rewrite]: Plates compared on a real GPU, and one ledger every plan of the series writes its figures into
    • Plan 088 [rewrite]: The tileset is a published product, named by a lock file; the web build bakes nothing and data/ leaves git
    • Plan 089 [rewrite]: The bakes are type-checked in CI against a baseline that only shrinks
    • Plan 090 [rewrite]: A tile's dressing arrives in the layout the GPU draws from
    • Plan 091 [rewrite]: A tile's rasters arrive as the GPU reads them — plain arrays for ids, blocks for soft fields, a few files and bindings
    • Plan 092 [rewrite]: The bakes work on site-wide typed tables, cut tiles last, and no step rewrites another's file
    • Plan 093 [rewrite]: The stream's tile is smaller than the bake's — a quadtree whose levels replace the raster twins, built only if a phone still asks for it
    • Plan 094 [rewrite]: The clay's limits are counted by a test, and every pipeline the scene draws with is known at boot
    • Plan 095 [rewrite]: The viewer is a package with one entrance, a coordinate's frame is its type, and bootApp is owners
    • Plan 096 [rewrite]: Every bake heuristic that guesses has a reference set and a score a bake PR must hold
  • What the data streams carry that the walker does not use yet
Entwicklung (English)

076 — Streaming without holes: the ground first, a plate under everything, coarse buildings and trees from the start

Status: BUILT (2026-11-04) — all four steps in the code: load order (stream-order.ts), ground plate (aefc090b), far buildings (a08c6813), trees from the start (4eafaf42). Open: the plan's promise of no cost in phone memory and frame time is unmeasured on a device (step 3 rests on "a sixth of the triangles, half the bytes"); measure on a phone, then condense into completed.md. Asked by the maintainer on 2026-10-25: the spawn tile loads in full while others show nothing, trees come late, long flights show large holes in the ground; everything should be there from the start and refine smoothly, with no cost in frame time, phone memory or the bytes before the first picture.

Findings (Dresden, gzip, 15 tiles)

Contentper tilewhole sitewhen it loaded
buildings, full LoD24.1 MB (max 7.4)61.5 MBwhenever the tile is in view, at any distance — first of all
fine ground (TIN) + its rasters2.3 + ≈ 4.9 MB34 + 73 MBwithin ≈ 2.6 km (a phone 2.1 km)
coarse ground (512²) + sky-view and horizon0.47 + 1.7 MB7 + 25 MBotherwise
coarse crowns0.13 MB2 MBbehind every fine dressing, one at a time
  • 3DTilesRendererJS sorts its queues by screen-space error, highest first; a tile's buildings carry TILE_ERROR (100 000) so that they always show, so every visible tile's buildings queued ahead of any ground.
  • Nothing stands in for a tile that never loaded or was evicted: loadAncestors only works between the two terrain levels of one tile.
  • Buildings have one level: a tile 5 km away loads the same LoD2 as the one underfoot.
  • The dressing (trees, lamps, furniture, rails) is one serial chain after the boot's gate; the coarse crowns wait behind the neighbours' fine dressings.

Steps

  1. Load order (built): lib/city/stream-order.ts, orderStreaming in tile-stream.ts. Nearest first with the coarse ground counted a tile (2 km) nearer, on one tile ground → buildings → fine ground; until the first frame the boot tile's ground and buildings first; a full cache admits in the same order (keepOrder). Measured headless, full profile, after a jump 400 m over the north-east of Dresden: see the PR.
  2. Ground plate (built): lib/city/ground-plate.ts, ground-plate-layer.ts, bakePlate in prepare-data.ts — one site file of 33² heights and classes per tile, drawn wherever a tile has no terrain on screen. ≈ 0.6 MB of GPU buffers for Dresden.
  3. Far buildings (built): not LoD1 blocks but the LoD2 itself, simplified to 0.5 m (city_<t>_far, FAR_CITY_ERROR 4 m): the baked mesh carries a vertex every 2 m along each wall for the ground the windows clear, so the simplifier drops five triangles in six and keeps the roofs — LoD1 blocks would have cost about as many triangles and lost the roofs. Only the tiles within ≈ 260 m load the baked LoD2, none from the air: the phone's memory falls. The distance falloff (errorFalloff) is not needed: the levels' screen-space error already counts the distance.
  4. Trees from the start (built): not a site file of every tile's crowns — on a phone that held all ≈ 136 000 of Dresden's coarse crowns (≈ 12 MB) for the whole visit — but the coarse crowns first and longer: a coarse level's dressing goes ahead of every fine level's in the dressings' turn (COARSE_DRESSING_RANK, lib/city/task-gate.ts's rank), and where a fine level shows before its own trees hang, its coarse level's crowns stand in on it (coarseCrownsStandIn, DressingPlugin.standInCrowns). Both levels are loaded anyway: no byte more.

Rejected for now: KTX2 for the rasters (data, not colour: block compression would change class ids), implicit tiling (15 tiles), runtime progressive meshes, Draco instead of meshopt, the library's TilesFadePlugin (it patches GLSL through onBeforeCompile, ADR 0027).

Previous
Plan 074: Bake the static dressing, load the optional features on demand, one store for the HUD
Next
Plan 077: One rasters module — a tile's rasters loaded, shared and weighed behind one interface, their files named by the artifact table
Source on GitHub: docs/plans/076-streaming-without-holes.md
On this page
  • Findings (Dresden, gzip, 15 tiles)
  • Steps