Zones and subzones
A code can say where a play started and where it ended. Courtside uses the same zone numbers as DataVolley and VolleyStation, so the zones in your files mean the same thing in every program.
The nine zones
Each half of the court has nine zones, numbered as that half's team sees them, facing the net:
net
4 3 2 front row
7 8 9 middle
5 6 1 back row
end line
Zones 1 to 6 are the usual rotation positions. Zones 7, 8 and 9 sit between the back and front rows: 8 is where a pipe attack starts.
Subzones
Each zone is split in four, lettered as the team sees it:
C | B net side
--+--
D | A end-line side
C and B are on the net side (left and right), D and A behind them.
Where the zones go in a code
| Position | Field |
|---|---|
| 10 | start zone |
| 11 | end zone |
| 12 | end subzone (A–D) |
*08AH#~~~48 is an attack from zone 4 into zone 8. *08AH#~~~48A lands in subzone A of zone 8.
Serve zones
A serve's start zone is where it was served from along the end line. From the server's left to right: 5, 7, 6, 9, 1.
Sets and blocks
A set and a block have one place: where the ball was played. DataVolley and VolleyStation both keep it in the end-zone position (11), and so does Courtside. When you type one zone on a set (VolleyStation style, see Typing styles), it goes there: 5K12B+ is a set from zone 2, subzone B.
Typing zones
- VolleyStation style: zones go straight before the evaluation.
9AQ35#is an attack from 3 into 5. One zone on an attack is the start zone:8A4starts in zone 4. - DataVolley style: zones go in their columns after the evaluation, with
~for the gaps.9AQ#~~~35. - With a combination, the start zone comes from the table, so the zone you type is the end zone:
8X56#is X5 into zone 6. - In a dot code, zones typed on one half go on the other. A block's zone is the mirror of the attack's: an attack from 4 is blocked at 2.
- On the play court, a mark writes the zones for you. See Marking where a play went.
Checks flag a zone that isn't 1 to 9 or a subzone that isn't A to D.