Category: Maps

Revisionist history: Karachi changed maps to support illegal housing development

I’m still reading Instant City: Life and death in Karachi, the book I reviewed a little over a week ago.

It seems that Winston Smith from 1984 works for the Karachi city government. Author Steve Inskeep describes his investigation into the life of activist Nisar Baloch and the alleged encroachment, a common occurrence, on a public park, Gutter Baghicha.

Nevertheless the investigator did find houses under construction in several of the acres that were in dispute. Now it became a matter of dry law, or so it seemed. One of the simpler questions was whether the construction was inside the national park or outside of it.

A map of the national park from 2005 clearly included the land where construction had begun. A map from 2009 clearly excluded the land where construction had begun.

Curiously, both maps were produced by the Karachi city government, which seemed to have altered the shape of the national park to accommodate the new settlement. That was how the city managed to claim with a straight face that the settled was outside the park. When I compared the two maps with Google images of the national park under construction, it was clear that Shehri [a local environmental protection and advocacy group suing the city about this encroachment] was right: the park’s boundaries had moved. The 2005 design of he park could not possibly fit in the remaining land now designated for it.

You’ll have to read the book to know the end of the story (buy it on Amazon and Kindle), and the end of Nisar’s life. The map below shows the park in the center of the city.


View Larger Map

Are protected bike lanes going in the right places?

Bike crash map of Ogden, Milwaukee, Chicago

Common bike-car crash locations in West Town. The bottom blue circle identifies Ogden/Milwaukee, where there is a yellow trap for northbound, left-turning motorists (from Milwaukee to Ogden) that makes them run into southbound bicyclists who have a green light.

My contribution to a discussion on The Chainlink, Are protected bike lanes going in the right places?

Kelvin, Milwaukee/Ogden/Chicago is the intersection along Milwaukee Avenue with the highest number of bicycle crashes. I created this table and map to show them, using data from 2007-2009.

The blue rings on the map are called, in GIS parlance, “buffers” and are circles used to select things (in this case, bike crashes) within a certain distance of the circle center. In this map I used 50 feet radius buffers (100 feet diameter). While this distance encompasses the intersection from center to all four curbs, it doesn’t encompass the crashes that happened just outside the buffer that were still most likely influenced by the intersection (like drivers’ turning movements).

I am working on a project with three friends to create a better map and “crash browser”. I mentioned it in the last story on Grid Chicago in this post. For this project, we are using 200 feet radius (400 feet diameter) buffers to ensure we encompass the entire intersection and the area in which it still has an effect. This also grabs the bike lane “pinch points”, places where a bike lane doesn’t start until 100-200 feet beyond the intersection.

I am also concerned with the strategy and approach CDOT is using to choose locations. It’s not transparent; at MBAC, CDOT said they were choosing locations “without controversy and that could be implemented quickly”.

Read more about Kinzie Street, Chicago’s first protected bike lane, and my other thoughts on protected bike lanes

Friday is final day for comments about Damen-Elston-Fullerton

Tomorrow, Friday, May 13, 2011, is the final day to email comments to Bridget Stalla, project manager for the Damen-Elston-Fullerton reconfiguration.

What should you do?

  1. Read an overview of the project and my analysis
  2. View photos of the posters at April’s open house to understand what will and won’t change
  3. Think of what you like or don’t like about the project
  4. Email your comments to Bridget: bridget.stalla@cityofchicago.org
  5. Think about posting your comments here.

My draft comments

Here’s what I plan to email Bridget tomorrow:

  1. Bike lane on Damen – There should be a bike lane on Damen connecting the two ends north and south of Fullerton. Additionally, the bike lane should go THROUGH both intersections. See an example of a “through bike lane” in this photo. Too often bicyclists in Chicago are “dropped off” at intersections, left to fend for themselves and get caught in the same problems as automobiles. But automobiles and bicycles are different kinds of vehicles and need different treatments and direction.
  2. Roundabout – Was a roundabout considered for any of the three intersections? What were the results of this analysis? A modern, turbo roundabout should be given serious consideration for at least one of the three intersections.
  3. Curve and wide road on 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.
  4. Removing the center island – Was removing the center island an alternative the project team considered?
  5. Queue backups caused by Fullerton-highway ramp intersection – The project area should be expanded to include the intersection to the west of the project area, at Fullerton/Kennedy 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.

A bird’s eye view of the new configuration.

New site brings together bike crash maps and projects

I just finished creating a website that brings together my original Chicago bike crash map and all of its offshoots created by others. It also includes a more details and updated FAQ page as well as a short history of how the map and data came to be.

Enter the Crash Portal.

Right now it features projects from myself, Francesco Villa, Derek Eder, and George Aye’s students at the School of the Art Institute “Living in a Smart City” class. The site also links to my inspiration: Boston and San Francisco. If you have a related project, email me and I’ll figure out a way to add it to the site.

Screenshot of new Crash Portal

Initial intersection crash analysis for Milwaukee Avenue

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.