Which database each finding comes from, why 250 metres, and what this evidence cannot do.
Where each number comes from
| Finding | Dataset | Source and coverage |
|---|---|---|
| Crashes, injuries, departure rebound, camera-free year | Traffic Collisions Open Data | Toronto Police Service ArcGIS FeatureServer. 790,725 records, Jan 2014 to Jun 2026; 84% carry usable coordinates. |
| The injury number specifically | INJURY_COLLISIONS flag within the collisions file | Any-severity personal injury, not the KSI file. Requires police attendance, so it is the outcome least exposed to reporting drift. |
| Camera sites, enforcement windows, camera tickets | Automated Speed Enforcement (ASE) Charges | Toronto Open Data, CKAN resource a388bc08. 520 sites, 627 enforcement periods, Jul 2020 to Nov 2025. |
| Deaths and serious injuries | TOTAL KSI | Toronto Police Service ArcGIS FeatureServer. 18,957 records, 2006 to 2023. Context only: the 4 to 15 figure is imputed from the injury effect, not counted here. |
| Police substitution and cost | Tickets Issued | Toronto Police Service. 769,678 speeding tickets, 2014 to 2024, by neighbourhood (158 neighbourhoods plus a residual code). |
| The Waterloo comparison | Collision occurrence data | Waterloo Regional Police Service. 92,985 records, 2019 to 2024, with UTM coordinates and severity classifications. |
| Cameras versus radar signs | Watch Your Speed sign deployments | City of Toronto. 4,565 locations. |
| Equity and placement | Census neighbourhood profiles and the City's Wellbeing Index | Statistics Canada and City of Toronto. 228 of 520 sites matched. |
| Speeds at camera sites | SickKids / Toronto Metropolitan University (2025) | Independent team, complementary study. 250 school zones. |
| London KSI evidence | The Lab's London analysis | 304 cameras, 652,697 records. |
Why 250 metres
How far from a camera does its influence extend? The literature uses a range, and our 250-metre choice sits in the middle of it and matches our own New York analysis, which allows direct comparison between the two cities.
| Study or report | Buffer | Context |
|---|---|---|
| NYC DOT (official reports) | ~400 m | Legal school speed zone boundary |
| Chicago DOT (official reports) | ~200 m | Illinois statute requirement |
| Tilahun (2023), Chicago | 250 m | Empirical Bayes with propensity matching |
| Guerra et al. (2024), Philadelphia | 200 m | Bayesian negative binomial |
| Mountain et al. (2004), UK | 250 m, 500 m, 1 km | Found strongest effects within 250 m |
| Our NYC study (2024) | 250 m | Cross-validated at 150–500 m |
The result does not depend on that choice. We repeated the analysis at six distances and out to a kilometre, and the effect is present and significant at every one, attenuating with distance as a spatial deterrence model would predict.
Why the police comparison runs at neighbourhood level
The Toronto Police "Tickets Issued" file records 769,678 speeding tickets from 2014 through 2024 by neighbourhood, using the City's 158-neighbourhood classification plus a residual code, and it carries no coordinates and no intersection, while the collision and camera files are geocoded to the metre.
So we can ask whether camera effectiveness differs between neighbourhoods with heavy and light police enforcement, which is the question we answer, and we cannot ask whether an officer and a camera worked the same corner. A neighbourhood is a coarse unit for this, since a camera appears to influence roughly 250 metres and a Toronto neighbourhood is many times that, so genuinely local substitution could be present and invisible to us. No evidence of substitution is a statement about what these data can detect.
The Waterloo 2024 vintage
Waterloo Regional Police changed its publication format from CSV to XLSX in 2024, and the data show the signature of a coding-threshold change rather than a change on the roads.
| Year | Waterloo collisions | Index (2019=100) | Injury rate |
|---|---|---|---|
| 2019 | 16,466 | 100.0 | 11.7% |
| 2020 | 11,631 | 70.6 | 15.3% |
| 2021 | 12,901 | 78.3 | 16.6% |
| 2022 | 15,224 | 92.5 | 17.2% |
| 2023 | 15,464 | 93.9 | 16.6% |
| 2024 | 21,299 | 129.4 | 7.1% |
Records jumped 38 percent while the injury rate halved, and the hit-and-run share rose from 13.4 to 17.4 percent. More records at lower average severity is the signature of a threshold change in what gets coded as a collision. Our primary specification therefore excludes 2024. The contrast that circulates most, Waterloo at 129 against Toronto at 85, takes that vintage, and we do not lean on it.
Limits we cannot argue away
We think readers are best served by the limits stated as plainly as the findings.
A single effect size. The estimate shifts with the research design, from roughly zero to −10 percent. Our judgment of −4 to −7 percent is a judgment, and we have tried to show the work rather than declare a number.
How much of the post-removal rise was camera-specific. The direction is clear; the magnitude is entangled with the post-pandemic recovery and cannot be separated from it with these data.
How much belongs to the camera alone. At 193 sites, or 37 percent, a radar sign's deployment overlapped the camera's, so what we call the camera effect there is strictly a bundle. An exploratory split on the busier half of the network puts cameras without a sign at −9.2 percent against bundled sites at −7.9, statistically indistinguishable. No cross-site split can separate the constants: school-zone signage, markings and zone speed limits persist at nearly every site.
Direct severe-injury effects. KSI events near camera sites are too rare to test, so those figures are imputed from the injury effect.
Risk per kilometre driven. Traffic-volume data for the period do not exist in public form. Our estimates are crash counts; a proxy adjustment using radar-sign traffic counts left the estimate essentially unchanged, at −11.1 against −10.9 percent.
That reporting practices held still. About 16 percent of collision records lack usable coordinates and differ modestly from those that have them, and Waterloo's 2024 data show signs of a coding change. Both are named and bounded; neither can be fully corrected.
Which sites will respond next time. Site-level outcomes are dominated by noise at the crash counts involved. Our best cross-validated model explains about 11 percent of the site-to-site variation.