No, I'm quite sure that the issue is that geocoding search fails and Maps has to fall back to a local search.
It is probably bad UX to not make it clear that this is what's happening. But it would be much worse to fall back to a local business search, drop a pin on the result, and have the user think that it was an actual geocoder result.
Intersection searches are rare, and there's a limit to how large a set of queries you can have in a "the results of these searches can never change" golden set. Again, these kinds of things have always happened with map data, it's not some kind of new phenomenon. I'd bet there's no less QA going on than during the times when you thought the quality was good.
Comments
No, I'm quite sure that the issue is that geocoding search fails and Maps has to fall back to a local search.
It is probably bad UX to not make it clear that this is what's happening. But it would be much worse to fall back to a local business search, drop a pin on the result, and have the user think that it was an actual geocoder result.
Intersection searches are rare, and there's a limit to how large a set of queries you can have in a "the results of these searches can never change" golden set. Again, these kinds of things have always happened with map data, it's not some kind of new phenomenon. I'd bet there's no less QA going on than during the times when you thought the quality was good.
Intersection searches are rare
No! Intersection searches are the norm, at least in New York City. And the intersection I listed is one block from the Empire State Building.
They may not be doing less QA. Just a crappier job.