Sign is now in a new location . Thank you! 😊

There are more problems with this installation the City could work on:
1) There are no 25mph warning signs as required by the NTMP.
2) The chevrons (paint on faces of humps) are incomplete, making sighting the humps after dark problematic.
3) The hump immediately west of Pamlico was to be removed at the same time as these new ones were installed. This was as a result of a unanimous City Council resolution some months ago. Indeed, the hump is marked "REM". Since I assume this stands for remove, not rapid eye movement, I suggest it be done, even though the supposed cost savings of doing it when the new ones were installed nolonger exists.

Amen! Neal is 100% correct!
Also the "brilliant" city planners have struck again. After almost destroying Currituck, they have moved on to Lassiter Mill near North Hills Mall - 4 lanes w a turning lane went to 2 lanes with a WIDE useless center lane. No longer a right turn lane to Currituck. In a heavy traffic area 4 lanes are always better than 2!!!???

When is the Raleigh Council, Planning Committee going to meet again?? The revised/corrected NTMP needs to be approved! NO further traffic calming should be done until there is a new NTMP!

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!

If there is any problem identifying the location of the problem, then someone is unable to read! Our erstwhile Traffic Calming Coordinator needs to get out and look at Northbrook from Six Forks going West, and then do something constructive for a change.

Thank you for contacting the city of Raleigh about this SeeClickFix request. Your request ID is 283445. We will be posting additional updates about your request as we have them.

Good job! Better late than never. The installation is now complete, albeit with the usual lumpy, random profiles on the new humps.

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!