A lot of what we refer to on online maps as “satellite imagery” actually isn’t: the high-resolution stuff is usually taken from airplanes. This can be a point of confusion for some—and, according to this Twitter thread from Google Maps co-creator Bret Taylor, also a point of contention for the Google Maps team before it launched. Some engineers felt that calling the layer “Satellite” was factually incorrect—because of that aerial imagery—and therefore shouldn’t be used; others argued for “Satellite” based on label size and usability studies. It nearly got called “Bird Mode” as a compromise. [Boing Boing]
Google integrates its maps into its search results: synergy! What, then, is scrappy upstart search engine DuckDuckGo, which makes a point of not tracking its users,1 to do in response? Answer: use Apple Maps. “We’re excited to announce that map and address-related searches on DuckDuckGo for mobile and desktop are now powered by Apple’s MapKit JS framework, giving you a valuable combination of mapping and privacy.”
CNet’s Kent German asks people to stop tech-shaming over old phones and paper maps, though I’m not exactly sure who exactly does this (it’s not like he provides any examples). Anyway, one example he does use to bolster his argument is the time a paper map saved him from getting lost in France when his rental car’s GPS didn’t have updated maps; the graft to the larger argument in favour of not being so quick to abandon old tech in favour of the latest and greatest does leave some visible seams. (He also drags the post office into the argument. It’s Luddite potpourri.) [MAPS-L]
The argument for paper maps is getting ever more insistent, even shrill, but it seems to me to be mainly coming from the tech side of things. My impression is that the people who rely too much on mobile maps haven’t lost the ability to read maps; they never had it in the first place.
A long exposé from the New York Times explores just how much location data is collected from mobile apps, to the point where the identity of an anonymous user can be reconstructed from where they’ve been. The key point: whatever purpose the app is collecting your location for (for example, to give you your local weather), that location data may be shared with and sold to other parties.
Apple now has a fleet of cars collecting data for Apple Maps. Since they’ve been making a point about consumer privacy lately, this page lists where their cars are going to be in the coming weeks. (AppleInsider notes that some of that data collection is pedestrian-based.) It turns out Google has a page for Street View data collection that includes similar information, though it’s far less granular: windows of several months, whereas Apple tells you where it’ll be within a two-week timeframe.
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.”
During a natural disaster like Hurricane Florence, crisis maps can be an invaluable source of information about road and bridge closures and other infrastructure outages. Trouble is, that information doesn’t always trickle down to mobile phones, which is where most people get their maps. (Especially when authorities have trouble keeping up with road closures on their own maps.) CityLab’s Clare Tran explores this question, looking at, for example, how Waze incorporates road closure data from Esri and its volunteers.
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.
Relying on your smartphone’s maps can be risky in places where cellular service is patchy. That goes for Gatineau Park, where, despite the fact that its southeast corner is surrounded by the city of Gatineau, Quebec (across the river from Ottawa), staff still recommend people use paper maps, CBC News reports. It’s a big park, after all, and not all of it is in the city. But it’s not just about dead zones and dead batteries: out of date trail information and lack of trail difficulty are also problems. None of these problems, mind you, are unfixable (except, you know, dead batteries).
“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.
A thing I missed when it came out last year: the INAT Metro Maps app, which collects, in digital form, the 40-odd maps that Jug Cerović produced for his One Metro World project. For the iPhone and iPad; costs 99¢ in the U.S., $1.39 in Canada, and (I assume) something comparable in other markets.
Traffic. Traffic congestion is a key feature of mobile mapping, and predicting it involves looking at historical data. CityLab reports on a recent study suggests that time-of-day electricity usage patterns can be used to predict traffic congestion patterns. A household that starts using power earlier in the morning gets up earlier and presumably will go to work earlier.) It’s another variable that can be put to use in traffic modelling.