mNo edit summary |
(Marked this version for translation) |
||
| Line 8: | Line 8: | ||
Editors can easily use this data for modifying and implementing [[Closures|closures]]. The bot is developed by <i>Wim Vandierendonck</i>. | Editors can easily use this data for modifying and implementing [[Closures|closures]]. The bot is developed by <i>Wim Vandierendonck</i>. | ||
<!--T:3--> | |||
Editors who are picking up these closure reports should check their validity before implementing them. The Ranking of the reporter can be helpfull. This <i>ranking</i> 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]]. | Editors who are picking up these closure reports should check their validity before implementing them. The Ranking of the reporter can be helpfull. This <i>ranking</i> 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}. | * Ranking 1-10 - Wazer's reliability, displayed between {brackets}. | ||
| Line 14: | Line 15: | ||
* Repeat count: number of times the same closure is reported in the last 7 days. | * Repeat count: number of times the same closure is reported in the last 7 days. | ||
<!--T:4--> | |||
Only reported closures with ranking 5+ are displayed on the [[Live map]].<br /> | Only reported closures with ranking 5+ are displayed on the [[Live map]].<br /> | ||
[[File:Slack-closure-bot-nl.png|right|290px]] Slack closure reports may contain a helpfull link to the [https://www.wegstatus.nl/ Weg status site]. | [[File:Slack-closure-bot-nl.png|right|290px]] Slack closure reports may contain a helpfull link to the [https://www.wegstatus.nl/ Weg status site]. | ||
<!--T:5--> | |||
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:Bord-C1.png]] <small>(:c2)</small> or [[File:Wme-trash.png]] <small>(:wme-trash)</small>. | 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:Bord-C1.png]] <small>(:c2)</small> or [[File:Wme-trash.png]] <small>(:wme-trash)</small>. | ||
Revision as of 14:00, 31 May 2020
Closures bot
The Waze Closures Bot publishes closure data, reported via the app in the Slack BeLux Closure channels. Editors can easily use this data for modifying and implementing closures. The bot is developed by Wim Vandierendonck.
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 interaction of users with the closure.
- Severity 1-5 - based on a combination of road type, amount of traffic and the importance of the road.
- Repeat count: number of times the same closure is reported in the last 7 days.
Only reported closures with ranking 5+ are displayed on the Live map.
Slack closure reports may contain a helpfull link to the Weg status site.
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).
-
App screen closures type selection
-
Explanation of the little pictures in front of the app closure reports
