Tag: Google Maps

Google Maps at 20

Published on by Jonathan Crowe

Google Maps launched 20 years ago today. Here’s what I posted at the time:

First impressions. This is frigging amazing, with smooth scrolling and zooming: you’re not constantly reloading pages like in MapQuest. Huge mapping surface. And drop shadows. […] I’m impressed by the detail. They’ve got my area, which is kind of a rural backwater: they’ve got the roads all named, but strangely not the towns. Oh well, data’s rarely perfect—especially when it’s just a beta launch. And for a beta this is awfully impressive.

A flurry of additional announcements followed in quick sucession: the launch of Google Earth, the Maps API that enabled people to build their own maps on top of Google’s interface. The mid-2000s were a busy time for online maps, let me tell you. I had so much to keep up with.

The development and origins of Google Maps, and Google Earth, are the subject of the latest and timely installment of James Killick’s “12 Map Happenings that Rocked Our World.” It seems that the Maps side of things was largely about providing Google search results through a map interface, and when you look at Google’s post commemorating the 20th anniversary, which highlights 20 features of Google Maps, it’s clear how expansive that idea has become.

James also makes reference to a book I somehow completely missed when it came out: Never Lost Again: The Google Mapping Revolution That Sparked New Industries and Augmented Our Reality, an insider history by Google project manager Bill Kilday. (Harper Business, 2018). Amazon (Canada, UK), Bookshop.

Google Maps to Use ‘Gulf of America’–Others Not So Much

Published on by Jonathan Crowe

Lots of news coverage about Google’s announcement that it will follow Trump’s lead and change Gulf of Mexico to Gulf of America (and Denali to Mount McKinley) on Google Maps once the GNIS database has been updated—at least when showing it to American users. Mexicans will still get Gulf of Mexico, while the rest of us will get both names. See coverage at BBC, CNBC, CNN, Guardian, TechCrunch, among many many many others.

I’m not sure why some people were expecting Big Tech to lead the resistance (especially a trillion-dollar company), and over one of the easiest things to undo once this is all over: Google has made a point of accommodating government requests on its maps, showing the “right” borders and place names to the right users. See previous post: Google Maps as Non-State Authority.

But not everyone is falling into line. The British government has no plans to refer to it as the Gulf of America, nor will British maps change unless it becomes the most commonly used name: see The Independent and The Telegraph.

Meanwhile, the Associated Press is updating its stylebook in a way that splits the difference, following Trump on Denali/Mount McKinley because it’s fully within his purview but pointing to the Gulf’s international status: “The Gulf of Mexico has carried that name for more than 400 years. The Associated Press will refer to it by its original name while acknowledging the new name Trump has chosen. As a global news agency that disseminates news around the world, the AP must ensure that place names and geography are easily recognizable to all audiences.”

Previously: Naming the Gulf.

Update 9:10 PM: More detail from CNBC, which reports that “Google’s maps division on Monday reclassified the U.S. as a ‘sensitive country,’ a designation it reserves for states with strict governments and border disputes […] Google’s list of sensitive countries includes China, Russia, Israel, Saudi Arabia and Iraq, among others. […] Google’s order states that the Gulf of America title change should be treated similar to the Persian Gulf, which in Arab countries is displayed on Google Maps as Arabian Gulf.”

Three Dead After Google Maps Routes Travellers Across Incomplete Bridge—That Wasn’t Closed

Published on by Jonathan Crowe

The headline accompanying this Economic Times (India) article is more than a bit misleading: ”Google Maps leads three men to death as car plunges from incomplete bridge into river.” Horrifying. The bridge across the Ramganga River in Uttar Pradesh was closed after a part of it had been washed away in a flood several months previously. But there’s a twist. Google Maps didn’t mark the bridge as closed, and did route the travellers across it, but the road hadn’t been blocked or marked closed on the ground either. This wasn’t a case of ignoring local signage and blindly following online maps: local signage failed too. Google isn’t a panopticon: someone would have had to tell Google Maps that the bridge was closed, and I have to wonder whether that happened. But a Google Maps error makes for a better headline, one that goes international, than a horrible local lapse. At any rate, an investigation is ongoing. [Jalopnik]

Some Google Maps Updates

Published on by Jonathan Crowe

