Every way across the GTA, and the intelligence behind it

Reroute pulls Mapbox live-traffic driving data with congestion detail and splits the path into segments shaded by severity. Where Mapbox has no coverage it labels the stretch 'Unknown Traffic' rather than faking a clear road.

Turning on avoid-highways or avoid-tolls asks Mapbox for alternate drives that skip motorways or toll roads. Each option is badged fastest, shortest, or scenic, and if the fastest breaks your rule, a matching alternative is promoted to the top.

Mapbox's walking directions return the route, which Reroute skips entirely beyond a 5 km straight-line distance. Its comfort score rises in adverse Open-Meteo weather, so a rainy walk honestly reads as more taxing.

Your filters drop non-matching trips after the MOTIS search. If nothing survives, Reroute re-runs with defaults and labels the restored routes 'shown by relaxing your filters', unless you have set a hard restriction it must respect.

Reroute fingerprints each trip by its lines and its boarding and alighting stops, drops phantom or trivial one-stop hops, merges near-identical feeder variants, and caps the result at six distinct options.

The leave-time control switches between leave now, depart at a set time, or arrive by a deadline. Changing it re-plans the trip, and MOTIS honors a strict arrive-by deadline so you land on time rather than just setting off then.

On leave-now trips, Reroute slides your first leg to an earlier departure on the same line, sized to how often the onward line runs (about 1.5 minutes for a frequent subway, up to 12). Your arrival stays the same because you still catch the same onward vehicle, now with a real cushion at the transfer.

When live GTFS-RT data shows your route running behind, Reroute surfaces on-time alternatives within six minutes of the delayed trip's total time, each tagged with how much time it saves.

Dragging the origin or destination marker reads the new coordinates and re-plans the trip immediately. It is disabled while you are navigating, so it can never disrupt a route already in progress.

When you name a stop like Union Station, Reroute matches it to the exact MOTIS stop and boards you there directly, with no awkward walk-in leg. If the name cannot be matched, it falls back to the map location.

To build a custom route, Reroute reads the GTFS schedule to find lines serving both ends plus the TTC interchanges that connect them. For a multi-stop trip, it computes an efficient visiting order so you cover every stop with the least backtracking.

Each route blends transfer count, predicted delay severity, live traffic, and adverse weather into one comparable number (driving adds congestion, or a rush-hour proxy when live data is missing). The delay term is display-only and never affects ranking, keeping delay from ever being presented as a probability.

The badge escalates only for real, nameable reasons: slow zones, surface traffic, service alerts, closures, or bunching. Pure context like rush hour, weather, or a weekend can never raise it on its own.

Each flagged leg lists structured factors (rush hour, weather, weekend, limited data, active alert), each with an icon and an info, warning, or alert severity. A 'Limited line data' chip honestly signals when an estimate rests on a broad baseline rather than line-specific history.

It measures the buffer between arriving and departing (live GTFS-RT times when the vehicles are tracked, otherwise scheduled), then runs a statistical model over the inbound line's real delay spread to estimate the make-it odds. This transfer signal is kept separate from delay risk so the two are never conflated.

It reads map-matched GPS vehicles grouped by route and direction, flagging gaps that fall below 40 percent of that lane's own median spacing (severe below 15 percent). It is a reliability flag only, never changing an ETA, and needs at least three vehicles to avoid false positives on busy lanes.

When an active GTFS-RT warning or error alert matches the line you asked about, it raises the risk to a minimum severity, lifts expected minutes to the 90th percentile, and shows that alert first. Mock feeds, info-level notices, and system-wide placeholders never trigger it.

The tables are built from the 2022 to 2026 TTC delay log; a lookup starts from a specific line, time, and day, then widens to coarser groupings if needed and reports how specific the match was, so the app always knows how line-specific each answer really is.

Lines with no service history or no logged incidents fall back to a neutral baseline instead of a misleadingly low number, and the risk index skips them rather than passing off a system average as that line's own record. This is what stops uncovered lines from silently inheriting Line 1's pattern.

The model trains on earlier dates and is evaluated only on later ones, so it is always tested on data it has never seen, and any features that would have let it peek at the answer were removed (they had inflated an old 98 percent accuracy headline). It reports honest calibration and error measures rather than a single accuracy figure.

It flags you off-route after three straight GPS fixes more than 50 metres off the line, then pulls a fresh Mapbox route from your live position and swaps it in, resetting steps, banners, and totals.

Each trip counts its reroutes and stops requesting new Mapbox routes after 20, staying on your current route instead of looping endlessly.

Arrival is declared only when you are within 60 metres of your destination and near the true end of the route, a double check that avoids both early and missed arrivals.

Transit and hybrid trips build banner and voice guidance from each leg of your route right on your device, only ever moving forward so GPS jitter can't snap the banner back to an earlier leg.

