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.
As of iOS 12, coming later this year, CarPlay will support third-party map applications like Google Maps and Waze, Apple announced during its WWDC keynote earlier today: AppleInsider, Engadget, The Verge. Up until now the only maps available via CarPlay were Apple’s own; drivers who would rather use something else—and I know lots of them are out there—will soon have that option.
Artur Grabowski spent most of 2017 testing three mapping apps—Apple Maps, Google Maps and Waze—to see which app was the most accurate in terms of travel time to destination. His questions: which app estimated the shortest travel times, which app actually got him to his destination in the least amount of time, and how much did each app over- or underestimate travel times? In the end, based on 120 trips in the Bay Area, roughly 40 using each service, Artur found that Apple’s estimates were the most reliable (indeed, Apple underpromised and overdelivered), but while Waze promised the shortest travel times, those promises were usually overly optimistic; it was Google Maps that provided the shortest travel times.
Why does Apple underpromise and overdeliver, while Waze does the opposite? Artur suspects it’s because Waze needs to monetize its app with ads, and Apple doesn’t:
For Apple, Maps is a basic solution for its average user who wants a maps solution out of the box. Apple Maps does not directly drive ad or subscription revenue for Apple so there is less reason for Apple to incentivize iOS users to use Apple Maps over other solutions. However, Apple does care about user experience, and sandbagging trip time estimates so that users arrive at their destination on time results in a great user experience. Hence, I believe that Apple is intentionally conservative with estimated arrival times.
At the other extreme, Waze (Alphabet) makes money through ads when you use their app. What better way to get people to use your navigation app than by over-promising short trip times when no one takes the time to record data and realize that you under-deliver? If an unsuspecting user opens Apple Maps and sees a 34-minute route and compares that to 30 minutes in Waze, the deed is done. Now Waze has a life-long customer who doesn’t realize they’ve been hoodwinked and Waze can throw at them stupidly annoying ads.
“If my parents lamented a generation lost to knowing how to read a paper map, I’m wondering if mine will note the loss of one who doesn’t need the people of the places it passes through,” writes Lorraine Sommerfeld in a piece for Postmedia’s Driving that celebrates the advantages of asking locals for directions rather than relying on your car’s navigation system.
We’ve all seen business listings on online maps that don’t quite jibe with reality: the map marker’s on the wrong place, and driving directions don’t get you to your destination. The Wall Street Journal reports on how businesses deal with online map errors. Getting a wrong listing fixed is a rather high priority (a lost customer is a lost customer, if you follow me), but it turns out to be a more time-consuming—and expensive—process than I thought: there are firms that charge thousands of dollars to solve this for you. [via]
Time’s John Patrick Pullen compares how easy or difficult it is to send driving directions to your phone using maps from Apple, Google and Microsoft before coming up with a surprise winner: “I pulled up MapQuest for a punchline on this story, but the joke’s on all of us. MapQuest is, by far, the easiest way to get maps from your desktop to your phone.” I really ought to try this out myself and see if I agree with him.