Google Maps imagery updates include improved satellite imagery thanks to an AI model that removes clouds, shadows and haze, plus “one of the biggest updates to Street View yet, with new imagery in almost 80 countries—some of which will have Street View imagery for the very first time.” The web version of Google Earth will be updated with access to more historical imagery and better project and file organization, plus a new abstract basemap layer. [PetaPixel]

Meanwhile, The Verge reports that Google Maps is cracking down on business pages that violate its policy against fake ratings and reviews.

Online Maps Roundup: August 2024

Published on by Jonathan Crowe

Apple Maps has launched real-time transit information for Tokyo. Meanwhile, MacRumors takes a look at what’s coming to Apple Maps in iOS 18, with an additional look at the upcoming “search here” function. Google and Waze updates announced at the end of the last month: Google Maps gets easier incident reporting and destination guidance (the building you’re heading to is highlighted on the map); Waze upgrades include new camera alerts, event-based (e.g. concerts and sporting events) traffic notification and reporting, and locked-screen navigation. Also, the Google Maps app now has a simplified tab bar. And they’ve changed the pin design too. What can I say: updates are a little less earth-shattering than they used to be.

Google Maps Navigation Updates

Published on by Jonathan Crowe

Google Maps is introducing a speedometer and speed limits to iOS and Carplay; the feature has been on Android since 2019. Meanwhile, Google has pushed back on the claim from one user that pop-up ads were turning up while navigating with Google Maps; rather, they say it was an instance of “promoted pins” that (should) only pop up if tapped on. 9to5Google: “we were able to replicate the exact same UI by tapping on a location on the map, so it seems the screen was either touched by accident or a glitch was at play.”

‘Map-Splaining’

Published on by Jonathan Crowe

Modern online maps have so much data under the hood, and provide an overabundance of detail, that they can’t help but bombard the user, The Atlantic’s Ian Bogost argues, coining a term for their “sheer exhaustiveness”: map-splaining. It’s a challenge to take all that data and make directions comprehensible.

The maps know that one road is five lanes wide and the other six; both have medians. They understand that right turns between the streets can be accomplished via dedicated merge lanes that skip the red light. They appreciate that two lanes allow left turns between each of these streets, facilitated by a left-turn-arrow traffic signal. Having all this information helps the maps give their step-by-step instructions: Take the first turn lane from northbound 28th Street, then a quick right into the parking lot for Flatiron Coffee. That level of precision may be convenient for some drivers, but it comes at the price of breaking down the built environment into lots of extra segments and transitions that may trigger the display of useless routing information. Perhaps the software should just be telling you to “go past the light and make a left.”

Google Timeline: Location History Moves to On-Device Storage

Published on by Jonathan Crowe

More details emerged this week on how Google Maps is changing how it stores users’ location data—which is that as of December 2024 it basically won’t: Location History has been rebranded Google Timeline and will be stored on-device, where you can set it to auto-delete after a specified period of time, rather than on Google’s servers. Not having your location data in the cloud is better for your personal security (Google can’t respond to geofence warrants if it doesn’t collect and store location data), but it also means that Timeline won’t be available via the web. This is a bit more definitive than what I understood it to be last December. See news coverage from 9to5Google, The Guardian and The Verge.

Online Maps Roundup: April 2024

Published on by Jonathan Crowe

Custom route creation and topographic maps are rumored to be coming to Apple Maps in the next iOS release, iOS 18. Google Maps has had custom routes since approximately forever; on Apple Maps we’ve had to choose between Apple’s generated routes without being able to edit them.

Google Maps announced updates focusing on EVs (EV charger search, nearby chargers in the in-car map, suggested charging stops, forecast energy consumption) and sustainability (lower-carbon travel options rolling out in 15 cities, estimated flight emissions). Also, Street View came to Kazakhstan last month. Meanwhile, Ben Schoon at 9to5Google says that while Google Maps on Android Auto is “a pretty solid experience,” it’s a different matter when you use Google Maps via Apple CarPlay, an experience he calls “a bit of a dumpster fire.”

Google-owned Waze announced updates last month that include roundabout assistance and notifications for the presence of emergency vehicles, speed limit changes, and things like sharp curves, speed bumps and toll booths [TechCrunch].

Google Maps Is Adding Generative AI

Published on by Jonathan Crowe

