Thanks citeman, I'll explain the problem to the reporter, and offer to create a Place point for them. Still, frustrating that Waze and family can't determine the correct point, but Bing and MapQuest can.

It's like admitting your kid is dumber or uglier than your neighbors kid.

I searched in the Android app, and as I typed it provided a list of matching addresses. I could see the city names (Brea, Fullerton, Anaheim) and definitely selected the Anaheim choice, and I got the wrong location. That being said, I agree that if you type in the full complete address, ignoring the suggestions, it will provide the correct location. Since I replicated the issue while being aware of the city name, I don't consider this a pebkac issue, I believe it's a Waze logic issue.

Now, since typing in the full address, including city/st and getting the correct location, I can now begin to type and there are two Anaheim addresses, one of the matching addresses will take you to the correct location, the other won't.

Thanks citeman!

And I certainly wasn't faulting what you said, nor do I think that ANY part of what Waze does is trivial. I've done a fair bit of coding myself , and I continue to be impressed every time I dig a little deeper into how Waze does what it does.

ababcock,
I have looked at the location you mentioned and everything looks mapped correctly; I don't think their is an editor fix available.

Yes, navigating to this area can be somewhat difficult because these cities use cardinal directions with their addresses. Hence if you start in the north, on N State College Blvd, Brea, and head south, you eventually end up on S State College Blvd, Brea, then N State College Blvd in Fullerton, then S State College Blvd, Fullerton, then N State College Blvd, Anaheim, and then S State College Blvd, Anaheim, and finally N State College Blvd, Orange; all within about 15 miles. That was three cities and 7 different address configurations.

ababcock wrote:Thanks citeman, I'll explain the problem to the reporter, and offer to create a Place point for them. Still, frustrating that Waze and family can't determine the correct point, but Bing and MapQuest can.

It's like admitting your kid is dumber or uglier than your neighbors kid.

When I searched, it did take me to the correct spot; I think it is how they are searching and which results they are choosing. If you just search for the address, without a City; multiple chooses show up. Unfortunately, because the street name is so long, you cannot see the city name and the wrong result can be picked. When I searched for the full street name with City, the provided result did route correctly.

I am the first to admit that the Waze search logic is not that best. However, that is not something you or I can fix. I was indicating that the street segments and house numbers appear to be mapped correctly in Waze. Now, I did notice the the Waze HN's had not been confirmed, so I did do that and that should help.

Thanks,