This will be so much helpful!

Waze Team - please pay attention to this suggestion one more time!

100% still relevant

An incorrect GMaps address pin can be extremely hard to remove or move to its correct location. More often than not, when I try to correct a GMaps address, it creates a new pin for the address rather than correcting the old/bad one, assuming it isn't just rejected. Having a Waze RPP (residential place point) able to be linked to a GMaps address pin (or more than one, because addresses often have multiple formats or cities!) could let Waze editors actually fix the problem for Wazers while Google Maps is oblivious that there is a problem and yet still offering bad results on both platforms.

This is very important! We editors spend a lot of our time, trying to get Google Maps to delete an incorrect pin. They do not have editors like Waze reviewing reports and their is no way to tell Google what the error is. The problem these Google errors are causing Waze to navigate incorrectly.

This is a very much needed request!

Absolutely agree!!!

This is still, in my opinion, a valid request. There continue to be issues with search and prioritizing Waze vs Google results.

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

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.

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!

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