2.5D Viewer

GeoPackage → procedural 3D

Projects

Version history 0

Every change is a restore point. Click one to go back to it — that is itself undoable. The most recent are saved with the project; the rest last for this session.

GeoPackage

or drop a file anywhere on the map

Stored files

Cesium ion access token

Kept with the rest of your settings — in data/settings.json under the dev server, otherwise in this browser’s database. You can also set VITE_CESIUM_ION_TOKEN in .env. Terrain needs asset 1 (Cesium World Terrain); every basemap has a token-free fallback.

Coordinate reference system

Override (EPSG code, proj4 or WKT)

Vertical reference

Z offset (m)

Heights are used as absolute metres above the WGS84 ellipsoid. If your ELEV values are orthometric (MSL / EGM96), add the local geoid undulation here so objects sit on the terrain.

Height exaggeration

Each layer is bound to an object type. The type decides which procedural generator runs and which design parameters apply.

No selection

Select features on the map (Ctrl-click to add) or in the attribute table, then move them into their own layer to style separately.

Renders automatically

Map source columns onto the roles the generators need. Auto-detected guesses are pre-filled — override anything that looks wrong.

Layer

Traffic simulation

Run traffic

Vehicles nearby

Active radius m

Time rate ×

Centrelines to drive on

Vehicles are simulated only within the active radius of wherever you are looking, and removed outside it — the same rule the scene uses for geometry. Speeds, following distances and braking come from a car-following model, so queues and gaps are what the drivers produce rather than something scripted.

Train simulation

Run trains

Railway centrelines

Stations

Station layer

Carriages per train

Interval s

Dwell at platform s

Line speed km/h

Carriage length m

Active radius m

Fragments of one railway are joined into a single route, so a line surveyed in five pieces still runs a train end to end. Trains brake into each platform on a proper braking curve, hold it for the dwell, and keep a braking distance behind the train in front.

Project configuration

Layer bindings, field mapping and every per-layer style.

The GeoPackage itself, all layer bindings, styles, seeds and per-feature overrides are written to the project’s data/ folder and reopened automatically next time. Without a dev server this falls back to the browser’s own database; the rows above say which is in use.

Statistics

Sweep features in plan view and give each class a layer of its own. A class claims feature ids — nothing is written to your GeoPackage, so this stays reversible.

Work on

Dim the layers you are not working on

Label point features

Basemap

Layers on the map

Show only what you need to read the plan — the layer you are classifying, plus whichever reference layers say what each feature is. This changes the map only: the 3D scene, the layer bindings and your data are untouched.

Draw new features

Put in geometry the survey does not have — a centreline where it only recorded edges. Drawn features live in this project, never in your GeoPackage.

Shape Snapping Add to layer

Assign by reference points

Classify the whole of the working layer at once: every footprint containing a point from one visible reference layer — and only one — is assigned to a class named after it. Footprints matching several layers, or none, are left for you.

Assign the selection

Destination

drag = select · Ctrl-drag = add · Alt-drag or right-drag = pan · wheel = zoom

Classes of this layer

No selection

Drop a .gpkg file to begin

Points, polylineZ and polygons become procedural 3D geometry.

Ctrl-click to add · Shift-click for a range

Idle

Feature