You can move around with your keyboard
plus
minus
left
right
Drop pin on the map to start a new report
space
Press space again to adjust the location
space
Start new report here Reposition report here
Back to all reports

Pavement too overgrown for safety…..

Reported via desktop in the Pavements category anonymously at 10:02, Fri 22 November 2024

Sent to Bristol City Council less than a minute later. FixMyStreet ref: 6770426.

The pavement on Dingle Road between Coombe Dale and Coombe Bridge Avenue is so overgrown that you cannot safely pass someone. His is not the same issue as the Russian Vine issue on the opposite side of the road). I walk this two or three times a week with my dog. Several times we have met people coming in the other direction and someone has to step in the busy road to get past. Yesterday we met a lady with a buggy. She couldn’t obviously step in the road; I couldn’t with my dog! So I turned and walked back 30 yards to let her past. But even if you meet one person (and we meet at least one person each time) there isn’t safely room to pass. Also the traffic is relatively fast there and you have to walk close to the road due to the overgrowth which is very unpleasant. Crossing the bridge is fine as there is no growth there! In places the path is potentially at least two to three feet wider up to the fence posts. No pavement surface works required - just bushes cut back and removed (and leaves currently).

Updates

  • This issue is currently under investigation. We'll provide updates on the outcome as soon as we can.

    Posted by Bristol City Council at 07:35, Thu 28 November 2024

  • A new enquiry has been raised for this issue.

    Posted by Bristol City Council at 17:25, Wed 4 December 2024

  • This issue has been resolved. No further action is required at this time.

    State changed to: Fixed

    Posted by Bristol City Council at 13:00, Wed 11 December 2024

This report is now closed to updates from the public. You can make a new report in the same location. Please reference 6770426 in your new report if it is an update on this one.