Hi all,
I’ve been dealing with a few URs recently where the driver is using Google places as their destination, and they are mostly reporting that they are driving to the wrong side of where they want to be. This happens even if there is a Waze place for the same thing.
I’ve attempted to move the Google Place on GMM, but they keep on rejecting the movements. I hate telling users that it’s Google Map’s fault they are being directed wrong. At the end of the day it’s the Waze app they are using, and they expect it to be right.
Has anyone got any suggestions?
Keith
I can only suggest you keep trying with GMM. My recent ones have been approved relatively quickly.
Sent from my Wileyfox Swift using Tapatalk
I don’t know if it was just coincidence but I reported some recently, and mentioned that I was a Waze editor dealing with a Waze user report and they did seem to get fixed a bit quicker.
You could also try the Help Center form for Search Issues in the App.
https://www.waze.com/forum/viewtopic.php?f=55&t=174260
I’m struggling with these too. I really don’t understand why Waze is encouraging people to report new Places, only to ignore them in the search and provide auto-complete from Google Maps 
I have just been dealing with a really good (or bad) example of this problem for the ‘Portsmouth Historic Dockyard’ that’s rather worse than just being taken to the wrong side.
Waze has it’s own Place with the navigation point correctly set at the public entrance.
The Google Map pin however, is further inside the dockyard and can therefore be reached via the private roads that form the active Naval Base, so people are being directly to enter the Naval Base via the main vehicle entrance which is over 1.5 miles away. :roll:
I’m not sure if it’s wise or not, but for the last couple of these I’ve been dealing with I’ve just directed the user to the Google Map’s place marker (by way of hyperlink) and advising them to ‘Suggest an edit’ on there, letting them know that it’s Google that’s the problem, not Waze.
Hi,
Google is a commercial organisation. Please tell me why any of us unpaid volunteers working on Waze (a google product) would willing work unpaid on google maps problems when they have both a raft of cash and offices full of paid employees?
Des. . . 
Let’s not forget that Waze is also a commercial organisation, even in the days prior to its assimilation into the Google empire (and post-assimilation they apparently have a fairly decent sized cash-raft of their own to play with now), yet that never stopped us all freely giving our time and energy to fixing the problems in their maps.
So if we’re that keen to resolve problems/improve the quality of the Waze product as a whole, then I don’t see there’s much if any difference between us spending our time tweaking the native Waze map data or tweaking the native Google map data that Waze currently also uses.
And personally, what I find rather appealing about tweaking the Google data (aside from the satisfaction you get of knowing that, in addition to helping fix a problem in Waze, you’re also helping to improve things for Google Maps users too) is that, after spending 5 minutes battling with Google Map Maker, it makes you realise just how good we’ve got it with WME…