Category: Map Errors

Null Island as Easter Egg

Published on by Jonathan Crowe
Stamen Maps

Null Island is an inside joke among cartographers: an imagined island situated at 0° latitude, 0° longitude, where maps suffering from data glitches point themselves. If your map is centred on Null Island, something has gone wrong. So of course mapmakers have been having some fun with it—after all, it’s not something you could stumble across by accident. In a blog post, Alan McConchie of Stamen Maps delves into the lore and history of Null Island and its status as an Easter egg on the Stamen Maps platform, where it takes the shape of the island from the Myst game.

(As an update to my 2016 post on Null Island: Alan reports that the buoy at 0°, 0° has ceased to be. Also, the Null Island website, complete with flag, has moved here.)

OpenStreetMap Is Dealing with Some Vandalism

Published on by Jonathan Crowe

It seems OpenStreetMap has had to deal with a wave of vandalism attacks lately. If you see some nonsense on OSM, this post on their community forum outlines what to do about it (it may have already been taken care of even if it’s still appearing, so check for that; also, don’t post screencaps, because propagating the nonsense is what the vandals want). The OSM ops team provided this update on Mastodon today: “OpenStreetMap is now stronger with improved monitoring, automatic blocking, and respectful limits on new accounts. The default osm.org map is now quicker at fixing large-scale vandalism. Offline actions are also progressing.”

Pokémon Go Users Are Adding Fake Beaches to OpenStreetMap

Published on by Jonathan Crowe

Some Pokémon Go players are apparently adding fake beaches to OpenStreetMap in order to improve their chances of catching a new pokémon. The pokémon in question was added to the game last month and only spawns in beach areas. Pokémon Go uses OpenStreetMap as its base map. It’s not hard to see how players can cheat by adding natural=beach nodes where no actual beaches exist, and indeed beaches started turning up in odd places in the game—and in the real-world map as well, because the game uses real-world map data, and that’s what gamers have been messing with. Receipts at the OSM community forum thread. [Atanas Entchev]

Apple Maps Lists Australian Restaurant as ‘Permanently Closed’—It Isn’t

Published on by Jonathan Crowe

ABC News (Australia) reports on how Apple Maps erroneously listed a Queensland restaurant as permanently closed, costing it thousands of dollars in lost business. What’s noteworthy is the difficulty the restaurant owner had in correcting the error. Apple accepts error reports via its browser and apps, and the owner is an Android and Windows user, but it seems to be more than that: a 9to5Mac commenter found it easier to correct map errors via their personal Apple ID than as a small business owner, whereas Google Maps makes it easier for businesses. The ABC News report goes on to note that this is not an isolated incident. [9to5Mac/AppleInsider]

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.

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.

What3Words Confusion Rate Under Scrutiny

Published on by Jonathan Crowe

The What3Words geocoding service assigns a three-word mapcode to every three-square-metre patch on the planet, the premise being that three words are easier to remember and share than longitude and latitude to the equivalent decimal places. But the main complaint about What3Words (apart from the proprietary nature of its algorithm and database) is that it’s possible to get even those three words confused, especially in contexts where plurals and homophones may not be heard clearly, or where similar combinations of words are close enough to each other that they can be mistaken for each other. There’s actually an entire website dedicated to chronicling errors in W3W.

W3W maintains that their algorithm keeps similar combinations “so far apart that an error is obvious. We also worked hard to remove homophones and near homophones like sale and sail.” They rate the the chance of two confusing combinations appearing close enough to be unclear at about 1 in 2.5 million. But in a new analysis of the algorithm, currently in preprint, computer scientist Rudy Arthur argues that despite W3W’s claims this chance of confusion is far higher, and warns against adopting W3W as critical infrastructure (it’s used by emergency services, particularly in the U.K.) without testing and comparing against available alternatives. [The Register]

Previously: What3Words Hasn’t Had the Greatest Couple of Months: A Roundup.

Can Places on Google Maps Be Trusted?

Published on by Jonathan Crowe

