Elevating Chicago

TR Archives

Moving on

When I started writing here almost a year ago, I wasn't sure what to expect. I'm just a mechanical engineer living in Washington, DC with an interest in transportation and urban planning trying to write about issues in Chicago. It wouldn't have surprised me if this blog proved to simply be me shouting into the ether, a few thousand words on transit oriented development and bike lanes before going quietly into the night. But I also had an idea for something bigger, something that would prove that while there may not yet be a StreetsblogChicago, it's not for lack on interest on the part of the city's residents. Obviously, Elevating Chicago has been much closer to the former than the latter, and that says more about me than about the community for these ideas. (One of Jane Jacobs' most basic ideas was that the city life--both good and bad--which we seek is everywhere around us all the time, if only we would look. It's hard to get a handle on that life from 800 miles away, and near impossible to advocate for it successfully by writing once a week or less.)

There's certainly an untapped well of interest in--and advocacy for--bringing to Chicago many of the of livable reforms and designs I've talked about here. From groups like the Active Transportation Alliance, to the Center for Neighborhood Technology, to individuals like Mike Payne, Jason Tinkey, Steve Vance, and Lee Crandell, there are plenty of smart, hard-working people in and around Chicago who understand how much greater the city could be. If, by some strange circumstance, you've been reading what I have to say but ignoring them, take it upon yourself to fix that now. (And if you're one of them: thanks for the writing you guys do. It's always smart, informative, and doesn't succumb to the cynicism that's all-too-easy to embrace in Chicago.)

UCBerkeley-logo.jpg

So why am I shutting this down, anyway? Well, I'm starting on the road to doing this professionally. Later this summer, I'll be moving to California to get a Master of Science in Transportation Engineering from UC-Berkeley. Between classes, research, and exploring a new city (both socially and transportationally), this blog would take even more of a backseat than it already does. My plan is to focus on intra-city mass transit, though who knows where my research will take me. And don't worry: I'll do everything I can to avoid becoming any version of this.

Perhaps I'll come back to Chicago when I'm done--that's still a long way off. In the meantime, I'm going to leave this blog up as long as ChicagoNow will let me. I'll still be paying attention to this stuff even if I'm not writing about it, but should events warrant a comment, having a (semi-) established corner of cyberspace could prove useful. If you've been following me on twitter, I think I'm going to shut @ElevChicago down. I'll still be going strong on my personal account, @RedTosenbaum--and that will start to skew more heavily toward urbanism and transportation (and away from sports, quizzo, and beer) in the coming weeks and months. And of course, there's always email, which I suppose passes for formal communication these days: ted [dot] rosenbaum [at] gmail [dot] com.

May all your trains arrive just as your reach the platform, and may your roads be efficiently priced.

Ted

Lies, Damn Lies, and Chicago's Congestion "Problem"

The Texas Transportation Institute's Urban Mobility Report is always good for a few screaming headlines, and this year's release doesn't disappoint. Chicago and Washington, DC tied for the longest commuter delays,* totaling 70 hours per commuter per year in 2009 (the most recent year for data). That's pretty awful, especialy when you compare that to the 64 hours per commuter per year we wasted in 2008.  And since 2009 was a worse year economically, this number certainly won't improve as more people (hopefully) get back to work, many of whom will commute by driving themselves.

Except that TTI's rankings are a crock. When a rough draft of this report came out last year, Chicago's own CEOs for Cities responded: their "Driven Apart" report is the most thorough debunking of TTI's methods I've ever seen.  Briefly, TTI has 2 main ranking systems, and both of them have fundamental flaws.

  1. "Delay Time." Chicago ranks #1 in the nation in total delay hours, but what is a delay? Well, anytime you travel on a highway below 60 mph or on an arterial below 30, you're adding to the delay.  Nevermind that most expressways around here have 55 mph speed limits and arterials are often 25 mph!
  2. "Travel Time Index" This is the one that really rankles, because it produces a score which state DOTs can use like a cudgel to convince politicians to waste taxpayer money on highway capacity increases that never solve congestion problems. I'll let David Alpert of Greater Greater Washington (our brethren at #1) take it away:

Consider two hypothetical cities. In Denseopolis, people live within 2 miles of work on average, but the roads are fairly clogged and drivers can only go about 20 miles per hour. However, it only takes an average of 6 minutes to get to work, which isn't bad.

