Category: Roadways

Improvements in store for the Damen-Elston-Fullerton intersection

April 28, 2011 / / 0 Comments

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.

Just how many taxi vs. bicycle crashes are there? A Google Refine story

April 26, 2011 / / 0 Comments

On this Chicagoist story about how IDOT will now collect data on doorings (instead of ignoring that crash type as they preferred), I opened the story photo entitled “Cabbie takes down another” by Moe Martinez. His photo caption reads, “you see it alot … thankfully this guy seemed to be relatively ok … coherent and what not.”

I wanted to know just how often “we” see taxi drivers crashing with people riding bicycles. You can’t filter by vehicle type in either mine or Derek’s bike crash maps, but you can via the Fusion Table.

I decided to get the answer via Google Refine and make a screencast to show you just how quick and powerful a tool it is.

It’s dead simple:

  1. Load a CSV of the data into Google Refine.
  2. Click on the VEH1_SPECL column’s down arrow, then Facet>Text Facet.
  3. In the facet box, sorted alphabetically, find “TAXI/FORE HIRE.”
  4. The number of rows that apply is listed: 353.
  5. Divide 353 by the total number of rows, 4931, multiply by 100, and you get your percentage.

Taxi drivers are involved in just 7.2% of bicycle crashes in Chicago in 2007-2009.

The majority of crashes, at 66%, involve people driving “PERSONAL” vehicles. And 80% of those crashes are with a passenger vehicle that’s not a van, minivan, SUV, truck, or bus (so probably a sedan or coupe). Let’s look at more data.

How many taxis are there and how many personal vehicles are there? Are taxicabs involved in a disproportionately higher number of crashes?

About 781,023 people drive to work, either alone or with someone else, in Chicago (data from 2005-2009 5-year American Community Survey). 1,063,047 households have 1,218,594+ vehicles available in Chicago. Let’s assume the 7,000 taxicabs in Chicago are not counted as a “vehicle available.”* That’s 1,225,594 “personal” vehicles. If all were on the road at the same time, only 0.57% of them would be taxicabs. But they’re not on the road at the same time. So let’s take that number of people who drive to work and add 7,000 vehicles to it. So of those 788,023 “vehicles” now on the road, just 0.88% of them are taxicabs.

So it does seem that taxicabs are involved in a disproportionate number of crashes when compared to their presence on the streets. However, taxicabs are most likely driven more more miles and for more time than personal vehicles thus making their exposure to people bicycling greater than drivers of other vehicles. (A majority of “personal” trips are very short.)

New data coming soon

I can’t wait to get the 2010 crash data. Here’s why: In 2007, students in a taxi driver training course at Harold Washington College received some education about sharing the road with bicyclists:

A pilot “Share The Road” education module was launched at the taxi training school at Harold Washington College. It includes a 25-30 minute lecture, with discussion. After the pilot, the class will be required for all people training to drive taxis in Chicago. In the future, bicycle questions will be included on the exams required to become taxi drivers. June 2007 MBAC meeting minutes (PDF).

The number of crashes between taxi drivers and people riding bikes jumped from 2007 to 2008, but declined heavily between 2008 and 2009. More data will show us a clearer trend that may lend insight into the impact of the “Share The Road” education module.

*Notes

The question (PDF) on the American Community Survey asks, “How many automobiles, vans, and trucks of one-ton capacity or less are kept at home for use by members of this household?” This may or may not include taxicabs stored at home.

I don’t know how many taxicabs there are in Chicago, but the Chicago Sun-Times reported there are approximately 7,000.

Initial intersection crash analysis for Milwaukee Avenue

April 25, 2011 / / 0 Comments
Slightly upgraded Chicago Crash Browser

This screenshot from the Chicago Crash Browser map shows the location of bike-car collisions at Ogden/Milwaukee, an intersection that exemplifies the yellow trap problem the city hasn’t remedied.

List of the most crash-prone intersections on Milwaukee Avenue in Chicago. Using data from 2007-2009, when reported to the Chicago Police Department. Dooring data not included on the bike crash map. I used QGIS to draw a 50-feet buffer around the point where the intersection center lines meet.

Intersecting street (class 4*) Bike crashes
Chicago Avenue (see Ogden below) 12 (17)
California Avenue 9
Halsted Street & Grand Avenue 7
Damen Avenue & North Avenue 6
Western Avenue 6
Ogden Avenue (see Chicago above) 5 (17)
Ashland Avenue 5
Diversey Avenue 5
Fullerton Avenue 5
Elston Avenue 5
Augusta Boulevard (not class 4) 5

