I agree with Julie!!! That light is ridiculous and yes, many do just run it. That is not the answer. Please fix the light!

It's been 24 days since I first wrote about this light. It still hasn't been fixed, and it's going to cause a serious accident if it's not addressed. It's more than an inconvenience, and I should have described this better the first time I wrote about this problem. Last Friday morning at 8:40 am, for example, two vehicles came from behind the line of five cars already waiting a very long time, and raced across the bridge to turn onto Riverside. The first vehicle was a long-bed pickup towing a trailer with yard equipment. He turned right onto Riverside, running the red light to do so, and just clearing the oncoming cars approaching the intersection. Right after him another car followed, just as a car turned onto the bridge from Riverside. But the first car sped up to make a left onto Riverside. There's no visibility of the cross street ( Riverside) once you're on the Riverview bridge, so both the truck and car could easily have caused an accident. These people are from my neighborhood, and like most everyone they're fed up when they approach the bridge and see an already long line of cars waiting. But charging down the wrong lane, across the bridge to run a red light, is a disaster waiting to happen. We don't all handle the frustration of sitting at this light as recklessly as these neighbors, but obviously some people will do this. I hope by writing, this issue can be taken seriously.
Isn't there a way to fix this light?

Thank you for reporting this issue. Your request has been referred to a supervisor to take appropriate action.

N. Floyd, Traffic Engineering designou esta questão a Shannon Callaway

I made some adjustments to the timing of this intersection specifically for traffic coming from the bridge. This should cut down on the wait time for a green light. I will continue to monitor this intersection for a few days before closing out this ticket.

Issue 7463311 has been marked as a duplicate of this issue.

Issue 7463311 is no longer marked as a duplicate of this issue.

This issue has been marked as a duplicate of issue 12910110.

If you are already receiving notifications regarding this issue,
you will now receive updates regarding issue 12910110.