Build an event from SpeedSkatingResults start lists

In long track, pairs are often drawn upstream, in SpeedSkatingResults. EVENT reads its start lists (JSON files), one at a time: the first one creates the event, the next ones add their distance, and the overall standings and the schedule follow.

Invented example: the "Imaginary Cup 3" (January 5 to 8), one file per distance: 500 m Women, 1000 m Men, 3000 m Women…

Open the first file

Choose the file
With no event open: FileOpen a SpeedSkatingResults start list… (also on the home page). One file at a time.
Read the preview
The What the start list changes in the event window says everything before writing: the new event (long track, Time mode, 400 m track), the distance, the races, the athletes, the categories, the warnings (an athlete without a seedtime, for example). Set the Changeover time between two pairs (m:ss): the schedule uses it.
Read the start list
Read the start list writes everything and opens the event.

The event has the competition's name, dates and venue; the "500m Femmes" distance has its races, one per pair.

The next files

A file from the same competition (same name and same start date) adds its distance, or reloads it if it is already there (same race number in the file). With no event open, the competition's event is found and opened: never a duplicate.
A file from another competition is refused in the open event, with the reason; EVENT offers to open (or create) that other competition's event.
A file already read (same content) does nothing.

What each file creates

In the file	In EVENT
The competition	The event: name, dates, venue; long track, Time mode, 400 m track; the shared long-track template if there is one, otherwise a minimal template (penalty codes, finish line, approximate race time).
The athletes of the start lists	The entries (bib = number, country, province); only the athletes on the start list are entered. Categories created from the file's codes (SA, N2, 30…).
The distance	An event distance (name, distance, gender, day), recognized afterwards by its number in the file.
The pairs	The line-up: one race per pair, inner lane in position 1, outer in 2 (quartets: 3 and 4); a pair with a single athlete stays a race. Mass starts (helmets) and team pursuits (two races per pair) too.
seedtime, sb, pr	The entry time (seedtime, otherwise sb, otherwise pr); sb and pr become performances.

Reload a distance

SpeedSkatingResults exports a list again when an athlete withdraws or a pair changes. Open the new file (same menu, or Reload from a SpeedSkatingResults start list… in the Line-up view):

races not yet started are replaced; a started race is never touched (the discrepancy is reported);
an athlete missing from the new file is removed from the distance, never if they have a time;
the preview shows what changes before writing, and everything goes to the log.

What is decided in SpeedSkatingResults

In such an event, the entry import is removed, the distance check boxes of the Entries tab are greyed out, and Generate races gives way to reloading: the line-up is imposed.

Overall standings, schedule, FINISH

The overall standings show each distance as soon as its file is read, athletes without a time ordered by pair and lane.
The schedule has one session per day; each pair lasts the slowest entry time plus the changeover time (no time: the approximate race time). Breaks and sessions placed by hand stay when reloading.
Towards FINISH, nothing changes: direct link, races in the database, .cfevent file, results back. The distances are reordered with Move up and Move down.