Fixed
Hedge overhanging pavement
Reported in the Trees category by Jack Reay at 18:15, Fri 12 August 2016
Sent to Hackney Council 4 minutes later. FixMyStreet ref: 877467.
The hedge in the garden of no3 Church Crescent overhangs the pavement by a considerable amount. The hedge has lots of sharp thorns, many at face level. The pavement is very narrow at this point, and is on a bus route, with car parking on the other side of the road, making this area potentially very dangerous, as pedestrians have to walk on the edge of the pavement in order to avoid the hedge.
Updates
-
Still open, via questionnaire, 18:36, Fri 9 September 2016
-
The hedge is overhanging more than ever. It is getting close to the road, making it VERY dangerous for pedestrians who have to swerve around it. The hedge has sharp thorns at face height.
Posted by Jack Reay at 18:36, Fri 9 September 2016
-
Still open, via questionnaire, 20:20, Fri 7 October 2016
-
The hedge has now been trimmed, but still overhangs the pavement by 2 feet. This is a narrow pavement on a route used by 2 buses. To pass this hedge, pedestrians have to walk extremely close to the pavement edge. In my opinion the hedge should be trimmed back so that it is level with the garden wall, which, interestingly, on the internal side, it is.
Posted by Jack Reay at 20:20, Fri 7 October 2016
-
Still open, via questionnaire, 23:24, Fri 4 November 2016
-
The hedge (obviously) continues to grow, and reduces the amount of room for pedestrians to safely walk by.
Posted by Jack Reay at 23:24, Fri 4 November 2016
-
Still open, via questionnaire, 13:36, Sat 3 December 2016
-
Someone has snapped off the most dangerous (ie face height) branches, but it still overhangs the pavement, and, as it grows, the branches get longer and lower.
Posted by Jack Reay at 13:36, Sat 3 December 2016
-
Questionnaire filled in by problem reporter; State changed to: Fixed, 15:54, Sat 31 December 2016
-
Questionnaire filled in by problem reporter
State changed to: Fixed
Posted by Jack Reay at 15:54, Sat 31 December 2016
This report is now closed to updates from the public. You can make a new report in the same location.