Watch: Best Side Cycling tours the new 15th Ave NE bike lanes + What can we learn from its shortcomings?

The new and improved 15th Avenue NE bike lanes opened last month, and much of the project is excellent. But the opening celebrations have been a bit dampened due to the city’s decision to ignore people’s requests to help them cross the biggest barrier to biking on this route: Lake City Way.

I have been a bit slow to write about this project because the city has put safe streets advocates in a bit of an awkward bind here. On one hand, they did build nearly one mile of new protected bike lanes. As important as it is to watchdog transportation projects, it is also important to celebrate wins. This is a mile of bike lane that is now part of our city, and that’s great. People will be able to travel by bike more comfortably and, hopefully, more safely. The bike lanes also significantly reduced the crossing distance for people walking across this street, which is far too wide for the relatively low amount of car traffic it carries. Bike lanes are not just about biking, they are part of a complete street that is safer for all users.

It is worth celebrating every time the city makes our streets significantly safer than they were before, and most of this project does so. I feel like I need stress that there’s a full stop after this sentence, even though I know you can sense the word “but” coming soon. This street is safer, and if this project works as well as we all hope then as many as 10 people will be spared from serious traffic injuries or death every year from now on. That’s a huge and very real improvement.

But (there’s that word) the project has some major shortcomings that undercut the effectiveness of the rest of the improvements, and it’s difficult to want to heap too much praise on the city because of them. However, the problems happened during the previous administration, and I hope that SDOT and Mayor Bruce Harrell can learn from these issues and avoid them in the future.

The highest-level takeaway is that SDOT and the mayor need to listen to advocates, who were genuinely engaged in this project’s design process. Mayor Jenny Durkan chose to completely shut out and ignore community members who volunteered their time and energy to engage with this project and suggest improvements. This was a major problem with Mayor Durkan’s leadership in general, and it’s consequences show up once again in the way this project turned out.

Project shortcomings

Design plan showing four general traffic lanes with no bike lanes between 80th and Lake City Way.

The paving plan near Lake City Way.

The biggest and most obvious problem with the street’s design is that all safety improvements end one block before reaching Lake City Way, one of the most dangerous streets in Seattle. The paving project continues all the way to the busy street, but the bike lanes and their related street safety benefits end at NE 80th Street. As the new roadway approaches Lake City Way, it balloons out from two general traffic lanes to four despite the fact that traffic volumes actually drop from 10,000 vehicles per day to 8,000 according to the city’s 2020 Traffic Report (based on pre-pandemic 2019 data). Even 10,000 vehicles per day is not much at all for an arterial street, and 8,000 will easily fit in two lanes. As the new lanes are added, all safety elements disappear. It is an enormous missed opportunity to keep people safe.

But to make matters worse, people made it very clear to the project team during the design phase that this was not good enough. Two years ago, when there was definitely enough time to make changes, I summarized what I had been hearing:

This means people biking north will lose all protection from traffic at the exact moment they need it most: The business district and the very busy Lake City Way crossing. The decision to end the bike lane a block and a half early also severely limits the benefit to all Lake City residents, who will still need to bike either in mixed traffic across a state highway or on sidewalks through the businesses district, neither of which are appealing options. This is a huge missed opportunity that severely undercuts the rest of the project.

Project map showing the purple bike lane line touching Lake City Way.

The project map showing the bike lane touching Lake City Way, which is not true.

But those concerns were disregarded completely, and no changes were made to the design. They did not even bother to update the project map, which still misleadingly shows the protected bike lane extending all the way to Lake City Way. The requests were so reasonable, and had the city listened they could have greatly improved the number of residents who could now benefit from the investment. Instead, people north of Lake City Way remain just as cut off from the bike network as they were before, and that’s a shame.

Protection for the bike lanes also drops at major intersections. NE 65th Street is a particularly frustrating missed opportunity because the city built protected bike lanes on that street a few years ago, which connect to Roosevelt High School, Roosevelt Station and Ravenna Boulevard. This was an excellent location to build and test a protected intersection. Instead, people lose their protection, and there is very little help for people turning left.

I believe in a Seattle that is always looking for ways to innovate and improve, and I think that’s the kind of vision that inspires residents to put their faith in our institutions like SDOT. This project is not an example of inspiring innovation.

Another issue is the decision to use temporary materials for the bike lanes and crosswalks even when rebuilding the rest of the road. The paint-and-post parking-protected bike lane design continues to be effective, especially for quick, low-budget bike lane improvements. When adding a bike lane to a street that is not being repaved, the city can save a lot of money by using plastic posts and paint to redesign the roadway instead of more expensive and permanent materials like concrete curbs. And at least in theory, saving money on materials allows the department to create more miles of bike lanes, which is a good thing. These paint-and-post lanes can then be upgraded whenever that street is repaved, a sensible financial management strategy because rebuilding the street is the most cost-effective time to build in more sturdy and permanent bike lane and crosswalk features.

In the below screenshot from Best Side Cycling’s video, you can see a large painted hashed out area before the car parking starts. This area is supposed to both protect the bike lane and also act as protection for people using the crosswalk. But there’s nothing actually stopping someone from driving straight through it. Why did the city go with a temporary safety feature instead of a permanent one? Do we anticipate a time in the future when we will not want this crosswalk to be safe?

