Category: Transportation

Proposed residential high-rise injects TOD and population loss into Logan Square conversation

A public notice stands in front of an affected property

There used to be a Max Gerber plumbing supply store here that the absent landlord demolished to reduce his property taxes. A developer has proposed built 254 units in two towers here, in spitting distance from the CTA’s 24-hour Blue Line.

Developer Rob Buono has proposed two towers for a vacant property 400 feet away (walking distance) from the Chicago Transit Authority’s California Blue Line station. It has caused quite a stir in Logan Square about how much development is the right amount, and brings into question residents’ understanding of how the neighborhood demographics have changed.

It has also brought “TOD” into the local conversation. Buono will get some relief from exceptional car parking requirements because of the land’s proximity to the ‘L’ rapid transit station.

The process will be a long one. The first meeting, called by Alderman Moreno, was held on Thursday night. I counted over 70 people on the sign-in sheet when I came in, and many people arrive after so saying 100 people were there isn’t a stretch. Moreno described his development policy: whenever they need a zoning change they must present their proposal to the community so Moreno can get their feedback.

Before Buono spoke, though, Moreno asked Daniel Hertz to briefly talk about transit-oriented development and why the development (or at least the number of units and car parking spaces it proposes) is a good project for this place, and in this neighborhood. In balancing concerns about car traffic, keeping people close to the services and products they need, and making it easy to get around, it makes the most sense to put the highest number of housing units in close proximity to high-capacity transit versus anywhere else.

Essentially, Logan Square has lost residents – 10,000 people since 2000 – concentrating the burden of patronizing local businesses, seen as a distinguishing asset in the neighborhood, on fewer people. Additionally, adding housing is the best way to combat rising home prices (and unaffordable rents) by offering more supply which reduces demand on richer people buying, converting, or tearing down existing buildings.

While no building permits will be issued for the towers until Ald. Moreno, Plan Commission, and City Council approve the zoning change, you can track what other kinds of buildings developers are building in the area surrounding 2293 N Milwaukee on Chicago Cityscape.

You’ll see quickly that a majority of the projects permitted this year are for single-family houses. Some of these are built on vacant parcels while at least one is  being built where there was previously a multi-family house.

In 2014, within 1/8 mile of the site:

  • +0 units in multi-unit buildings
  • -1 deconversion, turning two units into one unit
  • -1 teardown, turning a two-unit property into a single-family property
  • +17 single-familiy homes
  • Net gain of a maximum of 15 units

At this rate, Logan Square may grow at an extremely low rate – these homes will likely be filled with small families. The decreasing household size is another factor in Logan Square’s population loss.

Read about people’s reactions to the towers on other sites:

Joe Moreno

1st Ward Alderman Proco “Joe” Moreno gracefully – given the circumstances – moderates the meeting.

The Chicago Way: Potholes that definitely no longer exist

311 report for a pothole

Screenshot of the 311 service tracker that tells me that the photograph I submitted contains no image of potholes.

The Chicago Way is as much about the process as it is about the result. This story involves what happens when you can’t provide accurate information about a street inspection in the tracking system that has been built, effectively making a group of potholes disappear.

I submitted a pothole report via the Chicago open 311 system – assigning it service request #13-00420100 – on April 12, 2013 for 1653 N Milwaukee Avenue near Red Hen Bakery and Athletico. Three days later the inspection found no potholes and the request was closed.

The website or the Chicago 311 system seemingly could not provide a better answer. Certainly dismissing the existence of potholes is the wrong response. There’s no hope for the future in this response. Maybe there’s a plan to resurface this block. This could be the opportunity to inform a concerned citizen. Instead, the response told me I’m wrong.

Fast forward to now and the situation has devolved. Potholes have gotten a little bigger and they’ve spread as if the street is diseased. What also sucks is that this problem will probably persist for at least another year from my report (unit April 2015) because the hot asphalt plants are going to shutdown soon.

This reminds me of that Chicago maxim: “We don’t want nobody that nobody sent.” Or Metra, that the trains would be on time if they didn’t have to stop to pick up passengers.

#TheChicagoWay

Potholes on Milwaukee Avenue - I reported them over a year ago

The potholes as of August 2014.

The Chicago Way: The Fullerton sinkhole

the sinkhole before repair

The sinkhole before repair. Image from Smith’s newsletter.

In Alderman Michele Smith’s e-newsletter today is a story about #TheChicagoWay, which is that special way of fixing the streets we embrace in Chicago, despite our apparent disgust for low-quality infrastructure.

“Sometimes we really have to persist to get something fixed.” Here’s the story:

A deep sinkhole had formed at approximately 444 W. Fullerton Parkway, creating a significant public safety concern for both pedestrians and motorists. But no city department would repair it until we determined which agency was responsible.

