Category: Advocacy

Streetsblog Chicago deserves to come back

John and Steven dining at a restaurant table

John and I at Taqueria La Zacatecana in Avondale, where we first hashed out the details of what would become Grid Chicago that later transitioned into Streetsblog Chicago.

I haven’t talked about this here, but two months ago this weekend I got the message that Streetsblog Chicago wouldn’t continue because we didn’t raise enough money in the last fundraising round.

I didn’t talk about it here because I was busy with dealing with shutting that down, working with my partner John Greenfield to come up with a transition plan (to resurrect the site) and because I have myriad side projects that quickly and easily captured my newly-available attention. I eased right into developing those more and into involving myself in new jobs on a freelance basis.

Our readers dutifully expressed their support for my and John’s work at Streetsblog Chicago – providing an alternative voice for transportation and land use policy discussion.

The most heartening and unexpected expressions have come from the very agencies on which we report and criticize.

Our reporting was thoughtful and necessary they said, even though, and this has been unanimous, they sometimes disagreed with our perspective.

I believe their appreciation of our work has always been there but there was never a good moment, or a necessity, for them to make it known.

It’s heartening to know that our writing – advocating for safer streets, funding allocation that promoted efficient and active transportation, converting street space from moving cars quickly to moving people – was making its way in the corridors of the bureaucracies and street managers and place makers and bus operators.

I think what we did with Streetsblog Chicago was necessary, too, and I waited and worked to make it happen since 2007. I bided my time with this blog until meeting editor-in-chief Ben Fried in 2010. The conditions weren’t right then, and a friend at a 2011 Star Trek watching party (don’t ask) in Logan Square put me and John together after which we made the next best thing: Grid Chicago.

I want to keep writing Streetsblog Chicago and we need your help. John and I are raising $75,000 to resume publishing at very-close-to-before rate of five to seven original posts per week. Donate now.

We’ve already raised $36,905 and the Chicago Community Trust will give us $25,000 when we reach $50,000. The catch is that we must get there by April 8. Otherwise we’ll return all of the donations.

Since the January 8 hiatus we held a fundraiser in the pedway, which Moxie founder Daniel Ronan organized. We’ll be holding another fundraiser in Revolution Brewing’s taproom on Kedzie on Wednesday, March 26, at our donor appreciation party: Everyone is welcome but those who donate $100 on or before the party will get John’s book “Bars Across America” and their first round on the house.

I’m also putting together a tour of developments around Chicago near transit stations that have taken advantage of a city ordinance reducing their parking minimum. Save the date, Saturday, April 4.

The CTA must remove the Clark Junction bottleneck to modernize the Red Line

CTA Belmont bypass rendering

A CTA rendering shows what a bypass track for Brown Line trains north of the Belmont station might look like, alongside a new residential building on Wilton Street.

Ed. note: This is a guest post from Chicagoan Jacob Peters.

“Keep the RPM Project on Track – Uncouple the [Belmont Bypass] Roller Coaster” is the tagline for a new website called “Coalition to Stop the Belmont Flyover”.

Capacity is constrained at the Chicago Transit Authority’s Clark Junction track interchange (at approximately 3300 N Clark Street) which means that fewer Red Line trains can run than could be run if there wasn’t this conflict. In the same way there are opportunity costs in business, there are opportunity delays that are caused by this constraint on rail capacity.

For example, if there was no conflict at Clark Junction, then five more trains an hour could pass through the Red Line subway. This would increase Red Line capacity by 25 percent during rush hour, and fewer passengers would be left waiting for a train to arrive with space for them to board.

The way the website advocates against eliminating the bottleneck is hypocritical to the tagline of “keeping the Red Purple Modernization project” on track. That project, which would completely replace all track, viaducts, and embankments north of X station, and rebuild most stations (as well as widening and extending platforms) is largely based on a future service pattern that would run more and longer trains in the busiest transit corridor of Chicago.

This capacity increase would reduce their average commutes by a few minutes. Since the trains wouldn’t have to be spread out in order to maintain gaps in service for the Brown Line trains that need to cross the Red Line at Clark Junction, average wait times between trains would drop all along the Red Line at rush hour, further reducing commute times.

Lastly, when either the Brown, Purple or Red Lines are experiencing delays, and trains get bunched together, these delays ripple through the other lines. This happens because when a queue of delayed Brown Line trains are making their way through Clark Junction, Red Line trains must be held in order to let the delayed trains through the junction in an attempt to keep things moderately on schedule. If there was a bypass of this junction for northbound Brown Line trains, then a delay on either line would not affect the other. This would result in fewer days in which your commute is delayed.

Future capacity needs and current delay reduction is what the Belmont Bypass attempts to address. There may be other ways to achieve this with other alternatives, but the bypass would be far and away the cheapest and could be implemented soonest. Unless you plan to propose alternative means of resolving these conflicts, and funding mechanisms to make them possible, you are not really advocating to keep the RPM on track. Because without untying Clark Junction there is no true modernization.

