Category: Safety

photo of Hadiya Pendleton Park, seen from the 43rd Green Line station platform.

Traffic calming around Chicago schools and parks

July 26, 2023 / / 0 Comments

Reducing the number and speed of automobiles near schools and parks is a proven way to reduce the number of traffic crashes involving children, part of a practice known as “traffic calming”. In Chicago a key way to do that has been to “cul-de-sac” (which I’m using as a verb) a street to prevent through traffic (reducing the number) and preventing speeding (reducing the speed).

My study of this was inspired by the above tweet, where the person is accurate when they say, “it works with any street”. Indeed: Full access to the school or park and to every property on the block is maintained, but drivers are not able to go through while pedestrians and bicyclists can (another practice called “modal filtering“).

My favorite example in Chicago is Hadiya Pendleton Park, at 4345 S Calumet Ave. This project created two mid-block cul-de-sacs and a park in the middle of a block, using vacant city-owned land on both sides. Creating new open space is a common corresponding outcome of the cul-de-sac application, which is what occurred at Funston Elementary School (see the before and after aerial photos below).

two black and white aerial photos taken of Funston Elementary School, one in 1998 showing a 4-way intersection of McLean Ave and Central Park Ave and one in 2003 showing a cul-de-sac on McLean Ave west of the school and landscaped area between the cul-de-sac and the three-way intersection of McLean and Central Park.

Through Twitter I solicited additional examples of where the city has created traffic calming near schools and parks using cul-de-sacs. Examples were submitted by Roland, Emily (who mentioned Funston), Matt, Steven, and another tweeter.

Using OpenStreetMap, Overpass Query Language, and Overpass Turbo, we can find all of the schools and parks that are within a specified distance of a cul-de-sac. It turns out there are 153 schools and parks in Chicago that are within 150 feet of a cul-de-sac. (This considers only schools, parks, and cul-de-sacs, tagged as “turning circles”, currently mapped in OSM, and I have not verified each of the 153 instances.)

Map showing parks, schools, and adjacent cul-de-sacs, the results of the Overpass Turbo query.
Map showing parks, schools, and adjacent cul-de-sacs, the results of the Overpass Turbo query. An inset map shows a zoomed in portion of the map to illustrate the different types of features captured in the Overpass Turbo query (specifically it shows Graham Elementary School and McInerney Park).

The query below will find all of the cul-de-sacs (mapped as “turning circles” in OSM parlance) that are in Chicago, all of the schools and parks in Chicago, and then all of the two categories of features that are within 45 meters of each other. (Run the query and show the map, which will always grab the latest data.)

/*
example from OSM wiki: https://wiki.openstreetmap.org/wiki/Overpass_API/Overpass_API_by_Example
*/
[out:json][timeout:25];
// fetch area “Chicago” to search in
{{geocodeArea:Chicago}}->.searchArea;

// get cul-de-sacs
(
  node["highway"="turning_circle"](area.searchArea);
)->.turning_circles;

// get parks and schools
(
  way["amenity"="school"](area.searchArea);
  way["leisure"="park"](area.searchArea);
)->.schoolsParks;

// find parks and schools near cul-de-sacs
(
  way.schoolsParks(around.turning_circles:45);
)->.matchingSchoolsParks;

// find cul-de-sacs near parks and schools
(
  node.turning_circles(around.schoolsParks:45);
)->.matchingTurningCircles;

// output results to the map
(.matchingSchoolsParks; .matchingTurningCircles;);
out geom;

Read the three other blog posts I’ve written about using Overpass Turbo to quickly sift through and extract desired mapping data from OpenStreetMap.

Chicago Crash Browser updates with stats, filters, and news article links

August 9, 2022 / / 0 Comments

Today I’m adding a bunch of new features to the Chicago Crash Browser, which lives on Chicago Cityscape.

But first…special access is no longer required. Anyone can create a free Cityscape account and access the map. However, only those with special access or a Cityscape Real Estate Pro account will be able to download the data.

Five new features include:

  • Statistics that update weekly to summarize what happened in the past week: the number of crashes, the number of people killed in crashes, and the number of people with the two worst tiers of injuries. The statistics are viewable to everyone, including those without access to the crash browser.
screenshot of the new weekly statistics
The statistics will update every Sunday. The numbers may change throughout the week as Chicago police officers upload crash reports.
  • For data users, the crash record ID is viewable. The crash record ID links details about the same crash across the Chicago data portal’s three tables: Crashes, Vehicles, and People. My Chicago Crash Browser is currently only using the Crashes table. Click on the “More details” arrow in the first table column.
