This issue has been closed. If the problem persists, please re-open this issue and give us more detailed information on how to identify the location of the problem - then we will get right on it. Thanks a lot for reporting!

Very disappointed that this issue was closed without resolution. This Service Request had both a picture and an exact map location identified (Did anyone click on "Show On Map"?). This huge mess is still at location identified and has been for OVER TWO MONTHS. I had attached another picture taken today from Oberlin overpass on Wade Avenue, looking West to the ramp with the trash. Additionally, you can use map locators to find 2300 Wade Avenue at Pecora Lane

Thank you for contacting the City of Raleigh. Your service request ID is #594228. We will be posting additional updates about your request as we have them.

Still there today. I can’t believe how long this huge eyesore along a major artery had been allowed to sit there.

This issue has been closed. If the problem persists, please re-open this issue and give us more detailed information on how to identify the location of the problem - then we will get right on it. Thanks a lot for reporting!

OK, WE'LL CONTINUE TO PLAY THIS GAME! The items have NOT been picked up at 2300 Wade Avenue at Pecora Lane ramp. In fact, TODAY, there has been additional containers of trash dumped on West-bound Wade Ave. under the Oberlin overpass...from the exit ramp to the entrance ramp. Large plastic containers and boxes, plus additional trash. Apparently this location is now free from trash collection, and people know it!

Thank you for contacting the City of Raleigh. Your service request ID is #651208. We will be posting additional updates about your request as we have them.

City of Raleigh Solid Waste Services responded on Jan. 27th, saying collection would be done in two business days. It has now been another two weeks and nothing has been done. This trash has now been along Wade Avenue ALMOST FOUR MONTHS.

This issue has been closed. If the problem persists, please re-open this issue and give us more detailed information on how to identify the location of the problem - then we will get right on it. Thanks a lot for reporting!