Reroute picks a walking, cycling, or driving profile from your chosen mode and uses it for both the directions and the live session, so distances and times match how you actually travel.

When Mapbox returns no route, Reroute falls back to a straight-line path with an arrival estimate based on your travel speed and disables rerouting, so the fallback never chases a route that isn't there.

It tells an intentional close apart from an unexpected drop and retries up to 5 times with increasing waits (1, 2, 4, 8, 8 seconds), keeping all your step and route state while your session stays alive on the server.

Each GPS fix feeds your latitude, longitude, and heading into a lightweight once-a-second update that only moves and rotates the marker, so it never re-renders the whole navigation screen.

The full-screen view shows a progress bar, the current maneuver, and a 'Then' preview of the next turn; back and forward arrows let you peek ahead, and any real step change snaps live guidance back into control.

Arrival times are calculated in Toronto's local time zone, so they never show up hours off from the server's UTC clock.

When a Metrolinx connection is available, Reroute pulls the official distance-based fare for each GO station pair and returns the quoted price for your rider category and method (PRESTO, contactless, cash, or pass); it only replaces the estimate when every GO leg resolves, so real and estimated fares never mix.

Your rider-category and payment pills (Adult, Youth, Senior, Child, Post-Secondary, Fair Pass and PRESTO, Contactless, Cash, Pass) are saved on your device and flow into each route request, triggering a quick refetch that re-prices every leg, with children 12 and under always free.

Reroute checks each lot against Toronto local time, honoring weekend-free rules, free-after cutoffs, reduced afternoon rates from 3pm, and overnight gaps, so an off-hours or weekend planner sees FREE when parking really is free.

Gas is estimated from the route distance, a 9 L/100km consumption rate, and the current pump price, then $15 parking is added only when your destination falls inside the downtown core. Everywhere else in the GTA parks free, so no fee is invented, and a saved Home or Work stop parks free even downtown.

Reroute finds lots within your maximum drive radius sorted by distance, skipping paid-only GO stations and suspended lines, then uses them to build drive-to-station options and to answer the Google Gemini assistant's parking questions.

Reroute pulls Open-Meteo daily conditions (the same signals the delay model trains on), flags adverse weather, and shares one cached lookup across every route; the map's weather chip shows temperature and condition and opens the Commute Coach panel, falling back to default Toronto conditions when the service is down.

Peak-only lines (like Richmond Hill) are checked against Toronto local time; outside the morning and afternoon windows or on weekends, the card shows 'Weekday peak service only' and the station is left out of routing and transfer picks so you're never stranded.

Reroute filters to eligible stations (not excluded, not on a suspended line) and picks the nearest one, tagging that card with a 'Best' badge as an at-a-glance default.

A station name is matched through a cascade (exact match, alias table, normalized index, suffix stripping, then substring), so routing, chat, and the station browser all point at the same physical lot no matter how you spell it.

Reroute prefers a genuinely surveyed parking entrance and otherwise routes to the platform, marking it 'Approximate location' instead of silently pretending the platform is the lot entrance.

Recents and favorites live in two separate stores in your browser: recents (capped at 6) and saved places (capped at 50), so favoriting something never bumps a recent. Each recent is kept with its exact coordinates on every successful trip, so re-planning skips a fresh location lookup.

The More screen reads and writes every preference, and changing one triggers a debounced re-plan so routes update automatically. It adapts to your device, docking as a side panel on desktop or opening full-screen on mobile.

Your fare category (adult, youth, senior, child, post-secondary, or Fair Pass) and payment method (PRESTO, contactless, cash, or pass) are saved and applied to every route, so each transit leg is priced to exactly what you pay.

A nine-notch slider snaps your maximum drive distance onto a 5 to 25 km grid in 2.5 km steps. Committing a value re-plans your park-and-ride routes around the new radius.

Per-line chips, each shown in its official GTFS brand color, switch map overlays on and off, so the transit map draws only the routes you keep visible.

Three toggles control the traffic, reachability, and alerts map layers. Traffic recolors drive routes using Mapbox congestion data, while alerts surface live GTFS-RT shutdowns and slow zones on the map.

The whole trip, its route shape downsampled to at most 220 points and stored as a compact Mapbox polyline, is encoded directly into the link. Decoding fails safely, so any tampered or oversized link is rejected and shows a friendly invalid-link screen.

Opening a shared link loads the trip's start and end points and immediately re-plans for right now, dropping the original saved departure time. You get a current-time plan reflecting live conditions, not a replay of the sender's trip.

Every shared link is checked so both endpoints fall inside a Greater Toronto Area box (Hamilton to Oshawa to Barrie); if either is outside, the link is rejected. This keeps a crafted link from ever driving an out-of-region map request on the app's Mapbox token.