“Google wants to know where you go so badly that it records your movements even when you explicitly tell it not to,” the Associated Press reports. Their exclusive investigation discovered that “many Google services on Android devices and iPhones store your location data even if you’ve used a privacy setting that says it will prevent Google from doing so.” Basically, turning the “Location History” feature off doesn’t stop Google apps from recording your location at various junctures: your location data may still be found in places like “My Activity” or “Web and App Activity,” for example. Google insists its descriptions are clear; critics are calling Google’s hairsplitting disingenuous, disturbing and wrong.
Google is assigning names to neighbourhoods that, the New York Times reports, have little basis in reality—but once on Google Maps, those names swiftly come into a popular usage they never had before. The East Cut, in San Francisco, was the product of a branding agency; Fiskhorn, in Detroit, is actually a misspelling of Fishkorn, taken from a typo in the source map. (Searching for “Fishkorn” works just as well, though.) How such names end up on Google Maps, and therefore get a certain canonicity, is what’s interesting: it seems to be the result of a tech giant processing diverse data with remote fact checkers and not much in the way of local knowledge. [Boing Boing]
As of iOS 12, coming later this year, CarPlay will support third-party map applications like Google Maps and Waze, Apple announced during its WWDC keynote earlier today: AppleInsider, Engadget, The Verge. Up until now the only maps available via CarPlay were Apple’s own; drivers who would rather use something else—and I know lots of them are out there—will soon have that option.
Google unveiled its future plans for Google Maps at its I/O conference yesterday. They include an augmented reality mode that combines Google’s Street View and map data with the view through your phone’s camera and “assistive and personal” features that add some artificial intelligence to recommendations and reviews. The social and recommendation features are coming this summer; no word on when or if we’ll see the AR mode. AppleInsider, Google Blog, Engadget, The Verge.
We’re almost at the end of the week of Mario on Google Maps. Announced for March 10 (“MAR10” Day), the temporary feature changed the navigator arrow into Mario driving his cart. Announced for both Android and iOS, but for some reason it never turned up in Google Maps on either my iPhone or my iPad, so I didn’t rush to post. [Business Insider]
Public transit navigation now includes wheelchair accessible routes, as of yesterday: “this feature is rolling out in major metropolitan transit centers around the world, starting with London, New York, Tokyo, Mexico City, Boston, and Sydney. We’re looking forward to working with additional transit agencies in the coming months to bring more wheelchair accessible routes to Google Maps.”
Slashgear looks at the new Google Maps APIs for gaming, which, I guess, enable developers to build real-world games on top of Google Maps. Note that Pokémon Go is not built on Google Maps: I suspect this outcome means that Google has noticed that.
Artur Grabowski spent most of 2017 testing three mapping apps—Apple Maps, Google Maps and Waze—to see which app was the most accurate in terms of travel time to destination. His questions: which app estimated the shortest travel times, which app actually got him to his destination in the least amount of time, and how much did each app over- or underestimate travel times? In the end, based on 120 trips in the Bay Area, roughly 40 using each service, Artur found that Apple’s estimates were the most reliable (indeed, Apple underpromised and overdelivered), but while Waze promised the shortest travel times, those promises were usually overly optimistic; it was Google Maps that provided the shortest travel times.
Why does Apple underpromise and overdeliver, while Waze does the opposite? Artur suspects it’s because Waze needs to monetize its app with ads, and Apple doesn’t:
For Apple, Maps is a basic solution for its average user who wants a maps solution out of the box. Apple Maps does not directly drive ad or subscription revenue for Apple so there is less reason for Apple to incentivize iOS users to use Apple Maps over other solutions. However, Apple does care about user experience, and sandbagging trip time estimates so that users arrive at their destination on time results in a great user experience. Hence, I believe that Apple is intentionally conservative with estimated arrival times.
At the other extreme, Waze (Alphabet) makes money through ads when you use their app. What better way to get people to use your navigation app than by over-promising short trip times when no one takes the time to record data and realize that you under-deliver? If an unsuspecting user opens Apple Maps and sees a 34-minute route and compares that to 30 minutes in Waze, the deed is done. Now Waze has a life-long customer who doesn’t realize they’ve been hoodwinked and Waze can throw at them stupidly annoying ads.
Justin O’Beirne’s lengthy analyses of Google Maps and Apple Maps are always worth reading,1 and his latest is no exception. Looking at the rapid proliferation of buildings, areas of interest and other examples of Google’s Ground Truthing program, Justin discovers that Google’s buildings data are a product of its satellite imagery, its places of interest are a product of its Street View data, and its areas of interest (the orange-shaded areas that indicate business districts) are the result of combining those stores of data.
…so this makes AOIs a byproduct of byproducts[.]
This is bonkers, isn’t it?
Google is creating data out of data.
This is slightly more than Google’s competitors are able to match. As always, Justin’s analysis is worth reading in full, and comes complete with before/after animations that make his point visually clear.
What happens when a Google Street View car meets its Bing equivalent? The Verge explains: “As it turns out, when two Google Street View and Bing cars pass each other, only one (in this case Google) will admit to it publicly. Like an embarrassed or jilted lover, Microsoft masks the memory of the Google encounter with a giant white rectangle in Bing maps. […] Google however, proudly shows off the Bing car in all its glory.”
An experimental feature in the iPhone version of Google Maps that measured the calories burned (and equivalent in mini-cupcakes) when walking a route instead has been pulled due to complaints, TechCrunch reports: the feature couldn’t be disabled, the calorie counts were vague and unhelpful, and it could be actively harmful to users with eating disorders. More at Buzzfeed, Slate and The Verge.
The Moon and Mars were relatively early additions to Google Earth; that application may have been migrated to the web, but the planets and moons keep coming. Yesterday Google announced the addition of a dozen other worlds in our solar system; the space layer of Google Maps now includes planets Mercury, Venus and Mars; dwarf planets Ceres and Pluto;1 Jupiter’s moons Io, Europa and Ganymede; and Saturn’s moons Dione, Enceladus, Iapetus, Mimas, Rhea and Titan. Large moons Callisto and Triton aren’t included, and Iapetus is projected onto a sphere rather than appearing as the bizarre space walnut it is.
CBC News reports that more than 3,000 indigenous communities in Canada—traditional First Nations reserves as well as treaty settlement lands and urban reserves—have finally been added to Google Maps. For some reason I thought they already were—U.S. Indian reservations have been on Google Maps for some time, after all (their visibility, or lack thereof, was commented on in 2011: here, here and here).