screenshot of the data table showing the crash record ID revealed.
The crash record ID is hidden by default but can be exposed. Use this ID to locate details in the data portal’s Vehicles and People tables.
  • Filter crashes by location. There are currently two location filters: (1) on a “Pedestrian Street” (a zoning designation to, over time, reduce the prevalence of car-oriented land uses and improve building design to make them more appealing to walk next to); (2) within one block of a CTA or Metra station, important places where people commonly walk to. Select a filter’s radio button and then click “Apply filters”.
  • Filter crashes by availability of a news article or a note. I intend to attach news articles to every crash where a pedestrian or bicyclist was killed (the majority of these will be to Streetsblog Chicago articles, where I am still “editor at large”. Notes will include explanations about data changes [1] (the “map editor” mentioned in some of the notes is me) and victims’ names.
screenshot of the two types of filters

After choosing a filter’s radio button click “Apply filters” and the map and data table will update.
  • Filter by hit and run status. If the officer filling out the crash report marked it as a hit and run crash, you can filter by choosing “Yes” in the options list. “No” is another option, as is “not recorded”, which means the officer didn’t select yes or no.
  • Search by address. Use the search bar inside the map view to center the map and show crashes that occurred within one block (660 feet) of that point. The default is one block and users can increase that amount using the dropdown menu in the filter.
screenshot of the map after the search by address function has been used
Use the search bar within the map view to show crashes near a specific address in Chicago.

Footnotes

[1] The most common data change as of this writing is when a crash’s “most severe injury” is upgraded from non-fatal to fatal, but the crash report in the city’s data portal does not receive that update. This data pipeline/publishing issue is described in the browser’s “Crash data notes” section.

The “map editor” (me) will change a crash’s “most severe injury” to fatal to ensure it appears when someone filters for fatal crashes. This change to the data will be noted.

Chicago Crash Browser is back

May 7, 2022 / / 1 Comment

ChicagoCrashes dot org was, for many years, the only source for people to get information about traffic crashes in Chicago. I started it in 2011.

Chicago Crash Browser v0.2
A screenshot of Chicago Crash Browser v0.2 showing what the website looked like on December 30, 2011.

It was updated annually with data from two years ago, because of how the Illinois Department of Transportation processed the reports from all over the state. I shut it down because it had outdated code, I was maintaining it in my free time, and I didn’t want to update the code or spend all the time every year integrating the new data.

In 2015, the Chicago Police Department started testing an electronic crash reporting system in some districts that meant police officers could write reports and they would immediately show up in a public database (in the city’s data portal). The CPD expanded this to all districts in September 2017. (A big caveat to using the new dataset is that it has citywide data for only four and a half years.)

Since then, whenever someone asked me for crash data (mostly from John to illustrate Streetsblog Chicago articles), I would head to the data portal and grab data from just the block or intersection where someone had recently been injured or killed. I would load the traffic crash data into QGIS and visualize it. I found this also to be painstaking.

Now, with renewed attention on the common and unfixed causes of KSIs (“industry” term for killed or seriously injured) that we’re seeing repeatedly across Chicago – read about the contributing cause of Gerardo Marciales’s death – I decided to relaunch a version of Chicago Crash Browser.

The new version doesn’t have a name, because it’s part of the “Transportation Snapshot” in Chicago Cityscape, the real estate information platform I operate. It’s also behind a paywall, because that’s how Chicago Cityscape is built.

I wanted to make things a lot easier for myself this round and it comes with a lot of benefits:

  • Explore all crash reports in a given area, whether that’s one you draw yourself or predefined in the Cityscape database.
  • Quickly filter by crash type (bicyclist, pedestrian, etc.) and injury severity.
  • Download the data for further analysis.
A screenshot of a map and data table visualizing and describing traffic crash reports in Columbus Park.
What the crash data looks like within Chicago Cityscape.

How to access the Chicago Crash Browser

The crash data requires a Cityscape membership. I created a new tier of membership that cannot be signed up – I must grant it to you. It will give you access only to Transportation Snapshots.

  • Create a free account on Chicago Cityscape. The site uses only social networks for creating accounts.
  • Mention or DM me on Twitter, @stevevance, saying you’d like access to the crash data. Tell me what your email you used to create an account on Chicago Cityscape.
  • I’ll modify your membership to give you access to the “transportation tier” and tell you to sign out and sign back in to activate it.

Once you’re in, this video shows you how to draw a “Personal Place” and explore the traffic crash data there. Text instructions are below.

  1. From the Chicago Cityscape homepage, click on “Maps” in the menu bar and then click “Draw your own map”.
  2. On the “Personal Place” page that appears with a large map, decide which shape you’d like to draw: a circle with a radius that you specify (good for intersections), a square or rectangle (good for street blocks), or an arbitrary polygon (good for winding streets in parks). Click the shape and draw it according to the onscreen instructions. For intersections I recommend making the circle 150 feet for small intersections and 200 feet for long intersections; this is because intersections have an effect on driving beyond the box.
  3. Once you’ve completed drawing the shape, a popup window appears with the button to “view & save this Personal Place”. Click that button and a new browser tab will open with something called a “Place Snapshot”.
  4. In the Place Snapshot enter a name for your Personal Place and click the “Save” button.
  5. Scroll down and, under the “Additional Snapshots” heading, click the link for “Transportation & Jobs Snapshot”; a new browser tab will open.
  6. In Transportation Snapshot, scroll down and look for “Traffic crashes”. You’ve made it to the new Chicago Crash Browser.

To slow down drivers, we must speak up to our own drivers

November 20, 2016 / / 0 Comments

Backseat view of drive to Oak Park

We have a lot of power from the backseat to influence our drivers to drive better. We only have to speak up.  Photo: John Bracken

I’ve had a lot of experience with a major “transportation network company” this weekend. TNCs are also known as e-hail car services, and, inaccurately, “ride share”, because a car arrives at your location after pressing a button on an app.

I rode in one four times from Friday to Sunday because my visiting friend had a broken bone and couldn’t ride a bike – that was our original plan. Instead we had a multi-modal weekend and relied on walking, public transportation, another friend’s personal vehicle, and the TNC to go out.

These experiences reminded me that advocates for safe streets and better active transportation service and infrastructure – including myself – must directly battle entrenched norms about the “plight of the driver”.

In our final ride, on our way to the airport to drop off my friend, the TNC driver asked about the timing of our trip, if we were in a rush so the driver could know if they needed to drive a certain way.

I said that we were not, that we had budgeted plenty of time, and that Google Maps showed green lines on the local streets and highway between where we had dinner in Ukrainian Village and O’Hare airport.

As he was driving the car northbound on Western Avenue toward the Fullerton Avenue on-ramp to the Kennedy, my friend asked him about the app he was using that was speaking the turn-by-turn directions, and how it knew what the road conditions were.

The app uses the Waze service, which collects data from transportation departments, other drivers, and databases of upcoming road closures. The driver said he liked that it warned him of the locations of red light and speed cameras, too.

“I’ve gotten four speed camera tickets in the last year”, he said, “and they were all $100 each.”

I have written about Chicago’s speed cameras several times in Streetsblog Chicago, and I thought the cost was different so I asked, “Isn’t it lower for the first time?” Nope, he said.

When I looked it up at home I remembered why I was mistaken: The fine is $100 if you are traveling 11 miles per hour or more over the speed limit. The fine is $35 for traveling six to 10 miles per hour or more over the speed limit, but the cameras aren’t enforcing this range currently.

That was the end of our conversation, but I should have kept on.

The conversation we should have had would have questioned his driving behavior. I should have asked, “Why are you driving so far so often?” and “Why aren’t you slowing down? Don’t you know that speeding is dangerous to you, your passengers, and other people outside the car?”

I was spineless and didn’t challenge how he was contributing to unsafe streets in the city. My silence was tacit agreement that four $100 speeding tickets – for driving 41+ in a 30, or 31+ in a 20 in a school zone if a child was present – was a personal burden and not a necessary enforcement tool to try and reduce the number of injuries and deaths in car crashes in Chicago.

Later, on the Kennedy Expressway, he was traveling a bit over 70 miles per hour, or more than 25 miles per hour greater than the speed limit. Again I said nothing.

Another of the TNC drivers this weekend was likely high on marijuana. I shouldn’t have accepted any of these situations.

There are many kinds of shared space

May 29, 2016 / / 0 Comments

A guy standing in the middle of the intersection

I took this photo outside the café Memory Lane in Rotterdam because the man in the white shirt was standing in the “middle” of this intersection for a couple of minutes. Before he took this position, he was walking slowly across the intersection to the opposite corner as his car. He’s a livery driver, and he appeared to be waiting for his passenger.

This intersection is raised (the sidewalk is level with the road surface), and is uncontrolled (there are no traffic signals, stop signs, or yield signs). A bicyclist or motorist can pass through this intersection without having to stop unless someone is walking, or a bike or car is coming from their right.

This junction has no crosswalks, either. And no one honks. Especially not at the man who’s in the roadway.

Because he’s not in the roadway. He’s in a street, and streets are different. Streets are places for gathering, socializing, eating, connecting, traveling, and shopping. There was plenty of space for him to stand here, and for everyone else – including other motorists who were in their cars – to go about their business.