Chris
My feedback
8 results found
-
13 votesChris
shared this idea
·
-
347 votes
This suggestion has been added to the team's backlog, and is currently waiting for assignment. Will update when we have an established ETA.
Thanks to all who have helped us with further info!
Chris
supported this idea
·
-
85 votes
Hey,
We have looked at this suggestion, and in order to make some decisions about it, would like to kindly ask you to provide us with more data about it.
Please share some examples for when and where this restrictions apply? (use cases)
And any country you know relevant for it.
Thanks!
An error occurred while saving the comment -
110 votes
Hey!
Thank you very much for this great suggestion.
It was added to our backlog to try and see the possibility to implement it.Please note there is no ETA for it yet.
Best,
HeziChris
supported this idea
·
-
259 votesChris
supported this idea
·
-
491 votes
We plan to work on having an option to report a lane closure in the near future. In the meantime, make sure you’ve got the latest version of Waze for all the latest features.
Chris
supported this idea
·
-
3,218 votes
What we are aiming to do here is speed based alerters.
An error occurred while saving the comment Chris
commented
The only problem I have with this suggestion is that we can't be sure where the report marker has been positioned.
If it's at the point where the police are actually located then the current warning distance is definitely too low, but if it's at the point where an alert Wazer has first spotted the police off in the distance (i.e. at the point where the police will also then first be able to spot you approaching them), then the current warning distance is plenty sufficient and extending it might be counter-productive. Warning drivers too soon of a hazard is almost as bad as warning them too late - you want the warning to still be fresh in their minds as they approach the point on the road where they need to be aware of it...
As others have pointed out here, even if we could be sure that the alert was always generated at the appropriate time/distance, the way the app currently behaves when you've got several reports in close proximity doesn't help either - so as well as the popup alert system we have now, it might be nice to have a permanently visible "distance to next report of type X" readout somewhere that we could configure based on which report type we were most interested in knowing about.
-
86 votesChris
supported this idea
·
Some roads through the Royal Parks in London have restrictions which start or end at dusk - e.g.:
Green Park, no traffic allowed between 8am and dusk on Sundays or public holidays
https://www.royalparks.org.uk/parks/green-park/visitor-information/opening-times-and-getting-here
https://www.waze.com/en-GB/editor?env=row&lon=-0.13816&lat=51.50210&s=1144756211&zoom=5
Richmond Park: no traffic allowed between dusk and 7am (summer) or 7:30am (winter)
https://www.royalparks.org.uk/parks/richmond-park/visitor-information/opening-times-and-getting-here
https://www.waze.com/en-GB/editor?env=row&lon=-0.27269&lat=51.44028&s=1144756211&zoom=3
At both of the permalinks provided, you can see our attempts to map these restrictions as best we can using a series of TBRs with differing start/end times.