Feature Library

Architect’s site plan in SVG

0.03 CPU ms
A still of the Architect’s site plan in SVG demo
Still
The live demo starts when it’s in view.Drag to pan · wheel (after a click) or pinch to zoom · click a name or an area · Tab to the names, arrows between them, Enter to zoom to one

A site plan drawn from plain data in the conventions of an architect’s drawing.

What it costs a frame

0.03 ms
GPU
not used
CPU, median
0.03 ms
CPU, 95th pct
0.07 ms
Draw calls
0
Weight
Light

Measured 13 November 2026 on RTX 4060 Laptop, 13th Gen Intel(R) Core(TM) i9-13900H, Chrome 157, 1920×1080 at 1×. 600 frames × 3 rounds, median kept (rounds ranged CPU 0.03–0.03 ms). What ran: Measured with the plan zooming itself: every frame the camera eases between the whole plot and about four times closer and back (a 3 s cycle), so each frame moves the drawing, rescales the hatching, lays out the callouts and dimensions again and culls the room, path and note labels. At rest nothing runs. Phones: tiers are being measured next.

On every machine it was measured on
MachineGPU msCPU msCPU p95
RTX 4060 Laptop · 13th Gen Intel(R) Core(TM) i9-13900Hreference · measuring toolnot timed0.030.07
apple · Apple A19 Proin a browser tab · 16 November 2026not timed0.020.04
Intel Arc 140V (Xe2-LPG) · Intel Core Ultra 7 258Vin a browser tab · 15 November 2026not timed0.030.06

Bars against one 16.7 ms frame. A browser-tab run is timed in a visible tab without the tool’s scripted input, so read it as close, not exact.

What it needs

Renders with
DOM and CSSPlain DOM and CSS: every current browser.
Your browser
Runs hereNo WebGPU needed
Depends on
NothingNo other packages

What it’s for

  1. A campus, park, venue or office site with its buildings and grounds
  2. Floor plans and room schedules
  3. Showing what is proposed beside what exists
  4. Picking a building or area from a drawing (bookings, facilities, maintenance)
  5. Any zoomable SVG drawing whose labels must stay calm
  6. A map drawn from your own data, with no tiles and no map library

Pitfalls, in brief

  1. Coordinates are metres with y pointing south (down the screen), as SVG has it.
  2. Strokes keep their screen weight through vector-effect: non-scaling-stroke on the drawing.
  3. The hatching and stipples keep their spacing because their patterns are rescaled on every view change (patternTransform).
  4. The overlay is laid out in screen pixels on every view change; it is cheap (tens of elements), but a plan with hundreds of named features should cull callouts by priority before layout, not after.
  5. The wheel zooms only after the plan has been clicked or focused (Ctrl or a pinch always zoom), or a page could not be scrolled past it.
4 more in brief
  1. Label widths are estimated from the character count, not measured: a font much wider than the default may let two labels touch.
  2. Names and notes reach the SVG through esc(); a label you add to the markup yourself needs escaping too.
  3. insets keep the names and chrome out of an app’s own bars and panels: pass them again (set) whenever a panel opens or closes, as the demo does with its schedule.
  4. Pattern ids are made unique per plan (spl1-hatch…), so several plans can share a page; copy the module as a whole, not the SVG markup alone.
9 pitfalls in full, the hook-up guide, the module source and its tests come with the part.

Where it comes from

From HaTac. Fully custom code.

Architectural drawing conventions: The dash-dot property line, hatched sections, heavy cut walls, north point, scale bar and title block: conventions of the trade, drawn here by the owner’s code.

Austin Appleby, MurmurHash3 (public domain): Its 32-bit finaliser mixes the integer hash that gives each tree its own canopy.

svgsite planarchitecturefloor planmapzoompanpinchlabelslabel collisionleader linescalloutsscale barnorth arrowhatchingpatternskeyboardaccessibilityno dependencies

Near it in the frame