Runoff election

The RedEye published on Monday an overview of the transit platforms from the two mayoral candidates that have made it into a runoff. (Mayor Rahm Emanuel didn’t receive a sufficient number of votes, 50 percent +1, in the February 24 election.) Chuy Garcia released his transportation and infrastructure platform about two days before the election.

Garcia paints a beautiful transportation issues platform, but when faced with a truly transformative project he is unwilling to uphold his call for “reliable transportation”. I want to vote for him again, but if he keeps on watering down projects to a point of inefficacy then how are you going to convince anyone to expand transportation funding? How can I trust him to bring about the change is needed on other important issues if on the issue that he received a masters in, he is unwilling to apply best practices?

Emanuel and Garcia should avoid grandstanding on issues of transportation because opposing a necessary transportation investment for political reasons is to let down the electorate that you are campaigning to serve. For both traversing Ashland Avenue by transit and riding Brown, Red, and Purple Line trains through Clark Junction, there is no way to move more people reliably through these areas without infrastructure improvements. Garcia shouldn’t oppose projects without explaining his alternate plan to address the same issues and achieve similar benefits – otherwise there isn’t leadership.

Alternatives

There are few alternatives. First, you could study how to use the existing CTA land around the Belmont stop more efficiently and eliminate track conflicts. It would need to be studied whether a new northbound Brown Line track and platform just to the east and a few feet higher than the current track it shares with the Purple Line could allow for the Brown Line to get high early enough to bridge over the Red Line closer to School.

This option would spare the buildings on the commercial thoroughfare of Clark, and focus demolition on residential streets.  I am not sure if it is possible given how the Belmont station was reconstructed in 2009, but I don’t have a record of it being studied or laid out why it is not an option. Seeing as the anti-bypass group is claiming that the destruction on Clark would turn it into a “permanent under-El wasteland” I would think they would want to prove whether this is possible or not.

Secondly, any alternatives analysis process [which the CTA hasn’t conducted] would include studying a subway alternative for this portion of the Red Line. In the RPM’s subway alternative there was no need for the bypass. The CTA considered a subway from Loyola station to Belmont station, but never studied each section of the potential subway separately. I truly believe that a subway with a portal at Clark Street and a portal just north of Irving Park Road would eliminate the property acquisition, station constraint, and construction phasing issues to outweigh the increased cost of going underground, without needing to consider a two-track alternative.

There was a neighborhood proposal from the 1980s for a subway between Belmont Avenue and Irving Park Road which would act somewhat as a “flyunder”, so to speak. It would include a new Wrigley Field Station that could be built to handle more than the existing constrained Addison Red Line station, including a Purple Line stop in order to match the Purple Line limited service that stops at Sheridan that’s provided on select game days.

The “flyunder” could allow the CTA to forego the large amounts of property acquisition that would be required in order to straighten out the kinks in the elevated north of Belmont, and to smooth out the curve at Sheridan. The CTA could then sell land currently under the tracks for development. In order to see if this is now feasible given the way Belmont was rebuilt, the CTA would have to study whether a bilevel tunnel from Clark Junction to Irving Park would be possible under Clark Street, and parallel to Seminary Avenue.

There is also the alternative of proposing that eliminating the realignment of the Red Line, included in the Belmont Bypass literature, would be a way to eliminate the amount of buildings affected in the scope of the bypass.  But I think that is somewhat tied into the discussion about the other two alternatives. The point is that the elevated bypass is a simple (although in the CTA’s current process, clumsy) solution to the question of how do you eliminate the Clark Junction bottleneck and the unreliability in the system that it creates.

Anti-traffic safety is now a political platform

Three of the five men running for Mayor of Chicago have pledged to eliminate enforcing red light running with cameras. Many aldermen have done the same. The Chicago Tribune has factually pointed out that Mayors Daley and Emanuel have mismanaged the red light camera program, with the bulk of it falling upon staff in the Daley administration. (The only part of the program under Emanuel that could be considered mismanagement was changing the business rules to issue tickets when the yellow light was recorded as 2.90 to 2.99 seconds long; Emanuel’s administration changed the rule back and has implemented many other changes following the inspector general’s report.)

Red light cameras lead to an increase in rear-end crashes but decrease the more severe angle (T-bone) crashes, which the Chicago Tribune “sorta” pointed out when it looked at frequencies but not injury costs.

Current 2nd ward Alderman Bob Fioretti, Cook County commissioner Jesus “Chuy’ Garcia, William “Dock” Walls, and Willie Wilson all have decided that neither the facts nor safety for people inside and outside of multi-ton machines are important. They are supporting the right to endanger others by respecting the inconvenience of not always being prepared to stop at a traffic signal.