So we called upon each potential agency, leading to almost a dozen separate site visits by various inspectors between July and August. We finally discovered that this site had been an old Commonwealth Edison utility area. The abandoned vault had deteriorated, resulting in the sinkhole.

I am happy to report that Commonwealth Edison filled in the old vault and restored the street. Success!

I would definitely call a sinkhole fix that happens within three months a success.

How would it work for you and your job security if it took two months to find who’s responsible for a known bug?

Other ways to identify #TheChicagoWay:

  • There is a cone or sawhorse-style barrier INSIDE of a hole. And then you’ll see that thing fall deeper into the hole and a new thing will be added.
  • For bigger holes, there are “safety” barriers INSIDE the hole instead of AHEAD of the hole.
  • How do you identify #TheChicagoWay in the context of streets?
after the sinkhole repair

The sinkhole and pavement after repair. Image from Smith’s newsletter.

Playing around with Chicago data: who’s running red lights?

Range Rover with Illinois license plate "0"

A Range Rover with Illinois license plate “0” is seen moving 40 MPH in a 30 MPH zone through a red light at Ashland and Cortland.

I’m just seeing who’s driving around Chicago one night, using the Tribune-published dataset of over 4.1 million tickets issued from red light cameras.

The City of Chicago has installed at least 340 red light cameras since the mid-2000s to reduce the number of people running red lights and crashing. They’re supposed to be installed at intersections where there’s a higher-than-average rate of right angle (“T-bone”) crashes, which are more injurious than other typical intersection crash types.

Assessing safety wasn’t the Tribune’s story angle, though. It was about showing spikes in the number of tickets issued, which I verified to some extent. The article called the tickets issued during these spikes “undeserved” and “unfair”. The data doesn’t have enough information to say whether or not that is the case; a video or extensive photo review is necessary to rule out rolling right turns while the light was red (a much less dangerous maneuver unless people are trying to cross the street).

The first query I ran assessed the number of people who get more than one ticket from a red light camera. Since I was tired my query was a little sloppy and it missed a lot of more useful order choices and didn’t select the right fields. I fell asleep and started again in the morning. This time, I got it right in just two tries – I needed to try again because I mistakenly put HAVING before the GROUP BY clause.

Here’s the first query, in its final form, to retrieve the number of tickets for each license plate in each state (I assumed there may be identical license plates among states).

select max(ticket_number), max(timestamp), license_plate, state, count(*) AS count FROM rlc_tickets group by license_plate, state HAVING count(*) > 1 order by count DESC NULLS LAST

It resulted in 851,538 rows, with each row representing a unique license plate-state combination and the number of red light violations that combination received. You can reasonably assert that cars don’t change license plates more than a couple times in a single person’s ownership, meaning you can also assert that each row represents one automobile.

851,538 vehicles, which make up 35.1% of all violators, have received 2,601,608, or 62.3%, of the 4,174,770 tickets. (There are 2,424,700 license plate-state combinations, using the query below.)

select count(ticket_number) from rlc_tickets group by license_plate, state

Here’re the top 10 vehicles that have received the most violations:

  1. SCHLARS, IL, 78
  2. 9720428, IL, 59
  3. 8919589, IL, 57
  4. A633520, IL, 52
  5. 3252TX, IL, 45
  6. A209445, IL, 44
  7. N339079, IL, 44
  8. X870991, IL, 41
  9. 239099, IL, 41
  10. 4552985, IL, 40

The next step would be to design a chart to show these vehicles’ activity over the months – did the vehicles’ drivers’ behavior change, decreasing the number of red light violations they received? Did the vehicle owner, perhaps a parent, tell their child to stop running red lights? Or has the vehicle owner appealed erroneously-issued tickets?

When I ran one of the first, mistaken, queries, I got results that put license plate “0” at the top of the list, with only nine tickets (license plates with two or more zeros were listed next).

I googled “license plate 0” and found a 2009 Tribune article which interviewed the Range Rover-driving owner of license plate “0” and the problems he encountered because of it. The City of Chicago parking meter enforcement staff were testing new equipment and used “0” as a test license plate not knowing such that license plate exists. Tom Feddor received real tickets, though.

I then looked up on PhotoNotice the license plate and ticket violation number to find, indeed, the license plate belonged to someone driving a Range Rover at Ashland Avenue and Cortland Street on July 17, 2008. An added bonus was Feddor’s speed in that Range Rover: the camera recorded the car going 40 MPH in a 30 MPH zone.

I was done browsing around for the biggest offenders so next I wondered how many tickets were issued to vehicles licensed in Arizona, where U-Haul registers all of its nationwide vehicles. Arizona plates came in 29th place for the greatest number of tickets.

select count(*) AS count, state from rlc_tickets group by state order by count DESC NULLS LAST

