Using a mobile app launched last January (iPhone, Android), similar to the one used to study Swiss German dialect usage, Cambridge researchers have amassed a huge dataset of English language usage and are using it to map the decline in regional dialect words and pronunciations. [The Telegraph]
It shouldn’t surprise me that there’s a mobile version of the London A-Z Street Atlas. There are, in fact, several, the most recent of which is the Greater London A-Z Street Map, which covers some 3,743 km2 of territory and stores all its maps—the same maps you’d get in the paper edition—on the device. (Which makes it a fairly significant download: 603 MB on iOS, 382 MB on Android.) The iOS version costs £5 and is compatible with both the iPhone and iPad. The Android version is available on Google Play and costs about the same.
Researchers are mapping the shift in Swiss German dialect usage via an iOS app. The app asks users to take a 16-question survey based on maps from a language atlas that mapped Swiss German usage circa 1950. The app predicts the user’s actual home dialect location based on those maps; differences between that prediction and the user’s actual home dialect location reveal how Swiss German has changed over time. They ended up getting responses from 60,000 speakers. PLOS ONE article. [via]
The Barrington Atlas of the Greek and Roman World was a landmark in historical cartography: an atlas that pinpointed locations from classical antiquity on modern maps. The result of more than a decade’s work and $4.5 million in funding support (here’s the project website), the print version of the Barrington Atlas, which came out in 2000, was both enormous and expensive: larger than either the National Geographic or Times Comprehensive atlases,1 and priced at an eye-popping $395.
Now, as I mentioned earlier, there’s an iPad version of the Barrington Atlas, which (they say) contains the full content of the $395 print atlas and costs only $20 (iTunes link). On that basis it’s a no-brainer: $20 is better than $395. (95 percent off!) Classicists with iPads who don’t buy this app have something wrong with them. But how does it work as a map app?
At a list price of $395, the print version of the Barrington Atlas of the Greek and Roman World (Princeton University Press, 2000), was more expensive than some iPads. Which makes the forthcoming iPad version of the Atlas, described in the announcement as “complete content of the classic reference work,” a veritable bargain at only $20.
In 102 interactive color maps, this app re-creates the entire world of the Greeks and Romans from the British Isles to the Indian subcontinent and deep into North Africa. Unrivaled for range, clarity, and detail, these custom-designed maps return the modern landscape to its ancient appearance, marking ancient names and features in accordance with modern scholarship and archaeological discoveries. Geographically, the maps span the territory of more than seventy-five modern countries. Chronologically, they extend from archaic Greece to the Late Roman Empire.
It’ll be available on November 21: plenty of time for me to get a new iPad Air by then (it works on all iPads except the original).
Previously: Barrington Atlas.
Andy Drizen’s Tube Map Live (iTunes), a free iOS app (native iPhone and iPad versions) that shows the real-time positions of London Underground trains on the iconic Tube map, using official data. Hypnotic visualization, but the app essentially promotes Drizen’s £1.99/$2.99 Tube Tracker: tapping on trains or stations calls up an advertising popup. Via TUAW.
In 2007 Eddie Jabbour released the KickMap, a map of the New York subway system that tried to square the circle of various competing and controversial New York subway map designs. The KickMap later became an iOS app; I reviewed the iPad version in 2010. Now Eddie reports that he’s released a KickMap for the London Underground—not satisfied with updating Massimo Vignelli, he’s going after Harry Beck.
[W]hile the Tube Map’s updates over the decades have attempted to follow Beck’s design, a glance at the current iteration reveals that his design heirs have failed to retain his core credo of clarity and ease of use. Ongoing expansion of the Underground, the addition of the new Overground system, and essential disability access information have made most modern Tube Maps, both official and independent, overly complex and difficult to read. … [I]nstead of redesigning the entire map vocabulary as we did for KickMap NYC, we embarked on a fresh new effort to recapture Beck’s clarity and ease of use.
A regular Underground user would be able to evaluate whether the map succeeds in its goal to improve the Tube map’s clarity; I haven’t even so much as been to London, much less taken the Tube. But I’ve downloaded the app (disclosure: I received a promo code) and have played around with it a bit.
What I can say is that the map is gorgeous and scrolls fluidly (at least on an iPhone 5). In a nice touch, it adds detail like neighbourhoods and landmarks only when zoomed in, preserving a simpler, less cluttered map when zoomed out.
Those of you who’ve used the New York KickMap will find much that is familiar. While it can use your iPhone’s GPS to locate the nearest station—a nice touch on a non-geographic map—it does lack the New York app’s Directions function, which can route you between two stations on the network. Something to ask for, I think, in an update.
It costs only £0.69/$0.99 and is a universal iPhone/iPad app. iTunes link.
This is something I’ve been meaning to write for a while. I should have written it last December, during the hullaballoo over Apple’s maps, but I’ve never been one to strike when the iron is hot.
You’ll recall that there were a lot of complaints about Apple’s maps app when it launched with iOS 6, replacing the previous app that was powered by Google Maps. The map data didn’t match the user experience: it was a first-rate app that used second-rate data. Apple oversold the experience and failed to meet the high expectations of its customers. It was a problem that no other online map provider had ever had to deal with before, not least because no one had launched a new map service with the same amount of hubris, nor the same amount of scrutiny from day one.
But many of the complaints about Apple’s maps verged into hyperbole. The notion that Apple’s maps were uniquely bad compared to other online maps was frankly unfair. Because when you get right down to it, all online maps suck. They all fail in some way, somewhere, and some more than others—and if the maps you use seem fine to you, it’s because they suck somewhere else.
As announced by AllThingsD shortly before it happened, Google Maps for iPhone was released last night. If you rely on Google’s extensive local search database, Street View or transit directions, downloading this app is a no-brainer. You will say, “At last!” and go get it. Here’s the App Store link.
Some caveats: there is no native iPad version. Both Engadget and Techcrunch point out that this is a get-the-essentials-out-the-door-now maps app: certain features you’d expect from the desktop or Android version (e.g., biking, indoor, offline maps) aren’t available. While it’s vector-based, it seems to me to be a little slower and less responsive than Apple’s native app.
And its interface is quite different from the Google-based maps app we saw on the iPhone prior to iOS 6: not only does it adopt the design language of other Google iOS apps, like Google+ and the iOS 6 YouTube app (which isn’t to my taste, but Google is running with it), but it puts things in different locations: transit, traffic and satellite imagery are obtained by pulling from the right; local info and Street View are on the bottom. Obtaining the 3D map is not at all obvious: it requires a two-finger drag explained here. Which is to say that you may need to get used to the changes. If you were hoping to get the old Maps app back, that’s not happening.
Earlier this month Nokia, the parent company of Navteq, announced its cross-platform mapping service, which they’re calling Here. To that end, its free iOS app, Here Maps, appeared in the App Store this week. I’ve poked around with it a little bit today and have some thoughts.
Those seeking a true alternative to Apple’s (or Google’s) maps will probably be disappointed. It’s a perfectly serviceable portal to the Nokia’s map platform, but there’s nothing to ooh or aah over. Nokia’s maps aren’t necessarily better; as with all map platforms—Google’s, Apple’s, OpenStreetMap’s and Nokia’s—whose is better varies from place to place. For my little village, for example, Nokia’s street data is a bit better than Apple’s, and it has more POIs; on the other hand, some of Nokia’s POIs are misplaced, and Apple has better, higher-resolution imagery for my area. Again, it depends on where you are.
I’m not a fan of Here Maps’s UI: it’s rather clunky and appears to be designed to be the same across all platforms, rather than using native iOS widgetry. It seems better matched to the iPhone/iPod touch than to the iPad, where the non-native popup windows swallow too much of the screen. The map tiles are bitmapped rather than vector images, and load more slowly than I’d expect. To be sure, there is an offline mode, and a few other features I haven’t explored yet—see Cult of Mac, Macworld and TUAW for more thorough looks at this app. My first impression is kind of meh: it’s good to have multiple map apps, but this one doesn’t really stand out. But it’s free, so it can’t hurt to try it.
Details continue to emerge, as details tend to do, about how and why Apple replaced Google with its own maps in iOS 6. John Paczkowski reports that the Apple-Google maps arrangement faltered over voice-guided turn-by-turn directions, which Google Maps has had on Android for years but Apple couldn’t get from Google. John Gruber looks at the timeline of Apple’s contract with Google here and here, and has some ideas why Apple would give the boot to Google with time still on the clock.
Pogue calls Apple’s Maps app “an appalling first release. It may be the most embarrassing, least usable piece of software Apple has ever unleashed.” (I guess he never tried version 1.0 of the Podcasts app on older hardware.) In passing, however, he also mentions that Street View is coming to the mobile website in a couple of weeks. Street View is a big part of my own Google Maps usage; if it is for you as well, you’ll welcome that news. (The desktop web version requires Flash, so has not been available to mobile devices.)
The competition has been having fun at Apple’s expense, except that Motorola’s ad gave iOS a nonexistent address to get lost with.
Update: Apple CEO Tim Cook’s statement.
First, how to report a problem in iOS 6 maps: MacRumors, Macworld. Jamie Ryan reports that reported errors are being corrected quickly.
More information about Google Maps’s removal from iOS 6, and whether it will return with a Google-built app. Eric Schmidt said Monday that, contrary to rumours, Google hadn’t submitted an app yet, and things got muddled from there. The Verge and the New York Times’s Bits Blog reported last night that there was still a year left on Apple’s contract with Google, and that Google was caught flatfooted by the move and is scrambling to build its own map. They are building one, though. It’s just a matter of when we’ll see it.
One place where Apple’s maps are demonstrably better than Google’s is China, where Apple was able to draw upon maps from a Chinese company. The drawback is that the maps aren’t integrated with those in the rest of the world. Anthony Drendel, AppleInsider, Wall Street Journal.
TUAW argues that Apple dumped Google because it wasn’t allowed to do turn-by-turn navigation with Google Maps. Engadget’s Brad Hill believes that the switch was “shrewd, inevitable and an indicator that Apple understands the true battle it wages.” See also AppleInsider’s detailed multipage review.
I’ve been poking around with iOS 6 maps on both my fourth-generation iPod touch and on Jennifer’s third-generation iPad. My initial impression is that the app is fast and renders streets quickly, and turn-by-turn directions seem to be okay in practice. The satellite imagery comes from different sources than Google’s and in some areas is actually higher resolution than what Google offers. There’s a lot of missing data though: searching for local bank branches while we were in Ottawa this weekend, for example, was an exercise in futility.
More analysis from around the Intertubes:
- Ars Technica: Transit app developers see iOS 6 Maps as a chance to shine
- Counternotions: Apple Maps: The FAQ
- Forbes: Why Apple had to do maps: a mobile engagement analysis
- Jean-Louis Gassée: Apple Maps: Damned if you do, Googled if you don’t
- And some smart stuff from TeleMapics’s Mike Dobson.
The Next Web reports that Apple’s satellite imagery only shows China and Taiwan when viewed from China. TechCrunch reports that Apple is recruiting former Google Maps staff and points to weirdness that ensues when Apple Maps links are used on the desktop.
Regarding the pickle Apple has gotten itself into by providing its own maps in iOS 6, some context and analysis is provided by Gizmodo, the Guardian, Macworld and The Verge, all of which are worth reading. Cult of Mac suggests some workarounds. AllThingsD has a statement from Apple promising that it will get better, plus news that “the team assigned to the app is under lockdown right now working to fix it.” In general, everyone agrees that maps are hard to do and that Apple has a lot of work ahead of it. Dan Frommer is strangely optimistic, seeing in adversity an opportunity for Apple to prove itself. Meanwhile, 9to5Mac reports that Google does have an iOS map app that is awaiting approval from Apple. (Update: Dalrymple says nope, and he can be relied upon.)