Article 63J5C SDOT survey asks if they should improve the bike lane south of U Bridge (yes, obviously) – UPDATED

SDOT survey asks if they should improve the bike lane south of U Bridge (yes, obviously) – UPDATED

by
Tom Fucoloro
from on (#63J5C)
fab047b2-bdd1-4390-ac50-7a513c0c77e8-575

The answer is obvious. Take the survey and support Option 2.

Whatever you are doing, stop and fill out this quick survey to support safer bike lanes on Eastlake as part of the RapidRide J project. You can also attend one of two virtual community design sessions Wednesday from 12-1:30 p.m. or 6-7:30 p.m. (register here).

There are three major questions pertaining to bike safety in the survey. But let's start with the highlight: The block south of the U Bridge. The current plan would maintain the existing skinny, paint-only bike lanes, and we have written repeatedly arguing that the project needs to add more protection. So it is very exciting to see Option 2, which widens the bike lane and adds some buffer space. This would be a huge improvement over the previous plan, though it would be best if there were some protection to prevent people from parking in the bike lane.

37822f83-90a2-426c-bd8e-2734dcd7c583-575The survey also presents four options for the intersection at 11th Ave NE and NE 43rd Street. At this point, the bike lane had been planned to switch from the right side of the one-way northbound street to the left side, though that decision was made when the RapidRide line was going to run all the way Roosevelt Station or even Northgate Station as was the original plan. The idea was to reduce conflicts with the RapidRide bus stops and the bike lane.

However, the bus line now ends at NE 43rd street, which calls into question whether the bike lane should switch sides at all. Unfortunately, that is not one of the options presented. If nothing else, this intersection change requires the city to also have a full 11th/12th Ave NE bike lane ready to build at the same time that will need to reach NE 75th Street, where the bike route shifts to two-way on Roosevelt. If the left side bike lane doesn't reach 75th, then there will need to be another transition somewhere along the way, which would be absurd.

But if the bike lane will be constructed on the left side all the way to NE 75th, then the lane will need to change sides. In that case, either option 4 or a mix of options 3 and 4 seem the best. If someone biking uphill arrives when general traffic has a green light, there will be a huge incentive for them to not stop, at least not until they get across the intersection. And unlike Option 1, which provides essentially no guidance on what to do, Option 4 provides a clear space to wait for the light to change. Option 3 will likely happen whether there is space for it or not as people take advantage of the red light to cross to the correct side of the street. Option 3 also helps create space for people who take advantage of a break in traffic to merge left early.

dfc523ea-5809-46c7-864b-1039e773a7ed-539Another tricky intersection is the flux capacitor intersection where Fairview Ave N meets Eastlake Ave E. Options 2 and 3 are concerning mostly because the route is very confusing and inconvenient for people continuing straight on southbound Eastlake, which is a significant number of people. Option 1 allows the most straight-forward route option, though it relies on a new traffic signal, so signal timing will be important in order for it to work well. Option 4 is the most creative, though the crosswalks are probably the worst. An option that included the crosswalk in Options 1-3 in addition to Option 4 might be the best. I'm also a bit surprised that there is no option that includes a northbound bus-only lane on Fairview, which would allow them to use a bus jump signal and avoid traffic backups. That's the primary benefit of Option 3, which is the worst of them all.

1fe2387c-58c5-424c-af15-2158ed617480-575And finally, the survey asks for thoughts on the type of bike lane barrier that should be used. Honestly, I don't understand why they are even asking this. This is a major, high-budget roadway rebuild, of course they should use permanent materials like concrete. Paint and post bike lanes are temporary materials, making them inappropriate for a high-budget rebuild project. Regular people are not going to care about whether the curbs are cast-in-place or precast or need to be installed with a forklift, they just want it to be durable and safe. The city should be building whatever level of protection is needed to maintain safety and prevent people from parking in the bike lane. It's more of an engineering question than a public opinion question. The public should be asked things like, Would you prefer flower planters or space for murals? The public are not experts on what kinds of curbs are best at stopping cars. Of the options, I suggest concrete curb since it is the most purposeful and permanent option, though I have no idea if the entire length needs a curb like that.

UPDATE: Cascade Bicycle Club sent out the following action alert:

The Seattle Dept. of Transportation is hosting two virtual community design sessions this Wednesday, Sept 14th at 12-1:30pm or 6-7:30pm (meeting registration links here). There will be a presentation and discussion of several elements of the bike lane that will be built along Eastlake. There are two items in particular that SDOT needs to hear from us:

1. The final blocks of Eastlake just south of the University Bridge still need full protection. Originally designed as paint-only, there is now the option to add space for a buffer. This is progress, but SDOT needs to hear that this area needs full barrier protection to create a safe space for biking.
2. Concrete barriers for bike lane protection along the rest of the route. There are four options in total: Plastic posts are a start, but SDOT needs to hear that concrete barriers help people of all ages and abilities stay safe while biking.

External Content
Source RSS or Atom Feed
Feed Location http://seattlebikeblog.com/feed/
Feed Title
Feed Link http://seattlebikeblog.com/
Reply 0 comments