Tag: crash

The Chicago Fire Department has one of the least useful Twitter feeds, but sometimes it’s hilarious

20 minutes ago, when the Twitter outage probably corrected itself, the Chicago Fire Department’s Office of News Affair tweeted three photos, without comment. I’ve posted them in reverse order.

Tweet 3

The third photo (above) shows a BMW X5 SUV on top of a Jaguar sedan and Mercedes E320 sedan in a multi-level parking garage. The parking garage appears to be a split-level, and it seems the BMW SUV was moved forward from an upper level to the tops of these cars, which you can see in the second photo (below).

Tweet 2

Tweet 1

The photos appear to have been taken with a cellphone, using the flash. The license plates are obscured by their reflection of the flash. The car broke through the cables leading me to ask two questions: What is the level of tension on the cables? How fast did the car travel?

The @CFDMedia account is often cryptic. The Chicago Sun-Times provided more information an hour later:

A 74-year-old man driving a 2012 BMW X5 crashed through cable barriers separating two levels of a Loop parking garage Thursday — and his SUV came to a stop atop a 2005 Jaguar and a 2003 Mercedes-Benz parked on the level beneath him, police said.

Police cited the 74-year-old with driving too fast for conditions.

Updated 16:18 to add a report from the Chicago Sun-Times.

Policy insight for Monday, August 1, 2011

This isn’t refined. These are just my notes that I speak from. I may not have spoke about everything written here and I may not have written here everything I spoke about. This is for Moving Design

There was report of cyclist crashing on the Tuff Curb at the on-street bike parking facility in Wicker Park.

Installing the Tuff Curb

experimental projects need reviews. I don’t mean projects that are considered experiments, I mean projects that are new to the people who designed it, and new to the people who will be using it.

we need good data collection.

Did the Kinzie bike lane cause congestion? So what if it did?
We would need data points that were collected using well-known methods, and probably at different times of the day and week. And we’d have to be sure to count cyclists, too.
Then 3, 6, or 12 months later, we’d have to do it again.

What was the change?
Is that a change that meets our goals?

Back to the cyclist crashing on tuff curb, what is the city’s plan to monitor the use (or disuse) of the facility? How will the city collect data on something like this?

Census – not gonna happen in 2020
American Community Survey – 5-year estimates (with data gathered annually) will replace decennial Census.

“Here are a few Streetsblog posts about Census and NYC DOT’s bike counts, and the problems with each. The first post has some stuff about what could be done to improve on them:” (Ben Fried, Editor in Chief, Streetsblog NYC)

http://www.streetsblog.org/2010/04/27/how-many-new-yorkers-bike-each-day/
http://www.streetsblog.org/2010/10/01/did-nyc-bike-commuting-decrease-in-2009-thats-what-the-census-says/
http://www.streetsblog.org/2011/04/13/actually-if-you-build-it-they-will-bike/

Read more policy insights from Steven Vance. 

Improvements in store for the Damen-Elston-Fullerton intersection

Updated May 2, 2011, with additional comments and concerns.

The City of Chicago plans to make major changes to the intersection of Damen-Elston-Fullerton. They revealed a lot of these changes and invited the public to learn more and make comments on the current proposal at an open house event Wednesday, April 27, 2011, at the Wicker Park-Bucktown library.

What is now actually three, closely-spaced intersections with six legs (two of them skewed), will become three, distantly-spaced intersections at right angles.

Why is this being done?

  • The closely-spaced intersections “encourage poor decision making.”
  • Small radii makes it difficult for trucks to make turns.
  • The island and closely-spaced intersections makes for limited queue capacity which blocks the other legs.
  • There are a lot of crashes, over 400 in a 3-year period. That’s over 7 per week.

So what’s the solution?

The Chicago and Illinois Departments of Transportation, and project consultant Benesch came up with 4 alternatives.

  • Enhanced “no build” – no improvements, but modernize signals didn’t address safety or delay. [In infrastructure project planning, there’s always a “no build” alternative to which the other alternatives are compared.]
  • Fullerton tunnel, or underpass. A majority of Fullerton traffic would bypass the intersection, but the surface intersection would still have same conditions outlined under “why.” Additionally, there are many utilities under the intersection that would all need to be relocated. It would take 3 years to build. For the length of the tunnel, surface traffic on Fullerton could only make right-in, right-out turns.
  • Overpass. A majority of Fullerton traffic would bypass the intersection, but the surface intersection would still have same dismal conditions. This has the same turn restrictions as the underpass – this and its imposing aesthetics could impact economic development (the presentation didn’t say whether the project designers expected this to be positive or negative).
  • And there’s the “preferred alternative.” It has wider sidewalks, larger turn radii, and “safer bike accommodations.” Delays would improve from up to 7 minutes to under 30 seconds.

