Waze Closures Bot: Difference between revisions View history

(Prep for publish)
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
The Waze Closures Bot is an automated chat bot for use in the Waze Discord servers developed by {{Username|WimVandierendonck}}. The Waze Closures Bot is to help assist editors in modifying and implementing closures that have been entered by Wazers.  The Waze Closures Bot is to be used in conjunction with the guidance in [[Real_time_closures|Real Time Closures]] and regional wiki guidance.
The Waze Closures Bot is an automated chat bot for use in the Waze Discord servers developed by {{Username|WimVandierendonck}}. The Waze Closures Bot is to help assist editors in modifying and implementing closures that have been entered by Wazers.  The Waze Closures Bot is to be used in conjunction with the guidance in [[Real_time_closures|Real Time Closures]] and regional wiki guidance.


==== Who Can Use It ====
==== Who can use it ====
Any editor editing in USA or Canada can use the bot if it is activated in a regional Discord channel.
Any editor editing in USA or Canada can use the bot if it is activated in a regional Discord channel.


===== Current Regions Where The Bot Is Live=====
===== Current regions where the bot is live=====


[[USA/Great Lakes|GLR (USA)]], [[USA/Mid Atlantic|MAR (USA)]], [[USA/Northeast|NOR (USA)]], [[USA/Northwest|NWR (USA)]], [[USA/Plains|PLN (USA)]], [[USA/South Atlantic|SAR (USA)]], [[USA/South Central|SCR (USA)]], [[USA/Southeast|SER (USA)]], [[USA/Southwest|SWR (USA)]],  
[[USA/Great Lakes|GLR (USA)]], [[USA/Mid Atlantic|MAR (USA)]], [[USA/Northeast|NOR (USA)]], [[USA/Northwest|NWR (USA)]], [[USA/Plains|PLN (USA)]], [[USA/South Atlantic|SAT (USA)]], [[USA/South Central|SCR (USA)]], [[USA/Southeast|SER (USA)]], [[USA/Southwest|SWR (USA)]],


==== Actions for the Editor ====
==== Actions for the editor ====
* Research the reported closures to confirm they are valid.
* Research the reported closures to confirm they are valid.
* Implement/modify the closure to make it active in the WME app. (''Functionality currently restricted to L3+)''  
* Implement/modify the closure to make it active in the WME app. (''Functionality currently restricted to L3+)''  
Line 28: Line 28:


===== Links =====
===== Links =====
'''Wazer Username''' - Opens a new editor profile tab to the reporter or commenter.<br />
'''Wazer username''' - Opens a new editor profile tab to the reporter or commenter.<br />
'''Waze Editor Username''' ''(Comments only)'' - Opens a new editor profile tab to the closing editor.<br />
'''Waze editor username''' ''(Comments only)'' - Opens a new editor profile tab to the closing editor.<br />
'''PM Link''' ''(if the Wazer has a forum account)'' - Opens a new forum PM tab allow communication to the commenter or closing editor.<br />
'''PM link''' ''(if the Wazer has a forum account)'' - Opens a new forum PM tab allow communication to the commenter or closing editor.<br />
'''Live Map''' - Opens a new Livemap tab with a point at the closure location.<br />
'''Live Map''' - Opens a new Livemap tab with a point at the closure location.<br />
'''WME''' - Opens a new Waze Map Editor (WME) tab with the closure segment highlighted.<br />
'''WME''' - Opens a new Waze Map Editor (WME) tab with the closure segment highlighted.<br />
'''App''' - Opens the Waze app at the closure location. ''hint: To reply to closures.''<br />
'''App''' - Opens the Waze app at the closure location. ''hint: To reply to closures.''<br />


====Repeat Count Color Code====
====Repeat count color code====


{| class="wikitable"
{| class="wikitable"

Latest revision as of 03:20, 19 February 2018

The Waze Closures Bot is an automated chat bot for use in the Waze Discord servers developed by WimVandierendonck (PM [Help])  . The Waze Closures Bot is to help assist editors in modifying and implementing closures that have been entered by Wazers. The Waze Closures Bot is to be used in conjunction with the guidance in Real Time Closures and regional wiki guidance.

Who can use it

Any editor editing in USA or Canada can use the bot if it is activated in a regional Discord channel.

Current regions where the bot is live

GLR (USA), MAR (USA), NOR (USA), NWR (USA), PLN (USA), SAT (USA), SCR (USA), SER (USA), SWR (USA),

Actions for the editor

  • Research the reported closures to confirm they are valid.
  • Implement/modify the closure to make it active in the WME app. (Functionality currently restricted to L3+)

Examples

Waze Closure Bot Examples
Waze Closure Bot Comment

Definitions

{?} (Wazer Ranking) - Range: 1-10
The reporting Wazer's closure reliability based on the success of past closures.
Note: L6 will always be 10 and L5 will always be 9. Only 5+ show up on LiveMap

Closure Expires In - The remaining time of the closure duration that was selected by the reporting Waze. (Unknown, Less than an hour, Several hours, All day, Several Days, or Long term).

Rating - Range: 0-5
Assigned number based on the reporting Wazer's interaction with the app. Can change over time.

Severity - Range: 1-5
Assigned number based on a combination of road type, amount of traffic and the importance of the road.

Links

Wazer username - Opens a new editor profile tab to the reporter or commenter.
Waze editor username (Comments only) - Opens a new editor profile tab to the closing editor.
PM link (if the Wazer has a forum account) - Opens a new forum PM tab allow communication to the commenter or closing editor.
Live Map - Opens a new Livemap tab with a point at the closure location.
WME - Opens a new Waze Map Editor (WME) tab with the closure segment highlighted.
App - Opens the Waze app at the closure location. hint: To reply to closures.

Repeat count color code

Color Definition
Grey New Reported closure.
Orange Same closure has been reported between 2-4 times over the previous 7 days.
Red Same closure reported at least 5 times in the previous 7 days.
Black Comment on closure from Wazer

FAQ

I have made an in app closure and it wasn't picked up by the bot how is that possible?

There are multiple possible causes.

  1. One of the rating or reliability values was too low for the closure to become visible (not on live map).
  2. The chosen duration was too short and due to the bot retrieval interval it was missed.
  3. The bot failed.