Waze ignoring its own HN, going to Google?

Map Editors Community House Numbers (Addresses)
1

Problem location:
12804 NE 118th St
Orchards WA

New subdivision went in back around 2014.

There is no “city” called Orchards here, this is unincorporated Clark County outside of Vancouver WA, but within the Orchards CDP. And, per Waze Washington rules, we treat CDPs as cities.

This HN was added at least six months ago, but without full audit trail capabilities I can’t show how long it has really been there. Very likely longer than six months.

When you search for this address in Waze locally (less than 2 miles away), with no city specified, the Waze location is nowhere to be found in the list, but the Google result comes in, landing on the closest Google Maps instance of 118th St, which is 20 blocks away to the west - and incidentally is located in “Dollars Corner”, an adjacent city/CDP.

Google search result:
https://www.google.com/maps/place/12804+NE+118th+St,+Vancouver,+WA+98662/@45.7070982,-122.5653401,17z/data=!3m1!4b1!4m5!3m4!1s0x5495b1bc8e4ea701:0xd33d12f6a2511059!8m2!3d45.7070982!4d-122.5631514

Actual location in Waze:
https://www.waze.com/editor/?env=usa&lon=-122.53938&lat=45.70739&zoom=6&segments=84301549

Can anyone tell me why Waze is ignoring a Waze-verified (manually entered) HN and going with a Google result, and what I can do about it besides telling the UR author to use CDP names that are not in common usage locally for county searches?

2

I can’t explain the response.

But have you considered adding a residential point place?

3

I could, but this is a home fronted right to the street in a fairly dense suburban development, with no access complications. I am wholly uninterested in the chore of parking vast quantities of RPPs where HNs should clearly be working. The immensity of that chore would pretty likely make me walk away from editing, and find a new hobby.

4

This is a real problem with how waze does address search.
Period.

The best fix may be to fix the google map and/or to add an RPP

There are also problems with adding RPPs in locales where the city name in google maps is different from the city name you wish to use in your RPP. In some cases, the validation checks will prevent you saving the RPP if the city name does not match the Waze city name and/or the Google city name.
In other cases, Waze will prefer the Google result if the Waze city name in The RPP does not match the Google city name at that Lat/Lon location.

in some cases, where no waze-only solution works, fixing the Google map is the best way to fix things for wazers. After all, the Google map can handle “mailing address cities” (which often do not correspond to any municipality or CDP and in fact overlap portions of several different municipalities in several different counties).