Long Driveway Makes for Inaccurate Directions

Hello, When someone is getting directions to my house, 1656 Penllyn Blue Bell Pike, Blue Bell PA (Montgomery County), it directs them to the parking lot of the office park behind my house (Either Sentry Pkwy W or Veva Blvd) instead of to the entrance of my driveway, which is on Penllyn Blue Bell Pike. I have a long driveway and my address is associated with the actual home rather than the entrance. Is there a way to fix this? Thank you.

This can be adjusted by the PA editors. I have sent them this post and should be able to get it fixed relatively quick

I think that it’s worked out, thank you so much

How do we report bugs/suggest changes to the Waze app itself (rather than map errors)? I raise this question here because this particular map report is a recurring problem that needs to be addressed in the routing algorithms. I came to this forum specifically to address this issue.

As a food delivery driver, I use Waze heavily and often report routing problems. I have repeatedly run into situations where this particular routing problem ocurrs. A house is set back on a property with a long driveway, such that it is physically closr to a street other than the one that has its address. Waze will incorrectly route drivers to the other street, where there is no access to the property in question.

I have reported routing errors such as this several times, and they have quickly been resolved. However I believe the routing algorithm in Waze should be altered to prevent this from ocurring so often. If a user requests address 123 Park St, for example, doesn’t it make sense to route the user to the closest point to the building ON PARK STREET, instead of some other road that has nothing to do with Park street, but happens to be closer to the back side of the building?

The issue is related to how the other app passes information to Waze. Most pass GPS coordinates that are to the center of the property.

If you want to make a suggestion, or vote on an existing one, you can go to Uservoice. https://waze.uservoice.com/forums/59223-waze-suggestion-box

This actually does not have as much to do with the routing algorithm as you may think. It has more to do with where the search finds the house numbers (HN). If the HN is in the Waze Map Editor (WME), then the app will generally route you to the actual street because the HN stop point is on the actual street. If the HN is not in WME, then the app will most likely use the Google location of the HN. When using the Google location, the app will generally route to the nearest segment to the Google HN pin. Adding the driveway for houses that are set way back helps with the Google issue.

The best solution is to work with the editors in WME and try and get the HNs in WME.