Where should the next route go?
TransitFlow has always let you draw a route anywhere. Now it can tell you where a route is worth drawing.
Right now the map is a blank cheque. You can extend the Kitchener line to Cambridge, spin up a Brampton circulator, or connect two suburbs that already have four buses between them, and the tool treats all of it the same. There has never been a signal for this corridor is badly served and a lot of people travel it.
That signal is computable. The GO network is a graph, the timetables are exact, and “how long does it take to get from A to B, and how does that compare to a straight line” is a shortest-path problem, not a judgement call. The new Gap Finder panel ranks the worst-served corridors and hands you a starting point in the route builder.
Timetable in, shortest paths out
Every GO station and terminal is a node. Every scheduled trip between two stops on a typical weekday becomes an edge, weighted by how long the ride takes. Add a flat penalty for each transfer, cap the trip at three legs, and you can compute the fastest journey between any two points on the network.
Compare that journey to the straight-line distance at highway speed. When transit takes more than roughly twice as long, and a lot of service already runs through both endpoints, the corridor scores highly. Near-duplicate corridors collapse to one, radial trips that naturally route through Union are dropped, and, since this phase only proposes bus routes, both endpoints have to be places a bus can actually stop.
It's arithmetic over the schedule data TransitFlow already ships. No model, no inference.
Oakville and Clarkson to the 407
The Lakeshore West line runs a fast, frequent service into downtown Toronto. It has almost nothing going the other way. To reach the 407 Transitway corridor (the east-west busway that links Brampton, Vaughan and Markham), a rider from Oakville or Clarkson today goes inbound to a hub, transfers, and doubles back north.
- Straight line
- ~31 km
- Best transit today
- 3 transfers
- A direct 407 express
- ~35 min
A single bus up Hurontario and onto the 407 would put the whole Transitway network, and the 400-series park-and-ride lots along it, within one seat of the Lakeshore West stations. It's the kind of tangential connection a hub-and-spoke network structurally can't provide, and exactly what GO Expansion keeps identifying as a gap.
Waterloo to Niagara: the weekend case
Kitchener-Waterloo, Hamilton and Niagara are three of the busiest leisure-travel markets in the region: two university towns and a destination that draws millions of visitors a year. On a weekend, getting between them on transit means a transfer at Union and the better part of an afternoon.
- Straight line
- ~126 km
- Best transit today
- 3+ transfers · 3½ to 4 h
- Direct via Hwy 403/QEW
- ~2 h
This example also shows the tool's current blind spot. Gap Finder only looks at a weekday timetable, so it can't see that the demand here is a Saturday pattern, not a Tuesday one. A route serving students and visitors between the three campuses and the falls would barely register on the current score, and it's one of the clearest opportunities on the map. Weekend and time-of-day analysis is the next thing on the list.
What the panel shows this week
The live ranking mixes a few hand-picked regional corridors (starred) with the auto-discovered ones. Near the top:
- ★ Cambridge ↔ Bramalea GOno route today
- ★ Kitchener-Waterloo ↔ Niagara Falls3 h 27 · 4 transfers · ~1 h 41 direct
- ★ Guelph ↔ Niagara Falls2 h 23 · 3 transfers · ~1 h 26 direct
- ★ Guelph ↔ Highway 4071 h 12 · 2 transfers · ~51 min direct
- Aldershot ↔ Meadowvale1 h 41 · 2 transfers · ~26 min direct
- Cooksville ↔ Georgetown1 h 19 · 3 transfers · ~20 min direct
What's next
See the ranking, jump into the builder with the corridor's endpoints pre-filled, and design the alignment yourself.
Score the route you build: re-run the network with it added and report the minutes saved, transfers removed, and residents brought within a short walk of a one-seat ride. Plus weekend and peak-hour analysis.
Real travel-demand data in place of the current proxy, real road times in place of a straight line, and an assistant that drafts a first route for you to adjust.
The numbers are estimates from a first-pass model. It uses one weekday timetable, a straight-line stand-in for driving time, and trip counts as a rough proxy for demand, so it under-counts markets that no service exists for yet, and it can't see weekend or seasonal patterns. It ignores agency and municipal boundaries. TransitFlow is a what-if sandbox for exploring transit ideas, not a proposal to GO Transit or Metrolinx.
/ References
- Metrolinx: 407 Transitway and GO Expansion
- GO Transit: system schedules (the timetable data)
- Statistics Canada: commuting flows (the planned demand input)