Several weeks ago, Carol and I got stuck in traffic on I-25 on
the south end of Denver. We were trying to get home to Colorado
Springs, and traffic was at a standstill. We didn't know where the
problem was, nor how to get around it. So we took most of an hour
to get a couple of miles. The next day I tracked down a fuzzy
memory of a mobile app that maps traffic congestion using
crowdsourced reports from app users. It only took a minute to find
Waze. I
installed it on my phone, and Carol and I have been playing with it
ever since.
We don't punch a clock anymore and have no commute, but whenever
we have to go across town (which for Colorado Springs is about
fifteen miles tops) we fire up Waze and look at the prospective
route. It's definitely saved us some stop-and-go time, especially
on I-25, which is the only freeway we have here.
Waze is basically
an interactive map on which reports from users are
plotted in something very close to realtime. These include speed
traps, wrecks, potholes, construction, and other miscellaneous
hazards. The reports are generally accurate, right down to the
potholes. When traffic is slow, Waze knows it, because GPS can
calculate your speed. When two or more Waze users are going slow on
a particular route, Waze paints the road in red and indicates what
the speed currently is.
This is cleverness but not genius. Back in the wardriving era
when GPS was first commonly available (back in 2000-2003 or so) I
had this notion that a system could gather information about speed
traps, if only there were a way to get reports to the central
server from user cars. Then, wham! Smartphones happened. The rest
is history.
No, the genius part of Waze is that its creators turned it into
a sort of combination video game and social network. Waze users are
plotted on Waze maps right along with the speed traps and potholes.
It integrates with things like Foursquare. You get points by
submitting reports and spotting errors on Waze maps. (You actually
get points just by driving around with Waze running on your phone,
which allows them to gauge speeds on the roads.) People with the
most points get swords, shields, or crowns to wear on their little
ghost-like Waze icons. Intriguingly, you can send messages to other
Waze users, create teams of drivers, and other things that I
haven't quite figured out yet, including searches for cheap gas.
Even doing as little driving as we do, in three weeks we managed to
rack up over 900 points. There's a stack rank of users for each
state. (We're down in the 100,000 range for Colorado.) Carol got
some points for making roadkill out of a piece of hard candy that
mysteriously appeared on the Waze map in front of us. If that sort
of thing appealed to us, I suspect we would be addicts, like the
people with over half a million points obviously are.
There are two fairly obvious downsides to the Waze system:
- To be useful, Waze requires that a certain critical mass of
users be prowling around your town, reporting things. Here in the
Springs, this rarely happens outside rush hours. I'm guessing that
in smaller towns, Waze never really gets out of first gear. Like so
much these days, it's a YUH (young urban hipster) phenomenon.
- As if I even had to mention, it's yet another driver
distraction, probably in the same league with texting. That's why
we only use it when we're both in the car, and Carol typically does
the reporting and the sniffing ahead for congestion.
I'm starting to see articles about how cops hate it because of
speed trap reporting, which suggests that, at least in large urban
areas, it's working as designed. I like it for the sake of the
traffic reports, which I suspect will be even more useful the next
time we're in Denver, or lord knows Chicago. Problematic for one,
useful (and sometimes fun) for two.
Cautiously recommended.