Seating maps

A seating map belongs to a location. Find locations and existing maps with listLocationSeatingCharts (museumId for all locations of a museum, or id for one location).

The map is organised in levels, for example Section → Row → Seat. Each level has a name (label), an order from outermost to innermost, and public (whether guests see the level). Level names are unique within a map.

The places on a map form a tree of entries. Every entry sits on one level (organizationDimensionId), has a label (value, for example "A", "3", "12"), and points at the entry one level up (parentId). Top-level entries have no parent.

A capacity is attached to the entry that is sold as one unit, such as a row of 12 seats or a standing section for 200 people. Capacity is at least 1.

Build top-down

1. Create the map on a location (createSeatingChart).
2. Create levels, outermost first (createSeatingChartOrganizationDimension).
3. Create entries level by level (createSeatingChartOrganizationNode).
4. Attach capacities (createSeatingChartCapacityNode).

A map stays on the location and museum it was created for. Refer to levels and entries by id, never by name — names can be edited. When updating something by id, only the fields you pass change; pass null to clear a field.

A level cannot be removed while entries still use it. Remove child entries before their parent. Fetching a removed item by id still works; it carries the time it was removed.

Guest-facing names: see Languages.

Visual layout

A seating map drawing is a template: LAYER, TEXT, and SEAT nodes with x, y, and rotation. A SEAT should point at a capacity.

Prefer createTemplate, getTemplate, and insertTemplateNodes (seating-chart kind from getTemplateSchema). Attach the drawing with updateSeatingChart and templateId. Open the seating-map-layout guide for node rules.

The five seating-map layout tools still attach a drawing to a map. They are obsolete; prefer the template tools. See Seating map layout.