<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.10.0">Jekyll</generator><link href="https://blog.crashstop.org/feed.xml" rel="self" type="application/atom+xml" /><link href="https://blog.crashstop.org/" rel="alternate" type="text/html" /><updated>2026-10-21T20:34:30-05:00</updated><id>https://blog.crashstop.org/feed.xml</id><title type="html">Crash Stop Chicago Blog</title><subtitle>Updates and blog stuff for crashstop.org/chicago</subtitle><entry><title type="html">Streets are now segmented into blocks</title><link href="https://blog.crashstop.org/2026/10/21/street-segmented-into-blocks/" rel="alternate" type="text/html" title="Streets are now segmented into blocks" /><published>2026-10-21T00:00:00-05:00</published><updated>2026-10-21T00:00:00-05:00</updated><id>https://blog.crashstop.org/2026/10/21/street-segmented-into-blocks</id><content type="html" xml:base="https://blog.crashstop.org/2026/10/21/street-segmented-into-blocks/"><![CDATA[<p><img src="assets/images/street-segment-archer-ave.png" alt="image street-segment-archer-ave.png" /></p>

<p>Crash Stop Chicago now organizes data at the street segment (i.e. block) level, e.g. if you live on 125 N Dearborn Street you can now view traffic crash data for <a href="https://crashstop.org/chicago/street-segments/s-dearborn-st--100-199">100-199 S Dearborn St</a>, instead of needing to sort through the data for the entire stretch of <a href="https://crashstop.org/chicago/streets/s-dearborn-st">South Dearborn St</a>.</p>

<p>This took a lot of backend re-wrangling — mostly redoing how I transform the <a href="https://data.cityofchicago.org/Transportation/Street-Center-Lines/6imu-meau">city’s Street Center Lines database</a>, but I think it’s worth it because it opens the door to more pointed and relevant analyses, such as examining the impact of traffic safety features within their immediate blocks.</p>

<p>It’s also nice that you can now type in a partial address into the location search and find data within a block of you without me having to send your input into Google’s geocoder:</p>

<p><img src="assets/images/street-segment-autocomplete.png" alt="image street-segment-autocomplete.png" /></p>

<p>I’ve been making a lot of incremental interface changes over the past few weeks too, and plan to continue to do so until the data finally looks nice and understandable. My latest tweaks have been to the top infobox for location pages, de-emphasizing the historical total in favor of showing recent crash activity and comparing it to recent historical averages:</p>

<p><img src="assets/images/location-topline-kpi-redesign.png" alt="image location-topline-kpi-redesign.png" /></p>]]></content><author><name></name></author><category term="main" /><summary type="html"><![CDATA[]]></summary></entry><entry><title type="html">A page dedicated to Chicago traffic fatalities</title><link href="https://blog.crashstop.org/2026/08/26/fatalities-page/" rel="alternate" type="text/html" title="A page dedicated to Chicago traffic fatalities" /><published>2026-08-26T00:00:00-05:00</published><updated>2026-08-26T00:00:00-05:00</updated><id>https://blog.crashstop.org/2026/08/26/fatalities-page</id><content type="html" xml:base="https://blog.crashstop.org/2026/08/26/fatalities-page/"><![CDATA[<p><img src="assets/images/fatalities-map.png" alt="screenshot of the fatalities map and list" /></p>

<p>I’ve created a Crash Stop Chicago page dedicated to <a href="https://crashstop.org/chicago/fatalities">Fatalities (/fatalities)</a>. I’m still trying to manually curate stories for each and every one of them, so I thought it’d be good to have a page where visitors could easily browse the victims and their stories.</p>

<p>I don’t love the sterile data dashboard at top, but that’s something that will evolve as I build out the page and compile its data and stories.</p>

<p><img src="assets/images/fatalities-dashboard.png" alt="screenshot of the top of the /fatalities page showing a statistical snapshot of the Chicago traffic deaths" /></p>]]></content><author><name></name></author><category term="main" /><summary type="html"><![CDATA[]]></summary></entry><entry><title type="html">Ungeocoded crash records no longer omitted</title><link href="https://blog.crashstop.org/2026/07/08/ungeocoded-records-now-included/" rel="alternate" type="text/html" title="Ungeocoded crash records no longer omitted" /><published>2026-07-08T00:00:00-05:00</published><updated>2026-07-08T00:00:00-05:00</updated><id>https://blog.crashstop.org/2026/07/08/ungeocoded-records-now-included</id><content type="html" xml:base="https://blog.crashstop.org/2026/07/08/ungeocoded-records-now-included/"><![CDATA[<p>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.</p>

