Category: Research/Study

Morgan CTA station ranks highly in rail system for building permits

Let Your Conscious Be Your Guide

The gutted cold storage warehouse in the background is within a quarter mile of the Morgan CTA station. Photo by Seth Anderson.

Excluding all of the Chicago Transit Authority stations in the central business district you’ll find that the new Morgan station ranks highly in the number of building permits issued within a quarter mile. It has a top spot when you calculate those permits’ estimated project costs. The CTA recently discussed with DNAInfo the results of a preliminary study it conducted that showed how the Morgan station is at the center of a lot of construction growth in the West Loop/Fulton Market area, and a contributing factor to this growth.

Now that Licensed Chicago Contractors shows you the two nearest CTA and Metra rail stations to each building permit, and I’ve become well-versed in writing PostGIS queries on the fly, I wrote a query that lists the CTA stations with the most building permits within a quarter mile (“nearby”).

First, though, let’s count how many stations don’t have permits nearby. With the query at the bottom you get a list of station names, the number of permits nearby, and a sum of the estimated costs of those permits sorted by the number of permits. Since I used a “LEFT JOIN” I also get a count of all the permits (the table on the LEFT) that don’t have a match with CTA stations (the table on the right).

There are 127 rows returned and a previous count of the table told me there are 145 stations, including ones outside the Chicago city limits. (There are stations in Cicero, Wilmette, Evanston, Rosemont, Oak Park, Forest Park, and Skokie.) The first row represents NULL, or all of the stations that don’t have permits nearby. That leaves me with 126 rows and 19 stations without permits, or 19 stations outside the City of Chicago.

I verified this by eyeballing it. I looked at a map and counted roughly 19 stations that wouldn’t have the 1/4 mile overlap with a Chicago building permit. The two Austin stations, on the Blue Line Forest Park branch and the Green Line Oak Park branch, are near Chicago and also showed up as a discrete station in the query results. Austin on the Blue Line was dead last, actually!

Let’s get back on track and look at Morgan now. I don’t think it’s fair to compare the Morgan station area with an expected, higher-activity area like the Loop and Central Business District so I eyeballed the list and started the #1 ranking with the first station outside the CBD.

  1. Armitage (Brown, Purple Express) is the station outside the CBD with the most building permits nearby.
  2. Damen-Milwaukee (Blue)
  3. North/Clybourn (Red)
  4. Addison (Red)
  5. Morgan (Green, Pink)

There you have it, from 2009 to today, the Morgan station had the fifth highest number of building permits outside of the Chicago Central Business District. It beat Fullerton (Red, Brown, Purple) in Lincoln Park, and Roosevelt (elevated and subway combined) in the South Loop. The station’s construction began in 2010 and the grand opening occurred May 24, 2012. During this period Morgan had the second highest amount of aggregated estimated costs at $199,911,953.00, behind North/Clybourn, at $218,118,037.37.

Take this analysis with several grains of Morton salt, though, because the following caveats are important to consider: building permits are really speculative development; much of these may be for kitchen renovations or porch reconstructions; I didn’t look up when it was “for sure” that the station was being built so I don’t know when developers would have become interested.

Looking at a longer period

I will, however, run a few more queries to find how Morgan’s position changes, starting with expanding the query to “all time” data (really the end of 2006 to today). It turns out that when looking through all available years Morgan’s position remains at #5 but other stations change position.

  1. Fullerton
  2. Armitage
  3. Damen-Milwaukee
  4. Addison
  5. Morgan

During this period, which covers the end of 2006 until today, Morgan had the highest aggregated estimated costs of the above five stations, at $236,707,083.00. It beat Fullerton’s amount of $160,825,680.30.

Looking only at “new construction”

Since these include all permit types, including water heater installations and window replacements, it doesn’t give us a good look at economic expansion in the areas surrounding CTA stations. I’ve filtered the data so only “new construction” building permits come through. I’m still interested in stations outside the CBD. Here’s how Morgan performed when looking at purely the quantity of new construction permits issued from 2009 to today:

  1. Armitage, 46 new construction building permits
  2. Southport, 38
  3. Addison (Red), 34
  4. North/Clybourn,
  5. Wellington,
  6. California-Milwaukee,
  7. Belmont (Red)
  8. Ashland (Green, Pink)
  9. Irving Park (Brown)
  10. Fullerton
  11. Damen (Brown)
  12. Division-Milwaukee
  13. Western-Milwaukee
  14. Ashland (Orange)
  15. Damen-Milwaukee
  16. Western-Congress
  17. Paulina
  18. Addison (Brown)
  19. Diversey
  20. Sedgwick
  21. Loyola
  22. Montrose (Brown)
  23. Sox-35th-Dan Ryan
  24. Morgan, 13 new construction building permits

