About 1,000 crash records (including 9 fatalities) in the city database lack geocoordinates, and I had early on for some reason omitted those records from my site queries default — which left them out not only from the maps but also the statistical aggregates.
I’ve now removed that filter, so the stat aggregates will slightly change:
| Year | Crashes w/o coords | Fatalities w/o coords | Total Crashes |
|---|---|---|---|
| Total | 971 | 9 | 141,714 |
| 2026 | 81 | 1 | 9,184 |
| 2025 | 136 | 1 | 17,897 |
| 2024 | 141 | 1 | 18,441 |
| 2023 | 129 | 1 | 16,766 |
| 2022 | 100 | 1 | 16,033 |
| 2021 | 121 | 1 | 16,331 |
| 2020 | 79 | 1 | 14,167 |
| 2019 | 96 | 2 | 16,314 |
| 2018 | 88 | 0 | 16,581 |
An example: the data record for this July 14, 2022 fatal 4-car crash that killed a 29-year-old passenger (related Chicago Sun-Times story), which took place at 4331 N. Mannheim Rd, has empty latitude and longitude fields. This crash, like most of the non-geocoded records, appear to take place near freeways and/or the airports. I’ll have to figure out a way to manually add coordinates for these situations.