Maps in iOS 6

With Apple’s iDevice lineup, vertical integration has been a constant theme. In iOS 6, this trend continues, even if the motivations are a bit more contrived than a desire to further bring more of the iOS experience under Apple’s control. The drive this time is a souring relationship between Apple and Google which has been in the making for some time now. To a broader extent, the Maps.app experience on iOS has been aging for a while with no clear party to blame. iOS 5 lacked turn by turn navigation, 3D buildings, higher resolution map tiles or vector roads, and other modernizations that have been part of the Android mapping experience for quite a while. That is, until now.

With iOS 6 Apple moves to a solution completely detached of Google, and for the most part brings functionality back up to parity with the competition. The features I touched on already are the main highlights of the new Maps.app experience, as iOS 6 now includes: turn by turn navigation with voice guidance, fully textured 3D buildings, and vector roads. Most of the things users have come to expect from Maps.app remain as well, including three separate views: standard, satellite, and hybrid. Those almost don’t need explanation: standard is the typical solid colored region mapping paradigm we’ve grown accustomed to with vector roads, and points plus regions of interest, satellite includes purely aerial or satellite imagery, and hybrid overlays vector maps and points of interest on the satellite view. Nevertheless there are some things missing from the new Maps.app which we will touch on later.

   
Left to Right: Standard, Hybrid, Satellite

The amount of complexity in moving to a different mapping data source is not something to underestimate. Over the years, Google has built out an extraordinary mapping product with the conjunction of their own street view fleet (which collects both location data, driving conditions data, and a full two pi steradian sphere of imagery), and an even larger set of data contributed by individual handsets reporting back driving conditions which is aggregated into traffic data. Google also made some acquisitions of its own back in the day to catalyze its own Google Maps experience, and at present it is the 9000 pound gorilla for maps.

Most users don’t realize this, but this traffic data is often statistically derived and crowdsourced using data from handsets in areas where in-road inductive sensors aren’t installed. The mobile space has already seen one major battle over who gets WiFi location trilateration data (Skyhook, Apple, or Google) and this traffic data often comes back with WiFi location data as well if the interface is turned on. For traffic data, Apple has begun building out its own dataset with the same approach – by crowdsourcing the velocity vector from iOS 6 devices that are in motion. If you plug your handset into a car charger and have the setting ticked under System Services, you’ll notice “Traffic” showing a purple location services icon while rolling around town. It’s obvious to me that Apple is aggressively collecting data to build its traffic database and get close to parity with Google.

  
Maps.app settings (Left) showing data from TomTom and link, (Right) Traffic data aggregation in progress while driving around (purple location services icon)

For iOS 6 maps, Apple moves to a variety of data sources beyond what’s in their in-house collection, and for the most part they’re disclosed on the acknowledgements page under settings on iOS 6. There are obviously a few different components to the whole maps product: the road data itself, aerial, satellite, and building textures; business and point of interest listings; and finally reviews. If you look at that acknowledgements page, you can back out a mapping between data sources and the components they contribute. The names have already been pretty well discussed: TomTom, Acxiom, AND, CoreLogic, DigitalGlobe, DMTI, Intermap, Urban Mapping, Waze, Yelp, Flickr, NASA, OpenStreetMap, US Census, US Geological Survey, and the US National Mapping Agency. There are 24 different sources whose data is aggregated together into iOS 6 maps, at least in my region with my acknowledgements page. Apple has also acquired Placebase, Poly9, and C3 Technologies for adding to its own in-house maps team.

The other component is the 3D polygons and textures for terrain and buildings. Terrain elevation data comes from regional government data such as USGS, but for cities and higher resolution terrain data there’s one more key player. That player is C3 Technologies, a company Apple acquired which was an offshoot of SAAB AB. The polygons and textures are generated computationally by taking many aerial photos from small aircraft with a small swath size. For Apple, there are undoubtably some buildings which have seen hand massaging of geometry and textures, it’s in the vast majority of otherwise normal buildings that we can use to gauge quality.

This is an interesting contrast to Google’s 3D dataset, which started out supporting 3D buildings with contributed 3D Sketchup models that were manually built and submitted to Google Earth. After that, Google began also computationally deriving buildings using the isotropic aerial view, and further hand massaging trouble buildings.

If that all sounds complicated, it’s because it is. GIS (Geographic Information Systems) are a science in and of themselves, and the complexity and investment involved with Apple completely managing their own product is nothing to be underestimated. The fact that Apple is willing to not only move to, but also maintain their own GIS should emphasize to what lengths Apple is willing to go to distance themselves from reliance on Google.

What iOS 6.0 maps does away with are the few things that Apple and its data partners can’t yet replicate: street view, and routing on public transportation. For street view, you’re basically out of luck, and users will have to use a standalone Google Maps application in the future which hopefully includes this functionality. I’m told that Apple views 3D building support as the replacement for street view's absence. For routing, Apple is going to rely on 3rd party application support to provide public transportation routing data. Searching for directions and selecting the bus or public transport icon will bring you to a routing apps screen, which will be divided into installed routing applications and suggestions from the App Store based on your region. These will then hand a token back to the Maps app relevant data.

  
Routing showing toll road notification (Left), current location popup (Right)

So enough about all this theory and what the framework is like, how does the new iOS 6 Maps application actually work? Well, evaluating that whole experience requires us to break down the features into a few different areas. 