Combine the six-way (with center triangle) intersection of Ogden, Milwaukee, Chicago, and you see 17 crashes. Add the 6 just outside the 50-feet buffer and you get 23 crashes. Compare this to the six-way (without center triangle) at Halsted, Milwaukee, Grand, where there’s only 7 crashes.

What about the two intersections causes such a difference in crashes? Let’s look at some data:

Ogden, Milwaukee, Chicago Halsted, Milwaukee, Grand
Automobile traffic Approx 58,000 cars per day Approx 50,000 cars per day.
Bicycle traffic Not counted, but probably fewer than 3,100 bikes More than 3,100 bikes per day*
Bus traffic Two bus routes Three bus routes
Intersection style Island; three signal cycles No island; one signal cycle

*Notes

Traffic counts are assumed estimates. Counts are taken on a single day, either Tuesday, Wednesday, or Thursday. Bike counts at Halsted/Milwaukee/Grand were actually taken on Milwaukee several hundred feet northwest of the intersection so DO NOT include people biking on Halsted or Grand! This means that more than 3,100 people are biking through the intersection each day.

Intersection style tells us which kind of six-way intersection it is. At island styles you’ll find a concrete traffic island separating the three streets. You’ll also find three signal cycles because there are actually three intersections instead of one, making it a 12-way intersection. Also at these intersections you’ll see confusing instructional signage like, “OBEY YOUR SIGNAL ONLY” and “ONCOMING TRAFFIC HAS LONGER GREEN.”

These intersections are more likely to have a “yellow trap” – Ogden/Milwaukee definitely has this problem. The yellow trap occurs at that intersections when northbound, left-turning motorists (from Milwaukee to Ogden) get a red light but they still need to vacate the intersection. Thinking that oncoming traffic has a red light but are just being jerks and blowing the red light (when in fact they still have a green for 5-10 more seconds) they turn and sometimes hit the southbound traffic. The City of Chicago acknowledged this problem, for bicyclists especially, in summer 2013 but as of November 2014 the issue remains.

Here’s a more lengthy description of one of the problems here as well as an extremely simple solution: install a left-turn arrow for northbound Milwaukee Avenue. The entire intersection is within Alderman Burnett’s Ward 27.

Source and method

I can’t yet tell you how I obtained this data or created the map. I’m still working out the specifics in my procedures log. It involved some manual work at the end because in the resulting table that counted the number of crashes per intersection, every intersection was repeated, but the street names were in opposite columns.

Crash data from the Illinois Department of Transportation. Street data from the City of Chicago. Intersection data created with fTools in QGIS. To save time in this initial analysis, I only considered Milwaukee Avenue intersections with streets in the City of Chicago centerline file with a labeled CLASS of 1, 2, or 3.

Put the first cycle track somewhere else

April 6, 2011 / / 0 Comments

Updated 06-03-11: Grew the list below from 11 locations to 15 to match the full list on wiki.stevevance.net.

I propose 15 locations for Chicago (see link for ideal segments):

  • Archer Avenue (whole length)
  • Blue Island Avenue (between UIC and Pilsen, but then connecting Pilsen to Little Village via 26th Street)
  • Chicago Avenue
  • Clybourn Avenue (entire stretch, from Belmont to Division)
  • Damen Avenue (really easy south of Congress; difficult between Chicago and Congress, and north of Chicago)
  • Fullerton Avenue
  • Grand Avenue (at least California or Kedzie to Navy Pier)
  • Halsted Street (in some discrete locations)
  • King Drive (connecting downtown/South Loop to Bronzeville, Hyde Park, Washington Park)
  • Kinzie Street (connecting one major bike laned street, Milwaukee, to another, Wells)
  • Ogden Avenue (the entire street, from the city boundary on the southwest side to its dead end at the Chicago River near Chicago Avenue)
  • Vincennes Avenue (I haven’t figured out the extents for this one)
  • Wabash Street (connecting downtown and IIT)
  • Washington Boulevard/Street
  • Wells Street – this may be one of the easiest locations to pull off, politically at least, especially if Alderman Reilly pays for all or part of it with his annual appropriation of $1.32 million (“menu funds”).
  • Western Avenue

Notice how I didn’t propose Stony Island between 69th and 77th.

