Yesterday’s post was about the bike lanes on Chouteau that aren’t there…yet. While I was photographing the absence of bike lanes late last month I noticed something else as I crossed Chouteau at Tucker. The annoying pedestrian crosswalk buttons aren’t next to the curb ramp where they should be.
Pedestrian buttons should be reachable from the ramp, not 20 feet away! Personally I don’t think pedestrians should have to seek out and press button to get a walk signal — they should be automatic. Imagine driving and having to know just where to stop at a red light to give you a green light.
Pedestrian buttons are great for the sight-impaired. If done properly, once activated, it’ll verbally announce to the user when the walk sign is on and that it’s ok to cross. The rest of us shouldn’t have to press a button to get a walk signal.
Chouteau is maintained by MoDOT, I’ll alert them and the city about this.
Those of you who follow this blog on Twitter & Facebook know I post a few pics of the new protected bike lane last week. I’d read about it in an article on the 18th or 19th:
The city also announced the addition of its first parking-protected bike lane downtown on Chestnut Street between Fourth and 20th streets. It uses parked cars and flexible posts to separate the cycling lane from the driving lane. A striped buffer painted on the street also creates space between open car doors and the bike lane. (Post-Dispatch)
It was a few days before I could get over to Chestnut to see in person, passing by at 15th headed to transit.
With the bike lane running for 16 blocks, 20th t0 4th, I knew I couldn’t just cross at a single point and expect to understand it. If I wasn’t disabled, biking the mile distance would be the best way to experience it. Friday morning I started at 20th and made my way East to 4th, mostly on the adjacent sidewalk or at crosswalks. Let’s start at 20th:
So 20th to 15th is parking-protected, 15th to Tucker (12th) isn’t:
Protected: 5 blocks
Exposed: 3 blocks
As we continue East across Tucker things get more complicated. Also back to a single lane for vehicular traffic.
So Tucker to 4th the break down is:
Protected: 3.5 blocks
Exposed: 4.5 blocks
Which gives us totals of:
Protected: 8.5 blocks
Exposed: 7.5 blocks
Of the 16 blocks from 20th to 4th, just over half (53.125%) are protected.
The new white stripes look great against the dark black asphalt, but how will this look in a few years when both fade? I’d like to see the bike half block next to the Civil Courts be protected. When Kiener Plaza gets rebuilt hopefully those two blocks can become protected.
No surprise, but most who voted in the Sunday Poll favored an occupied building to replace a condemned parking garage downtown:
Q: The parking garage at Tucker & Locust, built in 1967, was condemned a few months ago. What should be the long-term outcome? (PICK UP TO 2)
Raze for new building w/zero parking 22 [34.92%]
Raze for new building w/some parking 21 [33.33%]
Renovation of structure, reopen garage 6 [9.52%]
Raze for new parking garage 5 [7.94%]
Unsure/no opinion 3 [4.76%]
Other: 3 [4.76%]
Apartments, parking, ground level retail.
Restaurant
Traditional incremental urbanism
Raze for surface parking lot 2 [3.17%]
Nothing, leave as is 1 [1.59%]
Raze for open space 0 [0%]
I was very happy nobody voted for “Raze for open space”, because we’ve got more open space than we need. I have to wonder about the person who voted that leaving a condemned parking garage is the best long-term outcome. Really!?!
Even in the short-term I’d oppose a surface parking lot. If built properly, it would likely stick around until fully depreciated — which isn’t short-term. We need to build on many of our existing surface lots to reduce holes in our urban fabric. A case could be made for a new parking garage on the site. At this point I’d give little chance the existing garage will be renovated — the repairs are just too costly.Without a doubt, a new building, with or without internal parking, is ideal.
The New Jersey-based entity that owns the condemned garage likely doesn’t care about what’s best for creating a more urban St. Louis, but I don’t care about their bottom line! In the Downtown Neighborhood Association’s Planning & Zoning Committee I’ll advocate for a position on this site that opposes just letting it sit or a surface parking lot, supports a building.
For over a decade I’ve written about pedestrians, including pedestrian deaths. It’s difficult to visit the sites and write about how the area could be designed better, but nothing like the pain experienced by the families & friends who’ve lost a loved one. Most recent was Bapi Gupta:
Gupta’s mother, Genie Dee, and Georgie Busch, who lost her daughter, Amber Wood, in a hit-and-run accident in the same location in 2012, are hoping to bring change to the stretch of roadway.
The string of fatalities and near misses has many calling for slower traffic in the area.
“Why is it 35 miles an hour here? Why isn’t there a stop light up the street here, which they took down, by the way,” said Michael Chekoudjian, the driving force behind a change.org petition asking for changes to the area. (KMOV)
With 3 fast lanes of traffic heading south, trying to beat the lights cars are exceeding the speed limit by 20 to 50 MPH. This is very Dangerous in an “Entertainment District” with as many as a 1000 people in the streets at times and as we know by the hit and run death of “Amber Wood” at the 700 block of Broadway in April of 2012 this is a very dangerous stretch of roadway. We the signers of this petition want Mayor Slay to put a stop to this speeding on this dangerous stretch of road in the name of “Amber Wood” NOW!
First let’s look at a couple of recent suggestions offered by family & friends:
Lower the posted speed limit: Motorists currently exceed the 35MPH speed limit, they’ll drive the same speed regardless of the posted limit. This is because people drive at what they perceive to be a safe speed based on the design of the road. If you want to lower the speed — you must change the design! More on the design later.
Traffic signal at previous intersection: The previous light at Cerre St was removed when a new ramp onto Eastbound I-64 made it a dead-end street. Putting a signal back doesn’t make sense. However, a flashing yellow signal overhead would be a good idea, changing to red if activated by a pedestrian wanting to cross Broadway.
There are things that should change, let’s take a look:
I sat here for a few cycles to time the lights. For vehicles the light is green for about 38-40 seconds. However, the pedestrian signal is “walk” for just 4 seconds before it begins to flash! It flashes for 10-15 seconds before going to a solid don’t walk, but the traffic signal remains green. Having such a short walk time with a longer traffic time encourages pedestrians to go for it rather than wait on the longer Broadway signal. The pedestrian signal timing needs to change immediately! Ok, let’s cross.
Based on my visit, here are my suggestions:
Immediate solutions:
Change pedestrian signal timing at Gratiot.
Short-term solutions:
Reinstall traffic signal at Cerre St., on yellow flash, changing to red if activated by a pedestrian.
Restripe Broadway, narrowing the 3 drive lanes.
Add a solid white lane to separate the outside drive lanes from the adjacent parking lanes.
Change pedestrian signals to have a countdown timer.
Long-term solutions:
New streetscape, putting the road on a diet with curb bulbs at all corners. Include mid-block planters in the parking lanes.
Return 4th & Broadway to 2-way traffic.
More observation, at different times, is needed. But this area must change or we’ll see more pedestrians hit.
AARP Livibility Index
The Livability Index scores neighborhoods and communities across the U.S. for the services and amenities that impact your life the most
Built St. Louis
historic architecture of St. Louis, Missouri – mourning the losses, celebrating the survivors.
Geo St. Louis
a guide to geospatial data about the City of St. Louis