The overall maps interface changes dramatically from iOS 5. The new iOS 6 maps interface includes a very different appearance or base layer, and again vector roads and street labels. In iOS 5, maps were previously served as texture tiles and scaled appropriately for different zoom levels. While the Google Maps for Android interface includes a combination of vector maps at some zoom levels and texture tiles at others, iOS 6 moves to an entirely vector approach for roads and graphics in the Standard map layout at every zoom level. In hybrid mode, there are vector roads drawn atop texture tiles, and in Satellite mode you get only the aerial tiles. Apple also changed around the unloaded region texture to a black grid with white lines which also scale.

 

Overall the appearance of Maps in iOS 6 is clean and unique enough to not be a direct ripoff of Google Maps. The jump to vector roads and labels comes with almost no performance hit on the iPhone 4S, where it remains smooth as butter when zooming and panning around. I played with Maps in the standard and hybrid modes on a 3GS and 4 as well, and didn’t see any unacceptable slowdowns. Performance has drastically improved since the first betas.

The quality of aerial textures at this point is perhaps my only major complaint with this new version, as the LoD can be quite low at some zoom levels, and varies wildly by region. Internationally I saw texture resolution jump around between completely unacceptable and quite good. It's obvious that Apple has prioritized home soil since in the USA things are better. Obviously the regions that have 3D building data offer very high resolution textures as a result of custom aerial capture.


This is as far as you can zoom into Seoul, South Korea in Hybrid or Satellite mode, due to low resolution aerial texture assets at present.

There’s no option to include or exclude point of interest labels, instead they appear at appropriate zoom levels automatically in the standard view. About the only option besides changing map modes under the in-app settings fold is inclusion of traffic notes on roads, and an option to print.


New iOS 6 map assets working in Tweetbot for iPhone

From a developer perspective, I'm told and have read that that the switch to Apple-supplied maps is transparent. All the same APIs are implemented with the new maps as in the past, including pins, overlays, the three already mentioned views (standard, satellite, and hybrid), traffic, and points of interest. The apps that I’ve played with which use the maps API work flawlessly so far on iOS 6.

 

 
Introduction and Overview Maps: 3D Flyover
POST A COMMENT

105 Comments

View All Comments

  • crankerchick - Thursday, September 20, 2012 - link

    The overwhelming theme I keep seeing as I read the various iOS 6 reviews is a tendency to make excuses for Apple. This article and Rene Ritchie's both say things to the nature of "It took a lot for Apple to do [x] so that is why this feature was [y]."

    I can't help but point out that when it comes to Android, reviewers are a lot quicker to point out something that sucks and offer no excuse for why it's excusable, yet when it comes to Apple releasing another boring update to iOS, with the exception of Maps, all is more or less excused because, "Maps took a lot of work and time."

    When I'm on Android-centric site, I get excuses for why Android is still the best. On an Apple-centric site, I get excuses for why Apple is the best. On AnandTech, I expect (and usually receive) more unbiased opinions. In this case, I don't get the bipartisan vibe though. It reaks of excuses. Just my opinion.
    Reply
  • UsernameAlreadyExists - Thursday, September 20, 2012 - link

    This is not the only article I've had this problem with. I had the same feeling while reading the article about the data&voice support. The worst thing is that I've used to rely on Anandtech being rather objective and declaring things as they are. I just hope that they won't invent a completely new camera into iPhone 5 when they review it like SlashGear did (unlike Engadget and Digital Photography Review). Reply
  • mrandross - Thursday, September 20, 2012 - link

    Does anyone know how they changed the wifi signal to display in dBs?
    They're not jailbroken with SBsettings on iOS6...
    Reply
  • yticolev - Saturday, September 22, 2012 - link

    I'd like to know that too, especially if it represents the cell tower data signal and not just wifi. I love having my iPhone voice bars represented in dB and would like the same for data as I do use data more often than voice. Reply
  • mrandross - Saturday, September 22, 2012 - link

    I found a couple different ways. If you had it previously from a jailreak and restored from that backup, then it'll appear again.
    If you don't have that available there's a plist edit
    http://idevicecentral.com/viewtopic.php?f=8&p=...
    Reply
  • yticolev - Saturday, September 22, 2012 - link

    Thanks! I saved the page for future use.

    I've never done a jailbreak. I used this method to hack the bars into dB:

    FieldTest dial *3001#12345#* - you can then keep numerics instead of bars in the top left by force quitting FieldTest after launching it (hold down power/lock until power off appears, then hold the home button).
    Reply
  • IndyJaws - Thursday, September 20, 2012 - link

    Perhaps I overlooked it at the iOS 6 announcement, but I'll admit to being disappointed for the lack of two main features for iPhone 4 (not 4S) owners - turn by turn navigation and panorama photos. I understand the graphical horsepower needed for 3D flyby, but sad that Apple chose to leave those of us out for the other two features, especially when there are a plethora of apps that do provide those abilities. Yes, I realize I can use them instead (in fact, must), but would prefer OS integration for convenience. Brian (or Saumitra) mentioned that there might be additional horsepower needed for the panorama feature, but there's nothing special about it that makes me think it's just a way to Apple to prod users to the latest phone. Reply
  • Stas - Sunday, September 23, 2012 - link

    Solution: give Apple more money for new device. Reply
  • Sind - Thursday, September 20, 2012 - link

    iOS 6 maps are terrible period. I'm starting to believe the hype that AnandTech is putting an Apple spin on things instead of one that is aimed for the consumer. Terrible biased review of a bad product that lowers user experience. What happened to "it just work's"? Don't release something until it is ready. Apple has put their corporate intentions ahead of the user experience and that is wrong, and Anand's failure to mention that is damning. Reply
  • ciparis - Sunday, September 23, 2012 - link

    Have you personally had trouble with Maps? Reply

Log in

Don't have an account? Sign up now