This week Mapbox launched a tool for the upcoming 2020 U.S. elections: Mapbox Elections, “a resource to help individuals, journalists, and organizations cover the elections, analyze the results, and build modern maps to display it all.” Their first product is a dataset including U.S. presidential election results from 2004 to 2016.
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.)
Last October Robin Kraft posted an online map of the northern California wildfires showing satellite imagery from before and after the fires (see previous entry); today he’s posted a blog entry explaining how he built it, in great technical detail. The timing is not accidental: “There is another fire raging in Los Angeles right now — if DigitalGlobe and Planet release their data, you can use this guide to make your own map.”
Almost all web mapping libraries render maps using Web Mercator, making an assumption that you generally can’t change out-of-the-box. This has advantages, but it posed a real challenge for us when we set out to build the Washington Post’s live election results map, where using the Albers USA projection was an important requirement. To meet that requirement, we built a pipeline to pre-process geometries.
It’s a bit of a kludge, a way of fooling Mapbox into showing a different projection—latitude/longitude coordinates aren’t accurate any more—but it’s an impressive stab at a real problem. The Dirty Reprojectors web app demonstrates the possibilities, with all the projections available through the d3-geo and d3-geo-projection libraries. [James Fee]
Saman Bemel Benrud, a designer at Mapbox, looks to print maps for inspiration. “I like looking at print maps because they remind me how far web map design has to go. Even an average print map involves a designer making thousands of small decisions about where to place individual features and how to kern and size each label,” he writes. “You can’t work like that with web maps that are global and zoomable.” Still, he provides some favourite design elements from paper maps; it’d be interesting to see how they might be rendered online.