Canvas

Every floor, one chart.

Up to nine floors live in a single chart document, each with its own blocks, objects, focal point, and background. A floor elevator moves buyers between them, or stacks them all in one view.

Explore highlights

Sound familiar?

A map per floor

Mezzanine.svg, Balcony_final.svg. Separate maps mean separate maintenance and buyers who book the wrong level.

Which floor am I on?

Switching levels by swapping pages loses all context. The elevator keeps the venue whole while floors change.

Floor logic in app code

Tabs you bolt on yourself drift from the data. Floors are chart data here. The renderer already understands them.

Multi-story without the mess

01Floors as dataEach floor carries its own blocks, objects, focal point, and background image, up to nine per chart.
02The floor elevatorA built-in control moves between levels; lock it to a floor when the context demands.
03Stacked all-floors viewStage or isometric projection shows every level at once. Buyers see where the balcony sits above the stalls.
04A floor APIgoToFloor, goToAllFloorsView, getFloors, plus change events for your own chrome.
05Per-floor backgroundsEach level traces its own plan image, so the ground floor and the gallery never share a compromise.
06One pin per sessionA session pins one chart revision, floors included, so multi-story inventory stays consistent.

Floors in three moves

  1. 01Add the levelsGround, mezzanine, balcony, each a named floor in the same document.
  2. 02Choose the viewElevator navigation, or the stacked all-floors projection.
  3. 03Let buyers rideFloor changes fire events; your UI stays in sync.

Ride the elevator

Multi-floor venues, live in the demo.