Okay... this is something different than my scenario in Baton Rouge. There, it was simply bad data from Google, verifiable on Google, and fixed using Google.
This is an example of the second thing CBenson said, yeah. Look at the westernmost segment of SW Barnes Rd in Portland
, open up the House Numbers. The next segment to the west is in West Haven-Sylvan, so Waze assumes that any number higher than 6600 or so in Portland
is crammed into the end of that segment.
You might be able to solve it by adding "SW Barnes Rd" in "Portland" as an alt name, but really what needs to happen is the search engine needs to be tweaked. Waze can't cram dozens of blocks of house numbers into ten feet of road just because a user's search city doesn't match up correctly. If SW Barnes only goes to 6700 in Portland and there's a 9555 in a neighboring city, search needs to be more forgiving and look at the neighboring city.edit
There's a marked difference in the search between the production and beta editors, btw. Beta is more willing to use Waze house numbers -- try 7155 Florida Blvd in Baton Rouge -- but production is not unwilling -- see the same bad result for "9555 sw barnes rd, portland or". Also, try searching "portland or" in either -- production gives you downtown, like Google might, while beta gives you what Waze considers the geographical center of Portland, I guess. Try the same with "new orleans la" -- production brings you downtown, beta brings you way out to New Orleans East, because most of the population of New Orleans is concentrated in the western part of the city.
Searching just "9555 sw barnes rd" in production gives a few different results, like you said -- the one in Beaverton always shows up and always gives the right location.
If the map is somewhere to the east of the correct location when you search, the result "9555 SW Barnes Rd, Portland, OR" will also show up in both editors, it seems. This gives the same incorrect location as you linked.
If the map is somewhere to the west of the correct location when you search, the result "9555 SW Barnes Rd, West Haven-Sylvan, OR" will also show up in both editors. This gives a location which is also incorrect, but closer to the right one, on the highest-numbered segment of SW Barnes marked as being in West Haven-Sylvan
. It's doing the same thing as before, but since West Haven-Sylvan is a lot closer, it's not as
Now here's the difference: if the map is somewhere to the west of the correct location when you search, only in the production editor
, an additional result is shown: "9555 Southwest Barnes Road, Portland, OR 97225". This is clearly from Google with its zip code and spelled out words and such -- and it brings you to the correct location.
I don't know what direction this is moving in, but Waze needs to change its game a little bit here. I can't move my client to Portland, so I can't tell what search would give me if I just searched "9555 sw barnes rd", but searching "9555 sw barnes rd, portland or" gives me the wrong location just like both editors do. City lines are not so hard and fast with street addresses.