Fioretti has said he will introduce soon an ordinance to remove red light cameras by April, but I haven’t found it in the legislation database.

Even though Streetsblog Chicago is no longer publishing, John Greenfield is hustling to get us both working again. In the meantime I intend to cover parts of the election, which takes place February 24, with assistance.

Bike lane mileage is the wrong metric for your city to publicize

Sometimes I tweet things that get pretty popular and then I need to go into more details. Case in point:

Which I followed by tweeting:

Knowing how many miles of bike lanes you have has little importance in determining if I’m going to bike in your city when I visit, or if I’m considering moving there, or if I want to add you to a “bicycle friendly cities” list.

What’s more important is how much the number of people bicycling on those bike lanes has changed. This number will reflect the quality of your bike lanes. Are they still in good shape or have they faded a lot? Do they connect to each other to create a network, or are there gaps that increase the stress of a route? How have you treated the bike lane at intersections, the place where a conflict and crash is most likely to occur?

Chicago Tribune architecture critic Blair Kamin touched on these points in his recent critique, one of the few worthwhile articles the Tribune has published in the last year about bicycling, by interviewing an organization that tries to make it politically palatable to build unconventional – in the United States – bike lanes.

“Chicago has made incredible progress over the last few years,” said Martha Roskowski, vice president at People for Bikes, a Boulder, Colo.-based advocacy group. But, she added, “Chicago also has a ways to go.”

That’s saying it nicely.

Addressing the gaps in the city’s network of protected bike routes, Roskowski said: “People evaluate a potential bike ride on the basis of the weakest link, the scariest part of the trip, which might be a really busy road you have to ride along or across. People have tolerance for a little bit of that. But if it’s sustained or if it feels dangerous, they just won’t do it.”

Enter Close Calls, deteriorating bike lanes, bumpy pavement, and constant obstacles and you get Chicago’s ridiculously low bicycle commute to work numbers.

Since Emanuel took office in 2011, Chicago has installed 52 miles of protected bike lanes [it’s only installed 16 miles of protected bike lanes], which use a variety of means — plastic pylons, striped pavement markings and non-curbside parking spaces — to separate bikes from vehicles. That brings the city’s total bicycle lanes to 207 miles.

That’s cool that we have 207 miles. How many miles of streets without bike lanes do we have? It’s 4,000 and some change minus 207.

Why doesn’t Mayor Rahm Emanuel talk about how many people have taken up bicycling since he took office, or how many more trips Chicagoans made (and where) because of those 52 miles of new buffered and protected bike lanes?

He can’t say how many people are riding their personal bikes because the city doesn’t track this.

Conversely we can track Divvy bike-share use down to the minute and the company announced that Saturday, May 24, they had their most trips ever. Only to be eclipsed by almost 4,000 more trips on Sunday, May 25 (helped in no small part by the Bike The Drive event where people can bicycle on a Lake Shore Drive that’s closed to vehicles).

In another blow to good data for Chicago, Divvy will only be releasing trip data twice a year, while Citibike in New York City will be publishing it monthly, an improvement of Capital Bikeshare’s quarterly data releases.

If you’re not tracking who’s using your infrastructure, will you be able to know if the people you set out to attract have come out?

Getting a little closer to understanding Chicago’s pothole-filling performance status

Tom Kompare updated his web application that tracks the progress of potholes based on information in the city’s data portal in response to my query about how many potholes the city fills within 72 hours, which is the Chicago Department of Transportation’s performance measure.

He wrote to me via the Open Government Chicago group:

Without completely rewriting http://potholes.311services.org, I added a count of the number of open (not yet addressed) pothole repair tickets (requests) that exceed 3 days old. As of today, the data from the City of Chicago’s Data Portal shows 1,334 or the 1,404 open tickets in the 311 system are older than three days.

Full disclosure: The web app actually looks for greater than 4 days old. The Data Portal’s pothole data are only updated once a day, so these data are always a day old. 4 – 1 = 3.

Keep in mind that this web app only shows how many are yet to be addressed, and does not count how many have been patched within CDOT’s 3-day goal during some arbitrary time period. That is a much more intense calculation that this pure client-side Javascript web application can handle due to bandwidth restrictions on mobile (3/4G). This web app already pushes the mobile envelope with the amount of data downloaded. I can fix that, but, again, not without a rewrite.

Still, 1,334 open repair requests (12/16/2013 Data Portal data) is quite different than the number of open repair requests reported by CDOT (560 in Alley, 193 on street) on 12/16/2013. I’m not sure what is the difference.

This reminds me of a third issue with the way CDOT is presenting pothole performance data online (the first being that it’s PDF, the second that it doesn’t work in Safari). The six PDF files are overwritten for every new day of data. If you want information from two days ago, well you better have downloaded the PDF from two days ago!