As you may have expected, four surrounding Midwest states, and Ohio, rounded up the top five states after Illinois – but this isn’t notable because most visitors come from there and they each only comprise less than 1.3% of the total tickets. The next state was Florida.

  • 3,986,739, IL
  • 51,104, WI
  • 40,737, MI
  • 27,539, IN
  • 8,550, OH
  • 7,684, MN
  • 7,139, FL

What’s next: I’m working on finding a correlation between the number of reported crashes, and type, at intersections with red light cameras and the number of tickets they issued. I started doing that before running the numbers behind this blog post but it got complicated and it takes a long time to geospatially compare over 500,000 crash reports with over 4.1 million red light tickets.

What else do you want to know?

I will delete all comments that don’t discuss the content of this post, including comments that call red light cameras, or this program, a “money grab”.

Red light camera ticket data insufficient to find cause for spikes

Spike in tickets issued at 119th/Halsted in May and June 2011. Nodes represent tickets grouped by week.

Spike in tickets issued at 119th/Halsted in May and June 2011. Nodes represent tickets grouped by week.

The Chicago Tribune published a dataset of over 4 million tickets issued to motorists for entering an intersection after the light had turned red. They analyzed the dataset and found unexplained spikes, where the number of tickets, being issued by the handfuls each day, suddenly tripled. (Download the dataset.)

I looked at the tickets issued by two of the 340 cameras. I didn’t find any spikes at Belmont/Sheridan (“400 W BELMONT”) but found a noticeable spike in May and June 2011 at the 119th Street and Halsted Street intersection (“11900 S HALSTED”).

I looked at three violations on one of the days that had an atypical number of tickets issued, May 12, 2011. Each motorist was ticketed, it appears, for turning right on red. It’s not possible, though, without watching the video, to see if the motorist rolled through the turn or indeed stopped before turning right.

The Tribune called tickets issued during these “spikes” “undeserved” but that’s hard to say without see the violations on video. The photos don’t provide enough evidence. The Tribune also reported that appeals during these spike periods were more likely to be overturned than in the period outside the spikes. The reporters discussed the possibility of malfunctions and malicious behavior, calling that an “intervention”.

The Chicago Department of Transportation, which oversees the program formerly operated by Redflex and now operated by Xerox, couldn’t refute either allegation, possibly with “service records, maintenance reports, email traffic, memos or anything else”. David Kidwell and Alex Richards report:

City transportation officials said neither the city nor Redflex made any changes to how violations were enforced. They acknowledged oversight failures and said the explosions of tickets should have been detected and resolved as they occurred. But they said that doesn’t mean the drivers weren’t breaking the law, and they defended the red light camera program overall as a safety success story. The program has generated nearly $500 million in revenue since it began in 2003.

The city was unaware of the spikes until given the evidence by the Tribune in January, said David Zavattero, a deputy director for the Chicago Department of Transportation. In the six months since, city officials have not provided any explanations.

“Trust me when I tell you that we want to know what caused these spikes you have identified as much as you do,” Zavattero said. “So far we can find no smoking gun.”

He acknowledged that faulty camera equipment likely played a role.

“I would say that is likely in some of these cases,” Zavattero said. “I cannot tell you that isn’t possible. It is possible. The old equipment was much more prone to break down than the equipment we are currently installing.”

You can download the data but you will likely produce the same results as the Tribune, but maybe a different conclusion. Their analysis has led people at all levels of the civic sphere to call for an investigation, including citizens, some of whom have filed a lawsuit, Alderman Waguespack and 19 other aldermen, and CDOT commissioner – who operates the red light camera program – Rebekah Scheinfeld.

I think they sufficiently identified a suspicious pattern. By the end of the long story, though, the Tribune didn’t prove its hypothesis that the tickets were “undeserved” or “unfair”.

In violation number 7003374335 you can see the driver of a Hyundai Santa Fe turning right at a red light. The Google Street View for this intersection shows that there is no RTOR restriction, meaning the driver is legally allowed to make a right turn here with a red light after coming to a complete stop and yielding to people in the crosswalk. But we can’t see if they stopped first. The next two violations that day at the same intersection I looked showed the same situation. (Find the violation by going to PhotoNotice and inputting 7003374335, NWD648, and CHI.)

I look forward to the investigation. The Tribune made a great start by analyzing the data and spurring the call for an investigation and it seems there’s not enough information in this dataset to explain why there are more tickets being issued.

One dataset that could help provide context – because these spikes, at least the ones that are sustained, don’t seem random – is knowing the number of vehicles passing through that intersection. The speed camera data has this information and allows one to show how different weekend traffic is from weekday traffic.

The "before" image showing the Santa Fe vehicle approaching the stop bar.

The “before” image showing the Santa Fe vehicle approaching the stop bar.

Violation photo 2

After: The Santa Fe vehicle is seen in a right turn.

Note: The Tribune identified 380 cameras but running a DISTINCT() query on the “camera name” field results in 340 values. Some cameras may have identical names because they’re at the same intersection, but you can’t discern that distinction from the dataset.