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.”
Tag: map vandalism
Pokémon Go Users Are Adding Fake Beaches to OpenStreetMap
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]
Google and Apple Updates
Google explains how they identify and take action against fraudulent content—fake reviews, fake listings, content vandalism—on Google Maps.
Meanwhile, the ability to pay for parking and transit fares is being integrated into the Google Maps app (Engadget, The Verge).
On the Apple Maps front, cycling directions have come to Portland, Oregon and San Diego, and turn-by-turn navigation has been expanded in the United Arab Emirates.
Anti-Semitic Map Vandalism Strikes Mapbox
An incident of map vandalism roiled the Internet last week. Users of several online services, including CitiBike, Foursquare and SnapChat, discovered that New York City had been relabelled “Jewtropolis” on the services’ maps: see coverage at Gizmodo, Mashable and TechCrunch. The problem was quickly traced to Mapbox, which provides maps to these services. Mapbox, understandably upset about the act of vandalism, soon figured out what the hell happened.
The problem was traced to OpenStreetMap, one of Mapbox’s data sources. On August 10 an OSM user renamed a number of New York landmarks, as well as New York itself, after a number of alt-right and neo-Nazi memes. The edits were quickly reverted and the user blocked—on OpenStreetMap. They nevertheless entered the Mapbox review pipeline, where they were, in fact, caught and flagged on the 16th, but a human editor mistakenly okayed the renaming of New York to Jewtropolis. A simple human error, but with a delayed fuse: the edit turned up on Mapbox’s public map two weeks later. When all hell broke loose on the 30th, the map was fixed within a few hours.
Vandalism of online maps isn’t a new thing: in 2015 Google ran into trouble when a series of juvenile map edits exposed the shortcomings of the Map Maker program’s moderation system and led to a temporary suspension of Map Maker (it closed for good in 2017) and an apology from Google. Anything involving user contributions needs a moderation system, and OpenStreetMap and Mapbox both have them. But moderation systems can and do still fail from time to time. (That’s a take on this incident that isn’t on Bill Morris’s list.)