← Hong Kong Performing Arts Venues Seat Configuration

Data format

How the seat lists are structured, and the rules behind them. Schema hkperf-venue-seats/seatlist@0.5. Last updated 4 October 2026.

In short: one JSON file per seating layout, with a CSV beside it. Each file lists the parts of house, their rows, the blocks within each row and the seats in each block, in number order, with the marks the plan prints. Everything is a fact read from the operator's published plan, with its source. There are no coordinates for single seats: where rows sit around the stage is recorded as an arrangement, not a measurement. Only round and surround halls, whose rows bend around the stage, also record where each run of seats lies on the plan (see Arc layouts).

Every file is checked when it is built: the seats counted must equal the totals printed on the plan.

Contents

  1. Files
  2. The venue index
  3. A seat list, top to bottom
  4. Parts of house, rows, blocks, seats
  5. Marks
  6. Seats with no printed number
  7. Totals and the count check
  8. Orchestra pits
  9. Sources and references
  10. Location
  11. Banks: arrangement around the stage
  12. Arc layouts: round and surround halls
  13. Rooms with more than one layout
  14. The CSV
  15. What the build checks
  16. Versions
  17. Drawing a map with an AI model

1. Files

FileHolds
data/index.jsonthe list of seat lists, with names, region and date added
data/<id>.jsonone seating layout of one hall: the full record
data/<id>.csvthe same seats, one line per seat box, for spreadsheets

An id is the venue's short code and the hall, e.g. ktt-aud (Kwai Tsing Theatre Auditorium) or swcc-th (Sheung Wan Civic Centre Theatre). A room with several seating layouts has one file per layout, e.g. ekcc-lab-end and ekcc-lab-thrust. Text is UTF-8; the CSV starts with a byte-order mark so spreadsheet apps read the Chinese names correctly.

2. The venue index

{"venues": [
  {"id": "swcc-th", "name_en": "Sheung Wan Civic Centre Theatre", "name_zh": "上環文娛中心 劇院",
   "region": "Hong Kong Island", "added": "2026-09-26", "file": "swcc-th.json"},
  ...
]}

region is Hong Kong Island, Kowloon or New Territories, and must agree with the venue's district. added is the date the seat list was added to this project.

3. A seat list, top to bottom

KeyHolds
schemathe format and version, hkperf-venue-seats/seatlist@0.5 (files written before 0.5 carry @0.4; see Versions)
venueid, name_en, name_zh
sourcethe seating plan the file was read from (see sources)
referencesother operator documents that confirm or contradict a figure, with quotes
locationaddress and coordinates, each with its source
layoutseat_1_side, an optional stage_label, a note on how the plan is numbered, and optionally banks, or for a round hall arrangement: "arc" with arc and aisles
markswhat each mark letter means on this plan
printed_totalsthe totals printed on the plan, per part of house and Total
totals_sourcewhere the totals come from, when the plan prints none (optional)
orchestra_pitseach pit option and the rows it removes (optional)
standingnumbered standing places, where the plan prints them (optional); after names the part of house they follow
zonesthe seats: parts of house → rows → blocks → seats
count_checkthe counts behind the build check, per part of house

4. Parts of house, rows, blocks, seats

zones[]          a part of house: name, name_zh, optional sections, counted_in, count_includes, count_excludes, default_off
  rows[]         a row: its label, optional marks, inferred_numbers and note
    blocks[]     a run of seats between aisles
      seats[]    seat ids, in number order from seat 1's end

A real row, from the Sheung Wan Civic Centre Theatre:

