Adding driveway to fix map error?

Hi guys - I have a little problem. My parent’s address is pretty far from the road, we have a long driveway. Whenever I type their address into Waze, it tells me to go to a street behind their house, where there isn’t a driveway to their house. You would have to walk through someone else’s yard, and around two fences to make it in. When I go into map editor though, the house is set to the correct street. Should I create a private road/driveway to correspond with their driveway so that this error doesn’t keep happening?

Thanks for any help you can give. It’s not a problem for me, but anyone else who uses Waze to get to their house calls me when they can’t find it.

I guess I should add after learning a bit more of the vocabulary regarding this matter - the stop point is in the correct place on the map editor. Even so, when actually navigating to the address in the app, it leads you to the wrong stop point, which is frustrating.

The address is 1733 Supplee Rd, Lansdale - if you search those directions from anywhere, it will take you to Patterson Drive, which is not the entrance to the property.

Couple of suggestions…

  • Take a look at Item # 27 of the Waze FAQ
  • Don’t use a Recent or Favorite Place when going there, do a NEW search. The Recent & Favorite Places in your app only store the GPS coordinates of the initial lookup, they do not perform a new search when selected.
  • Don’t accept the auto-complete suggestions. Type in the entire address yourself and hit the magnifying glass on your keyboard. Make sure you are looking at the Waze tab for the results.
  • Give the house number & stop point a bit of a nudge (IF the address falls in the dark area, you will need a senior editor to help with this step). This will mark the number as “user adjusted” and give it more weight when searching. Then repeat steps 2 & 3 above.
  • Once you have the correct location, you can save it as a Favorite (make sure to delete the old one) or use the Recent list.

I’ve looked at the Google address - Google maps actually routes the address the correct way, and the pin is in the same spot. Waze has the pin set in the same place, but it does not route to the correct street. I’ve tried a new lookup, and even used directions in the “live map” on the computer - same results. I’ve moved the house number / stop point two or three times now, and still haven’t been able to figure it out - though I have put in a “map problem” waypoint on the address to try and rectify the situation. I figure there is something that I’m not seeing that is causing the problem.

Google and Waze act differently when dealing with end destinations, even when they’re using the same address pins. Waze, when using a google address, will route you as close as possible to the actual pin. That’s why 1733 Supplee Rd takes you to a stop point on Patterson Dr while 1731 Supplee Rd will take you to a stop point on Supplee. The pin for 1733 is just physically closer to Patterson than Supplee.

I would follow AndysPoms’s recommended steps. Additionally, you could also move the address pin in Google Maps just a tad closer to Supplee Rd.Either way, I don’t think adding a private road/driveway would be appropriate in this situation, based on the driveway wiki

Wow! No reviewers needed on your google pin move.
And looks like the Waze HN is active – the stop point is now at the street on Supplee rd. I can’t see the details because I can’t edit in Lansdale.

I think that solved the problem. Everybody just needs to remove the address from their favorites/recents and start a new search.

https://www.waze.com/livemap?lon=-75.31939&lat=40.22453&zoom=15&from_lat=40.22453&from_lon=-75.31939&to_lat=40.21927&to_lon=-75.31507