<p>I’ve now removed that filter, so the stat aggregates will slightly change:</p>

<table>
  <thead>
    <tr>
      <th>Year</th>
      <th style="text-align: right">Crashes w/o coords</th>
      <th style="text-align: right">Fatalities w/o coords</th>
      <th style="text-align: right">Total Crashes</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Total</strong></td>
      <td style="text-align: right"><strong>971</strong></td>
      <td style="text-align: right"><strong>9</strong></td>
      <td style="text-align: right"><strong>141,714</strong></td>
    </tr>
    <tr>
      <td>2026</td>
      <td style="text-align: right">81</td>
      <td style="text-align: right">1</td>
      <td style="text-align: right">9,184</td>
    </tr>
    <tr>
      <td>2025</td>
      <td style="text-align: right">136</td>
      <td style="text-align: right">1</td>
      <td style="text-align: right">17,897</td>
    </tr>
    <tr>
      <td>2024</td>
      <td style="text-align: right">141</td>
      <td style="text-align: right">1</td>
      <td style="text-align: right">18,441</td>
    </tr>
    <tr>
      <td>2023</td>
      <td style="text-align: right">129</td>
      <td style="text-align: right">1</td>
      <td style="text-align: right">16,766</td>
    </tr>
    <tr>
      <td>2022</td>
      <td style="text-align: right">100</td>
      <td style="text-align: right">1</td>
      <td style="text-align: right">16,033</td>
    </tr>
    <tr>
      <td>2021</td>
      <td style="text-align: right">121</td>
      <td style="text-align: right">1</td>
      <td style="text-align: right">16,331</td>
    </tr>
    <tr>
      <td>2020</td>
      <td style="text-align: right">79</td>
      <td style="text-align: right">1</td>
      <td style="text-align: right">14,167</td>
    </tr>
    <tr>
      <td>2019</td>
      <td style="text-align: right">96</td>
      <td style="text-align: right">2</td>
      <td style="text-align: right">16,314</td>
    </tr>
    <tr>
      <td>2018</td>
      <td style="text-align: right">88</td>
      <td style="text-align: right">0</td>
      <td style="text-align: right">16,581</td>
    </tr>
  </tbody>
</table>

<p>An example: the data record for this <a href="https://crashstop.org/chicago/crashes/31881cfc3d0a9b4a172ab170210891adc9b7263c639beaf16b05fde86e207092de9b33006c7e6608b324fad1994fe574ef3b40d666faf3d3e8d6629bf8d03993">July 14, 2022 fatal 4-car crash</a> that killed a 29-year-old passenger (<a href="https://chicago.suntimes.com/news/2022/7/15/23219846/man-dead-3-year-old-boy-among-3-others-hurt-in-traffic-crash-near-ohare-airport">related Chicago Sun-Times story</a>), which took place at <a href="https://www.google.com/maps/place/4331+N+Mannheim+Rd,+Schiller+Park,+IL+60176/">4331 N. Mannheim Rd</a>, 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.</p>

<!--
-- Query for reference sake

WITH
Src AS (
  SELECT
    SUBSTR(crash_date, 1, 4) AS Year
    , fatal_tally
    , latitude is null AS missing_coords
FROM crashes_serving
)

SELECT
Year
, SUM(missing_coords) AS [Crashes w/o coords]
, SUM(IIF(missing_coords, fatal_tally, 0)) AS [Fatalities w/o coords]
, COUNT(1) AS `Total Crashes`

FROM (
    SELECT * FROM Src
    UNION ALL
    SELECT 'Total' AS Year, fatal_tally, missing_coords FROM Src
)

GROUP BY Year
ORDER BY Year desc
 -->]]></content><author><name></name></author><category term="main" /><summary type="html"><![CDATA[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.]]></summary></entry><entry><title type="html">Crash Count Chicago is now Crash Stop Chicago (crashstop.org)</title><link href="https://blog.crashstop.org/2026/07/07/crashcount-org-is-now-crashstop-org/" rel="alternate" type="text/html" title="Crash Count Chicago is now Crash Stop Chicago (crashstop.org)" /><published>2026-07-07T00:00:00-05:00</published><updated>2026-07-07T00:00:00-05:00</updated><id>https://blog.crashstop.org/2026/07/07/crashcount-org-is-now-crashstop-org</id><content type="html" xml:base="https://blog.crashstop.org/2026/07/07/crashcount-org-is-now-crashstop-org/"><![CDATA[<p>A few days after I soft-launched “Crash Count Chicago”, I stumbled on the excellent <a href="https://crashcount.nyc/">CrashCount.nyc</a> site, which launched just a couple months earlier and has much of the same mission and data focus as Crash Count Chicago (and is in many ways, a much more interesting site!)</p>

