Why don't you use some more up-to-date FUD? Apple Maps is as accurate if not more so than Google Maps now. . . and even in September of 2012, had only a few extremely hyped issues with directions, as Apple leased it's data from Tom Tom, a well known and respected mapping source.
In fact, a side-by-side comparison of directions between Apple Maps and Google Maps in the USA at the time found the directions that often Apple had shorter and quicker response time with better routing when actual addresses were input. Where Google showed better was in mapping business locations by name where a business had to be looked up. Apple was using Yelp! data and it was frequently out-of-date or erroneously located, while Google was less frequently out-of-date but still often had closed or missing .
The other issue was in Apple's 3D view with some hilarious results where 3D roads followed the terrain or bridges swooped down into river beds. . . but Google had no better results when they introduced the feature two years later while Apple had pretty much perfected it.
Three of your link's "Six most Epic Fails," to use their headline title, refer to 3D graphics failures as the system tried to render things like bridges and buildings from 2D images. Something no other mapping software had ever been done before on a handheld, such as:
- 2. Brooklyn Bridge Plunge.
- 3. Sydney Anzac Bridge Plunge.
- 6. Cape Cod bridge detached from the road.
Apple Maps 3D View of the Brooklyn Bridge today.
I don't see any plunge, do you?
Apple Maps 3D View Cape Code Bridge today.
I don't see any road detachment, do you?
Two had to do with missed addressing having to do with out-dated data from Yelp!
- 1. 747 Rendezvous. Wrong access for Washington D. C. Dulles Airport. Road Closed due to new runway and terminal construction. Yelp not updated by the Dulles PR Department.)
- 5. Florida hospital replaced by supermarket. (Hospital torn down and replaced by a supermarket. Not updated in the Yelp Database by the hospital PR department.)
And finally,
- 4. Israel missing its capital. As Haaretz reports, Apple Maps. . . does not show Jerusalem as the capital of Israel. . . moreover, it does not affiliate Jerusalem with a country.
The Tom Tom data base from which Apple was leasing its data, is a Netherlands company. . . a country with a large Muslim population. . . a country which does not recognize Jerusalem as the capitol of Israel. They, being politically correct, like the United States, absurdly list the capitol of Israel as Tel Aviv.
As for errors in directions, Google had about the same number of mis-directed travelers as did Apple Maps. . . but Google was not directing the FUD campaign against their own product as they were against Apple Maps.
Your characterization of why Apple dropped Google Maps is wrong. Google was deliberately providing a crippled version of Google Maps without turn-by-turn for iOS devices while providing a full featured version with voice turn-by-turn for Android devices and refused to provide one for Apple—although Apple had helped them develop turn-by-turn voice for the iPhone or iPad. That was a deliberate marketing ploy by Google to make Android a better choice for Google Maps. Apple dropped them because of that choice on Google's part.
It had nothing to do with "valuable information" but rather with choices made by Google in order to push Android.