Dirk Willden
My feedback
5 results found
-
10 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
An error occurred while saving the comment -
1,267 votesDirk Willden supported this idea ·
-
1,910 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
An error occurred while saving the comment Dirk Willden commentedSounds like a good idea but with the delay between reporting and when it shows up on the map, (roughly four minutes, sometimes more if there are cell network issues). The only people that report is really going to help will never see the report.
Those going slower than the cop don't have to worry and the report will always be appearing roughly four miles behind them (assuming traveling 60 mph). For those about to catch up with the officer, the closest report is still going to be three to four miles behind the officer so they won't see it. And if the Officer is driving far enough without pullng over or off the road, that some speeder can cover the four miles: A: the officer is most likely off duty and thus won't really care unless they are speeding stupidly fast and deserve to get caught, and B: The driver will most likely have forgotten the report that is now cruising four miles behind them.
Perhaps Waze can drop the delay between reporting and it appearing on the map, but then you get people complaining about someone being able to track their movements to easily. The delay is designed to provide privacy protection, so I don't see it getting dropped.
-
266 votesDirk Willden supported this idea ·
An error occurred while saving the comment Dirk Willden commentedI disagree with your understanding of who is sitting atop the scoreboard. Now I can't speak for the ROTW server, but on the NA server the top scorers are all editors, myself at #15 in NA with 1055396 points on 6292 miles driven. It's the over 300k edits under my belt that pushed me so high, not the driving.
That said I will toss a vote towards this on behalf of giving those poor professional drivers a scoreboard they can feel good about. ;)
Oh and ZW4020 it's 750 point candies for every 500 edits not for time. And you find an untouched city or town to fix and you can rack up a few thousand qualified edits in an hour or less, with all the resulting candies.
-
291 votesDirk Willden supported this idea ·
Nope, because different roads of the same type can have different speeds in close proximity. And Roads of the different types can have the same speed settings.
Example a road called Hwy 89 that runs from Canada to Mexico through Montana, Idaho, Utah, and Arizona. The legal speed limit on this road changes constantly across it's length, in many areas it's a two lane rural highway with a speed limit of 55, but every time it enters a city the speed limit will drop, some times to 45 sometimes to 35 and even all the way down to 25. In other areas it's basically a freeway with a speed limit of 65 which of course means drivers cruise at 75 to 80. Yet across it's length except for when it merges with an actual Interstate freeway, it is Known as Hwy 89 and is marked as either a minor or a major highway. Most of it's length is classified as minor highway with a few higher volume segments as Major or even freeway (when merged with a freeway).
Your system would change a very consistently classified road into a hodgepodge mess of different classifications which would also trash the routing along the Hwy. Even though the speed limit changes frequently along this road, for most of it's length it is a primary travel route and should be preferred in the routing algorithms even though it's speed drops to 25 mph through some towns.