Where bike accidents happen most often in Toronto

The Globe did a great thing today—they got, and mapped, twenty-five years of cycling collision data. And then they released the data, which makes it much easier for people like me to tell you, say, the total number of reported collisions on any street you can name. Which is what I’m going to do here.

Here are some of the Toronto streets that stuck out from a glance at the map as especially accident-heavy, as well as the number of collisions those streets have per kilometre, with the obvious caveat that these counts don’t necessarily reflect how safe or dangerous a street is (College–Carlton is the street where the greatest number of cycling accidents occur per kilometre, but a lot of cyclists use it), and also that my per-kilometre counts are rough because I used this to determine how long any given street is within Toronto.

EAST–WEST

COLLEGE/CARLTON: 1319 accidents since 1986 (6.5 kilometres of road within Toronto; 202.9 reported accidents per kilometre of road)
QUEEN: 2169 accidents (14 km long; 154 accidents/km)
BLOOR/DANFORTH 3244 accidents (28 km long; 115 accidents/km)
KING: 836 accidents (8 km long; 104 accidents/km)
DUNDAS: 1795 accidents (23.5 km long; 76.4 accidents/km)
DUPONT: 378 accidents (5 km long; 75.6 accidents/km)
DAVENPORT: 413 accidents (6.5 km long; 63.5 accidents/km)
EGLINTON: 814 accidents (33 km long; 24.7 accidents/km)
FINCH: 728 accidents (37 km long; 19.7 accidents/km)
SHEPPARD: 636 accidents (34 km long; 18.7 accidents/km)

NORTH–SOUTH

BAY: 754 accidents (4 km long; 188.5 accidents/km)
YONGE: 1599 accidents (18 km long; 88.8 accidents/km)
SPADINA: 574 accidents (7.5 km long; 76.5 accidents/km)
DUFFERIN: 640 accidents (11.5 km long; 55.6 accidents/km)
BATHURST: 987 accidents (18 km long; 54.8 accidents/km)
WESTON/KEELE/PARKSIDE: 759 accidents (18 km long; 42.1 accidents/km)
  1. kindbikes reblogged this from davidtopping
  2. saila reblogged this from reporterly and added:
    And the Data Bureau springs to life
  3. reporterly reblogged this from davidtopping
  4. davidtopping posted this
Tweet