Allow link RPP and Google addresses
Why we can link POI but can't link addresses?
We have a lot of problem with google addresses and have to use different hacks for it.
I suggest add function linking RPP and Google addresses like in POIs
Thank you for voting for this suggestion!
We’d like to know if this is still relevant, or if the issue was solved through auto-complete for prioritized Waze addresses.
Please let us know in the comments if it was, so we can close the suggestion.
Andrey (Sapozhnik) commented
Auto-complete was broken several years ago and doesn't work correctly at all.
Bugs in center code ware opened but still ignored.
Auto-complete doesn't solve problems of incorrect data from google
I agree it's still relevant. There are still times when the GMap address search comes up first for the user, especially when they enter full suffixes like 'street', 'drive' vs 'st', 'dr'. In many cases the GMap location is bad too. Linking the GMap address place to an RPP (where the RPP will always come up as a replacement for the matching GMap place), would be very useful.
To restate my reply:
You said: We’d like to know if this is still relevant, or if the issue was solved through auto-complete for prioritized Waze addresses.
Yes, it's still relevant.
Waze results are NOT prioritized in autocomplete. Let me know if you need specific examples.
Yes, it's still relevant. Waze is supposed to put RPPs at the top (according to the hierarchy) but it does not. Sometimes they aren't even visible at all, without very specific searches beyond the auto-complete.
Wazers start typing and choose an address and if they pick the GMaps address, it might be junk. I've had a few update requests lately for incorrect address where GMaps had duplicates and the only way to fix the issue was to call my GMaps buddy and have him fix it. The RPP never showed up (and still doesn't) in the search priority... just GMaps. Another workaround is to add a PP to the residence then link externally. What we're asking for here is to be able to link externally to the RPP, so we don't have to game the Waze system to make up for 1) search shortcomings and 2) Gmaps errors. Thank you
Greg Clopp commented
Yes! Still relevant!
Nothing has changed from my point of view, this is still relevant :)
You should correct the address on Google Maps as well.
In my city, the biggest issue is with interrupted streets and the way they are named in Google Maps. If the name is slightly different between sections, or missing a translation, it can screw up everything.
Ideally there should be a way for WME editors to send tickets to Google Maps, other than the existing methods for any Google Maps user.
Andrey (Sapozhnik) commented
We have a lot of streets which were renamed last several ears but anybody changed them in Google. We have a multilanguage search which correctly understand google but doesn't understand Waze at all. We have long names of street which don't work correctly in Waze.
Everything it can be solved by linking RPP
We can't link them because the system should be doing this by itself :) But fails as in many cases.
This would be really good!
Keith Baumgart commented
Due to how the quick results show on the client, users will frequently default to choosing those results. Oftentimes it will be a google result which may be incorrectly placed. We can account for that for place points, but when a user is searching for an address we are stuck with adding an RPP and submitting a change to Google for them to change things whenever they get around to it. This creates an issue where in the editor things are correct, but from the user perspective it will not be (even after clearing history)
Allowing this would be a great way to resolve this issue