Other benefits of the preferred alternative include:

  • Access to properties is preserved.
  • Simpler intersections means fewer conflicting movements.
  • A “new bike lane” (I disagree with calling it new – the project is preserving the existing bike lane, bringing it into the new route of Elston Avenue, or whatever the new street will be called).
  • Supports future economic development by having simpler traffic.

What’s the timeline?

  • 2011 – Finalize phase 1 engineering. Seek approval from IDOT and the Federal Highway Administration (FHWA). Start the design process.
  • 2012 – While continuing work on the design, begin acquiring right of way.
  • 2013 – Finish design, and bid out project.
  • 2014 – Award project and begin construction.

The project is estimated to cost $32 million, with funds coming from the TIF Bank, grants from the FHWA, and the City’s own capital improvement funds.

Comment on the design until May 13 by emailing Bridget Stalla, the project manager who works for the City of Chicago. All emails to her about this project will go on the public record.

So what are my comments?

Lack of bike lanes

Currently there’s no striped bike lane for .26 miles on Damen Avenue between where it ends at the I-90/I-94 highway and railroad viaducts to where it ends on the hill to the bridge over the Chicago River.

The project does not add this bike lane, which I feel is much needed for the cyclists who deal with the congestion and tight spaces. I talked to Bridget and Colin Coad, a staffer at Benesch about this. Both admitted that a bike lane in this location was considered. It wasn’t in the current design because Damen Avenue must have two lanes northbound to keep the queue capacity and keep delays down. An animation showed the difference in delays between the existing and proposed intersection configuration. The delay reduction in the new configuration was very noticeable. This doesn’t preclude installing a bike lane.

An attendee asked Ryan Thady, who was explaining the animation, if Benesch had done analysis on a single northbound travel lane south of Fullerton Avenue on Damen Avenue. He answered, “No. If there’s one lane, there’s an increased delay.”

Colin said that a bike lane has always been under consideration and will be again under consideration. Bridget says she realizes there’s a need to reevaluate the bikes on Damen Avenue situation. “We need the two lanes to really make this thing work like it’s supposed to. We will look at extending the bike lane on Damen north of Fullerton [from the bridge approach to the intersection of Damen and Elston].”

I’m confused about “making this thing work like it’s supposed to.” After hearing this, I felt that I don’t know if it’s clear to me what this thing is supposed to do. I thought it was about improving safety and reducing delays. By having a bike lane, bicyclists’ safety will be improved and their delays will also be reduced.

Some bicyclists may be involved in collisions with motor vehicles here because they move against signals. The same is probably true for drivers who get into collisions: frustration and impatience and simply not knowing when you’ll have a turn may lead road users at this intersection to proceed when it’s not safe to do so (and against the signal). The project designers said that this intersection “encourages poor decision making.” With dedicated space, in the form of a bike lane, as well as simpler design and an expectation of when it will be one’s turn to go, bicyclists and drivers alike will better comply with intersection controls.

