Case Date:

4/24/2019

Hyde park neighborhood, multiple locations of damaged roads and potholes (Olcott near Moore’s pike but all along Olcott in various areas...)

Case Date:

5/5/2019

2901 Olcott. Dead branches, over sidewalk and street. Hit by trucks, knocked down by storms.

Case Date:

5/12/2019

#168401 case, not resolved. Sorry, but I was pointing to the dead limbs on the east side of Olcott, at 2901, on the pond side of the street. Those remain in place. Thanks, Jim Madison

Case Date:

7/16/2018

Multiple potholes on Mcintyre drive, near many MD offices. Also large hole on Cota drive just past hospice house.

Case Date:

6/22/2018

Not a big problem really and also I don't know which option to use for walking/biking trails so I am using the sidewalk one: a kroger shopping cart is sitting on the pedestrian/bike trail (Polly Grimshaw trail) just east of the bypass and way west of Pete Ellis Drive and parallel to the railroad track. See photo attached.

Case Date:

2/8/2024

Large pothole on Pete Ellis; watched everyone turning from 3rd street hit it while stopped at the light

Case Date:

12/10/2024

Road plate over street cut is ajar.

Case Date:

5/4/2020

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.

Case Date:

12/26/2012

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

Case Date:

1/9/2013

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.