Limit number of reports that can be dropped in a small area
This morning a Wazer dropped 17 reports in a parking lot. This is really uncalled for. The number of reports should be limited to X number of reports to X number of feet/km. It is OK if it is coming from multiple users, for instance an accident or closure on a highway. But one user should not be able to drop that many reports in one small area. This was limited to a small parking lot where this happened.
-
wxw777 commented
Looking at TxAgBQ's location, it appears the user submitted the URs on the successive days which I believe is beyond the scope of this request and what staff have been working on. As long the the report is valid and on successive days, that's probably going to be continued to be allowed.
If the user is dropping them to be abusive even after being responded to, the current mechanism would be to escalate to the regional coordinator for a possible ban (after validation by staff).
-
TxAgBQ commented
Check here. Wazer complains we sent 100 messages but that's because they submitted a ton of duplicates. You need to block users who do this and limit their ability to do this.
-
Kathy Kendall commented
It might be good to limit the number of UR's per time period (maybe for R1 editors only?), also -- so they can't just drive down the road and drop them every mile or two. (That could bite us as editors, though, if we are doing BOTG. Sometimes BOTG requires multiple legitimate UR's in a small area.)
-
mapman44 commented
Recently I handled a situation where a kid playing with his mother's phone dropped over 40 "turn not allowed" URs in about 5 minutes as she drove on I-85. Then I spent over a half hour figuring out if any were legitimate and cleaning up the rest. WME also has difficult when multiple URs are dropped in exactly the same spot. This needs attention too.
-
whathappened15 commented
Please implement some sort of solution here. We just cleared another instance of UR spamming, in which the user dropped over 145 URs in 65 minutes. All other app Reporting functions are limited in frequency before a cool-off period to prevent point farming. URs should be as well to prevent valuable volunteer editor time from being wasted.
-
Kodi75 [5] commented
36 URs submitted at one location within a minute .
https://www.waze.com/en-US/editor/?env=usa&lon=-75.78596&lat=38.69625&zoomLevel=17&mapUpdateRequest=10028014 -
Larryhayes7 commented
Here is another one one of the SAT SM's found just a few days ago.
-
Larryhayes7 commented
We are keeping this area with all these UR's open so you can review
-
wxw777 commented
After further discussion with other editors, it may be better to give the user a pop-up indicating only a single report is needed and give them the opportunity to enter more details. As opposed to just rate limiting them. This would help with education. Hands-free, dictated additional info would be ideal when there is no navigator.
-
TxAgBQ commented
6x URs right on top of each other. Ironically, you allow Wazers to report multiple issues, but not Waze editors. https://waze.com/en-US/editor?env=usa&lat=29.78018&lon=-95.33895&zoomLevel=17&segments=48796813&mapUpdateRequest=9812159
-
TxAgBQ commented
2x URs within a minute - same GPS track 0- https://waze.com/en-US/editor?env=usa&lat=29.57015&lon=-98.65218&zoomLevel=18&segments=48134136
-
TxAgBQ commented
3x URs within 1 ft of each other - https://waze.com/en-US/editor?env=usa&lat=29.71369&lon=-95.21495&zoomLevel=18&segments=517613749&mapUpdateRequest=9808078
-
TxAgBQ commented
2x URs within 25 seconds with no info. https://waze.com/en-US/editor?env=usa&lat=29.79216&lon=-95.79139&zoomLevel=18&segments=523745212&mapUpdateRequest=9807904
-
TxAgBQ commented
2x URs 9 feet apart, within 24 seconds of each other. Neither has any details. https://waze.com/en-US/editor?env=usa&lat=29.74791&lon=-95.36093&zoomLevel=18&mapUpdateRequest=9806733
-
Steve Moore commented
I like this idea. Especially when we find an excessive number stacked in a parking lot with no route/GPS trace, comments, etc. If these could be processed automatically it would save a lot of time. We’ve had 3 or 4 of these in as many weeks.
-
Larryhayes7 commented
Additional screenshot this is what started my suggestion
https://drive.google.com/file/d/10_Ge9Lc3LKf979TfNW-yJ5rjekvjFNzu/view?usp=sharing
-
Larryhayes7 commented
Adding PL of the area for review
-
Larryhayes7 commented
-
AdminWaze Team (Admin) (Admin, Waze) commented
Hi all,
Thanks for making this important suggestion! We've moved it to the WME suggestion box, as we feel this aspect of URs most affects the Editors community.
Moving forward, please put suggestions which have an impact on Editors in the WME Suggestion Box, even if it is a grey-area like URs.
Thanks!
Waze Communities Team -
wxw777 commented
This sounds like a good idea as editors have no way of knowing if all the requests are from the same person. It also is of no benefit to the user to have us replying to each requesting additional info and then they get bombarded with "spam" from the responses. It ultimately would be a win-win for both editors and users.
I agree that it may be best applied to only L1 editors or users with no editor profile. The range or time-threshold between reports is the only real question mark.