{"row": "W",
 "blocks": [{"seats": ["1", "2", "3", "4", "X1", "X2"], "side": "left"},
            {"seats": ["W1", "W2", "9", "10", "11", "12"], "side": "right"}],
 "marks": {"X1": "X", "X2": "X", "W1": "W", "W2": "W"},
 "inferred_numbers": {"X1": "5", "X2": "6", "W1": "7", "W2": "8"},
 "note": "The left block ends with two solid black management boxes after 4; the right block opens with two
          wheelchair boxes before 9. The four boxes between 4 and 9 fill 5-8 exactly. No centre block."}

layout.seat_1_side says which end of each row seat 1 is at, as drawn with the stage at the top (left or right), and layout.note explains anything unusual: skipped numbers, missing row letters, rows that restart their numbering. Where the front is not a stage, layout.stage_label gives what to draw in its place, e.g. "SCREEN 銀幕" for a cinema.

5. Marks

A row's marks map a seat id to one or more letters. Each file's top-level marks gives the plan's own wording for each letter it uses.

LetterMeaningIn the printed total?
Wwheelchair spaceyes
Xmanagement seat, kept by the venueno
Rrestricted sightlineyes
Llimited legroomyes

Letters combine: "RL" is a seat with both a restricted sightline and limited legroom.

6. Seats with no printed number

Plans often print wheelchair spaces and management seats as boxes with only W, a cross or a solid fill. Such a box keeps a label (W1, X1…) and gets a number in inferred_numbers only when that number is certain:

Otherwise it stays unnumbered, and the row's note says what is likely and that it is not printed. The CSV gives each seat's number_basis: printed, inferred or none.

7. Totals and the count check

printed_totals copies the plan's figures: {"Stalls": 172, "Gallery": 71, "Total": 243}. The rule that ties the seats to them:

Printed total = boxes on the plan − management seats (X). Wheelchair, restricted and limited-legroom seats are counted. This rule is our reading, not printed on the plans; it has matched every part of house of every plan so far.

count_check records the arithmetic for each part of house: boxes, each mark's count, boxes minus X, and the printed figure.

Totals from elsewhere. Where a plan prints no totals, totals_source says where the checked figures come from, e.g. the operator's technical sheet (Hong Kong Cultural Centre Grand Theatre).

Parts of house totalled together. Where the operator gives one figure for two or more parts of house the plan names separately, each of those zones carries "counted_in" with the name of that figure in printed_totals, and the zones are checked together against it. The Grand Theatre's Stalls 1 and Stalls 2 have "counted_in": "Stalls" (788); count_check then has an entry for Stalls listing its zones.

Seats a figure leaves out. Where the operator's figure leaves out a kind of seat the plan draws, the zone carries "count_excludes" with its mark and a count_note: Ko Shan Theatre's plan adds its six wheelchair spaces to the total separately, so its Stalls have "count_excludes": ["W"] and are checked as boxes − X − W. A part of house the operator gives no figure for at all — a promenade the plan draws but the tier figures leave out — carries "count_excludes": ["*"] (every box in it is left out) and "default_off": true, so it is closed in the default configuration and the checked total still matches. The Hong Kong City Hall Concert Hall's promenade is one.

Exceptions. Where the operator's figure for a part of house also counts its management seats, that zone carries "count_includes": ["X"] and a count_note explaining it; the check then counts every box there, and count_check records the exception. Nothing is adjusted to make a figure fit.

8. Orchestra pits

{"name": "Orchestra pit (10 × 2 m)",
 "rows_removed": ["AA", "BB"],
 "rows_basis": "stated",
 "rows_reasoning": "The technical sheet names the rows. AA + BB = 17 + 18 = 35 boxes ...",
 "seats_removed": 35, "total_with_pit": 447,
 "stated": ["seats_removed"],
 "source": {"url": "...swcc-th-lfe.pdf", "document_version": "V. 2026.03.09", "quote": "35 seats will be lost ..."}}

9. Sources and references

source identifies the plan exactly: publisher, url, file name, sha256 of the file read, the plan's printed version if any, and the credit line; where the file holds more than one plan, pdf_page (from 1) names the page read. If the operator replaces the file, the hash shows the data was read from an earlier version.

references are other documents from the operator, each with URL, title, printed version, hash, date retrieved, exact quotes and a note. They confirm totals, wheelchair numbers and pit figures, and record conflicts openly, e.g. a booking form that gives 592 where the plan and technical sheets give 596.

The data comes only from the operator's own published material. Ticketing and box-office data, and seat maps drawn by others, are never used.

10. Location

location holds address_en, address_zh, district, latitude and longitude, reproduced from LCSD's open data on DATA.GOV.HK. Each part names its source record (coordinates_source, address_source), and a script re-reads the open data to confirm them. Coordinates are LCSD's point for the building, not for the hall.

11. Banks: arrangement around the stage

In most halls every row faces the stage, and the map draws them one under another. Some rooms seat the audience on more than one side: a thrust stage, rows along the side walls, boxes. For these, layout.banks records the arrangement, still without coordinates. A bank is a group of rows, or single blocks of rows, on one side of the stage.

KeyHolds
ida name for the bank, e.g. stalls-left
sidefront, back, left or right of the stage (back is the far side, e.g. the opposite audience of a transverse or arena stage)
rowsits rows, nearest the stage first: a label for a whole row, or {"row": "A", "block": 1} for one block ([2, 3] for several); add "zone" where row letters repeat across parts of house
seat_1which end seat 1 is at: left/right for rows drawn level; downstage/upstage for upright rows
rows_runside banks: along the side (upright; default) or across (level, facing the stage)
in_lineupright side rows that follow one another down a wall, rather than sit side by side
afterside banks against the walls after a front bank, e.g. boxes between stalls and balcony
level_withside banks against a side wall, starting level with a named row of a front or back bank, e.g. boxes beside the stalls
besideside banks whose rows sit level with the same rows of a front bank, across the aisle
alignother side banks: level with the stage's front (downstage) or back (upstage), centred on the stage (stage), beside the front banks (house), or along the room (room)

The long-thrust layout of EKCC's The Lab, for example:

"banks": [
  {"id": "stalls-left",  "side": "left",  "rows": ["BA", "BB", "BC", "BD"], "seat_1": "downstage", "align": "upstage"},
  {"id": "stalls-right", "side": "right", "rows": ["DA", "DB", "DC", "DD"], "seat_1": "downstage", "align": "upstage"},
  {"id": "stalls-end",   "side": "front", "rows": ["AA", "AB", "AC", "AD", "AE", "AF"], "seat_1": "left"},
  {"id": "gallery-left", "side": "left",  "rows": ["BN"], "seat_1": "downstage", "align": "room"},
  ...
]

The viewer draws the stage in the middle, front banks below it, back banks above it (rows level and facing the stage) and side banks beside it. Order and neighbours follow the plan; distances do not. Every block of every row must be in exactly one bank. Files without banks are drawn with every row facing the stage.

12. Arc layouts: round and surround halls

Where the seats wrap the stage, rows bend around it and banks cannot say where. Such a file sets layout.arrangement to "arc" and records where each block lies, measured on the plan: East Kowloon Cultural Centre's The Theatre (seats on three sides) and the Hong Kong Cultural Centre Concert Hall (seats all round). Angles are bearings, degrees clockwise from the top of the plan, about layout.arc.centre; lengths are in the plan's units. Seats are not placed one by one: the viewer spreads a block's seats evenly along its run.

KeyHolds
layout.arccentre, the point bearings are taken about (plan units); scale, plan units to the drawing; drawing options: stage_span (a stage wedge at the top, in degrees) or stage: {"shape": "circle", "radius": r} (a stage in the middle), rotate_seats, ring_gap, and row_labels: "along" (row labels in line with each row's ends rather than above them)
layout.aislesbearings of the aisles several rows share
block shape, view, offset, start, end a straight run ("line") facing bearing view at distance offset from the centre, its first and last seat centres at bearings start and end; an "arc" block follows a circle of radius instead
block runsa block that bends: one entry per straight run, each with count (how many of the block's seats it takes, in order) and its own shape, view, offset, start, end
block inner, outerthe radius band the block's seats fill
zone arcfor rows with no block geometry, the ring: start, span, dir (cw or ccw); optionally label_at, where the plan prints the part of house's name, [x, y] from the centre
zone vomitoriaentrances cut through some rows: rows, bearings from–to, radii inner–outer, and a note

A block of the Concert Hall's Stalls 1, row A, which bends twice:

{"seats": ["18", "19", ..., "35"],
 "runs": [{"count": 6, "shape": "line", "view": 25.34, "offset": 196.26, "start": 205.0, "end": 191.22},
          {"count": 6, "shape": "line", "view": 360.0, "offset": 200.91, "start": 188.08, "end": 174.41},
          {"count": 6, "shape": "line", "view": 334.41, "offset": 192.2, "start": 171.3, "end": 157.44}],
 "inner": 185.2, "outer": 209.4}

Everything else is as in any other file: the parts of house, rows, blocks, seat ids, marks, totals and checks. A reader that ignores arrangement still gets every seat and every count.

13. Rooms with more than one layout

Flexible rooms publish one plan per seating layout, e.g. an end stage and a thrust stage. Each layout is its own seat list with its own totals; a layout's name is in its venue names, and its layout.note says which other layouts exist.

14. The CSV

One line per seat box, in the order of the JSON:

ColumnHolds
venue_idthe seat list's id
part_of_house, part_of_house_zhthe zone's names
row, blockthe row label, and the block's position in the row (1 = seat 1's side)
block_areathe block's side or area, where recorded
bankthe bank the block is in, where the layout has banks
seatthe seat id (12, W1, X2)
seat_number, number_basisits number, and whether that is printed, inferred or none
marksthe mark letters, then one 0/1 column each: wheelchair, management, restricted_sightline, limited_legroom
orchestra_pitsthe pit options that remove this seat

The viewer's download adds counted and not_counted_reason for the configuration chosen on screen.

15. What the build checks

A seat list is written only if all of these hold; otherwise the build stops with the reason.

Where a plan's PDF carries text, every seat number in the file was also matched one for one against it; scanned plans were read by eye from zoomed crops. Each script's header says which.

16. Versions

VersionChanges
seatlist@0.5adds the arc layout for round and surround halls (layout.arrangement, layout.arc, layout.aisles, block geometry, zone arc and vomitoria) and the bank alignment stage. Nothing earlier changed, so a 0.4 reader still reads every seat; files written before 0.5 keep @0.4
seatlist@0.4adds the back bank side for a far-side audience (transverse and arena stages); nothing else changed
seatlist@0.3adds optional layout.banks and the CSV's bank column; nothing else changed
seatlist@0.2the first published format

Planner files have their own formats (plan@0.2, plan-protected@0.1), described in the repository's README.

17. Drawing a map with an AI model

The viewer is one way to draw the data. If you would rather have a language model draw a seat map for your own use, here is an example prompt. Attach or paste one seat-list JSON file after it. It asks for a self-contained SVG and for the model to count its own output, which you should still check against the file's printed_totals.

You are drawing a schematic seat map from a structured seat list. The seat list follows the
schema hkperf-venue-seats/seatlist@0.5 (https://code.denniswu.org/hkperf-venue-seats/schema.html).
It is attached below. Produce one self-contained SVG, then a short check report.

WHAT THE DATA IS
- zones = parts of house (e.g. Stalls, Balcony). Each zone has rows; each row has blocks (runs of seats
  between aisles), listed from seat 1's end; each block lists seat ids in number order.
- Seat ids are printed numbers ("12") or labels for boxes printed without a number ("W1", "X1").
  If a row's inferred_numbers gives a number for such a box, you may show it in a tooltip, not on the seat.
- A row's marks map seat ids to letters: W wheelchair space, X management seat, R restricted sightline,
  L limited legroom. Letters can combine ("RL").
- There are NO seat coordinates. Do not invent positions, curves, rakes or distances. Draw a schematic.
  The one exception is rule 0 (arc layouts), whose block positions are measured from the plan.

LAYOUT RULES
0. If layout.arrangement is "arc", ignore rules 1-2. Bearings are degrees clockwise from up, about
   layout.arc.centre; multiply every offset, radius and inner/outer by layout.arc.scale (default 1).
   For each block (or each entry of its runs, taking the next "count" seats): its seats lie evenly on a
   straight line from the point at bearing "start" to the point at bearing "end", where a point at bearing
   b lies at distance offset / cos(b - (view + 180)) from the centre. Turn each seat to run along the line.
   Draw the stage as layout.arc.stage describes (a circle of that radius at the centre), else as a wedge
   of stage_span degrees at the top. Put each zone's heading at its arc.label_at (x, y from the centre,
   scaled) if given, else below the seats. Label each row at both ends, just beyond the end seats.
1. If layout.banks is absent: put a stage box at the top. Draw each zone in order, with its name
   (name and name_zh) as a heading, and each row as one horizontal line under the previous one, centred.
   Within a row, draw blocks left to right in drawing order: if layout.seat_1_side is "right", reverse
   the block order and the seat order in each block, so seat 1 ends up on the right. Leave an aisle gap
   between blocks. If two neighbouring blocks skip numbers (e.g. 11 then 32), leave room for the missing
   seats instead of an aisle. A block with "side": "left" or "right" goes to that edge of the widest row.
2. If layout.banks is present, follow it instead. Each bank is a group of rows (or single blocks,
   {"row": "A", "block": 1}) on one side of the stage, listed nearest the stage first.
   - Put the stage in the middle. Front banks go below it, one after another, rows level and centred.
   - A row reference may name its part of house ("zone") where row letters repeat across levels.
   - Side banks (left/right) go beside it. With rows_run "along" (default) each row is an upright column
     and the bank's rows sit side by side, nearest the stage innermost; with in_line true they follow
     one another down the wall instead. With rows_run "across" each row is level, one behind another.
   - seat_1 says which end seat 1 is at: left/right for level rows, downstage/upstage for upright rows
     (downstage = the end nearer the front audience).
   - after: the bank sits against the side walls after the named front bank. level_with: it sits against
     the side wall, starting level with the named row of a front or back bank. beside: each row sits level with
     the same row of the named front bank, across the aisle; rows it lacks continue below.
   - align (other side banks): downstage = level with the stage's front, upstage = with its back,
     stage = centred on the stage, house = beside the front banks from their first row, room = centred along the whole room.
   Keep the order and neighbours exactly; distances are free.
3. Label every row at both ends (or at both ends of each column) with its row label.
4. Draw every seat as an equal square with its seat id inside; wheelchair seats show "W". Style marks:
   W filled blue, X crossed out and greyed (not counted by default), R with an inner outline,
   L with a light fill. Add a legend for the marks this file uses (file's top-level marks has the wording).
5. For each orchestra_pits entry, add a dashed outline around its rows_removed (the whole row, or only the
   block an entry names, found the same way as a bank's rows), labelled with its name and
   "rows stated" or "rows inferred" from rows_basis. If standing.places exists, draw them as round places in a
   row, after the part of house standing.after names (the last part of house when it is absent).
6. Under the map, add this text, unchanged: "Not the venue's seat plan. This map is drawn from the seat
   data: a machine-assisted reading of the rows and seats of the venue. It is not the actual seat plan.
   For the actual seat plan, refer to the version published by the operator:" followed by source.url.
7. Title the map with venue.name_en and venue.name_zh. Credit: source.credit. Data: CC BY 4.0.

SVG REQUIREMENTS
- One <svg> with a viewBox; no external files or scripts; readable text (seat numbers at least 7px).
- Give each seat a <title> tooltip: row, seat, part of house, mark meanings, and any row note.
- Use data attributes on each seat: data-zone, data-row, data-seat, data-mark.

CHECK REPORT (after the SVG)
- Count the seat boxes you drew per zone, and how many carry X. Show: boxes - X = count, and compare it
  with printed_totals for each zone and for Total. They must match; if not, say which rows differ.
- List anything in the data you could not place, rather than guessing.

SEAT LIST:
[paste or attach one data/<id>.json here]

The drawing is yours to use under the data's licence (CC BY 4.0, with the credit line). It is a schematic, like the viewer's map, not the venue's seat plan.