Category: Transportation

Welcome to the Land of No

No bike riding!

The Lincoln Park Zoo has a Nature Boardwalk at the South Pound near 2000 N Cannon Drive. Each venue has their own signs listing the rules for their respective properties.

Each sign employs a different symbol to communicate the same thing – bicycles cannot be ridden in the parks – but their designs take two approaches.

One says no and the other says yes.

  • The Zoo’s symbol uses the color red, a line slashed over a bicycle, and “Please do not:” text to prohibit the activity of riding a bike.
  • The Pond’s symbol uses the color blue and suggests walking your bike, accompanied by the text, “Please walk your bike”.

Please walk with your bicycle. 

Bicyclists – and drivers for that matter – are constantly being told no. Might there be a friendlier, more positive way to communicate rules?


View Larger Map

Even the grocery stores are bike-friendly in Portland

Kenda tube vending machine

Swipe your bank card and get a new inner tube, next to a repair stand to help you change it.

Mike Cobb sent me this photo of a vending machine outside the Green Zebra Grocery in Portland, Oregon, that sells Kenda brand bicycle inner tubes. These vending machines are more common in Germany and the Netherlands although I only spotted one in Berlin.

Fahrrad schläuche

A tube vending machine, Fahrrad schläuche in German, outside a bike shop in Berlin.

He says they have a repair stand under shelter, air pump, tethered tools, and all-weather electricity outlets, too.

“Yeah, I’ll shop there every time I’m within a 1/2 mile,” he said. Mike is busy planning Disaster Relief Trials around the country this year and we’re working to make one happen in Chicago. But we need a title sponsor who has thousands of dollars to donate.

Seattle DRT: did it! (photo by Fred Bretsch, FEMA Region 10)

Mike in Seattle after winning DRT there. Photo by Fred Bretsch, FEMA Region 10.

Going to worship at The Beer Temple takes too long

Minor suggestion to improve Elston-California-Belmont

A map of Belmont, Elston, California with lines and labels that show how I get to The Beer Temple and where I think the city should add car parking.

The Beer Temple opened two blocks from my house in Avondale last year, at 3185 N Elston Ave, on the six-way intersection of Belmont Avenue, Elston Avenue, and California Avenue. This intersection is beastly.

And it’s timed wrong. Since I live southwest of the great craft and imported beer store and it’s on the northwest corner of Elston (a diagonal street) and California, I have to cross twice. I make the first crossing, east-west across California at my street, and then walk north to the second crossing, north-south across Elston.

I cross at my street across California because there’s no light to wait for, and the crossing isn’t diagonal like my other option at Elston (which would mean I walk north, then diagonally south and east). Once I get to Elston, though, I’m screwed because the walk signal is about 15 seconds long but the wait for the next walk signal is about 90 seconds long.

It’s so long because the green for Elston is held for Elston traffic, but also held green for eastbound Belmont traffic that makes a right turn onto southeast-bound Elston. Instead of the walk signal being green for two phases of the cycle (for two of the three streets), it’s green for only one cycle: California’s.

This is because this six-way intersection is the less common type, the type with an island in the middle. It’s got the island because the three streets cross each other at different points and don’t share a common cross point. I’ve got to wait for two phases because Elston needs to stay green for Belmont traffic because you can’t have drivers waiting in the island area – too many cars may stack up and block cross traffic during another phase.

(At many intersections I would just cross whenever there’s a gap between fast-moving cars, but with six-way intersections you don’t always know from where a car will be speeding towards you.)

I get that, but that makes it suck for walking in this area. This design also makes it suck for people biking and driving to turn left from certain streets to other streets because they can’t make the left turn and keep on going. They make the left turn and then have to stop and wait for a second phase to keep going.

I’ve racked my mind for ideas on how to improve this intersection just mildly, in such a way that few would oppose (because that’s really the threshold you can’t cross to have a nice outcome in Chicago).

My idea? Add car parking in front of Dragon Lady Lounge in the “non-identified lane” there. It’s used as a travel lane, or a right-turn lane, depending on who’s driving and how they choose to maneuver their vehicle. It’s not needed for either because of the way traffic moves southbound on Elston past Dragon Lady Lounge and that Elston only has one travel lane in each direction on either side of this big intersection.