Let’s remove that date filter and look at the whole building permits period of late 2006 to today.

  1. Southport (Brown Line), 80 new construction permits, all-time
  2. Armitage (Brown, Purple), 72
  3. Western-Congress (Blue), 66
  4. Addison (Red), 64
  5. Belmont (Red, Brown), 63
  6. Western-Milwaukee, 59
    Damen-Milwaukee, 59
  7. North/Clybourn, 55
    Diversey, 55
  8. Division-Milwaukee, 53
  9. Sox-35th-Dan Ryan, 51
  10. Wellington, 50
  11. 35-Bronzeville-IIT, 48
  12. Irving Park (Brown), 44
  13. Morgan, 43 new construction permits

Now switching the order method around and Morgan appears better when you look at aggregated estimated costs, from 2009 to today.

  1. Illinois Medical District, $236,020,000.00
  2. North/Clybourn, $172,373,335.00
  3. Loyola, $161,744,075.00
  4. Polk, $106,000,000.00
  5. Grand-Milwaukee, $77m224,500.00
  6. Wellington, $72m802,300.00
  7. Belmont (Red), $71,300,302.00
  8. Morgan, $68,300,800.00

Last query – remove the data filter and look at aggregated costs for the whole building permits period where Morgan maintains a top 10 position.

  1. North/Clybourn, $277029045.00
  2. Illinois Medical District, 236,020,000.00 (same as 2009 to today period)
  3. Polk, $188,794,975.00
  4. Loyola, $185,444,075.00
  5. Belmont (Red), $1635,00,085.00
  6. Fullerton, $129,444,051.00
  7. Wellington, $111,335,051.00
  8. Granville, $99,356,702.00
  9. Morgan, $83,995,800.00

The data I’d really like to have, though, is sales tax receipts for the same years.

This is not a valid PostgreSQL query. The brackets indicate the options I was using to retrieve the above results. The geometries are in or transformed to EPSG 3435 (Illinois StatePlane East Feet) and 1,320 feet is a quarter mile.

SELECT
 COUNT (P .permit_) AS count,
 MIN (C .longname) as name,
 min(lines) as lines, 
 sum(_estimated_cost) as sum
FROM
 permits P left join
 stations_cta C
ON
 ST_DWithin (
  ST_Transform (P .geometry, 3435),
  C .geom,
  1320
 )
[WHERE] [EXTRACT (YEAR FROM issue_date) >= 2009] [_permit_type = 'PERMIT - NEW CONSTRUCTION']
GROUP BY
 C .gid
ORDER BY
 [count,sum] DESC

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”.

Chicago wards with the most landmarked places

Montgomery Ward Complex

People float by the Montgomery Ward Complex on Kayaks. Photo by Michelle Anderson.

Last week I met with the passionate staff at Landmarks Illinois to talk about Licensed Chicago Contractors. I wanted to understand the legality for historic preservation and determine ways to highlight landmarked structures on the website and track any modifications or demolitions to them.

I incorporated two new geographies over the weekend: Chicago landmark districts, and properties and areas on the National Register of Historic Places (both available on the City of Chicago open data portal).

I used pgShapeLoader to import them to my DigitalOcean-hosted PostgreSQL database and modified some existing code to start looking at these two new datasets. Voila, you can now track what’s going on in the Montgomery Ward Company Complex – currently occupied by “600 W” (at 600 W Chicago Avenue) hosting Groupon among other businesses and restaurants.

Today I was messing around with some queries after I saw that the ward containing this place on the National Register – the 27th – also had a bunch of other listed spots.

I wrote a query to see which wards have the most places on the National Register. The table below lists the top three wards, with links to their page on Licensed Chicago Contractors. You’ll find that many have no building permits associated with them. This is because of two reasons: the listing’s small geography to look within for permits may not include the geography of issued permits (they’re a few feet off); we don’t have a copy of all permits yet.

[table id=15 /]

4 wards don’t have any listings on the National Register of Historic Places and nine wards have one listing.

Why are children getting hurt in the street because of “looming”?

Adults are better than children at detecting the speed of a car that’s traveling faster than 20 miles per hour and are more likely to avoid crossing, thus not getting hit. 

Director of New York City-based Transportation Alternatives Paul Steely-White asked on Twitter for a plain English translation of this three-year old journal article about vehicle speeds and something called “looming”.

The article is called “Reduced Sensitivity to Visual Looming Inflates the Risk Posed by Speeding Vehicles When Children Try to Cross the Road”.

Skip to the end if you want the plain English translation, but I’ve posted the abstract below followed by excerpts from Tom Vanderbilt’s Traffic.