Google has been plagued with fraudulent and scammy business listings on Google Maps for years (1, 2). Last April, Google posted about the steps it takes to combat fake content. James Killick points to more recent incidents and wonders whether places on Google Maps can still be trusted; given that he was able to add a fake listing and have it appear on the map within hours, signs point to no.

‘One Bad Map a Day in February’

Published on by Jonathan Crowe

#mapfailbruarychallenge: a list of categories to create one bad map a day in February.

It’s like the #30daymapchallenge in November, in which mapmakers are challenged to make a map a day on a given daily theme, only the reverse: the MapFailbruaryChallenge is about making a bad map on a given daily theme. “The idea is to create the worst map possible.” Bad maps happen; will a deliberately bad map be better or worse? Either way, it’s probably worth stocking up on popcorn for when maps with the #mapfailbruarychallenge hashtag start showing up on our timelines.

(Failbruary. Fai-EL-bru-AIR-y. Say that ten times. And resign yourselves to the fact that Reddit is probably going to kick everyone’s ass on this.)

Update, 19 Jan: There’s an official website now.

All Online Maps Don’t Suck?

Published on by Jonathan Crowe

OpenStreetMap was always pretty good but is also now *really* good? And Apple Maps's new zoomed-in design in certain cities like NYC and London is just gorgeous. It's cool how there are all these good maps now!The notion expressed in Monday’s xkcd, particularly in the alt-text—

OpenStreetMap was always pretty good but is also now really good? And Apple Maps’s new zoomed-in design in certain cities like NYC and London is just gorgeous. It’s cool how there are all these good maps now!

—is unexpectedly more on point than not.

In 2013 I wrote a screed saying that all online maps sucked: that no one map platform had a monopoly on errors. At the time Exhibit A for the suckiness of online maps was Apple Maps; since then, and particularly since 2018, Apple has been putting in the work. Not that they’re done, but still: the product is fundamentally better now than it was then. And it’s not like the other platforms have been idle in the meantime. No one platform is going to achieve Cartography’s ideal of the universal and accurate Map—that’s inherently unachievable—but better? I’ll take better.

Google Rerouted Traffic Up Poorly Maintained Mountain Roads During a Blizzard

Published on by Jonathan Crowe

Screenshot of Google Maps showing driving directions in California
Screenshot (Crystal A. Kolden/@pyrogeog on Twitter)

Last week, when a snowstorm closed Interstate 80 east of Sacramento, Google Maps started redirecting traffic up poorly maintained mountain roads, which is about as good an idea during a blizzard as it sounds.

As SFGate reports,

Other dispatches from Twitter allege that the service—particularly its mobile app—directed people to closed-off highways, mountain passes and lakeside roads to get around. This is in direct contrast to Caltrans’ messaging to avoid workarounds. Caltrans District 3 spokesperson Steve Nelson told SFGATE on Monday that they were seeing drivers trying to skirt highway closures with side streets. “They’ll take side roads and try and sneak past the closures, and that never ends well,” he said.

Google engineer Sören Meyer-Eppler responded on Twitter to spell out some of the technical and logistical problems involved in rerouting traffic during bad weather: the difficulty in finding timely data (and in such cases data need to be really timely) and the risk of false positives. More at Jalopnik.

Google Maps Called Out for Showing ‘Potentially Fatal’ Mountain Routes

Published on by Jonathan Crowe

The Guardian: “Scottish mountaineering charities have criticised Google for suggesting routes up Ben Nevis and other mountains they say are ‘potentially fatal’ and direct people over a cliff.” Google Maps’s issue with Ben Nevis is that it routes to a parking lot nearest the summit, then more or less straight-lines it from there; as a dotted line it’s meant to indicate a route very imprecisely, but it also corresponds to a higher-difficulty ascent route that could land even experienced hikers in trouble. Not meant to be taken by people who don’t know what they’re doing—the people who might have no clue that it’s a bad idea to use Google Maps for mountain hiking, for example.

To be clear, I think this one’s on Google. A lot of people trust online maps implicitly because they have poor navigation skills and have a hard time overruling what the directions tell them: this is why people keep driving into rivers and onto tracks. It’s a design failure not to account for this in every circumstance.