QR Codes at Transit Stops: Real-Time Arrivals and Journey Planning

1. Use Case

A rider scans the QR at a stop and sees the next few arrivals for that stop in their browser, no app required. The QR encodes a URL with the stop ID embedded.

2. URL Pattern

`https://transit.example.com/stop/12345`

The stop ID is in the URL, so each stop has a unique code. The page queries the GTFS-Realtime feed and renders arrivals. The QR code itself is static and cheap to print.

3. Offline Fallback

If the server is unreachable, display the scheduled timetable from a cached fallback. Something is better than an error page.

4. Physical Maintenance

Bus stop signs face weather and vandalism. Use durable aluminium panels, level Q error correction, and a printed stop number as a text fallback for phone-based timetable lookups.