Rasmussen backs away from plan to delay Northgate bike/walk bridge funds

This map by Cascade shows the dramatic increase in walk/bike access if there were a bridge

This map by Cascade shows the dramatic increase in walk/bike access if there were a bridge

The Northgate walking and biking bridge may no longer be in danger of delays, according to Councilmember and Transportation Committee Chair Tom Rasmussen.

We have reported previously on a still-underfunded plan by the city and Sound Transit to build a walking and biking bridge across I-5 near the future Northgate Station. The bridge — which would dramatically increase the number on homes and destinations within easy walking or biking distance of the station — has strong Council support, and the Mayor’s proposed budget includes funding to begin early design work.

Sounds secure, right? But a proposal briefly under debate by the Council would have pushed $500,000 in funding for bridge planning back from the 2014 budget to the 2015 proposed budget. The $500,000 freed up in the 2014 budget would instead have been directed to the Fauntleroy Green Boulevard project.

The Council’s original proposal document said the $500,000 for Northgate is not necessary in 2014 and can be pushed back to 2015. However, following reporting in the Stranger, Feet First sounded the alarm, saying they were concerned the delay could jeopardize the bridge’s chances of winning grants needed to fill the budget hole in time for it to move forward.

Now, West Seattle Blog reports that Rasmussen is backing off plans to move the Northgate Bridge money, but at the cost of reducing the Fauntleroy Green Boulevard project budget to $1.3 million. Planning for that project is expected to cost $1.8 million, and the proposed budget note cites an intention to fill the hole either during mid-year supplemental budget or in a future year’s budget.

Funding for Fauntleroy would also come at the expense of reducing the sidewalks budget. The updated proposal notes that the city for some reason can’t use that much sidewalk money in 2014.

Early plans for the Fauntleroy Green Boulevard (does not include bike lanes)

The Fauntleroy project has been in the works for a long time. Early designs did not include bike lanes, but planners have expressed interest in building protected bike lanes as part of the final design. This will happen especially if the need for protected bike lanes is included in the final version of the Bike Master Plan (they were included in the latest draft of the BMP).

It’s great that the Northgate Bridge funding has been preserved, but it’s frustrating that we have to choose between worthy projects. How amazing would it be if Mayor-Elect Murray secures a sustainable and significant funding source for biking, walking and transit projects? That way, we won’t have to choose between great neighborhood projects, we can just build them all.

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

2 Responses to Rasmussen backs away from plan to delay Northgate bike/walk bridge funds

  1. Al Dimond says:

    It would be interesting to see what parts of the “Green Boulevard” have to be cut if it loses a half-mil in funding. The big parts of the plan appear to involve adding a couple traffic signals and squaring off the Fauntleroy/Alaska intersection, which may be even more important than bike lanes (best case medium-term scenario for the corridor being something like LCW around 125th, though some parts of that seem like a stretch). Hopefully they’ll also fix sensor loops at the intersections — last couple times I was there the one on NB 35th at Fauntleroy didn’t pick my bike.

    • Karl says:

      I believe, if you contact the city, they will rectify traffic sensors that aren’t picking up bicycles. No need to wait for a hoped for redesign of the area!

Add Comment Register

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>