Support this post. Easy fix that directly impacts the residents of the neighborhood.

Yes, this is very discourteous and a real hazard to many that need this curb-cut to cross this intersection safely in Boylan Heights. I hope this request will receive the City of Raleigh's immediate attention.

Additionally, I would recommend putting "no parking" signs to make left turns from Dupont onto Boylan safer. At present, cars often line the curb the the way around the corner/curve where that ramp is, making it difficult to see oncoming traffic from the left.

This crossing has been poorly maintained for over half a decade. The road markings are non-existent, the curb ramps on either side have deteriorated making them hazardous for those with accessibility needs to use, and there's no signage to inform drivers not to park there. With the success of the downtown Warehouse district, we're seeing a lot more traffic and cars looking to park in the neighborhood. The city should be maintaining street markings and providing signage to ensure crossings like this are not blocked by cars.

Please address this issue promptly as we have enjoyed significant increases in pedestrian traffic and we all need to be able to cross safely.

Please correct this issue - it is completely unacceptable.

Here is a different car parked there tonight also blocking the ramp.

Support this post. Painting the curb and providing crosswalk markings are minimal solutions to make this more visible

Agreed! please help keep our sidewalks and ramps clear.

So what is going on with this? It has been more than 2 months now, and nothing has happened.

Where is the city update on this?

We are approaching one year. What's up city of Raleigh?

We are approaching 2 years now, the city has done nothing, and the problem is only getting worse. Please fix this now!

Thank you for making us aware of this concern. We are working on installing crosswalk pavement markings and coordinating so that it is timed with wheelchair ramp updates to be ADA-compliant.

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!