Methodology

How the rankings are built

Every number on this site comes from a public dataset, joined by a documented rule. This page is the rule book. The data is rebuilt from the source on every deployment; the current build was generated Oct 25, 2026.

Sources

Two ways to count collisions

The most collisions rankings use the police dataset — the big number, dominated by property-damage collisions, which tracks volume closely. The most dangerous rankings use the City's KSI dataset — only collisions in which someone was killed or seriously injured, a far smaller number that says more about consequence than frequency. Every intersection page shows both, and neither is a statement about fault.

Names

The City names each node by every road that meets there ("Spadina Ave / Bloor St W / Spadina Rd"). Pages use the spoken two-street form — "Bloor & Spadina" — chosen by rule: ramps, trails and river names are dropped, a road that continues under a different name is counted once, east/west or north/south halves are merged, the more prominent street (the one appearing at more intersections citywide) goes first, and a short list of well-known pairs overrides that order ("Jane & Finch", "King & Spadina"). The formal name and the City's node name appear under every heading.

What an intersection is

An intersection is a node in the City's centreline network. Its name is the City's own (e.g. "Kennedy Rd / Lawrence Ave E"), shown here with an ampersand. An intersection gets a page when it has a traffic count dated Jan 1, 2015 or later, or at least one KSI collision matched to it. 5,838 of 6,122 counted intersections qualify in this build.

Matching collisions to intersections

Each collision record carries coordinates. KSI person-level rows are first combined into one collision per collision ID; police records are deduplicated by event ID. A collision is attributed to the nearest intersection node within 65 metres — roughly the width of a six-lane arterial crossing — whether the police coded it as intersection-related or mid-block; beyond 65 m it is attributed to no intersection. In this build 5,253 of 7,668 KSI collisions matched an intersection.

A collision counts as fatal if any involved person's record is classed Fatal; as involving a pedestrian / cyclist / motorcyclist if the City flags that road user in the collision; and as in darkness if the light condition is recorded as dark (with or without street lighting).

Windows and comparability

Red-light cameras

Cameras are joined to intersections by the City's intersection ID, falling back to the nearest node within 40 m. Ontario ended automated speed enforcement on 14 November 2025; speed-camera locations are therefore historical and are not shown as active.

Tickets. The City publishes Red Light Camera Annual Charges as a spreadsheet: one row per camera site, one column per year since 2007. It is joined to the camera list by the City's location code (the spreadsheet numbers sites from 2501, the camera list from 6001 — the same sites, offset by 3,500), with a fallback on the two street names. "Charges" are tickets issued, not convictions. The current year is partial — the file states the cut-off date and the pages repeat it — so rankings use the last complete year. Sites the City has decommissioned stay in the spreadsheet and are listed separately with their totals. In this build 301 of 301 cameras matched a ticket record (0 by street name).

Collisions recorded after the window closed (from January 2026 to the latest date in each dataset) are never hidden: they appear on the intersection page as a separate "since January" line in the cards, tables and text, and a fatal one is stated in the first paragraph. They are simply not part of the ranking, which needs complete years.

"What's here" layers

Each layer is a proximity join from the intersection node, computed at build time from a City dataset. On the 79 corners along Steeles Avenue, the city limit, one side of the street is in Vaughan or Markham and outside every dataset here; those pages say so. Distances are the distance you would walk — see “How far is it?” below.

Layers are best-effort: if a source is unavailable when the site is rebuilt, that layer is left blank rather than stale.

How far is it?

Every distance on this site is the distance you would walk, not the straight line between two points. A shop 200 m away across a rail corridor is not a 200 m walk, and saying so would flatter every corner in the city that sits next to a barrier.

The walk is measured on the City's own Toronto Centreline — 59,033 segments of street, laneway, trail and walkway, 6,646 km in all, filtered to what a person can actually walk on. Expressways, ramps, rail corridors, rivers, hydro corridors and the shoreline are in the same City file and are excluded; ravine paths, park paths and the Waterfront Trail are kept, which is why a walk through a park counts. Streets the City lists as planned but not yet classified are left out, so the route can never take a shortcut down a street that may not exist.