Uh-oh. Generative AI is coming to Google Maps. Google is using large-language models to give suggestions on where to go based on its vast horde of reviews, ratings and other contributor data. “Starting in the U.S., this early access experiment launches this week to select Local Guides, who are some of the most active and passionate members of the Maps community. Their insights and valuable feedback will help us shape this feature so we can bring it to everyone over time.” Other LLMs have a tendency to push out magnificently wrong answers; it’ll be interesting to see what results Google will get with this specific set of data. (The chances of spectacularity are not zero.)

Google Maps Updates Will Make It Impossible for Google to Respond to Geofence Warrants

Published on by Jonathan Crowe

Last week I mentioned forthcoming changes to how Google Maps stores users’ location data. According to the Electronic Frontier Foundation, those changes could spell the end of what are known as geofence warrants, which “require a provider—almost always Google—to search its entire reserve of user location data to identify all users or devices located within a geographic area during a time period specified by law enforcement.” The EFF believes geofence warrants are unconstitutional in the United States. Defaulting to on-device storage, deletion after three months, and encrypted cloud backups means Google can’t access that data: there’s nothing for them to turn over.

“All of this is fantastic news for users, and we are cautiously optimistic that this will effectively mean the end of geofence warrants,” says the EFF. “However, we are not yet prepared to declare total victory. Google’s collection of users’ location data isn’t limited to just the ‘Location History’ data searched in response to geofence warrants; Google collects additional location information as well. It remains to be seen whether law enforcement will find a way to access these other stores of location data on a mass basis in the future.”

Via Daring Fireball (where Gruber notes that Apple has never collected location data, i.e. there’s a reason it’s “almost always Google”).

Google Maps Updates Offer Users More Control Over Their Data

Published on by Jonathan Crowe

Forthcoming updates to Google Maps will give users a bit more control over their location data. Location History—off by default—will have the option of being stored on-device rather than on Google’s servers, and auto-delete will default to three months instead of 18. Meanwhile, users will be able to delete activity (“searches, directions, visits, and shares”) related to a specific location—the online maps equivalent of clearing your browser history, I guess. (I can’t help but notice that announcing greater user control over this information highlights the fact that this information is being collected in the first place.)

Google Maps Sends Drivers into Nevada Desert After Interstate Closure

Published on by Jonathan Crowe

Last month, after a dust storm shut down Interstate 15 between Las Vegas and Barstow, Google Maps sent drivers off-roading, rerouting them via barely passable desert trails. Some were stuck for hours. Google has since apologized.

Jalopnik describes this as yet another case of blindly following, but I think this is a more specific failure mode. Rerouting due to road closures or traffic jams opens up routes that the algorithm would normally deprecate, and catches more drivers unprepared. It’s one thing when that means a quiet residential street gets an expressway’s worth of traffic, quite another when the second best choice is a dirt track—or a 500-mile detour. When the best answer the algorithm can give you is a bad one, it will still give you that answer.

Previously: Man Dies After Driving Across Collapsed Bridge, Family Sues Google; Google Rerouted Traffic Up Poorly Maintained Mountain Roads During a Blizzard; Google Maps Called Out for Showing ‘Potentially Fatal’ Mountain Routes.

Thoughts on Google Maps’ New Design From a Former Google Maps Designer

Published on by Jonathan Crowe

Among the recent updates to Google Maps is a new colour palette, which has been rolling out incrementally to users. Elizabeth Laraki, who worked on the design of Google Maps 15 years ago, has some thoughts.

It seems the goal was to improve usability and make the maps more readable. Admittedly, I do think major roads, traffic, and trails stand out more now. But the colors of water and parks/open spaces blend together. And to me, the palette feels colder and more computer generated. But color choices aside … If the goal was better usability, the team missed a big opportunity: Google Maps should have cleaned up the crud overlaying the map.

[Daring Fireball]

Man Dies After Driving Across Collapsed Bridge, Family Sues Google

Published on by Jonathan Crowe

The family of a man who died after driving off a collapsed bridge is suing Google; they allege that despite multiple reports from users, Google Maps continued to mark the bridge in North Carolina, which partially collapsed in 2013, as passable, directing him and other drivers across it. The family is also suing local companies for failing to maintain the bridge or put up barricades and hazard warnings.