The Portland Bureau of Transportation is making updates to SE Sandy Blvd between Burnside and Alder. Sandy is being repaved, so the city is grabbing the opportunity to tweak the striping and add other features they hope will make the street safer.
This half-mile section of Sandy is a key connection between the Lloyd (via 12th Avenue) and the central eastside (where it turns into 7th Avenue). However, despite its value in our network, this section of Sandy is currently striped as a standard, unprotected bike lane. We need better facilities here because it’s on a hill (down going south, up going north) and because there are several tricky crossings. In particular, the crossing of the Ankeny neighborhood greenway has been a stressful spot for years. The large intersection of SE Washington and 7th is also a sketchy spot that isolates bicycle riders in a wide expanse of pavement with threats from all directions.
PBOT’s fixes will include a lot more green coloring to add conspicuity to the bikeway, more buffers to increase the separation between modes, and plastic delineator wands that will act as low-budget median islands and effectively reduce the width of some of the intersections (second to last image below). In addition, to improve the notorious Ankeny crossing, PBOT says they plan to pull back auto parking, “to daylight the pedestrian crossing.” A new bike corral is also slated to be installed.
The new striping will connect in the southbound direction to the existing green-colored bike lane on 7th Ave as it approaches Morrison.
Advertisement
Here are the more of the project drawings supplied by PBOT (from north to south):
This project will also include a new signal at the tricky Ankeny/11th/Sandy intersection. Funding for the signal comes from PBOT’s federally-funded Central Eastside Access and Circulation Enhancement Project which we covered back in February 2017.
UPDATE: Friend of the blog John L shared this hair-raising video of this exact stretch of Sandy in a Facebook post last month:
— Jonathan Maus: (503) 706-8804, @jonathan_maus on Twitter and jonathan@bikeportland.org
Never miss a story. Sign-up for the daily BP Headlines email.
BikePortland needs your support.
Thanks for reading.
BikePortland has served this community with independent community journalism since 2005. We rely on subscriptions from readers like you to survive. Your financial support is vital in keeping this valuable resource alive and well.
Please subscribe today to strengthen and expand our work.
Not good enough. NE 11th north of this intersection needs to be turned into a dead-end street. Ankeny east/west should be bike-only and dead-end for drivers. Then you can add proper crossings for cyclists and pedestrians.
I think they should divert southbound travel on 2th on to Couch/11th, and make Sandy one way NE between 11th and 12th.
“NE 11th north of this intersection needs to be turned into a dead-end street. ”
Adding congestion to traffic will only make things worse. Especially at this particular intersection. It will force car commuters to divert down neighborhood and greenways in order to just drive north-south across central SE.
We must design to allow traffic (particularly the imminently predictable rush hour traffic) to flow not intentionally reduce throughways.
“Not good enough.”
Absolutely nothing ever will be for many bike activists.
We need to work together with car commuters to improve the situation for everyone, and we absolutely must ditch the “bad for cars good for bikes” mentality…it’s simply counterproductive.
“We need to work together with car commuters to improve the situation for everyone, and we absolutely must ditch the ‘bad for cars good for bikes’ mentality…it’s simply counterproductive.”
Your bland assertions that we must sing kumbaya with automobilists is charming but hardly adequate. Several of us have specifically asked you in comments here to respond to critiques of your assertions, but so far you haven’t.
Burnside has 3 lanes for auto traffic. If you have ever tried to drive or bike through this interesection at rush hour, you’d know how disfunctional it is. Both cyclists and drivers get delayed here because there are too many directions of travel. Closing 11th would improve throughput.
“Closing 11th would improve throughput.”
No, routing cyclists somewhere safer would, however.
You admit that motor vehicles are dangerous and you advocate for more danger by telling the victims to get out of the way.
This is bully mentality.
It’s obvious what you are trying to do. I will ignore all future comments you make here.
“We must design to allow traffic … to flow”
No. That’s incorrect.
We must design to allow traffic to be safe. Then if possible we can make it more efficient as long as that doesn’t make it less safe.
Victims don’t care that their assailants are in a hurry.
This is as good a time as any to point out the different ways modes scale. One car doesn’t endanger the rest of society or a street that much. But a thousand cars is an entirely different matter. The speed, risk, emergent dangers all increase nonlinearly.
But with human powered transit it works very differently. One person walking or a thousand? A bike or a thousand? I can’t think of a study that suggests much less finds a nonlinear increase in risk from scaling human transport up.
Flow, so understood, is or could be a goal of human transport. I can’t think of any reason not to install enough turnstiles at the entrances to subway stations that maximize throughput of humans. But when you substitute cars for humans, everything changes. Flow as a goal comes with risks, dangers, tradeoffs, the costs of which someone will bear.
I can’t quite tell from the drawings but it looks like they’re not going to put in a physical barrier just south of Burnside. It’s rare that I don’t see a car encroaching on the bike lane here. I’ve reported this problem to PBOT numerous times.
Other than right hooks at Stark, you could see and react to everything from a mile away at those vast intersections.
My girlfriend was nervous about the former design but I guess it’s my turn now.
I have trouble predicting which cars are going to completely cut into the bike lane while going southbound on 12th as it passes Burnside. I guess one could just assume that they will all do it…
yeah…crossbikes are great!
It’s just a matter of time before somebody is killed in one, and their family learns that they had no legal protection while they were in it. I know, you’re not concerned about the liability issues after the fact, but some people are.
IMO, excessive concern over being killed and attendant legal liability is a form of fearmongering.
The way I’ve seen crossbikes implemented in Portland implies some sort of right of way over cross traffic, when there is none. One in particular that I’m familiar with is where Johnson crosses 14th next to REI. I have on more than one occasion seen someone on a bike roll through the stop sign when they cross 14th, without accounting for the actual right of way of cross traffic.
“The way I’ve seen crossbikes implemented in Portland implies some sort of right of way over cross traffic, when there is none.”
Yes, that’s a major problem with cross-bikes now since they look just like a bike lane continuation. But people are treating them like crosswalks thinking that it gives them the right of way when it doesn’t because they have no legal meaning.
Now we have the bike lane dashed green through the intersection break and that is actually a legally protected space.
We’re asking drivers to think more than they’re capable of.
I guess you missed the post below where a judge ruled (for the 2nd time) that bike lanes do not continue through an intersection and are, therefore, not legally protected spaces.
It’s bizarre how upset “experienced” people are about crossbikes and how how supportive most of these same people are of these nearly identical “continuation of a bike lane”.
Looks like a legally meaningless crossbike but is actually a legally defined bike lane.
Not sure why they expect drivers to be able to tell the difference.
Hawthorne is next?
Or maybe 82nd?
😉
Hawthorne seems to be evolving on it’s own. Thankfully. I am seeing more and more people reclaiming the right lane to ride side by side and chat, as well as e-scoot. Drivers are then channeled into the left lane, and from what I have observed have been doing so without being complete jerks about it. The lower speed limits were a good first step. I hope it continues. It’s a perfect street to reduce to two auto lanes, at the very least.
“PBOT says they plan to pull back auto parking”
Which they should have been doing the entire time because there are laws against parking near an intersection that the city won’t enforce.
Wondering why nobody has implicated them in a lawsuit for this lack of enforcement.
Because there is another law that says cities are the road authority over city streets and therefore the parking setback law only applies to state-owned roadways unless the City chooses to pass a similar law. In other words, no lawsuit on this issue would be successful. If you want universal parking setbacks, you would have to convince Portland’s City Council to change the City law, not rely on a state law that doesn’t apply to City streets.
I keep hearing about this law but I can’t find it and nobody cites it. If you know what law this is then please let me know.
ORS 810:
https://www.oregonlaws.org/ors/810.010
UPDATE, 3:17 pm: We’ve also heard from a reliable PBOT source that a signal is coming to the SE Ankeny crossing! It’s funded “in the near-term”. We are working to get more details and will share them when we do.
New signal should be part of this funded project — ftp://ftp.oregonzoo.org/dist/tran/RFFA/Step%202%20project%20description%201-pagers/Portland%20-%20Central%20Eastside.pdf
You’ve covered this!
https://bikeportland.org/2017/02/03/portland-wins-10-million-in-federal-grants-for-bikingwalking-projects-216297
Sheesh. Hate when that happens. And how do you have a better memory about what I’ve posted than I do?
FINALLY FINALLY FINALLY. Hopefully 16th and Burnside crossing will get a signal next.
Interesting that they’re only putting the green pain on the north side lane where cyclists are going downhill and they assume it will be a problem with drivers not properly gauging the speeds of cyclists. However, with more e-bikes on the road I think it’s safe to assume that any given cyclist will be doing the speed limit in a bike lane no matter the terrain.
It’s also playing to the inattention of motorists, like all paint, and they may stop paying so much attention to the bike lanes without color. We need to start using colored pavement so that it lasts.
TBH, this is pretty disappointing. Central City in Motion didn’t study inner Sandy, because it was shown as a “will be built” part of the low stress network (https://www.portlandoregon.gov/transportation/article/671701). What we have here is better than before, but it’s still mostly door zone bike lanes with fresh paint, and far from an all ages and abilities design. Much like the recent repaving of SW Jefferson, I feel like we missed an opportunity to do something much better.
The reconfiguration at 7th/Washington/Sandy is great! I was riding on Sandy the other day and very happy to see it. Really simplifies a gigantic intersection.
These are all useful for able cyclists and I ride this stretch daily.
It is not for children or new cyclists at all.
We need all we can get so I am happy for anything.
Sandy is not for the 8 to 80 crowd no matter what.
Totally agree — and what annoys me is that people drive into the bike lane at *every* street that bends and where the bike lane is on the inner side of the curve. Take 21st and Tillamook. Or the 20s bikeway up the ridge at Alameda. Or really any other example. Just look a the paint disappearing and you can see where people drive! Or hang out at one of these places for, like, 5 minutes and watch the traffic. And yet, we do this over and over and over again. Why continuing an infrastructure design that’s clearly not working and that puts people who bike in danger? We need a physical separator here, so that people driving these streets notice where their lane ends. This design, in may view, accepts that people will drive into the bike lane all the time, because it is plain obvious that this is what happens (and will happen). It accepts that risk and I find that, well, not acceptable.
It’s not just on curves. The bus rides the white line the entire length of SE Flavel, eroding the paint. It’s only a bike lane when bikes are in it, the rest of the time it’s a buffer for drivers to get then away from the only thing they care about, danger from head-on collisions.
That’s a lot of paint… and I imagine I’ll feel the same way riding on the street as I did before.
The intersection of Sandy and Stark [and 8th] is very dangerous relative to turning movements, especially from Stark onto Sandy. I often use the southwest crosswalk to get across Sandy, and have to be super-diligent about westbound auto drivers turning left onto Sandy … they rarely anticipate and look for pedestrians. They end up getting themselves committed to clearing the intersection and charging toward pedestrians in the crosswalk. REALLY dangerous there, and I see no fixes here.
Kudos on the treatments at Washington [our shop is right near there]. However, even when I drive, I don’t enter Sandy from the east side of Washington … northbound traffic on 7th is coming around a blind corner and accelerating in anticipation of the hill up to Stark. T-bone potential is too great for my tastes – I’ll go down 8th to get to Morrison, thank you.
And if we’re going to consider future dreams, the final block of Sandy from Stark to Washington would make a great car-free pedestrian plaza / parklet. For those who would cry foul of busting the link from Sandy to 7th: with the recent closures of Sandy for repaving, I observed surprisingly few traffic jams – people drove like water and got around obstacles easily.
So, slow Sandy Blvd with the bodies of cyclists with green paint (but no protection in the in the intersections)….when something great could be done…. https://www.youtube.com/watch?v=gohSeOYheXg
I’d love to see the rest of Sandy get bike and slow-down modifications: perhaps turn it into on lane each way with bike lanes on either side, less parking, and a dedicated left turn lane? Given all the backups and chaos that come from drivers taking lefts, maneuvering around cyclists, and avoiding people getting out of cars, it might even make the whole boulevard smoother.
Rode this stretch this morning. I gotta say, it’s not great. I only noticed two places where there was significant improvement: the intersection with Stark SW-bound on Sandy provides great separation (although just paint) that makes right hooks feel much less likely, and the bollards on the intersection with Washington are great: although the intersection ends up feeling a bit cluttered/confusing, it’s actually having the effect of making people slow down.
The biggest question for me is: why the heck do we need auto parking on this stretch of Sandy? There’s plenty of side-street parking and almost no businesses that front Sandy itself. Losing the parking would allow plenty of room for a physically separated bike lane that doesn’t have to swerve around parked cars in the door zone.
Oh shit, I totally just assumed that was intended to be parking and the buffer was the bike lane. Actually a little more positive about the approach if they paint these & get up some no parking signs.
I rode this today. I guess it’s a small improvement. That section with the unmarked buffer mentioned in other comments is still like that. There’s a spray painted hash mark that makes it appear they’ll properly paint them, hopefully. The smooth pavement and not quite the worst possible bike lane here makes 7th look even worse than before. What a disaster of a bike lane that one is.