<p>Well, they got the name/branding first, so I brainstormed some alternative names and <strong>Crash Stop Chicago</strong> had the best sound to it and thematic overtone, so <a href="https://crashstop.org/chicago">crashstop.org</a> it is!</p>]]></content><author><name></name></author><category term="main" /><summary type="html"><![CDATA[A few days after I soft-launched “Crash Count Chicago”, I stumbled on the excellent CrashCount.nyc site, which launched just a couple months earlier and has much of the same mission and data focus as Crash Count Chicago (and is in many ways, a much more interesting site!)]]></summary></entry><entry><title type="html">Crash Count Chicago soft launch</title><link href="https://blog.crashstop.org/2026/05/27/crashcount-org-soft-launches/" rel="alternate" type="text/html" title="Crash Count Chicago soft launch" /><published>2026-05-27T00:00:00-05:00</published><updated>2026-05-27T00:00:00-05:00</updated><id>https://blog.crashstop.org/2026/05/27/crashcount-org-soft-launches</id><content type="html" xml:base="https://blog.crashstop.org/2026/05/27/crashcount-org-soft-launches/"><![CDATA[<p>A lot of unchecked items on the todo list, but I think <strong>Crash Count Chicago</strong> (update: <em><a href="/2026/07/07/crashcount-org-is-now-crashstop-org/">Crash Stop Chicago</a></em>) is ready for the public.</p>

<p>My <a href="https://bsky.app/profile/dancow.bsky.social/post/3mmuln5oib22p">bluesky post</a>:</p>

<p><a href="https://bsky.app/profile/dancow.bsky.social/post/3mmuln5oib22p">
<img src="/assets/images/bluesky-soft-launch-post.png" alt="My bluesky post announcing crashcount.org/chicago" />
</a></p>]]></content><author><name></name></author><category term="main" /><summary type="html"><![CDATA[A lot of unchecked items on the todo list, but I think Crash Count Chicago (update: Crash Stop Chicago) is ready for the public.]]></summary></entry><entry><title type="html">January 2026 CDOT Monthly Summary of Fatal Traffic Crashes</title><link href="https://blog.crashstop.org/2026/02/17/cdot-january-2026-monthly-traffic-fatality-report/" rel="alternate" type="text/html" title="January 2026 CDOT Monthly Summary of Fatal Traffic Crashes" /><published>2026-02-17T00:00:00-06:00</published><updated>2026-02-17T00:00:00-06:00</updated><id>https://blog.crashstop.org/2026/02/17/cdot-january-2026-monthly-traffic-fatality-report</id><content type="html" xml:base="https://blog.crashstop.org/2026/02/17/cdot-january-2026-monthly-traffic-fatality-report/"><![CDATA[<p>This is a mirror of the CDOT monthly report of traffic fatalities for January 2026, which was last updated on February 16, 2026.</p>

<ul>
  <li><a href="https://www.chicago.gov/content/dam/city/sites/complete-streets/pdfs/MonthlySummary/2026/Fatal%20Traffic%20Crash%20Monthly%20Summary_January%202026.pdf">Original official link at chicago.gov</a></li>
  <li><a href="/assets/reports/cdot-fatal-traffic-crash-monthly-summary-2026-01.pdf">Mirror</a></li>
</ul>

<div id="pdf-cdot-fatal-traffic-crash-monthly-summary-2026-01"></div>
<script src="/assets/js/pdfobject.min.js"></script>

<script>
  PDFObject.embed("/assets/reports/cdot-fatal-traffic-crash-monthly-summary-2026-01.pdf", "#pdf-cdot-fatal-traffic-crash-monthly-summary-2026-01");
</script>]]></content><author><name></name></author><category term="crash-stories" /><category term="reports" /><category term="monthly-summary" /><category term="cdot" /><summary type="html"><![CDATA[This is a mirror of the CDOT monthly report of traffic fatalities for January 2026, which was last updated on February 16, 2026.]]></summary></entry></feed>