Glossary
Deutsch: Glossar
The abbreviations and jargon used in this project, in plain words. Geodata terms first, then rendering terms, then project terms.
Geodata
The datasets themselves have full fact sheets (abbreviation, collection method, update cycle, accuracy, suitability, strengths and weaknesses) in Where the data comes from; the entries here are the short form.
AAA / GeoInfoDok — the nationwide data model behind ALKIS, ATKIS and the survey control points (AFIS-ALKIS-ATKIS), documented in the GeoInfoDok. The Basis-DLM follows its schema 7.1.2; that is why its object types are identical in every German state.
ALKIS — Amtliches Liegenschaftskataster-Informationssystem, the official German cadastre: parcels, owners' plots, building footprints and functions. The building attributes in the 3D model (function code, roof type) follow ALKIS code lists. Parcels themselves are not used yet.
ATKIS — Amtliches Topographisch-Kartographisches Informationssystem, the nationwide system of official topographic data. The Basis-DLM is its most detailed landscape model.
Basis-DLM — Digitales Basis-Landschaftsmodell: the vector map of what covers the ground (roads, rails, water, forest, farmland, settlements), with attributes, maintained by the survey office from orthophotos, the terrain model, field measurements and other authorities' data; every object checked every 3–5 years, important ones every 3–12 months; positional accuracy ±3 m for main line objects. Delivered as Shapefiles, statewide, refreshed quarterly. The viewer's ground colours, hedges, railways and bridges come from it. Fact sheet.
CityGML / CityJSON — two encodings of the same standard for 3D city models. CityGML is XML and is what the portal ships; CityJSON is a compact JSON form of it that the project converts to. Both describe buildings as solids with semantic surfaces (wall, roof, ground).
CRS / EPSG:25833 — a coordinate reference system says what the numbers in a coordinate mean. EPSG:25833 is "ETRS89 / UTM zone 33 N": metres east and north of a reference point, covering eastern Germany. All project data is kept in this system; the viewer's scene units are metres.
DGM1 — Digitales Geländemodell 1, the terrain model: bare-ground heights on a 1 m grid, interpolated from the ground points of an airborne laser scan; height accuracy up to ±0.15 m. Buildings, bridges and vegetation are removed. Dresden was scanned in November 2024. Fact sheet.
DHHN2016 — Deutsches Haupthöhennetz 2016, the current German height reference; heights are "metres above sea level" in this system.
DOM1 — Digitales Oberflächenmodell 1, the surface model: the first surface the laser hit, on a 1 m grid — roofs, tree tops, bridge decks. From the same flight as the DGM1; DOM1 − DGM1 gives the height of everything on the ground. Fact sheet.
DOP / DOP20 / RGBI — Digitales Orthophoto: an aerial photograph rectified over the terrain model so every pixel sits at its true map position; "20" = 20 cm per pixel; "RGBI" = red, green, blue plus near-infrared channels. Flown by survey aircraft, each tile about every two years, alternating spring and summer; positional accuracy ≤ 0.4 m. These tiles date from 19 March 2024. Fact sheet.
DTK — Digitale Topographische Karte, the official topographic map series (DTK10, DTK25, DTK50, DTK100 for the scales 1:10 000 to 1:100 000), available as raster tiles from the same portal; not used yet (a candidate for a cartographic minimap).
DWD — Deutscher Wetterdienst, Germany's national weather service. Its volunteer observers record every year when the plants around them leaf out, flower, turn and drop their leaves (phenology); the viewer shifts each city's year of the trees by what they recorded around it. The providers.
Deterministic / inferred — how the viewer comes by a statement. Deterministic (taken, computed): from the source or by a fixed formula, the same data give the same result. Inferred (detected, assumed): added by a rule, a match or a design choice. The four badges.
Echo (first / last / only) — a laser pulse can return several echoes: the first from the top of a tree or a roof, the last from the ground beneath. The surface model uses the first echoes, the terrain model the ground-classified points.
GDAL — the open-source geodata toolkit the bakes use to clip, reproject, rasterise and convert. It comes inside the Python libraries of the bake package, so it needs no separate installation.
GeoJSON — a simple JSON format for points, lines and polygons with attributes. All small per-tile vector files are GeoJSON.
GeoTIFF / world file (.tfw) — a TIFF image that also knows where on
Earth it sits. When the position is not embedded, a small .tfw text file
next to it supplies it.
Geofabrik — a company that publishes regional OpenStreetMap extracts for download, rebuilt daily; the project reads the Saxony extract.
GeoSN — Landesamt für Geobasisinformation Sachsen, Saxony's state survey office and the provider of all official datasets used here.
GLO-30 — the Copernicus DEM at 30 m: a surface model of the whole world, made by DLR and Airbus Defence and Space from radar satellites. The viewer reads it only for the land beyond a city's tiles: the hills on the far horizon and the rim of the valley. The providers.
Ground resolution / GSD — the size of one pixel on the ground (ground sampling distance): 20 cm for the DOP, 1 m for the height models.
Land-cover class — the land-use category of a pixel in the baked class raster: background, farmland/meadow, forest, copse, built-up, railway, path, road, water, arable (ids 0–9). The file holds only these numbers; the browser paints each class in its pastel colour (see Splatmap).
LiDAR / laser scanning — light detection and ranging: measuring distances with laser pulses from an aircraft; the survey method behind the point cloud, the DGM1, the DOM1 and the roof shapes of the LoD2.
LoD1 / LoD2 — level of detail of a 3D building model: LoD1 is a flat box per building, LoD2 adds the standardised roof shape fitted to the laser scan; LoD3 would add facade detail. The model is generated automatically from cadastral footprints and the point cloud; a tile's currency is that of its inputs (here: 2016 laser scan, 2021/2022 footprints). Fact sheet.
LSC — Laserscandaten, the classified laser point cloud itself (LAZ files), the raw material of the height models. Read offline, where a survey office offers it (Saxony, North Rhine-Westphalia), for hedge heights, garden trees and the sheds the 3D building model lacks. Fact sheet.
Pattern recognition — here: a rule with thresholds decides what something is (a tree at a crown's peak, a shed in the laser scan), or two sources are matched (a shop is assigned to a building). Open and reproducible, but not infallible; the viewer marks it detected. The four badges.
nDOM — normalisiertes DOM: surface model minus terrain model, i.e. the height of things standing on the ground. Computed by the project from DOM1 and DGM1; the portal also offers it on request.
NDVI — Normalized Difference Vegetation Index: (infrared − red) / (infrared + red). Healthy vegetation reflects infrared strongly, so the index is high on lush plants and near zero on roofs, roads and water. Only as good as the photo's date (a March image shows bare deciduous trees). Fact sheet.
ODbL — Open Database License, the licence of OpenStreetMap; requires the credit "© OpenStreetMap contributors".
dl-de/by-2-0 — Datenlizenz Deutschland – Namensnennung – Version 2.0, the licence of GeoSN's open geodata; requires the credit "Quelle: GeoSN, dl-de/by-2-0".
OSM / Overpass — OpenStreetMap, the volunteer world map, mapped from GPS traces, surveys and traced aerial imagery, updated continuously, with no accuracy guarantee. The viewer's lamps, walls, stairs, platforms and bridge structure types come from it; the bakes read it from the Geofabrik extract. The Overpass API is a live query service for it; the bakes no longer use it, but the committed lamp, platform and bridge-structure files were still fetched through it. Fact sheet.
.osm.pbf — the compact binary file format of OpenStreetMap extracts.
Raster / vector — a raster is a grid of pixels (the terrain model, the aerial photo); vector data is points, lines and polygons (buildings, roads, tree points).
Shapefile — an old but ubiquitous vector file format; the Basis-DLM comes as one file set per object type.
Tile / Kachel — a 2 km × 2 km square of the state's tiling scheme. The
name 33412_5656_2_sn means UTM zone 33, easting 412 km, northing 5656 km
(the south-west corner), 2 km edge, Saxony. The site config lists fifteen of
them for Dresden; the first is the spawn tile. The viewer streams them
(see Tileset).
Rendering
three.js — the JavaScript library that talks to the graphics card through WebGPU; the whole scene is built with it.
WebGPU — the browser's newer interface to the graphics card. The viewer needs it; a browser without it (older iPhones, Firefox on some systems) gets a message instead of the city.
Shader / node material — the small programs the graphics card runs to colour each pixel. Here every material is written as a node material (three.js's TSL): the look is assembled from building blocks, which three.js translates for WebGPU.
Mesh / triangle — everything drawn is triangles. A mesh is a set of triangles with a material. The buildings of a tile are one mesh; a "building" is identified per vertex so that one can be demolished.
glTF — the standard file format for 3D models, often called "the JPEG
of 3D". The buildings and the terrain reach the browser as glTF files,
compressed and gzipped (.glb.gz), so any glTF viewer can open them.
3D Tiles — an open standard (by the OGC, the body behind many geodata standards) for streaming large 3D worlds: a small index file describes a tree of tiles and their levels of detail, and the files themselves are usually glTF. The viewer reads it with the library 3DTilesRendererJS.
Tileset / streaming — the index file tileset.json lists every tile's
buildings and its terrain at two levels of detail, a coarse one (512²
grid) and a detailed one (a TIN, see below) that replaces it when the camera
comes close. From it the viewer decides what to load: only what the
camera can see, in detail near you, coarse far away; what you leave far
behind can be dropped again.
Heightfield — a regular grid of heights, such as the DGM1. The build step turns it into a ready-made terrain mesh; the browser no longer receives the grid itself.
TIN — triangulated irregular network: a terrain mesh whose triangles are not laid on a regular grid — more triangles where the ground bends, few where it is flat. The detailed terrain level is a TIN of the DGM1 that stays within ±15 cm of it; the coarse level is a 512² grid.
Splatmap — a texture that tells the ground shader which colour to use where. Here it is not downloaded: the browser paints it once per tile on the graphics card, from the land-use class raster and one pastel palette; its transparency channel encodes water coverage, softened at the shore.
Instancing — drawing thousands of copies of one shape (trees, lamp posts) in a single draw call, each with its own position and scale.
LOD — level of detail: a cheaper version of a shape drawn when it is far away (the tree crown has two versions, the terrain two levels; see Tileset).
Shadow map — a depth image rendered from the sun's point of view; every pixel then checks whether it is the closest thing to the sun. Soft edges come from sampling it several times (PCF).
Contact shadows (SSAO, GTAO) — screen-space ambient occlusion (SSAO) is the family of methods that darken corners, under eaves and where objects meet the ground, computed from the depth buffer. The viewer uses one of them, GTAO (ground-truth ambient occlusion), at half resolution.
Depth of field (DoF) — the photographic blur before and beyond the focus distance; here always focused on the centre of the view. Not on phones.
Post-processing — effects applied to the finished image: contact shadows, depth of field, anti-aliasing (SMAA; on phones the lighter FXAA), depth grading, vignette, paper grain.
Fill-rate — how many pixels per second the graphics card can shade; the scene's main cost driver, which is why phones render fewer pixels.
Frustum — the pyramid of space a camera (or the shadow camera) sees; things outside it are skipped.
BVH — bounding volume hierarchy, a search tree over triangles that makes "what is under the pointer" and collision checks fast.
Pixel ratio (DPR) — how many rendered pixels per screen pixel; at most 1.5 here, on phones and on computers with a high-resolution screen alike, to save fill-rate.
SwiftShader — a software renderer used by the headless test browser; it draws the scene on the CPU, slowly and without the real look.
Planning drawings
The views of Modell (see Using the viewer).
Parallel projection / axonometry — a drawing whose lines of sight all run parallel: no vanishing point, equal lengths stay equal anywhere in the picture, and the picture has a scale. Axonometries are the parallel projections that show three sides of a block.
Isometrie (isometry) — the axonometry that shortens all three axes alike (× 0.816): seen from 35.26° above the ground, turned 45° to the block, the ground's edges run at 30° on the sheet — hence "30° isometry".
Militärperspektive — an oblique axonometry: the ground plan is drawn undistorted and to scale, turned (usually 30°/60° or 45°/45°), and the heights stand straight up over it, true or shortened to two thirds.
Vogelschau — "bird's-eye view": here a parallel view from above at any tilt.
Lageplan — the site plan: straight down, north up, to scale.
Ansicht / Schnitt — the elevation and the section: level views onto a line. A section cuts there and fills what the cut opens (the poché, here black), with the ground drawn as a profile (Geländeschnitt).
Schwarzplan — the figure-ground plan: buildings black on white, nothing else; the oldest way of reading a city's grain.
Maßstab (scale) — 1 : n means one unit on the sheet is n in reality. On screen the viewer takes a CSS pixel as 1/96 inch (0.26 mm); the exported picture states its scale at 300 dpi.
Verschattungsstudie (shadow study) — the same view at fixed hours on the equinox (21 March) and the solstices (21 June, 21 December): how much sun a place gets over the year.
Project
Bake — any offline or build-time step that turns a heavy input into a
small, ready-to-use artifact. The offline bakes are one Python package
(pipeline/), run with bun run bake <site>; the build-time one is
scripts/prepare-data.ts, run for every city by scripts/prepare-sites.ts.
Artifact — one of the prepared files the browser may request. The
tileset names all of them; the list of a tile's side files (rasters and
feature files) lives in lib/city/tile.ts.
Site config — sites/dresden.ts: everything about the place that is
not data — its name, coordinate system, tiles, spawn tile, viewpoints and
credits. The bakes and the viewer both read it; one deployment shows every
site whose data it was built with, each at its own address (/dresden).
Start page — the page at /: one card per city the deployment was
built with (its land-cover map, its Land, area and viewpoints), each
leading to that city's viewer.
Manifest — public/data/<site>/manifest.json (one per city), mapping
plain file names to the fingerprinted names they are served under.
Content hash — the eight-character fingerprint in a served file name; changes whenever the content changes, so caches never serve stale data.
Lite profile — ?scene=lite (/dresden?scene=lite): the spawn tile only, tiny shadow map,
half resolution; for automated tests only.
Snapshot — the JSON text that captures camera, date/time, the
picture style, the fog and the data layers, used to
reproduce a view; a view link (?snap=) carries one in its address.
Scenic view / Aussichtspunkt — one of the authored vantages the camera can glide to; one of them is the start view.
Spawn tile — the tile you start on, the first in the site config. The first picture waits only for it; after that it has no special role: distance from the camera, not the tile, decides what is drawn in detail, and walking, collision and the demolish tool work on every tile in view. (Earlier versions loaded a fixed block of four and called this the primary tile.)
ADR — architecture decision record: a short document stating one decision, its context and consequences; see docs/adr.