The parking would have the obvious benefit of putting customers closer to their destination, but would have the less obvious benefits of protecting people on the sidewalk, buffering noise and speeding vehicles from sidewalk users, and slow traffic past Dragon Lady Lounge when people are parking.

One day left to enter the Divvy Data Challenge

Divvy dock post-polar vortex

Divvy bikes have been covered in snow frequently this winter. Photo by Jennifer Davis.

As self-proclaimed Divvy Data Brigade Captain* in Chicago’s #opendata and #opengov community I must tell you that all Divvy Data Challenge submissions are due tomorrow, Tuesday, March 11. Divvy posted:

Help us illustrate the answers to questions such as: Where are riders going? When are they going there? How far do they ride? What are top stations? What interesting usage patterns emerge? What can the data reveal about how Chicago gets around on Divvy?

We’re interested in infographics, maps, images, animations, or websites that can help answer questions and reveal patterns in Divvy usage. We’re looking for entries to tell us something new about these trips and show us what they look like.

I’ve seen a handful of the entries so far, including some to which I’ve contributed, and I’m impressed. When the deadline passes I’ll feature my favorites.

Want to play with the data? You should start with these resources, in order:

  1. Divvy Data Challenge – rules and data download
  2. divvy-munging – download an enhanced version of Divvy’s data, with input from several #ChiHackNight hackers
  3. Bike Sharing Data Hackpad – this is where I’m consolidating all of the links to projects, visualizations, analysis, data, and blog posts.
  4. Divvy Data Google Group – a discussion group with over 25 members
  5. #DivvyData – chat on Twitter

It’s not too late to get started now on a project about the bikes themselves. Nick Bennet has crunched the numbers on the bikes’ activity and posted them to the Divvy Data Google Group. Want to use his data and initial analysis? He said “run with it”.

Share your work ahead of time and leave a comment with a link to your project.

* This title is a play on Christopher Whitaker’s position as Code For America Brigade Captain and all around awesome-doer of keeping track of everything that’s going on in these communities and publishing event write-ups on Smart Chicago Collaborative.

Let’s get rid of beg buttons

As much as you may believe, because you encounter them so rarely, Chicago indeed has several types of “beg buttons”. This is a mechanism wherein a person walking along a street must apply to cross another street. You are begging for permission. They are not popular, many are not even hooked up anymore, and they don’t call the pedestrian signal any sooner (their purpose is to make the green traffic signal long enough for a person to cross).

Jan Gehl et. al. succinctly demonstrate in Cities for People the opposing methods of telling a person when they can cross the street (meaning cross traffic has been halted).

The 2013 Chicago Complete Streets Design Guidelines and 2012 Pedestrian Plan reorients the city to prefer facilitating and encouraging transportation by foot over all other modes of travel.

The Pedestrian Plan says that beg buttons should have an LED light that indicates to the pusher that the button has been pushed. (The Pedestrian Plan also calls “traffic signals” a high cost pedestrian safety tool, alongside the high cost of “pedestrian hybrid beacons” and the medium cost of “rectangular rapid flash beacons”. Slow traffic, on the other hand, doesn’t have an operating cost, but it definitely has a “we’re getting there cost”.)

The Plan also says to get rid of them “except for locations where they are necessary to bring up a WALK phases for pedestrians” and without saying what makes it necessary to bring up a WALK phase (versus always having a WALK phase for that direction of traffic) and if that “necessary” is aligned with the Complete Streets Design Guidelines’ paradigm shift. Systematically removing inoperable ones is a separate, medium term milestone (alongside developing a location database).

The CSDG thankfully considers many other realities in Chicago that go against the new transportation paradigm that puts the pedestrian first. For example, it calls for the systematic removal of all slip lanes – none of which I’ve heard or seen removed in the year since CDOT created the guidelines.

Untitled

I want the city to systematically remove all beg buttons. If the green signal is too short for a person to cross the street, then it’s probably too short for a bicyclist to cross in the green signal (yes, this exists in Chicago). It also means the street is too wide to foster it being a place over being a pipe for cars. And if it’s not a place, what is it and why are people walking there? What personal needs – like a job, food, and socializing – are not being fulfilled where they live that people have to cross this road to meet those needs?

Updated March 10 at 12:56 to clarify what the Pedestrian Plan says about beg buttons.