(Page creation) |
Geen bewerkingssamenvatting |
||
| (11 tussenliggende versies door dezelfde gebruiker niet weergegeven) | |||
| Regel 2: | Regel 2: | ||
<languages /><translate> | <languages /><translate> | ||
==Closures bot== | ==Closures bot== <!--T:1--> | ||
[[File:Slack-closure-bot.png|right|300px]] | [[File:Slack-closure-bot.png|right|300px]] | ||
The Waze Closures Bot publishes closure data, | The Waze Closures Bot publishes closure data, reported via the [[Waze app|app]] in the [[Slack]] Closure channel. | ||
Editors can easily use this data for modifying and implementing [[Closures|closures]]. The bot is developed by <i>WimVandierendonck</i>. <br /> | Editors can easily use this data for modifying and implementing [[Closures|closures]]. The bot is developed by <i>[[User:Wimvandierendonck|WimVandierendonck]]</i>. <br /> | ||
<br /> | <br /> | ||
Editors who are picking up these closure reports should check their validity before implementing them.<br /> | 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]].<br /> | ||
* 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. | |||
<br /> | <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]. | |||
<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>. | |||
<!--T:2--> | |||
{{clear}} | |||
<gallery mode="nolines"> | |||
App-closure-screen.png|App screen closures type selection | |||
App-closure- emoji.png|Explanation of the little pictures in front of the app closure reports | |||
</gallery> | |||
{{clear}} | |||
</translate> | </translate> | ||
__NOTOC__ | __NOTOC__ | ||
{{Bottomline}} | {{Bottomline}} | ||
Huidige versie van 26 mrt 2020 om 16:27
Closures bot
The Waze Closures Bot publishes closure data, reported via the app in the Slack Closure channel.
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 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
