The demos are small, but they are built like production systems: reproducible data pipelines, typed APIs, a database, and a 3D client tuned for large datasets. Performance numbers below are measured in visitors' browsers, not estimated.
| Demo | Input | Processing | Delivered as | Client technique |
|---|---|---|---|---|
| City Digital Twin | GIS footprints (synthetic or OSM), sensor registry | Extrusion attributes; IoT simulator as a pure function of time | GeoJSON + SSE stream + snapshot / series API | One batched Primitive for all buildings, per-instance colour updates, PolylineCollection for traffic |
| BIM–GIS | IFC4 / IFC2x3 | web-ifc (WebAssembly) parse → mesh extraction → simplification → georeference from IfcSite → semantic mapping | In-browser conversion; nothing uploaded | GeometryInstance per IFC element (pickable by expressID), 4D filter by property-set dates |
| Asset Management | Asset register, inspections, defects | Validated CRUD, workflow states, condition analytics | REST API + SQLite (PostGIS in production) + CSV export | Procedural 3D bridges with defects in structure-local coordinates |
| Underground & Tunnel | Utility network, tunnel alignment, monitoring | Depth-aware 3D pipe geometry, ring schedule, settlement series | GeoJSON / JSON | Globe translucency, underground camera, clearance analysis |
| Metro Line 3 | OSM alignment (viaduct + tunnel), stations, corridor buildings & roads | Chainage & vertical profile, viaduct/pier/tunnel geometry, timetable-driven train simulation | JSON / GeoJSON | Instanced trains on a polyline-chainage model, follow camera, globe translucency for the tunnel section |
| Point Cloud | LAS/LAZ scans (synthetic by default) | Classification, LOD tiling, DSM gridding, epoch differencing | 3D Tiles (.pnts) + DSM grids | Streaming LOD, eye-dome lighting, style expressions, volume from DSM |
| Urban Planning | Parcels with zoning rules, buildings | Rule engine (height, FAR, coverage, setback) | GeoJSON | Interactive massing, sun-position shadows, scenario compare |
Generated by the scripts in tools/ with fixed seeds, so every number is reproducible.
| Loading… |
Every demo page measures its own load time (navigation → interactive scene) and the average frame rate over the first seconds, then reports it anonymously. Automated test runs are excluded.
| Loading… |