>Here in Manhattan, where I live, basic search by building names is profoundly degraded in Apple's maps search. "Bloomberg" doesn't find the Bloomberg Tower; on Google Maps it's the first result. Searching for its address "731 Lexington Avenue" yields that address on Lexington Avenue in Brooklyn. It's fine to think that perhaps I wanted the address in Bed-Stuy, but even appending "NY, NY" or "Manhattan, NY" still yields the Brooklyn address. Google maps has none of these comprehension issues. I understand this is due to Apple partnering with Tom Tom, whose maps are considered to be lower in quality than other players like Nokia, but I'm not informed enough to say with certainty whether that's the case.
Noticed this today. I wanted to get the cross-street of an address on Broadway.
First, I get an address on Broadway in Bayonne. Okay, almost plausible, since I was in Hoboken. I append 'New York, NY' to the address. Now I get an address in Brooklyn. Completely ridiculous. I append 'Manhattan, NY' to the address. Still Brooklyn.
At that point I added Google Maps to my home screen. If someone posts a clear guide to jailbreaking iOS 6 and re-adding the native Google Maps app, I'll probably do it.
I've noticed this problem also. With the old Google Maps app, there were very rare and very infrequent obvious failures of searches. If I searched "741 Lexington" it'll take me to the right place in Manhattan always.
Whereas in iOS6, I swear, the search is wrong more often than it's right. It will take me across state lines, across the country, and sometimes even across the ocean for a search that Google has no problems comprehending.
This isn't a data issue, this is a technology issue.
http://dashes.com/anil/images/lexington-map.jpg
Source: http://dashes.com/anil/2012/09/who-benefits-from-ios6s-crapp...