kGeen bewerkingssamenvatting |
kGeen bewerkingssamenvatting |
||
| Regel 12: | Regel 12: | ||
* Severity 1-5 - based on a combination of road type, amount of traffic and the importance of the road. | * Severity 1-5 - based on a combination of road type, amount of traffic and the importance of the road. | ||
<br /> | <br /> | ||
After processing a bot closure report the editor should add a reply to show what has been done with the report, f.i. via an icon like [[ File:C2.png|22px]] <small>(:c2)</small> or [[File:Wme-trash.png|22px]] <small>(:wme-trash)</small>. | |||
</translate> | </translate> | ||
__NOTOC__ | __NOTOC__ | ||
{{Bottomline}} | {{Bottomline}} | ||
Versie van 1 apr 2018 01:10
Closures bot
The Waze Closures Bot publishes closure data, reported via the app in the Slack BeNeLux Closure channels.
Editors can easily use this data for modifying and implementing closures. The bot is developed by WimVandierendonck.
Editors who are picking up these closure reports should check their validity before implementing them. The Ranking of the reporter can be helpfull. This ranking is based on the reporting Wazer's past closure reliability, which is based on the success of past closure reports. Only closures reported by Wazers with a minimum ranking show up on the Live map.
- Ranking 1-10 - Wazer's reliability, displayed between {brackets}.
- Rating 1-5 - based on the reporting Wazer's interaction with the app.
- Severity 1-5 - based on a combination of road type, amount of traffic and the importance of the road.
After processing a bot closure report the editor should add a reply to show what has been done with the report, f.i. via an icon like 
(:c2) or 
(:wme-trash).