Toronto Transit Reachbrowser build

Classic OpenStreetMap tiles, no API key. Click anywhere on the map: every stop you can reach is shaded by how long it takes, over the full TTC + YRT + MiWay network. The search runs in your browser.

This is the browser-only build. There is no server: the whole graph is inlined in the page and the reachability search — a port of the same Dijkstra in routing.py — runs in JavaScript. Every wait is therefore modelled (half the typical headway for the mode running the line), not measured: GTFS-realtime needs a backend to fetch it, so live waits and service closures are not in this build, and neither is trip planning. Run the Flask app for the live-data version →

Loading network…

Where you are

Heat radar

Shade level 60%

Browser-only build

Trip planning needs the local Flask app — see the README. This build answers the reach question only: click anywhere and every stop is shaded by how long it takes to get there, computed here in the page.

Datamodelled

Time filter

Reachable within 30 min

0 min1530 min

Nearest stop

Name—

Est. time—

Reachable stops—

Fixed schematic network model (TTC subway/streetcar/bus + YRT/Viva + MiWay + highway corridor hubs) with typical dwell/wait/transfer times — not a live feed. In this build the routing runs in the browser, over a copy of the graph generated from the Python network package by tools/build_static.py; the Flask app in the repository is the same page with a live feed and a trip planner behind it.