3D Flyover

New in Maps is the 3D flyover feature which is limited in iOS 6 to devices with an A5 SoC or better. This means the iPhone 4 (GSM and CDMA), iPhone 3GS, and iPod Touch 4th Generation get excluded from the 3D buildings experience. 3D buildings already taxes the 4S considerably and drops frames from time to time, so I can see why the 4 and 3GS didn’t make the cut. 3D buildings on the iPhone 5 is completely fluid 60 fps, it seems.

On applicable devices, there’s a 3D button alongside the location indicator (which snaps to your present location or toggles compass mode) which toggles a perspective tilt. If theres a region in the current view with 3D building data and you’re at a sufficient zoom level, this changes to an icon with buildings, and tapping enables 3D building rendering. On excluded devices without the right SoC you simply don’t see this toggle at all and can’t two-finger tilt.


NYC was recently added to the iOS 6 3D Maps dataset

These buildings generated using aerial captures as I touched on earlier, and pop in with dynamic Level of Detail (LoD) both for geometry and textures. If you’ve used Google Earth on a mobile device and seen the 3D buildings Google has and the way they pop in, you’ll instantly know what I’m talking about. Generally the geometry starts very smoothed, and Apple has done a good job in iOS 6 of keeping visible switching around between levels hard to notice.

When it comes to evaluating the detail and quality of 3D buildings, the difficulty ultimately lies in selecting the right features to compare. I suspect Apple is also doing some hand massaging of building geometry in some of the more notable urban centers, something Google has told me they do as well, in addition to the user-contributed sketchup buildings. Thus, comparing notable landmarks gives an idea for the best case but not the empirically derived geometry that makes up most of the dataset. Of course in the dense urban environment reconstructing geometry and imagery requires a lot more hand massaging because of occlusions and other considerations.

Cities like Chicago are stunningly detailed.

The level of geometry detail is mostly great in the markets that I checked out. Trees and other geometry which isn’t like a building also gets represented, though some palm trees end up looking like elongated lightbulbs at times. It isn’t always perfect though.


A trouble building I found while making a cursory inspection of Los Angeles. Update: The building actually looks like this (Google Maps) as pointed out by a commenter. Still, it's possible to find buildings with strange geometry and textures applied in iOS 6.

I’ve browsed a lot of buildings which aren’t noteworthy landmarks or part of a city skyline and seen some interesting geometry and texture interpolation errors. Thankfully they’re not super common, and not even Google’s 3D database is free of them, so it’s nothing I hold against Apple’s crew.

The other question then becomes how many cities actually have 3D buildings available from Apple. To find out I manually checked the top 100 most populated cities in the USA and top 30 globally, and made a huge spreadsheet. Unfortunately as of my checking there really aren’t that many markets at all. In fact, it isn't much of a stretch to say that Apple's 3D buildings database is actually very limited at the moment, and basically only includes the USA.

Internationally, none of the top 30 cities have any 3D buildings. In fact, the only international 3D support that I’m aware of is a small region around the Sydney opera house, the Colosseum in Rome, and parts of London in the UK. I was actually surprised to see London get added into the dataset right for the iPhone 5 keynote, as I had checked and seen it was absent just a day before.

In the US, 26 or so cities have 3D building data as of this writing. For the number of the cities which do have it, it tends to be a small grid localized around the densest urban area, which isn’t surprising. Apple doesn’t seem to have prioritized its launch markets by population either, and there are some fairly notable exclusions as well.

Hopefully Apple continues building this dataset out at a good pace, because at present the dataset for 3D buildings and acceptable aerial photography is honestly disappointing compared to Google Earth's impressive dataset. That said, we've already seen Apple deploy more 3D markets between iOS 6 beta 4 and the GM. The question for the future is not only how long it will take to get adequate coverage of the top 100 markets in the USA and abroad, but beyond that point what the re-visit schedule for this dataset will be. 

Maps in iOS 6 Maps: Turn by Turn Navigation and Listings
Comments Locked

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.
  • 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).
  • 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...
  • 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.
  • 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=...
  • 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).
  • 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.
  • Stas - Sunday, September 23, 2012 - link

    Solution: give Apple more money for new device.
  • 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.
  • ciparis - Sunday, September 23, 2012 - link

    Have you personally had trouble with Maps?

Log in

Don't have an account? Sign up now