Waze Will Now Warn Drivers About Crash Dangers Using Historical Data (arstechnica.com) 23
An anonymous reader quotes a report from Ars Technica: Traffic navigation app Waze is adding a new feature to its toolbox today. It's called crash history alerts, and it's meant to warn drivers about dangerous hotspots, based on a combination of historical data plus road and traffic data. Originally an independent startup, in 2013 Google purchased the Israeli company for $1.15 billion, perhaps beating Apple to the punch. [...] One feature of Waze that was unique for a long time was its ability to crowdsource traffic information. Users add live traffic information to the app as they drive, like a car stopped by the side of the road or a crash.
Waze now leverages that data, together with geographic information, including road layout and elevation, plus typical traffic levels, to determine whether a particular stretch of road has a high crash rate. Should that be the case, the app will warn the driver. However, Waze says that to minimize distractions, it won't show these alerts on regularly traveled roads and will limit alerts on unfamiliar roads to prevent driver overload.
Waze now leverages that data, together with geographic information, including road layout and elevation, plus typical traffic levels, to determine whether a particular stretch of road has a high crash rate. Should that be the case, the app will warn the driver. However, Waze says that to minimize distractions, it won't show these alerts on regularly traveled roads and will limit alerts on unfamiliar roads to prevent driver overload.
Find the cops (Score:3, Interesting)
Re:Find the cops (Score:5, Informative)
Waze already does this.
"In 2015, Waze drew the ire of the U.S. National Sheriffs Association, which argued the police-spotting function interfered with officers' ability to catch speeding drivers."
https://www.cbc.ca/news/canada... [www.cbc.ca]
Re: Find the cops (Score:1)
Re: Find the cops (Score:4, Interesting)
It doesn't. I'm not sure how valuable it would be. The ~40 mile section of I-5 I drive twice a week, always see at least one cop, sometimes two. Not bad for 40 miles but if they used historical data I'd get a report every mile. Those two cops are rarely in the same place.
I suppose SOMEONE has to be the first to see the cop but in my experience using Waze I have NEVER been that person during sane hours. Only time I get to report rather than confirm the cop is at 3AM.
This is, IMHO, Waze's niche. I personally find the UI cumbersome and the app occasionally buggy. If I'm not speeding Apple or Google Maps are both better. On a long road trip through, where speeding actually adds up to real time savings, or if I just feel like being a speed demon for whatever reason (driving fast can be fun), Waze every single time.
Waxe is better than any radar detector I've ever owned. When I see the little police icon I slow down within plus/minus 5 miles of it, on the theory he may have moved. Zero tickets. Zero pull overs. And I have done some truly obnoxious trips on Waze. Averaged >100moh on the Portland to Seattle run once, under two hours for what's normally over three. Averaged ~95mph when moving across CONUS; shaved almost a full day off that trip.
If Waze had existed in my 20s I'd have donated a lot less money to the People of the State of New York. ;)
Re: Find the cops (Score:3)
I use Waze for long distance for the same reason - when speeding may actually add up and save time. I'm confused, though, about the status of Waze. It was bought by google awhile back (~2013?), but google maps and Waze still seem very independent and far apart in asthetics and features. Why hasn't google started incorporating more of Waze into their maps app, or vice versa? I like the google maps UI better and it's less buggy, but I like Waze features, like more detailed descriptions of traffic ahead, obst
Re: (Score:2)
I honestly kind of felt like Waze was abandonware for the longest time. Just a source for some extra ad revenue Google was slowly content to let atrophy. There were (perhaps still are) several longstanding bugs in the app, bugs that don't seem like they should be that hard to fix, and I've also encountered a disproportionate number of occasions where the issue seems to be with the cloud/servers underpinning it. Map a path somewhere and it hangs for minutes, despite perfect Internet connection, where both
Re: (Score:2)
Re: (Score:3, Insightful)
Ah yes, blame the cops when you're speeding, blowing through stop signs, not stopping at red lights, or passing school buses. Clearly the cop is at fault.
Re:Find the cops (Score:5, Interesting)
That's great that you've never been driving through a small town in a different state and have the cops pull you over while you're not breaking any laws, write you a completely bogus speeding ticket while knowing full well that to fight it you've got to travel back across the country to the little podunk town for at least one court appearance and likely two that will be heard in a small town court by a judge that's likely as corrupt as the cop who wrote the ticket in the first place. And of course they'll let you plead it down to a non-moving violation without needing to show up in court, but the fine for that is the exact same as if you paid the original fine, just as long as they get their money.
Fuck you, Jennings, LA.
Re: (Score:2)
Re: (Score:3, Insightful)
I think I'd mind speed traps less if cops actually were trying to encourage safer driving habits, but mostly they seem to camp out at spots intended to generate revenue rather than increase safety. For example, around here I frequently see a cop:
On a straight, level road where the speed limit drops from 45 MPH to 30 for no discernable reason.
Near an onramp with a 30 MPH limit, even though it can safely be taken at 40 MPH if you're driving a sedan or coupe.
In the touristy part of town waiting for people to
Re:Find the cops (Score:4, Insightful)
Oh, you thought police presence was for safety and not revenue generation?
Re: (Score:2)
Re: (Score:1)
Ah yes, blame the cops when you're speeding
Another one who hasn't grasped that speeding isn't the issue. Prevalent road conditions, obstructions, maintenance and driver ability are what kill. NOT speed. Speed is easy to measure and monetise. The "Speed Kills!" marketing BS is propaganda aimed at slow thinkers.
Traffic is a complex system that relies on flow to reduce failures. Anything that impedes the flow raises the chance of failure. This includes speed traps.
It really is time to have adult converstaions about this.
That is a great idea, public API? (Score:1)
I can see where that's a nice feature to have unique to your app...
But it's SO useful, it sure seems like that would be great data to have available by a public API that any map app could make use of.
Just like they have warnings about traffic light intersections now in a lot of nav apps, I would love to know I was approaching an intersection where a lot of people ran lights to be extra careful, and/or slow down more before I reached it.
I guess personally as a driver, I already feel like I'm cautious enough
Re: (Score:2)
it sure seems like that would be great data to have available by a public API that any map app could make use of.
My state publishes road crash data as a scrapable URL of CSV with GPS co-ordinates, type of crash, human fatalities and injuries, and pedestrian involvement. Its possible, but every state may have it's own format and therefore the data import needs maintaining in the app.
Make it play "Deadman's Curve" based on GPS (Score:1)
Instead of just warning ... (Score:4, Interesting)
Re: (Score:2)
Brilliant (Score:2)
However, Waze says that to minimize distractions, it won't show these alerts on regularly traveled roads and will limit alerts on unfamiliar roads to prevent driver overload.
Won't be long before the first lawsuit alleging the driver crashed because Waze failed to alert them to section of road it knew to be dangerous.
Also... (Score:2)
Also, how about a warning when dangerous drivers are nearby.