The plan does nothing to add bike lanes through the Elston or Damen intersections. The Damen bike lane currently ends 700 feet before the intersection. The Elston bike lane ends 400 feet before the intersection. That funny business needs to stop and we need bike lanes in Chicago that go THROUGH intersections, much like you see in New York City (example photo 1 and photo 2.

Complete Streets

My final comment, a quick one, is that the project made no mention of reduced travel times for those who ride the Fullerton or Damen Avenue buses through this intersection. We still have a long ways to go in accommodating, and caring about, our sustainable transportation modes.

Bicycle crashes are also not mentioned in the documentation, while motor vehicle crashes with pedestrians are. There were more crashes with bicyclists than with pedestrians in the 3-year period of 2007-2009 (12 versus 4). Bicycle counts have not yet been taken at this location; they should be conducted as soon as possible.

Complete Streets in Illinois needs to stop being a policy without any teeth and put into regular practice. Enough with just “considering” all transportation modes; we need to “provision” them.

Roundabout

Was a roundabout considered at this location? The Pennsylvania Department of Transportation’s Guide to Roundabouts (PDF) lists criteria on where to use roundabouts, including these which describe the intersections in question:

  • Large traffic signal delays
  • Heavy left turning traffic
  • More than four legs or unusual geometry
  • History of crashes involving crossing traffic
  • Traffic growth expected to be high and future traffic patterns uncertain or changeable [because Elston is a diagonal and near shopping, traffic volume will not change]
  • History of right angle crashes [this is true because of the confusing signal phases]

While three roundabouts may not be necessary, one should be considered at least for the Elston-Fullerton intersection, which has the most space available for such a facility.

Curve and wide road of New Elston Avenue

On “New Elston Avenue,” between Fullerton and Damen, there are two regular lanes and one bike lane in each direction. The widening of Elston was not justified. The high radius curve on New Elston Avenue on the east side of the project, and two regular lanes in each direction, will likely cause higher-speed traffic than bicyclists are used to on many roads on which they travel in great numbers. Automobile drivers speeding around the curve may enter the bike lanes. This is a good case for protected bike lanes at least on this part of the roadway. Thank you to A. Lottes for pointing out the curve to me.

Removing the  center island

Some commenters on The Expired Meter have suggested removing the tinny center island (as well as removing the second stop bar and signal every road user passes over) and converting it to a simple six-way intersection like Lincoln-Ashland-Belmont. While doing so may reduce delays or the number of crashes, it would probably fail to do both. I think it should be a considered alternative.

Queue backups caused by Fullerton-highway ramp intersection

The plan does not address the westbound queue backups that start at the Fullerton intersection with the I-90/I-94 highway ramp. Westbound drivers constantly and consistently block the Fullerton intersections with Damen and Elston while waiting to go through the signal at the highway ramp. This intersection is outside the project area but pivotal in its success at reducing delays, at least with the “remaining,” new intersection at Damen.

More information

The end of the presentation said that all exhibit materials would be on the City’s website, but I didn’t find all the poster boards, so here are most of them in my Flickr photoset. I assume they would be posted here.

Photos

A visualization of the crash history (only automobiles and pedestrian types included) at the intersection.

Bird’s eye view of preferred alternative.

Best ways to present bicycle crash data

I started some preliminary work on my crash reporting tool. I haven’t written any code, but I’ve been working on the logistics of analyzing and presenting the data to the public.

I obtained bicycle crash data for 2009 from the Illinois Department of Transportation’s Division of Traffic Safety. I’m not able to distribute raw data (you’ll have to ask for it yourself) and Illinois statutes prevent me from distributing personally identifying data (but it’s really hard to know what this is). In the meantime, based on Ben Sheldon’s suggestion, I loaded some of the data into a private Google Fusion Table that instantly maps geocoded data (it can also geocode the data for you).

Richard cautions me about way I choose to present data. I need to choose terms and descriptions carefully to avoid misinterpretations. Pete from the Boston Cyclist’s Union recommends against accepting self-reported data. I’ll be taking their advice into consideration as I move forward.

You see in the map (top) that a lot of crashes happen on Milwaukee Avenue (above). That’s where a lot of people ride (over 3,000 in 24 hours in the fall).

I have not begun to review the narrative details in the crash reports. Actually, they’re not very narrative because they’re fixed responses – no free writing allowed. And not every record represents a collision (meaning a crash with at least two parties). Many are self-crashes (is that a legit phrase)?

I’m not sure exactly what story I want the data to tell so it will probably be a while before I make anything public. One of my favorite geographic information books, Making Maps, talks about the endless ways maps can be designed and portrayed and that each tells a different story. It’s best if I know the story (a goal) ahead of time.

I want to make a crash reporting tool

UPDATE 12-01-10: Thank you to Richard Masoner for posting this on Cyclelicious. I have started collecting everyone’s great ideas and responses in this development document.

Hot off the heels of making my “Can I bring my bike on Metra right now?” web application, I am ready to start on the next great tool*.

I want to create a bicycle crash reporting tool for Chicago (but release the source code for any city’s residents to adopt) along the lines of B-SMaRT for Portlanders and the Boston Cyclist’s Union crash map based on 911 calls.

I’d rather not reinvent the wheel (but I’m very capable of building a new web application based in PHP and MySQL) so I’ve been trying to get in contact with Joe Broach, the creator of B-SMaRT, to get my hands on that source code.

Not exactly the type of crash I’ll be looking for. Photo by Jason Reed.

I want the Chicago Crash Collector (please think of a better name) to have both citizen-reported data, and data from police reports. I just sent in my FOIA request for police data to the Chicago Police Department, but I’m not holding my breath for that.