On the other hand, in Sprawlville, people live about 30 miles from work on average, but there are lots and lots of fast-moving freeways, so people can drive 60 mph. That means it takes 30 minutes to get to work.

Which city is more congested? By TTI's methods, it's Denseopolis. But it's the people of Sprawlville who spend more time commuting, and thus have less time to be with their families and for recreation.

Of course, who needs a hypothetical when there's a perfectly good real-world example of this: according to the report, Chicago and Houston have the same Travel Time Index of 1.25 (which ranks us 5th among very large cities, for the record). However, Chicago drivers only need an average of 13.5 miles to reach work, while Houston's average commute distance is 22.1 miles. We are desneopolis, and that's a good thing.

*Really, Jon Hilkevitch? You're gonna fall for TTI's trap too? I know you saw the CEOs for Cities report back in September--you wrote about it very cogently. So why the regurgitation of TTI's press release now? I'll give you credit for not stooping to repeat TTI's claim that "in the end, there's a need for more capacity" and instead pointing out how much worse it would be if Chicago didn't have good public transportation. But why not mention Driven Apart and say that although TTI is (unfortuantely) the standard, there are serious problems with it? Help make us an informed citizenry and all that, right?

Train Tracker Thoughts

As you've probably heard by now, the CTA will introduce a Train Tracker pilot program in the next month or so.  This is, undoubtedly, terrific news.  But until we get further details about the system and can play around with it, I'd like to present some ideas/potential pratfalls for the new system.

traintracker screen shot.gif

--Location, location, location.  How the CTA places these screens at stations is vital to their usefulness.  Obviously one at platform level is vital--always good to know how much longer you'll be standing in the cold.  The question is, where should the street-level screen go?

I'd say there are really only two locations to choose from.  One, facing the fare gates (or just outside them) and clearly visible before you pay your fare.  The second is physically outside the station.  For elevated stations, the station entrance is usually directly below the tracks, so a screen that is visible as you approach on the sidewalk would be protected from the elements (and could be protected from birds easily enough).  Similarly, at subway stations, a screen visible before going below ground would be best--though since most stations have multiple entrances, the cost of placing a display at every one may not be worth it.

--Online.  Since this is only a pilot and there won't be displays at every station, making Train Tracker easily available online is the only way most riders will interact with the system.  And most of those people will be checking the site on their mobile phone, so it's even more crucial that the interface be top notch.  Washington, DC does a fantastic job in this regard.  Here's their mobile site.  It's easy to navigate and almost entirely text, so it loads quickly, even on a slow network. The only thing I'd add would be an auto-refresh option--if the arrival times will update every 25 seconds, set the refresh period to 30.

--Open Source.  Considering the success of 3rd party applications (not to mention the manifold uses for the Bus Tracker API), there's no reason not to release the QuickTrak/Train Tracker data similarly.

--Depth of Information.  Looking at the mockup screenshots the CTA includes in their press release, it looks like we'll get 6 pieces of information: time of the last update, current temperature, line, direction, run number, and estimated time of arrival.

I'd push for 2 more pieces of information: one, give the update time down to the second.  I know the ETA isn't necessarily going to be accurate down to the second, but keep in mind: if the "as of" time is only accurate to the minute, and ETAs are accurate to within 30-45 seconds, you're looking at almost a 2 minute margin of error.  The CTA says the displays will update every 20-30 seconds, so why not tell us exactly when it last queried the system, and cut the margin of error in half?

Second, the displays should include the number of cars in the train that's about to arrive.  It may seem like a small thing, but if you know the length of the train, you can figure out whether or not you can spread out from everyone else along the platform, without having to catch up to the final door as it slides by you.  I actually asked the CTA about this over the summer, and here's the crux of their response:

"One of the purposes of the pilot would be to test the different capabilities of the program. At this time there are no plans to display the number of rail cars on an approaching train - some of the LED signs used for the program  pose character limitations for the additional information and adjustments are often made based on special events or circumstances on a particular day on a particular line that requires rail operations to deviate from what is normally put into service."

Ok, some of the signs can't hold that much information.  (Again, I think DC is instructive here: the displays have all the screen resolution of a game of pong, but they still manage to fit the number of cars.)  But why not make sure the system is at least disseminating this data, and then program each display based on its capabilities? The CTA could still include this information online, which is the only way people will get the info anyway if they're not at a pilot station.  Additionally, the CTA wrote:

