If you compare the first example image from the article [2] with the TomTom data [3] you can see the minor roads are present in TomTom's data, present in Google's data, but absent in the screenshot of Apple's software.
This may well indicate a problem with Apple's software.
[1] http://routes.tomtom.com [2] http://news.bbcimg.co.uk/media/images/63010000/jpg/_63010615... [3] http://routes.tomtom.com/map/Sunderland%2520Street%252C%2520...
Vector slippy maps run on bounding box searches - if I look at New York, my client says to the server "Tell me all the roads within this square" with the latitude and longitude of wherever I'm looking.
There's a lot of data - too much to store on one server - and the data doesn't all shard naturally. You can divide the world up into squares and store different squares on different servers, but long roads cross many squares, big objects like country borders belong in many squares, and when you're zoomed out your view covers many squares.
The server also has to be clever; I don't actually want every road in New York or the data would take forever to load. I only want the major roads when I'm zoomed out.
All these problems are solvable - spatial databases like PostGIS have been able to perform bounding box queries for years - but I don't know of anyone using PostGIS to support the millions of users Google have. It's well known that for regular data Google has things like BigTable, fancy NoSQL stuff that's supposed to scale well; I assume they have a geospatial database along similar lines. It's possible Apple decided to develop something similar.
My guess as to how [1] came about is that the user started zoomed out, so they only got sent major roads, then when they zoomed in some hiccup prevented loading the minor roads. This could have been as simple as the user's wifi going down, or it could that Apple's database servers are overloaded or have bugs.
[1] http://news.bbcimg.co.uk/media/images/63010000/jpg/_63010615...
No wonder it's so terrible. I have Waze but I see it as nothing more than a navigation toy. It has turn by turn but otherwise it's pretty terrible compared to google maps.
I'm downgrading back to 5.1.1.
That may sound flip, but I'm very serious. Their app commits the cardinal sin of going out of its way to distract people who are driving a ton of metal and plastic at high speeds (what the hell is a mapping application doing with "pick-ups" on the road and why the hell is it beeping at me for it?!). It's the most irresponsible app I've seen on a phone. I don't call many companies "evil" but Waze seems maliciously so.
That's more or less what they did, the maps are coming from TomTom and Waze. The main issue with the iOS 6 maps application appears not to be with the map data itself, but with the (lack of) points-of-interest and their accuracy, which cripples the search functions. A company like TomTom is mainly concerned with maps and points-of-interest for car navigation, much less with finding individual shops, landmarks or other places you find by other means than street address. Probably you won't have any problems finding gas stations, motels or roadside restaurants and such with iOS 6 maps, but good luck finding all widget shops in New York. TomTom's navigation units do have some points-of-interest outside of what you'd expect from a satnav, but it's a far, far cry from the amount of data Google has.
As it stands, I don't think there is any single party besides Google that has so much diverse geographically indexed data. There simply is no company that Apple could have bought to fill that gap. It will probably take them years to gather even half of the data Google Maps already provides.