Remember the bike lane on NW 14th Avenue we highlighted last week?
The lane had disappeared without any warning, forcing road users into stressful and dangerous situations. While they still haven’t explained why they didn’t catch the problem earlier, the Portland Bureau of Transportation told us the bike lane vanished because of a construction project on one side of the street and a new, wider sidewalk that was installed on the other side of the street. “These two things have narrowed the roadway,” PBOT’s John Brady said, “and we need to install some temporary striping to fit the new road conditions.”
Now we have the details on what that temporary striping will look like.
In a letter and email sent to nearby businesses and residents today, PBOT Capital Project Manager Scott Cohen explained the problem and showed a cross-section drawing of the “temporary operational plan” that will be in place for the next year.
Here are the elements of that plan (emphasis mine):
• Offering pedestrian and ADA access to all legs of the intersection during construction.
• Improved sidewalk corridor in a busy Central City neighborhood.
• Providing space for people bicycling on a busy corridor.
• Improving existing auto lane shift north of NW Glisan that addresses safety issues for merging vehicles.
• Improving freight turning movements and helping move vehicles through the intersection more intuitively.
Cohen says city staff will monitor traffic for the next year to determine the best way to permanently configure NW 14th after construction is completed. Hopefully by next year we’ll just keep this wide bikeway in place for good — since 14th plays a starring role in the future protected bike lane network PBOT is working on.
As for why PBOT failed to catch this before the bike lane became blocked by the sidewalk, we never got a reply when we asked about it. However, our smart commenters seem to have figured it out. Here’s the salient exchange from the comment thread of our post last week:
When the protected walkway was put in the striping was moved west, which can be seen in the first photo. When that traffic control plan was approved the person who reviewed that was likely unaware of the planned widening of the sidewalk on the east side of the street (to the same width as the block faces to the north and south). My guess is that no one realized the combined effect of these two separate projects would be to remove the bike lane, i.e. PBOT messed up here through a lack of internal coordination rather than through any kind of bad intent.
Correct. Permit jobs are reviewed independently, often by separate staff, and I can see how this got missed. Unfortunate, but these things happen.
If you have feedback about PBOT’s plans for 14th, you can reach Scott Cohen at (503) 823-5345 or via email at scott.cohen (at) portlandoregon.gov.
— Jonathan Maus: (503) 706-8804, @jonathan_maus on Twitter and email@example.com
Never miss a story. Sign-up for the daily BP Headlines email.
BikePortland needs your support.
The bike lane didn’t just ‘vanish’; someone, probably from PBOT, used a grinder to remove it, that’s quite obvious in the photo.
The re-striping probably wasn’t done by someone at PBOT, and was likely performed by a subcontractor working on behalf of the construction project going on at the west of the street. The striping was moved prior to construction of the new sidewalk, as can be seen in Google Streetview shots from September:
Bravo to PBOT staff for their overall responsiveness in recognizing this urgent safety issue and coming up with a temporary plan to accommodate bikes and peds through this corridor. Let’s hope this configuration eventually becomes permanent.
Bravo to PBOT??? Let’s back up a minute:
“As for why PBOT failed to catch this before the bike lane became blocked by the sidewalk, we never got a reply when we asked about it.”
Hardly worthy of a bravo.
This post sort of buries the lede on the real story here. This “temporary” reconfiguration is not PBOT’s endgame for 14th. If things go according to plan, there will be a protected bikeway in this stretch as part of a planned repaving project. This change is real progress.
The end result might earn a “bravo” but this is a cluster anyway you slice it.
Honestly, NW 14th is a cluster however you end up sliced.
In what world is taking an entire travel lane away from motor vehicles considered to be “minimal action”?
A world in which self-important, over-privileged, over-entitled motorists are not always first in line by caveat?
They took an entire travel lane away from cyclists.
Yeah and they could have just plopped down a Bikes on Roadway sign for the duration of the building construction and called it good.
The removal of a travel lane along this busy and dangerous corridor is a long time coming for the neighborhood and nearby businesses. PBOT quickly realized their mistake and didn’t “let a good crisis go to waste”. Instead they took advantage of the opportunity and have proposed *improving* the bike and pedestrian environment over what was there pre-construction.
It’s ok to give credit where credit is due occasionally.
I’ll give credit for the end result but this is a cluster. Let’s not whitewash it.
Sound like someone is a butt-hurt PBOT employee…just sayin’…
PBOT will get credit when credit is due, but this is not it.
Oh please, this is the same tired routine you bring to the comments of every article on this site. Nothing is ever good enough for you, apparently.
The next time you compliment PBOT on something will be the first time…just sayin’…
Their response is better than what we would see from 99% of the cities in the US. You have somewhat unrealistic expectations.
We know that we are living in a better ( and more sustainable) world when permit Snafu’s remove an entire freeway, and PBOT has to have a staffer who coordinates the occasional ( Summer Motorways) when the dusty old motorcars are unpacked from their garages and driven around in a loop of neighborhood streets where they are normally prohibited.
Thanks for flagging John.
To everyone else, if you reply to a comment with “comment of the week!” it will help me find one.
It looks like the final configuration will be like the Everett to Flanders block south of here, with on parking, 3 travel lanes and a bike lane on the right. Except, the left-most travel lane will become a turn lane, and disappear north of the intersection.
The new sidewalk on the east side appears to line up with the blocks north and south. The new sidewalk on the west side will, I expect, line up with the sidewalk on the south half of the block.
The only reason they can’t maintain 3 travel lanes now is they’re allowing the construction work to project beyond where the new curb line will be, with their protected sidewalk. Removing an auto travel lane on this block during the project seems like an improvement. Perhaps it will work for auto flow, (With the 2-1 lane transition happening in this block instead of the Glisan-to-Hoyt block), and be made permanent after the building is completed, and give a wider than usual bike lane with buffer in this block.
Agreed. The new paint on Willamette is already being worn away by folks who seem unable to keep to their lanes.
PBOT didn’t bother to install the torch-down durable paint on the repave last year of SW Beaverton-Hillsdale Highway. However, Washington County put the torch-down paint on a far less busy SW Scholls Ferry Road, meandered the bike lane paint for automobile traffic calming, and put more frequent bike lane symbols.
If executed, preferably with with bollards (at least), I am grateful for this. However, I think it’s worth noting that this situation played out for months prior during construction, and nothing was done. The bike lane disappeared into a #WorkZoneWTF before now disappearing into a sidewalk. When I contacted PBOT, I was told that a temporary fix would happen to avoid dumping people into oncoming car traffic. Nothing was done. And here we are.
I still think something like wands or a bit of barrier needs to be where the bike lane jogs left. Otherwise some drivers will inadvertently drive into the bike lane, especially in poor visibility situations or when traffic is heavy.
The freeway brings too many cars. The bikeway will need extra protection.
what will they be evaluating? LOS? I think the modal priority goes like this: Pedestrian, Bike, Vehicles, but before we change anything we need to check with the vehicles and make sure it won’t be too inconvenient
Has PBOT ever “accidentally” removed a lane of auto travel? I’d bet that there are strong internal processes to ensure that never happens, but those processes aren’t applied when bike lanes hang in the balance.
It’s notable that this fix only covers one city block- the entire length of 14th ave needs a bit of attention. It’s taken lives due to its’ design for at least 10 years, and I can state without hyperbole, every time I ride it I have to perform emergency maneuvers to keep from smashing into a rolling wall of steel and glass. I think it’s time to look at this street in a wholistic manner.
Thank you for reporting on this new and NOT improved bike lane gap along one of the few North/South corridors with a bike lane at all. I’m thankful that the section is going to be revised. I only hope that collisions and injury can be avoided between now and the implementation.
1)imagine if bike portland hadn’t been there to hold PBOT accountable. The fishwrapper was not.
2)There are three lanes going one way. There should only be 2 tops. That leaves 9 feet for people.