Mapping
Layers & zoom
What appears when, and why — one gate per kind of data, ordered so the map never looks half-loaded. Numbers measured from the shipping map.
Zoom gates
< 11The region shellLGA fills as invisible click targets (they exist ONLY below 11), the urban footprint at 0.32. The region view is for choosing a council, not reading one.11The council fabricParcels, zoning and every constraint overlay share ONE gate (COUNCIL_MINZOOM) — half the layers arriving before the other half reads as a broken load.13.2Cadastre linesBoundary strokes fade in 0.35 → 1 over half a level — a fade replaces the pop — and the width grows 0.4 → 1.1 toward z19 so overzoomed lots stay readable lines.13.6Selection floorBelow it the viewport streaming that resolves a clicked lot cannot run, so no parcel framing ever lands under it.14BuildingsFootprint tiles begin; the extrusions themselves fade in from 14.5 (see 3D & massing).14.2Council arrivalThe default zoom a council opens at. Every layer's gate sits AT or BELOW it — a layer gated above the arrival zoom looks broken on arrival (the mains learned this at 15).18Parcel ceilingParcel fits never land deeper — past it a suburban lot is wall-to-wall polygon and context is gone.The rules
- A gate belongs on the layer, not only the source. A source-level minzoom holds in one serving mode and silently vanishes in the other (the archive's own TileJSON wins); the layer's gate holds in both.
- Source maxzoom is the baked maximum (lots 15, overlays 14) and everything deeper is overzoom — free, and sharp, because vector geometry scales. Tiles are never baked deeper to chase a zoom level.
- Nothing pops. Strokes fade in over half a level, buildings over a full level, the basemap raster over 300 ms. A layer that appears at full strength in one frame reads as an error even when it is correct.
- Gates are stated once and shared. Four hazard overlays share one constant; the day a fifth arrives it inherits the behaviour instead of inventing a neighbour to it.