SLUR behavior (speed limit update request)
a few month ago Irad told to make suggestions about SLUR, I took my time but here it is :
In the beginning, we had a SLUR for every request, and there were way too much of them because sometimes there is a lag in showing the new speed limit so people were reporting speed limit that were already good, and also because speed limit were not visible in the client until you exceeds the limit.
The idea of grouping them making cluster was implemented (against our will), and according to Merav last time I spoke with her about it, it was a "total failure" with groups of different update requests in various languages where we miss the localization since they are grouped on one request at a random place of the segment : "Speed limit: 90 km/h,Limite de vitesse : 70 km/h" And it is a nice one, sometimes you have 5 different speed reported".
When you answer you don't know if nobody receive the response, or if everybody is getting it or maybe one of the reporter.
What I suggest since the beginning :
Do not group requests in a cluster
Ignore update requests suggesting the speed that is already set on the segment (if someone reports 90km/h on a segment but it is already 90, just close the SLUR without showing it in WME.
Do not allow user to submit SLUR in the wrong unit. If I am in France people should never submit a speed in miles/h.
Link to original suggestion: https://www.waze.com/forum/viewtopic.php?f=1525&t=284047
Thank you for this suggestion.
As it was announced in the forum we are currently working on improving the SLUR workflow and user experience.
This suggestion will be taken into consideration in the work.
So, thank you again we will update accordingly.
Jon Angliss commented
@Admin Since the forum has been updated, I've not been able to find any details on SLUR workflow discussions. Can you provide the link to the announcement? And maybe an update on what the improved workflows might look like?