Support card number changes for relay races via pre-start check

[martinkrivda]

Is your feature request related to a problem? Please describe.
Currently, handling card number changes in relay races is problematic and not sufficiently supported in the workflow.

Describe the solution you'd like

• Extend the pre-start call-up area to be available more than 5 minutes before start
• Use standard ochecklist flow with support for:
  • Multiple checklist devices running in parallel
• When an unknown card is detected:
  • Automatically trigger the camera
  • Scan the QR code on the bib number
  • Resolve and assign the correct runner/card mapping

Preconditions

• QR codes can be printed or attached (e.g. stickers) to bib numbers
• The event organizer is willing to support this process operationally (handling QR codes on-site)

[lukaskett]

QR Code Design Proposal

Notes on QR Implementation

• QR code with high error correction (H)
• black code on white background – high contrast
• matte paper (resistant to glare)
• size 4–5 cm – has a major impact on reliability
• placement is critical: avoid folds! ideally in the upper area, away from the center
  (center = chest bending/folding, bottom = wrinkling, mud)
• QR with a thin frame (quiet zone) – improves scanning reliability

Data Format

• optimized for machine processing
• fixed numeric format (no delimiters) – smaller and “cleaner” QR → faster real-world scanning
• TTTTLL
  • TTTT = relay/team number (0001–9999)
  • LL = leg number (01–99)

Parsing

• team = value // 100
• leg = value % 100

Reasons for Selection

• smaller and simpler QR → faster camera detection in motion
• QR is resistant to wear/damage
• better scanner support and faster reading compared to alternatives

Issue in Czech Republic

• in teams events (3+ legs), bib numbers are often reused (4th leg uses 1st, 5th 2nd, ...)