page 3 of 5
The location in question does show up on iOS 6 Maps. It just doesn’t show up when you type in a non-existent address. One could argue that Google Maps is better at dealing with indeterminate data. This is academic. How many times have you entered a fictitious address in a map or navigation app? Nonetheless, one could say that iOS 6 Maps handled it better, assuming it was a mistake and that the user meant an address that does exist, which could be mistaken for E 15th Street. When you input “315 e 15th street ny” in iOS 6 Maps, it finds 315 Marlborough Road, which, as you can see, could be mistaken for 315 E 15th Street — an address which does not exist.
Since Marlborough Road is next to 16th street, and there is a 315 Marlborough Road, Apple’s logic assumes you made a mistake. There could be a fanboy flame war as to which is better. The two apps just handle indeterminate data differently. Google Maps creates its own 315 E 15th Street, which isn’t an address, and labels it “approximate”. iOS 6 Maps assumes it is a mistake, and thinks you mean something else. It’s a very Apple way of dealing with indeterminate data. This Apple way of doing things had me turning off the auto-correction on my iPhone!
It is noteworthy to mention, when you type a search query into Google that it “thinks” is a mistake, it will ask you “did you mean so-and-so?”. For some reason, with Google Maps, they departed from this logic. If the address does not exist, they will assume you meant an address in between existing addresses.
Another blogosphere lie is that iOS never had turn-by-turn navigation. While it is true that iOS Maps and Google Maps (for iOS) did not have turn-by-turn navigation, myriad apps offered this feature. MapQuest for iOS had turn-by-turn nav with spoken directions for quite some time. I used that. Now I use iOS 6 Maps.