I selected streets where there’s already much cycling happening – whether it’s directly on that street and for long distances or neighborhoods the street passes through. I also selected streets where there’s some cycling happening but make the all-important bikeway network connections on streets with high automobile or high speed traffic (like Western Avenue) or lead to places that attract trips by bike (like train stations). And I selected streets that lead towards downtown, to transit stations, to schools, and to jobs. The segment of Stony Island from 69th to 77th leads to a small shopping district on 71st Street and a Metra Electric train station with 197 weekday boardings (from 2006 survey).

A cycle track location will be most effective where it can:

  • attract the most new riders (goal #1 in the Bike 2015 Plan)
  • make the biggest increases in safety by reducing injuries (goal #2 in the Bike 2015 Plan)
  • (and for the city’s first cycle track, be used by the most existing riders)

It is in these locations where these facilities will be quickly adopted by people bicycling to and from that neighborhood for their shopping, school, and social and work trips. It will also help lead the City and its residents to attaining the quite ambitious goals of the Bike 2015 Plan (have 5% of all trips under 5 miles by bike and cut frequency of injuries by half).

NACTO’s new Urban Bikeway Design Guide recommends cycle tracks for “streets on which bike lanes would cause many bicyclists to feel stress because of factors such as multiple lanes, high traffic volumes, high speed traffic, high demand for double parking, and high parking turnover.”

Stony Island between 69th and 77th has many lanes, high speed and high volume traffic, but low parking turnover (there’s a low density of businesses and many have their own parking lots). This area has low cycling levels and a grand bike facility here would do little to help Chicago reach the plan’s goals. We won’t see any benefit in terms of mode shift here.

Without further information on the intentions (see paragraph “On intentions” below) of those who selected this location and their goals for Chicago’s first cycle track, my surmise is that it was selected because of the roadway width (four lanes in each direction with a wide parallel parking lane, see map), where taking away a lane from car driving may be more politically and technically feasible – I believe this is the wrong way to begin a protected bike lane program.

On intentions: A former CDOT employee left a comment on my blog in December 2010 addressing the site selection: “Stony Island was recommended as a part of a Streetscape Master Plan [I can find no information about this plan]. It wasn’t like people were sitting around saying ‘Where can we put a buffered bike lane?’ It was really just a plan of opportunity since Stony Island is crazy-wide. Nevertheless, it will connect with a new bike path along the side of Marquette Dr in Jackson Park, which connects to the Lakefront Trail.”

While Stony Island could be a good demo location to prove that this type of facility won’t be harmful to drivers, as a demonstration of the power of protected bicycling infrastructure, it won’t do a good job.

A two-way protected bike lane (just like Prospect Park West in Brooklyn) in downtown Vancouver. Photo by Paul Krueger.

A one-way protected bike lane on 9th Avenue, New York City’s first cycle track. Photo by Jeramey Jannene.

Do you want this facility? Where?

April 4, 2011 / / 0 Comments

Take a look at this protected two-way bike lane in Brooklyn, New York City.

Some people are suing to remove (or change it). If you’re someone who doesn’t live there, here’s why this fight could still be important for you. Or maybe you want to know why the bike lane was installed.

If your city’s transportation or public works department proposed a protected bike lane or cycle track for your town, where should the first one go?

I propose 11 locations for Chicago (see link for ideal segments):

  • Blue Island Avenue
  • Chicago Avenue
  • Fullerton Avenue
  • Grand Avenue
  • Halsted Street (in some discrete locations)
  • King Drive (connecting downtown/South Loop to Bronzeville, Hyde Park, Washington Park)
  • Ogden Avenue (the entire street, from the city boundary on the southwest side to its dead end at the Chicago River near Chicago Avenue)
  • Wabash Street (connecting downtown and IIT)
  • Washington Boulevard/Street
  • Wells Street – this may be one of the easiest locations to pull off, politically at least, especially if Alderman Reilly pays for all or part of it with his annual appropriation of $1.32 million (“menu funds”).
  • Western Avenue

    Notice how I didn’t propose Stony Island. Here’s why.

    P.S. This will not be like the case of high-speed rail in America, where if one governor refuses money for an HSR project, other governors can compete for that money. The Prospect Park West bike lane will not be picking up and moving to another state 😉

    Look at all that room for people to go about their business, whether by car, bike, roller skates, wheelchairs, or their own two feet. Photos by Elizabeth Press.