Deployed Sign Map

Captured transit-sign deployment snapshot

—field players
—online / offline in field
—excluded
Location evidence: Native stop IDs resolved through CAD/AVL → GTFS. Marker and navigation coordinates come only from GTFS. Two kiosks use station reference points; their bay IDs are resolved.
online offline kiosk ▧
Street tiles need internet. Embedded routes and markers work offline.
Route lines · GTFS colors · service October 28, 2026
Select a player to emphasize routes serving its resolved stop(s). Kiosk routes come from the mapped bays only.

Resolved native stop-ID crosswalk

Native stop IDs resolved by explicit source IDs. Each native GetStop response supplies SrcStopID, which joins to current GTFS stop_id. Names and coordinate differences are included for review. Native IDs must not be assumed to share the GTFS identifier namespace.

Marker and navigation coordinates always use GTFS stops.txt. Native API coordinates are retained only for comparison; OnSign locations are unused. Native stops that differ from GTFS by more than 25 metres are flagged for coordinate review. This does not invalidate their explicit ID mapping. Kiosk device positions remain unknown; station reference points and mapped bays are clearly labeled.

Player / native IDVerified GTFS stopCoordinate evidence

Sources, dates & limits