Linked by Thom Holwerda on Thu 20th Sep 2012 19:24 UTC
Apple "The major new feature of the company's new iOS 6 mobile operating system is a new mapping module developed by Apple itself - a replacement for the Google-supplied maps that have been standard on the iPhone since it debuted in 2007. It is a change borne not of user demand, but of corporate politics: Google's Android platform is the biggest competitive threat to the iPhone, so Apple is cutting ties with Google. iPhone owners might have loved Google Maps, but Apple has no love for Google. Unfortunately, Apple's new maps are simply not as good as Google's." That's putting it mildly - my own town barely even exists on Apple's maps. It's basically a trainwreck, and according to The Verge, Apple has been working on this for the past five years. This is what happens when a company cares more about stupid grudges than its customers. Considering how much effort it has taken Google to get where it is now with maps, don't expect Apple's maps to even get near Google Maps any times soon. This isn't going to take months - this is going to take several years, if at all.
Thread beginning with comment 536005
To view parent comment, click here.
To read all comments associated with this story, please click here.
StephenBeDoper
Member since:
2005-07-06

What I don't know about the map implementation of Apple is how up to date is their data, is it a fork of OSM(if it is they can got f#$% themselves)


I seem to remember that Apple was using OSM previously in some other application (iPhoto?), and there was some controversy because the data was used without proper attribution. And in coverage of that controversy, I thought I saw it mentioned that Apple was using old OSM data specifically to get around the attribution requirement (something about the old data being covered an older license that didn't require attribution).

Sadly, I can't find the details anymore, so grains of salt & all that.

EDIT: found it:

http://www.osnews.com/thread?510047

It's speculative, but that may still turn out to be the explanation for some of the issues (using/forking old data to get license requirements).

Edited 2012-09-21 19:36 UTC

Reply Parent Score: 4