The crosswalk at this intersection is not cycling to "pedestrian walk", despite having the buttons being pressed. This started happening 3 days ago before construction started in the area. Since this is by a large complex by a busy road, I would really appreciate if you could fix this issue soon! Thanks!
Greetings! The traffic lights at the intersection of Walnut and old-37 on the north side of Bloomington seem to have a problem detecting large vehicles (I drive a Durango) on the west-bound side (east side of intersection). This problem has been ongoing since mid-summer when the first maintenance began on the traffic equipment at this intersection. The problem is most noticeable at night when no cars are in the east-bound lane to trip the light. At times I have waited up to 5 minutes and have had to just drive through the red light if no other cars come behind me or pull up on the east-bound lane to trip the light. Often I have to back up and move forwards again multiple times to trigger the light. I live near this intersection and have to drive it daily late at night so this has become a major nuisance. Thanks for your consideration of investigating this issue. Thanks, -Nathan
The red light on Old 37 isn't changing. Some cars are choosing to run the red light. This intersection is an incredibly dangerous intersection to do that. Intersection at North Walnut and Old 37.
This light is getting stuck for SEVERAL minutes every morning. This is a very popular intersection for students trying to get to North in the mornings and this morning I witnessed several of these students trying to get accross that intersection between traffic even with the light being red. It stays at red for the Old 31 traffic for so long that traffic often backs up past Marlin Hills and up the very slick and dangerous hill east of Dunn Street. This is going to cause an accident if it isn't handled immediately. As a parent of a child trying to make this drive every morning as well as myself PLEASE get the timing corrected before someone is hurt.
Hi, I'm reporting this issue for a second time. The west-bound lane detector has been intermittently failing to detect vehicles since work started on this intersection in the summer of 2012. I think Tuesday night this week I pulled up behind a half-dozen cars and watched as each had to drive through the red light (turning left onto Walnut) because the light would not turn green for east-west traffic. The problem is intermittent. Since reporting this problem 2 weeks ago I have found that it won't detect my car if I stop at the new stop line. I have to pull ahead past it, and that still doesn't guarantee it will always work. Thanks, -Nathan
Signal at intersection of N old SR 37 and N Walnut, which is part of the Cascades bike&ped path, does not ever give a 'walk' signal, even if the button is depressed. It just says out loud 'wait' and then doesn't ever show white/walk. The city's transportation plan says peds are the highest priority out of all transportation users, so consider making it good. The light should be in pedestrian recall mode, so that there is a 'walk' every phase whether someone touches the button or not. The default 'walk' should be long enough to cross that leg of the intersection. When the button is pressed, it should be the highest signal priority and car traffic should see an instantaneous yellow light, and then a red light should be displayed in both directions (all cars stop!) for long enough to cross both crossings (~150ft, so at *least* 60 seconds). There must be a 'no turn on red' for cars northbound on Walnut turning to east, because visibility there is poor. There should be a 'no turn on red' for cars westbound on old 37.
Traffic signal is flashing red in all directions.
The lights on 3rd going over 37 and points west are not timed correctly... The traffic backup in the evenings rivals cities 5 times our size!
The green arrow for the westbound traffic on 3rd street to turn southbound onto High street is burned out.
Complaint of eastern traffic light out at the corner of W 3rd St. and SR 37. Complaint made 6/4/17 at 12 p.m.