ABSTRACT: Almost all locomotor animals respond to visual looming or to discrete changes in optical size. The need to detect and process looming remains critically important for humans in everyday life. Road traffic statistics confirm that children up to 15 years old are overrepresented in pedestrian casualties. We demonstrate that, for a given pedestrian crossing time, vehicles traveling faster loom less than slower vehicles, which creates a dangerous illusion in which faster vehicles may be perceived as not approaching. Our results from perceptual tests of looming thresholds show strong developmental trends in sensitivity, such that children may not be able to detect vehicles approaching at speeds in excess of 20 mph. This creates a risk of injudicious road crossing in urban settings when traffic speeds are higher than 20 mph. The risk is exacerbated because vehicles moving faster than this speed are more likely to result in pedestrian fatalities.

The full text is free to download, but I think Steely-White needs to learn more now, so I pulled out my favorite book about driving, Tom Vanderbilt’s “Traffic”.

Page 95-97:

For humans, however, distance, like speed, is something we often judge rather imperfectly. Unfortunately for us, driving is really all about distance and speed. Consider a common and hazards maneuver in driving: overtaking a car on a two-lane road another approaches in the oncoming lane. When objects like cars are within twenty or thirty feet, we’re good at estimating how far away they are, thanks to our binocular vision (and the brain’s ability to construct a single 3D image from the differing 2D views each eye provides). Beyond that distance, both eyes are seeing the same view in parallel, and so things get a bit hazy. The farther out we go, the worse it gets: For a car that is twenty feet away, we might be accurate to within a few feet, but when it is three hundred yards away [900 feet], we might be off by a hundred yards [300 feet]. Considering that it takes about 279 feet for a car traveling at 55 miles per hour to stop (assuming an ideal average reaction time of 1.5 seconds), you can appreciate the problem of overestimating how far away an approaching car is – especially when they’re approaching you at 55 miles per hour.

[Here comes the keyword used in the journal article, “looming”]

Since we cannot tell exactly how far away the approaching car might be we guess using spatial cues, like its position relative to a roadside building or the car in front of us. We can also use the size of the oncoming car itself as a guide. We know it is approaching because its size is expanding or looming on our retina.

But there are problems with this. The first is that viewing objects straight on, as with the approaching car, does not provide us with a lot of information.

[…]

If all this is not enough to worry about there’s also the problem of the oncoming cars speed. A car in the distance approaching 20 miles per hour makes passing easy, but what if it is doing 80 miles per hour? The problem is this: We cannot really tell the difference. Until, that is, the car gets much closer — by which time it might be too late to act on the information.

[the topic continues]

Plain English translation

However, nothing I found in Traffic relates children and “looming”. The bottom line is that children are worse than adults at detecting the speed of a car coming in the cross direction and thus decide wrongly on when to cross the street.

Update: Based on Vanderbilt’s writing, it seems that humans cannot really be taught how to compensate for looming, to build a better perceptual model in the brain to detect the difference between cars traveling 20 and 80 MPH. If this is true, and I’d like to see research of pedestrian marketing and education programs designed for children, it may be that we should stop trying this approach.

Revealing driver behavior on Clark Street with a radar gun

People prefer to cross Clark Street at Menomenee Street in groups of unacquainted individuals.

This is a more detailed post of the one at Streetsblog Chicago.

On the overcast morning of Friday, May 4, 2012, I recorded the speeds of 412 cars at four locations along Clark Street in Old Town and Lincoln Park for 15 minutes at each location. I missed counting the speeds of 42 cars. The embedded map shows the locations and some basic statistics.

What did I find? There’s a relationship between street width and the speed people drive. The highest speeds were found on the widest portions, and the lowest speeds on the narrowest portions. However, this basic study is far from scientific. A better study would record the locations simultaneously (necessitating 4 radar guns), calibrated equipment, consistent training for the researchers on data collection methods, a longer recording duration, and comparison to a control street that had a uniform width at four locations.


View Radar gun places on Clark Street in a larger map

1. Southbound Clark Street at Germania Place

My assistant and I set up the radar gun and camera immediately south of Sandburg Terrace and pointed the radar gun at people driving southbound on Clark Street between a row of parked cars at the concrete median (pedestrian refuge island). Classes would start soon at the Latin School on the east side of Clark Street. Compliance with state law requiring drivers to stop for pedestrians in the crosswalk was weak, to say the least, but compliance wasn’t explicitly measured.

  • Average speed: 17.21 miles per hour (MPH)
  • Maximum speed: 30 MPH
  • Cars measured: 151
  • Speed limit: 30 MPH
  • Drivers exceeding the speed limit: 0
  • Width: 224 inches (from west curb to pedestrian refuge island)
  • Effective width: 140 inches (excludes parking by subtracting 7 feet)
  • Crashes: 35, of which 4 were bicycle, and 3 were pedestrian.

