The Verge’s Dan Seifert tries out Google Maps and Waze on CarPlay, and concludes that “neither Google Maps or Waze are particularly compelling compared to their Android Auto counterparts or even Apple’s own Maps app.” The unkindest cut: “If I’m traveling somewhere unfamiliar, Apple Maps is just more reliable to use than Google Maps or Waze in CarPlay, which is frankly surprising to say.”
“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 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.
Another piece on the various attempts to create detailed, high-definition maps for self-driving cars, this time from Bloomberg’s Mark Bergen, who views it through the prism of Google’s efforts in that space, and whether its competitors will be able to stop Google from dominating the high-definition mapping space the way it has come to dominate consumer maps.
There are, Bergen reports, two ways to make high-definition maps for self-driving cars:
The companies working on maps for autonomous vehicles are taking two different approaches. One aims to create complete high-definition maps that will let the driverless cars of the future navigate all on their own; another creates maps piece-by-piece, using sensors in today’s vehicles that will allow cars to gradually automate more and more parts of driving.
Alphabet is trying both approaches. A team inside Google is working on a 3-D mapping project that it may license to automakers, according to four people familiar with its plans, which have not previously been reported. This mapping service is different than the high-definition maps that Waymo, another Alphabet unit, is creating for its autonomous vehicles.
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.”
Earlier this year, we shared the first results of this effort with pollution levels throughout the city of Oakland.
We’re just beginning to understand what’s possible with this hyper-local information and today, we’re starting to share some of our findings for the three California regions we’ve mapped: the San Francisco Bay Area, Los Angeles, and California’s Central Valley (the Street View cars drove 100,000 miles, over the course of 4,000 hours to collect this data!) Scientists and air quality specialists can use this information to assist local organizations, governments, and regulators in identifying opportunities to achieve greater air quality improvements and solutions.
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.
A new version of Google Earth launched today. Unlike previous versions, the desktop version runs in a web browser rather than a standalone app. Also unlike previous versions, it’s no longer cross-platform: for now at least, the desktop version only runs in Chrome, and the mobile app is Android-only.
Frank Taylor has been covering the new release at the venerable Google Earth Blog and has a first review.
For my part, I’ve poked around in it in Chrome a bit and I found it fairly responsive and easy to use. If it runs this well in the browser I can see how a standalone app would be redundant; this is a better delivery method. I would much prefer it, though, if it also ran on platforms that didn’t belong to Google.
Update, 21 April: Coverage from AFP and Geoawesomeness focuses on the features, which I gave short shrift to above.