The obvious answer will be, “Budget!” But that answer reveals the ongoing problem within SDOT’s paving program. Treating the clean sheet of asphalt as the primary project goal and the safety elements as nice-to-haves fails to make safety the top priority as the department consistently claims it to be. Safety elements are part of SDOT’s core mission, and if there’s not enough money for the safety elements, then there’s not enough money for the paving project. Until the department and political leaders shift their thinking and goal-setting around this, we will continue to miss opportunities to make our streets safer. Everyone needs to remember that the true cost of failing to make our streets safe is too enormous to count.

The good news is that SDOT is getting a new Director and Mayor Harrell is leading a new transportation planning effort for the city. With clear leadership, SDOT is fully capable of doing better.

This entry was posted in news and tagged , , . Bookmark the permalink.

6 Responses to Watch: Best Side Cycling tours the new 15th Ave NE bike lanes + What can we learn from its shortcomings?

  1. Stephen M says:

    I know that we need to celebrate gains when they’re made. And I understand that the entire protected bike network can’t be built at once, in the blink of an eye, if you will. These things take time (and more time in Seattle than anywhere else I know of). But this abandoning folks in the middle of a route with no indication of how to safely proceed or even articulating a plan and a timeline for completion of a route is unconscionable at least and dangerously negligent at worst. This lures folks out onto bikes with the promise of a safe route only to abandon them mid-ride. In the long run this will actually serve to *discourage* the very people these “safe streets” improvements are intended to encourage to walk or cycle.

    Those of us who are intrepid riders will ride on the best options for the circumstances and adjust accordingly en route as conditions change. But if we can’t in good conscience encourage other, more inexperienced or hesitant folks to give it a try then these “incomplete streets” have very little value until they are completed and might be doing more harm than good.

  2. RossB says:

    Is that little section (between 80th and Lake City Way) really a priority? Once you get to 80th, you have several choices:

    1) Continue north on 15th up the Maple Leaf hill. This is challenging. It is a big hill, there isn’t much there, and there are no bike lanes.

    2) Turn right onto Lake City Way. Yowzer! Anyone who does that isn’t concerned about the bike lanes on 15th.

    3) Turn left on 80th and then right on Roosevelt. There are bike lanes on Roosevelt, and it is where most of the destinations are.

    4) Turn left on 80th and then right on 5th. Fifth is the easiest way to go over the hill. It too has some bike lanes and destinations (although not as much as Roosevelt).

    5) Turn left on 75th and do the same sort of thing as a way to avoid 80th (75th has some bike lanes — they aren’t great, but something).

    6) Turn right on 80th, and work your way into the neighborhood. You can also head north via 17th. You have to dogleg a bit here and there, but there is a nice crosswalk on 82nd (close to 17th). 17th on Maple Leaf cuts across the hillside. Another alternative is to use 20th.

    7) Do the same sort of thing, but turn right on 77th (avoiding the arterials).

    8) Just stop here, as you’ve reached your destination (more or less). At most you walk your bike a block or so (or ride on the sidewalk).

    It seems to me that the first two are the *least likely* things to do. In contrast, turning right or left is quite reasonable.

    I think the use case you are describing is just tiny. Even for the area the priority should be making 80th safer for bikes (so that riders can dogleg to Roosevelt and 5th) not extending the bike lane to a street very few are interested in crossing, and even fewer will ride.

    There is no question that they screwed up the map. They shouldn’t show the bike lanes going all the way to Lake City Way. But if they did build that, the vast majority of riders wouldn’t use that last little section — most would turn before then.

    Unless, of course, you plan on running bike lanes on 15th all the way to Pinehurst. That is quite reasonable, but a completely different (and bigger) project. Extending north of 80th should be considered part of that project, not this (far more important) one.

    • Frank says:

      @Ross I think getting as far as 82nd would have been nice, as that is the official cross-town greenway. From 82nd you can get safely to Wedgwood in the east or Maple Leaf / Northgate / etc. to the west. Taking 80th is not fun, even for a couple of blocks, as it is an arterial and people drive fast and there are cars always parked on the sides which leaves little room for passing.

      The new crossing at 82nd/LCW is a huge improvement, as are the other 82nd street crosswalks you mention. I’m not sure if SDOT has any plans for the intersection of 15th & 82nd, but that would be the logical place to end the bike lanes.

      • Adam says:

        I agree with Frank that getting to 82nd would be a big improvement. Riding on 80th is unpleasant. 82nd gets you access to the park and you can cross over to Roosevelt to continue north. There may be some benefit in continuing the bike lane to 88th to connect with where the greenway will start on the north end of the park.

        Ross is correct though that continuing north on 15th isn’t the best. I will almost always take Roosevelt instead. As far as the difficulty of the hill, I don’t know that going up the hill north of 80th is anymore difficult than up the portion from 65th to 80th.

      • RossB says:

        Good point. I could see it being extended to 82nd. That is probably a lot easier than adding bike lanes to 80th. My point is that the map was not well designed. Worrying about the fact that SDOT didn’t follow it misses the point. They still need to work out how to connect to the rest of the network. Either go up to 82nd, or add bike lanes on 80th.

  3. eddiew says:

    Yes, Mapleleaf has a hill. In the early 70s, I biked between Shoreline and UW via 15th Avenue NE. Metro could consider deleting Route 73; it is too close to the more frequent Route 67 on Roosevelt Way NE. SDOT could make 15th Avenue NE a bike priority street. I often used 20th Avenue NE; it is calm, has signals, and connects with the nice bridge over Ravenna Park.

Leave a Reply