Only one car-car crash (actually a 3 car crash) produced an injury. What’s interesting about this location is that in a lot of the crashes, the cars were traveling in the same direction. There’s a lot of school drop off and pick up activity here for Latin School of Chicago students, so it could be that many people are pulling away from the curb to merge into traffic and collide.

2. Northbound Clark Street at Menomenee Street

  • Average speed: 30.83 miles per hour (MPH)
  • Maximum speed: 50 MPH
  • Cars measured: 121
  • Speed limit: 30 MPH
  • Drivers exceeding the speed limit: 53.72%
  • Width: 395 inches (from east curb to dividing line). This includes the parking lane but no cars were parked within 50 feet, north and south, of the measurement location.
  • Crashes: 20, of which 2 were bicycle, and 1 were pedestrian. Many of the non-bike and non-ped crashes involved a parked car or taxi. The only injuries experienced were by the 2 cyclists and 1 pedestrian.

3. Northbound Clark Street at Lincoln Park West

We stood on the “pie” (traffic island) that separates northbound Clark Street traffic from northbound Lincoln Park West traffic to measure the traffic driving on Clark Street between the pie and the concrete median separating it from southbound Clark Street.

  • Average speed: 25.60 miles per hour (MPH)
  • Maximum speed: 40 MPH
  • Cars measured: 58
  • Speed limit: 30 MPH
  • Drivers exceeding the speed limit: 27.59%
  • Width: 252 inches (from concrete median curb to west curb on the pie)
  • Crashes: 4, of which 1 was bicycle, and 2 were pedestrian.

4. Northbound Clark Street between Lincoln Park West and Dickens Avenue

This location is 125 feet north of the previous location.

  • Average speed: 22.54 miles per hour (MPH)
  • Maximum speed: 35 MPH
  • Cars measured: 58
  • Speed limit: 30 MPH
  • Drivers exceeding the speed limit: 2.44%
  • Width: 264 inches (from east curb to dividing line).
  • Effective width: 180 inches (excludes parking by subtracting 7 feet)
  • Crashes: 0

Me measuring speeding drivers on Clark Street with the speed gun, my clipboard and paper, and a GoPro camera to record the speeding drivers and the results on the speed gun. 

Bike Walk Lincoln Park’s proposal

In 2011, Michelle Stenzel and Michael of Bike Walk Lincoln Park published a document to “Make Clark a Liveable Street“. The first two pages show an aerial photo of the same section of Clark Street where I measured automobile speeds, North Avenue and Armitage Avenue. On the first page, existing conditions are laid out. The second graphic shows proposed improvements.

At Menomonee Street, measurement location 2, the document says “pedestrians must cross 6 lanes with no safe haven”, a width of just under 66 feet. In the later pages, the first existing condition is blatant: “Wide lanes of auto traffic moving at speeds in excess of the speed limit”. My analysis in May demonstrates this.

How does BikeWalk Lincoln Park propose to “transform this stretch from a car-oriented ‘super-highway’ to a people-oriented liveable street”? By installing protected bike lanes, putting the street on a diet, and installing new and well-marked crosswalks among other ideas.

Width and speed summary

Ordered by location:

  1. 224/140 inches. 0% of drivers exceeded 30 MPH speed limit
  2. 395/395 inches. 53.72% of drivers exceeded 30 MPH speed limit
  3. 252/252 inches. 27.59% of drivers exceeded 30 MPH speed limit
  4. 264/180 inches. 2.44% of drivers exceeded 30 MPH speed limit

Ordered from narrowest to widest to see how width relates to speed:

  • 224/140 inches. 0% of drivers exceeded 30 MPH speed limit
  • 264/180 inches. 2.44% of drivers exceeded 30 MPH speed limit
  • 252/252 inches. 27.59% of drivers exceeded 30 MPH speed limit
  • 395/395 inches. 53.72% of drivers exceeded 30 MPH speed limit

Notes

Crash data is within 100 feet to avoid the overlap of the final two locations, which were 125 feet apart. Crash data comes from the Illinois Department of Transportation for 2005-2010. The Bushnell Velocity Speed Gun was borrowed for this analysis. The radar gun was filmed to show a speeding car and its speed simultaneously. The video below shows a driver traveling at 50 MPH in a Children’s Safety Zone (as it’s within 1/8 mile of a park, Lincoln Park, making it eligible for automated speed enforcement).

Curiously, no traffic counts have been collected on Clark Street near any of the count locations.

View the video on Vimeo.

Screenshot of traffic count website. Go to the Traffic Count Database System and search for “1700 N Clark Street, Chicago, IL” in the map.