"We have a schedule that designates how many cars are in each consist on any train based on ridership demands [sic].  However, this plan is subject to change - adjustments are often made based on special events or circumstances on a particular day on a particular line that requires rail operations to deviate from what is normally put into service.  This is not something that we would be able to provide."

Well, that's a relief--the CTA has a schedule, but are willing to deviate from it depending on the day's circumstances.  And when they deviate, they no doubt know the new trainset's length.  So as that train makes its way through the system, this shouldn't be a hard piece of data to include, right?

Additionally, it'll be interesting to see how Train Tracker handles arrivals.  In Washington, DC, there's both an "ARR" notation just before the train enters the station, and then a "BRD" as the train stops and opens its doors.  Whether or not the CTA can give that kind of granularity depends on whether or not there's a sensor at the entrance to the station, but we'll see.

Finally, a bonus for any programmers out there: if and when the API is released, it's screaming for an animation of Tower 18's operations (that's the intersection of Wells & Lake).  I'll take a stab at this, but if you write it, I will pimp the hell out of it here, on twitter, and anywhere else people will listen.

An Open Letter to Gabe Klein

Dear Mr. Klein,

I heard that come January 1, you'll be out of a job.  What a bummer.  But Washington's loss has to be someone's gain, right? Have you thought about Chicago?

First, let me level with you: Yes, we get snow regularly.  But we know better than to proclaim a snowfall as "Snowmageddon" until it's over 2 feet.  We have the infrastructure to clear it--and a populace that isn't afraid to use a shovel (perhaps you remember one of our former residents referring to our "flinty toughness"?)  And yes, as a result, we get enough potholes to make driving more painful than a trip to the dentist.  But we're already the home of Lollapalooza, why not bring your famed (?) Potholepalooza to town?

But!                                      Gabe Klein Dreaming.png

You may not have heard, but we're gonna have a new Mayor here next year.  You joined Mayor Fenty's staff in Washington halfway through his term and accomplished a ton.  Imagine getting in at the start of a new mayor's term (our first new Mayor in over 2 decades!) and having nearly free reign, since the new Mayor's priorities will likely be on reducing crime and improving the school system.

Although actual policy statements have been rare thus far in the campaign, everyone agrees that the Mayor's office needs to become more open.  You helped bring DDOT into the 21st century by actually establishing a twitter presence, opening data sets to the public, and more--CDOT needs that kind of reform badly.

You can be the first great Transportation Commissioner here since... well, it's been a damn long time.  We've had repeated turnover in the job in recent years as Mayor Daley tires of each new placeholder.  While they've all mostly moved the ball forward on incremental reforms, it's only been at the whim of a Mayor whose attention is obviously divided.  So while we have a bike plan (which DC's now almost dwarfs when you consider the disparity in size between the cities themselves), and a Central Area Action Plan, and even a few Streetscape plans, no one has laid out the grand vision that Chicago needs to become a city that works for everyone--not just drivers--once again.

And just think: You won't have to fight anymore turf wars.  The National Parks Service won't claim jurisdiction over every random triangle park or circle and then fail to maintain it.  Though there are certainly NIMBYs here like anywhere else, there's no Committee of 100 to try to thwart you at every turn.  It's all yours.  We only have a few diagonal avenues to break up our lovely street grid, a fantastic slate upon which you can build a shining beacon of Bus Rapid Transit, bicycle infrastructure, and whatever else you want.

Speaking of bike infrastructure, did I mention Chicago's topography? We're flat.  Utterly, completely, incredibly flat.  When you try to push out a bike sharing program (because I'm sure Alta would be more than willing to work with you again to bring their system to America's third largest city), you'll never have to worry about overcrowding at stations at the bottom of hills--there aren't any.

You've worked hard to bridge gaps between the rich and poor areas of DC, promoting capital-intensive projects like the new streetcar lines in the worse-off areas, hoping to spur improvement.  Chicago is one of the most segregated cities in the country, and it's high time our transportation options linked these areas rather than divided them.

So go take your vacation in January (you've clearly earned it).  And when you get back, come by and leave your card with the Mayoral frontrunners.  It'll be one less tough decision for them, and one new fantastic opportunity for you.

More Chicago transit data than you can handle

The folks at the Center for Neighborhood Technology (CNT) have done transit nerds yet another huge favor.  First it was their H+T Index, which was rolled into Abogo, their walkscore-esque tool that helps you measure your carbon footprint.  Now, they've gone and put an enormous collection of data online in an open, easy-to-use Transit-Oriented Development Database.  For lack of a better phrase, this is data porn.  Specifically, transit data.  You can look at every type of data imaginable for the areas within a quarter- or half-mile of any individual train station (what CNT calls the "transit zone" for that station) or collection of stations (the "transit shed").

I'll be rummaging through as much of the data as I can in the coming days and weeks (especially the job density statistics), but for now, here are a few tidbits to hold you over:

-- Based on 2000 population estimates, only about 1.15 million people live within a half-mile of L stations.  For reference: Chicago's population was about 2.9 million in 2000.  But keep in mind those 1.15 million include residents of Cicero, Oak Park, Skokie, and Evanston, where the L extends past Chicago's borders, so in reality an even smaller part of the city's population is transit-oriented.

pop density near Ls.png

-- Although average density can be a very misleading statistic, it's useful in this sense: ideally, the areas near train stations should be significantly more dense than the city as a whole.  (Unless you're dealing with a uniformly-dense place like Manhattan, where even the low-density areas can support transit.)  Chicago's average density is about 13,000 people per square mile.  But as you can see above, nearly half of the 142 L stations have local densities (within 0.5 miles of the stop) under 13,440 people per square mile.  Granted, some of these stops are like O'Hare or Midway, but many of them are not.

-- 26 of the 27 densest stations by population are on the Red/Brown/Purple north side.  The lone outlier is Damen, on the Pink Line.

Much more to come, or add your own findings in the comments.


New Monroe St. Crosswalk: thanks for following the law!

Before the weekend sets in, just a tinge of outrage over something that is so close to being perfect.  Blair Kamin writes about the new crosswalk on Monroe between the Art Institute's Modern Wing and Millenium Park.  It's a great compromise between safely getting pedestrians across the street and unnecessarily impeding traffic with a full-on traffic light.

It's very simple: you press a button, wait for the big flashing yellow lights around the pedestrian signs to alert the cars to your presence, (very handy as daylight gets shorter as we head into winter,) and then cross! Cars continue on their way, you enjoy your day, everybody's happy.

monroe st xwalk sign.jpg

Image courtesy Chicago Tribune


But wait, what's that last note there? "Thank the driver"? Yes, even the mechanical voice that accompanies the signs reminds you, "And remember, thank the driver for stopping as you are crossing the roadway."  I'm all in favor of Nice Midwestern interactions, but as of this summer, all cars must stop for pedestrians in a crosswalk.  Yes, that's right, we're now being instructed to thank people for following a simple, straightforward law.  A law which, if drivers follow it, will mildly inconvenience them--if they ignore it, odds are a pedestrian gets hurt or dies.

So much of the rest of this--from process to final product--was executed well, but this kind of auto-centric urban design is absolutely flabbergasting.  Go enjoy your weekend, and be safe in those crosswalks.

Officially Going to 2040

Yesterday, leaders of the 7 counties that broadly make up Chicagoland voted on the Chicago Metropolitan Agency for Planning's (CMAP) final version of their Go To 2040 regional plan. Not surprisingly, it passed unanimously. Now what? Well, it's now up to the cities and counties in the region to get on with implementing the strategies CMAP has outlined, and funding and building some of the projects Go To 2040 calls for. First though, let's remind ourselves exactly what we're left with.

Because CMAP is regional, Go To 2040 tries to build toward a scenario where all of Chicagoland prospers equally in the next three decades. The plan talks about local municipalities partnering together to create livable communities, where water is preserved, human capital is attracted and retained, and people can get to and from their jobs in a timely fashion. When CMAP discusses competition, it is against other metropolitan regions--both nationally and internationally.

CMAP 2040 Capital projects

Image courtesy CMAP

If CMAP's models prove correct, Chicagoland will add 2.4 million residents by 2040. Many of them will be of working age. However, the plan makes no preference or prediction for where those jobs will be. This leaves us to mull over the likely outcomes: in one scenario, the region experiences a massive decentralization--the jobs move out of the current urban core and, in harmony with the livable communities CMAP advocates, people will live near where they work. In another scenario, jobs continue to accumulate as they have for the previous three decades--mainly near the loop, with suburban office parks (like those near O'Hare) dotting the periphery.

Note that neither of these scenarios is inherently better than the other. They both have their positives and negatives, and recognizing that the relationship between the city and its suburbs is symbiotic--not parasitic--is crucial to any kind of regional success in the next three decades. But in both cases, there will be winners and losers. Yes, a prosperous region is not a zero-sum game, but the past is instructive. The entire post-World War II era has been prosperous for America as a whole and the Chicago region in particular. But it would be foolish to argue that Chicago itself felt that prosperity as thoroughly as its suburbs have.

So how will this growth and prosperity shake out in the next generation? Without either a massive infrastructure change (which CMAP readily admits we don't have the money for) or a sudden, similarly massive change in how people do business (say, a continually growing emphasis on the service industry and a daily telecommuting approaching 50% of the workforce) I don't see any evidence for a fundamental deviation from the status quo. The vast majority of new jobs in the region will be where they are today: inside Chicago's city limits, and mostly in and around the loop. And in order to keep those business functioning (and ideally to attract new ones) people have to reach their jobs efficiently. Perhaps, with a good urban infill program, people will move closer to the dense core (a kind of melding of the two scenarios I outlined above), but for several reasons* that likely won't be enough.

What then, will be enough? Better transportation, simple (and as complicated) as that. Go To 2040 has listed just about every conceivable project Chicago could hope to undertake in the next 30 years here. I'll get into it in the future, but to put it simply: the questions over how our limited funds will be distributed for these projects will determine the shape and prosperity of the region. Will the West Loop Transportation Center add core capacity to the L (as opposed to simply being a high-speed rail hub)? Will the city spur development around the proposed red line expansion, or waste these new stations as park-and-rides? (Or, perhaps go another route all together--Gray Line, anyone?) Will the expansion of IL-53 grow as a real urban boulevard, or just a slightly prettier version of US-41? Will the Mid-City Transitway ever be real? These are the battles that will make a difference.

*the liquidity (or lack thereof) of housing and the state of public schooling in Chicago, just to name two.

Labor Day Weekend Food for Thought

A few items to ponder over the long weekend, which I hope to expand on next week.

More on Street Signs
I've been thinking more about street signs--and especially numbering on street signs.  What strikes me is how infrequently block numbers are posted at all.  Every quarter or eighth of a mile on arterial streets is ok when you're driving, because if you miss your turn or turn the wrong way, it doesn't take much effort to double back to where you want to go.  But suppose you're on foot or on bike.  Suddenly making the wrong turn becomes a larger issue.  It's an issue both because of the effort you have to expend to correct it, but also because it will likely take longer to realize you've made a mistake in the first place.  So many of Chicago's residential neighborhoods have zoning requirements for setbacks that, without well-lit front doors, you can walk a full block without being able to make out an address.  In the loop, where many buildings are known simply by their address, it isn't a big as big a deal that the street signs almost universally do not include block numbers.  But if the loop is all we're concerned with, we're doing something wrong.

Frequent Network Maps
Building off a discussion from Jarret Walker at Human Transit, Jeff Wegerson at Prairie State Blue has mapped out a rough version of Chicago's Frequent Network Map.  His includes both bus and rail, and a few things jump out at me. First and foremost is how the canal carves up South Side transit options.  From 18th to (what looks like) 55th, there's no good east-west transit. These maps also really drive home how dense the loop is compared to the rest of the city, and how dramatically that skews our transit.  If you look at the 11 minute map in particular (below), you can start to see the skeleton of a corridor-based growth pattern that, if developed correctly, could help make Chicago more poly-centric, which would both ease the burden on the L and very likely lower total miles per vehicle in the city.  This is an idea I really want to get into in more depth, so if anyone knows of any studies about VMT and polycentricity, I'd love some light reading for this weekend.

Jeff Wegerson 11min FNM.png

Jeff Wegerson's 11-minute CTA Frequent Network Map


Circles and Circumference
Also at Human Transit (what can I say, he's got a lot of good stuff going on over there), Walker talks about how the Moscow circle line is probably a bit too small with a diameter just under 4 miles.  Now, clearly both the urban and transit geography of Chicago and Moscow are very different, but the planned Circle Line here would suffer from a more extreme case of the same problem Moscow's line faces.  There, there's no reason to ride more than half the line.  Here, because there's nothing (from a transit standpoint) east of the loop, you'd never ride for more than a quarter of the line.  I'm not going to say that this is proof that the Circle Line is a waste of money as-designed--the need for any kind of inter-line connection that doesn't force riders all the way into the loop is desperately needed--but I think we as a city need to think long and hard about our current and future geometry. (I'd hate to turn it into a buzzword, but polycentricity is a big part of this, too.)

Where you are vs. Where you're going

Suppose you're driving west on North Avenue.  You cross the river, scoot under the Kennedy, and come to the light at Ashland.  You look up at the street sign and notice: you're at 1600 West.  That's great.  Your friend lives on Sawyer, which you know is just past Kedzie.  Just over two miles to go, no sweat.  When you approach the light at Kedzie though, you double check your friend's address--in the 1800 block.  Quick: which lane do you get into?  Like a good Chicagoan, you know that North Avenue is 1600 North, and you'll be making a right onto Sawyer to head north a couple blocks.   Easy. (Sawyer's also one way north, so it was really your only choice.)

Thumbnail image for North Ave sign.png

But what about everyone else?  The ones that don't know the names and numbers of every east-west arterial from Howard to 130th.   Well, they've got two options.  One is to try and crane their neck as they pass through one of the major intersections and hope to make out what the sign for North Avenue says--this is more than a little dangerous, and you've probably sworn at an out-of-towner who slowed down through an intersection to try this.  The other option is trial and error--but with one-way streets, that's a recipe for disaster.  Chicago has made a subtle value judgment here; it's more important to know the addresses on the street you're on than the ones on the street you're about to cross--or turn onto.  In our example above, it was nice to know that you were 2 miles from Kedzie, but was that bit of knowledge more important than knowing which way to turn on Sawyer?

If you've ever navigated in another city that consistently puts block numbers on its street signs, you've probably noticed that they do it differently.  In fact, Seattle is the only other major city I could find which numbers the Chicago way. In Philadelphia, Washington, DC, San Francisco, and many others, the system is exactly reversed.

Kater st Philly - Edu-Tourist.jpg

Turn left for the 2000 block of Kater St. in Philadelphia, right for the 2100 block. Photo courtesy of Edu-Tourist on Flickr.

Taking our original example, every street sign you'd see on North avenue would, in one way or another, tell you that turning left (as you head west) will take you down the 1500 block, while if you turn right, you'll be on the 1600 block.   There's an assumption here that once you're on the same street as your destination, you either know what hundred you turned onto it (and so can count blocks until you're on the right one) or you can catch the address of any building as it passes by.

Having navigated extensively in both systems, I still can't decide which I like better--and which I think is better for the city as a whole, which is a different question.  I think Chicago's system is better for locals, but the other way is more straightforward for tourists and new residents--especially because these cities tend to put numbers on street signs at more than just major intersections. Anyone have a strong preference one way or another? And more interestingly, does anyone know the how/when/why behind this decision?

Sure, call it a comeback

After huddling in the studio for over a month, Elevating Chicago is here to announce a reboot, with some changes.  Before we go forward though, it's important to straighten out how we got here.  So full disclosure: I don't live in Chicago.  I grew up there here (I'm going to keep writing with the local voice.  So sue me) but I now live in Washington, DC--hence posts like this.  This worked out mostly ok, because Scott was still in the city and was a great help for me to get the details right, not to mention his own terrific posts.

In July, Scott moved away.  We were left without an anchor, and unsure of what to do.  He's pressed for time now and so most likely his byline won't appear in these parts anymore.  I, however, still can sneak in some time for this corner of the internet.  And I still love Chicago, so I'm going to keep writing.  Because for every good idea the city tries (rebuilt L stations, the upcoming BRT pilot) there are half-measures (the bike sharing pilot) and utter failures (how about a CDOT commissioner that sticks around for a while?)  So, although I won't be able to experience a lot of what happens first-hand, I'll be keeping a watchful eye on things (and talking to the friends and family I still have in Chicago) and offer my two cents.

So this post is also a bleg: if you see something that I might miss by not walking, driving, and riding around, tell me.  Email, twitter, carrier pigeon, whatever.  And if I miss details, correct me.  It won't be the first time I've been wrong, and the most important thing I can do here--elevating the conversation about making Chicago more livable for all of us--will never work if I'm inaccurate.

And now, on with the show...

Most Active Pages Right Now

ChicagoNow.com on Facebook