The join is exact rather than approximate, which is unusual and worth stating. The centreline records the intersection id at each end of every segment, and those are the same City ids this site keys its pages on — so each of our 5,822 intersections is a node in that graph, matched by id. Nothing is snapped, so nothing is snapped to the wrong corner. Destinations do have to be attached to the network, and each is attached at up to four nearby doors with the shortest way in winning, because a park with two entrances has two ways in and a shop on a corner has more than one frontage.

How long that takes. Walking times beside the distances assume 5 km/h (1.4 m/s), the usual planning figure and the speed Google, Walk Score and transit apps assume, so the times read the way you expect. It is not the only defensible number: Toronto Transportation Services uses a slower 1.0 m/s in its own pedestrian network data, chosen to include older and slower walkers. If that is closer to your pace, add about 40%. Times are shown only for walks over 250 m, because below that the distance has already said it.

What we checked

Across more than 200,000 measured pairs, the typical walk came out at 1.25 times the straight line it replaced. Published figures for walking circuity in North American cities run from about 1.15 in a tight grid to 1.40 in sprawl, and the textbook factor for Canada is 1.30 ± 0.10, so ours sits where a city of Toronto's shape should. The neighbourhoods with the longest detours are Parkwoods-O'Connor Hills, Guildwood, Flemingdon Park, Don Valley Village and Elms-Old Rexdale — the parts of the city cut by ravines, rail corridors and the 401, which is the answer the geography predicts. The check script ships with the site.

What it still cannot see

Every one of these makes a walk look longer than it is, never shorter. Where this site is wrong about distance, it is wrong in the direction of understating how walkable a corner is.

"Within a walk" — our own score

Every intersection page carries a score out of 100 under Within a walk (until 16 September 2026 it was headed "Errands on foot", a name that promised more than City records can see: shops, banks, gyms and clinics are in no City dataset and score nothing anywhere), and the most walkable intersections page ranks the city by it. It is ours, computed here from the layers above — not a licensed walkability rating bought from anyone, and not comparable with one. It answers a single question: how much of an ordinary week is within a walk of this corner?

Six parts add up to 100. Each is a short ladder rather than a curve, so you can check the number against the lists on the page itself:

Highway ramps and collector-lane nodes are not scored or ranked. Until 16 September 2026 each score also carried a verdict phrase — "most errands need a car", "everything on foot" — in five bands: 85 and over, everything on foot; 73, most errands on foot; 52, some errands on foot; 38, a few errands on foot; below that, most errands need a car. The phrase is no longer shown: it was a judgement the records cannot support, since a corner with a plaza across the road in Vaughan, or a bank and a hardware store the City does not list, scored "most errands need a car". The number stays, with the city median beside it.

The score's thresholds are fitted to the real spread of scores, and re-fitted whenever the measurement underneath them changes. They moved once already: switching from straight-line to real walking distance took about nine points off every score.

What the score is measured against

There is no true walkability number to be right or wrong about, so the score is tested the only honest way available: against behaviour. The 2021 Census records how people in each Toronto neighbourhood get to work. Taking each neighbourhood's mean errands score and comparing it with the share of residents who walk to work gives a rank correlation of 0.73 across all 158 neighbourhoods — higher than population density alone manages (0.55) on the same test. The script that runs this check ships with the site, so the figure can be reproduced rather than taken on trust.

That test is also how the weights above were set. An earlier version counted parks, schools, libraries and child care anywhere within 1.5 km, and inside 1.5 km of a Toronto intersection there is almost always a park and a school: those parts were at full marks for about 70% of the city and were measuring nothing. Tightening the radii to 500 m and moving weight toward the parts that tracked behaviour raised the correlation and, more importantly, gave the score a usable spread.

One result is worth stating plainly rather than hiding. "Crossing on foot" correlates negatively with walking to work (−0.23 on its own). That is a confound, not a finding: traffic signals, accessible signals and leading pedestrian intervals get installed on arterial roads, and arterial roads are where people drive. It is kept in the score anyway, because whether you can actually cross the road is the one thing this site knows that a general walkability rating does not.

What it cannot see

Four limits, none of them papered over:

It also measures what you can reach, not how pleasant or how safe the walk is. Collisions involving pedestrians are published on the same page and deliberately kept out of the score: a busy corner has both more shops and more collisions, and folding them together would mostly measure traffic volume.

What this site does not claim

Licences

Contains information licensed under the Open Government Licence – Toronto. Collision data originates with Toronto Police Service and is published by the City under the same licence. Corrections and questions: see the data page.