https://www.waze.com/wiki/USA/api.php?action=feedcontributions&user=Vaindil&feedformat=atom
Wazeopedia - User contributions [en]
2024-03-29T00:29:54Z
User contributions
MediaWiki 1.40.2
https://www.waze.com/wiki/USA/index.php?title=Wazebot&diff=160850
Wazebot
2017-09-30T22:49:57Z
<p>Vaindil: </p>
<hr />
<div>Wazebot is an automated chat bot for use in the Waze Discord servers and Google Hangouts chats. <br />
This is not to be confused with "WazeBot" which is part of the "Feed the Waze" project.<br />
<br />
'''This page discusses the details for the Discord version of the bot. For more details on the Google Hangouts bot, see the [https://vaindil.com/wazebot Wazebot] external page.'''<br />
<br />
== Features ==<br />
<br />
==== Role Syncing ====<br />
Wazebot can sync your roles across the regional Discord servers. A limited number of roles are set by the bot for security reasons; others must be set manually and are not synced automatically. The table below gives the available roles and the permission required to set them. For example, the L6 role can only be given by champs, and only when the command is used in the national server.<br />
:''NOTE: Any command which includes @username in the table below cannot be used on yourself--it must be assigned by someone else with the appropriate permissions.''<br />
{| class="wikitable"<br />
!Role<br />
!Bot Command<br />
!Role Required<br />
|-<br />
|Country Manager (CM)<br />
|!cm @username<br />
|CM or above<br />
|-<br />
|State Manager (SM)<br />
|!sm @username<br />
|SM or above<br />
|-<br />
|Large Area Manager (LAM)<!-- The LAM role is applied in those regions that use LAMs. In other regions, the bot will assign the AM role. --><br />
|!lam @username<br />
|SM or above<br />
|-<br />
|Area Manager (AM)<br />
|!am @username<br />
|SM or above<br />
|-<br />
|Mentor<br />
|!mentor @username<br />
|SM or above<br />
|-<br />
|Region-specific<br />
|!region @username<br />
|SM or above<br />
|-<br />
|Level 6 (L6)<br />
|!l6 @username<br />
|Champ in national server<br />
|-<br />
|Level 5 (L5)<br />
|!l5 @username<br />
|SM or above<br />
|-<br />
|Level 4 (L4)<br />
|!l4 @username<br />
|SM or above<br />
|-<br />
|Level 3 (L3)<br />
|!l3 @username<br />
|SM or above<br />
|-<br />
|Level 3 (L3)<br />
|!l3<br />
|Anyone (role is assigned to command user)<br />
|-<br />
|Level 2 (L2)<br />
|!l2 @username<br />
|SM or above<br />
|-<br />
|Level 2 (L2)<br />
|!l2<br />
|Anyone (role is assigned to command user)<br />
|-<br />
|Level 1 (L1)<br />
|!l1 @username<br />
|SM or above<br />
|-<br />
|Level 1 (L1)<br />
|!l1<br />
|Anyone (role is assigned to command user)<br />
|}<br />
<br />
== Commands ==<br />
<br />
=== Glossary ===<br />
You can search for glossary terms with the command <code>!glossary</code>, using the format <code>!glossary search term</code>.<br />
<br />
=== Lookup ===<br />
Some channels may have a linked Google Spreadsheet. If your channel does, you can search it using <code>!lookup</code>. An example command is <code>!lookup search term</code>.<br />
<br />
=== Autoreplies ===<br />
An autoreply is a message that the bot will reply with automatically when a certain phrase is said in chat. Autoreplies can be created at the channel, server, or global levels. The syntax is by nature somewhat convoluted due to the features provided. To trigger an autoreply, the keyword is sent preceded by an exclamation mark <code>!</code>.<br />
<br />
Channel and server autoreplies can be set by SM+, and global autoreplies can be set only in the national server by champs.<br />
<br />
The base command is <Code>!autoreplies</code>, by itself this will bring up a list of available autoreplies for the area it is used in. To add or remove autoreplies, send the command from the server, and/or channel you want it to apply to. The command is made of four parts; '''base + action + area + trigger term + autoreply text'''.<br /><br />
'''base''' = <code>!autoreplies</code><br /><br />
'''action''' = <code>add</code> or <code>remove</code><br /><br />
'''area''' = <code>global</code>, <code>server</code>, or <code>channel</code><br /><br />
'''trigger term''' = the keyword that when typed will trigger this response. Do not include the preceding exclamation mark.<br /><br />
'''autoreply text''' = the full formatted text that should be return when the trigger term sent.<br />
<br />
Here's an example command:<br />
<br />
<code>!autoreplies add server testing This is a test.</code><br />
<br />
<code>!autoreplies remove global anothertest</code><br />
<br />
====Available autoreplies====<br />
Below is a list of some of the global autoreplies which have been set.<br />
{|class="wikitable sortable"<br />
!Trigger !! Response Text<br />
|-<br />
|!help || Link to this page<br />
|-<br />
|!copyright<br>!sources<br>!externalsources || Information about using external sources and © content<br />
|-<br />
|!nickname || Instructions to set up a proper nickname on Discord<br />
|-<br />
|!ping<br>!status || Check if bot is working<br />
|-<br />
|!source || Link to source code for the bot<br />
|-<br />
|!soon || 🔜 parody<br />
|}<br />
<br />
=== Keyword Subscriptions ===<br />
You can subscribe to keywords and the bot will message you whenever one is used in a channel that you're in. The commands are somewhat complicated because of the functionality available.<br />
<br />
==== Notes ====<br />
Keywords must be at least 2 characters long. Keywords are not case-sensitive, but regex special characters such as <code>\W</code> are respected.<br />
<br />
==== Base command ====<br />
The base command to use is <code>!keyword</code> or <code>!subscription</code>, or variants of these.<br />
<br />
==== Regular Expressions ====<br />
Regular expression keywords are supported. To use them, create a keyword as normal but wrap your regex in <code>/</code>. For example, <code>!keyword add /.*/</code>. Note that regex keywords are case-sensitive by default. To make them case-insensitive, you can add a keyword with the normal regex format but append <code>i</code> to the end: <code>!keyword add /.*/i</code>. Special identifiers like <code>\W</code> will still be preserved.<br />
<br />
==== List keywords ====<br />
Your existing keywords can be listed using <code>!keyword list</code>.<br />
<br />
==== Add a keyword ====<br />
To add a keyword, use <code>!keyword add keywordhere</code>. You can use multiple words, but note that you will only be messaged if the entire phrase you use is a match. To add multiple separate keywords, you need to use the command multiple times in individual messages.<br />
<br />
==== Remove a keyword ====<br />
Remove keywords using <code>!keyword remove keywordhere</code>. The keyword must exactly match one of your existing keywords or the command will fail.<br />
<br />
==== Ignoring keywords in servers or channels ====<br />
By default, the bot will message you if a keyword matches in any channel that you're in. You can ignore specific keywords in certain servers or channels with these commands. To find the server or channel ID, see the Getting IDs section below.<br />
<br />
===== Ignore a keyword in a server =====<br />
To ignore a server: <code>!keyword ignore server serverid keywordhere</code>. For example, you could ignore the keyword "testing" in the national server by using <code>!keyword ignore server 300471946494214146 testing</code>.<br />
<br />
===== Ignore a keyword in a channel =====<br />
Ignoring a channel uses the same syntax as ignoring a server, except the word "channel" is used instead of "server": <code>!keyword ignore channel channelid keywordhere</code>. For example, to ignore the keyword "testing" in the GLR channel on the national server, you would use <code>!keyword ignore channel 300568375900504074 testing</code>.<br />
<br />
===== Unignore a server or channel =====<br />
Unignoring a server or channel uses the same syntax as ignoring, but with the word "unignore" instead of "ignore". For example: <code>!keyword unignore server 300471946494214146 testing</code>.<br />
<br />
==== Mute servers or channels ====<br />
You can mute all keywords from a given server or channel using these commands.<br />
<br />
===== Mute a server =====<br />
Mute a server using <code>!keywords mute server serverid</code>. For example, <code>!keyword mute server 300471946494214146</code>.<br />
<br />
===== Mute a channel =====<br />
Mute a channel using <code>!keyword mute channel channelid</code>. For example, <code>!keyword mute channel 300568375900504074</code>.<br />
<br />
===== Unmute a server or channel =====<br />
Unmute a server or channel using the same commands as above, except using <code>unmute</code> instead of <code>mute</code>.<br />
<br />
== Getting IDs ==<br />
Several bot commands use either channel or server IDs to identify those channels or servers. Getting these IDs is relatively straightforward. Navigate to the channel or server that you want the ID for, and look at the URL of the page. For example, the #michigan channel in the GLR server has this URL:<br />
<br />
<code><nowiki>https://discordapp.com/channels/299563059695976451/299567520652853248</nowiki></code><br />
<br />
In all URLs, the first large number is the server ID and the second number is the channel ID. In this example, the server ID is <code>299563059695976451</code>, and the channel ID is <code>299567520652853248</code>.<br />
<br />
Alternatively, you can use the command <code>!whereami</code> and the bot will give you these IDs.<br />
<br />
'''Note that the server and channel IDs may be the same!'''<br />
<br />
== Technical ==<br />
The bot's identifier is WazeBot#1984, and its internal ID is 299667737368592385. It is written in C# and runs on .NET Core. Source code is available on [https://github.com/vaindil/wazebot-discord GitHub]. Core functionality is provided by [https://github.com/RogueException/Discord.Net Discord.Net]. Contact vaindil (vaindil#2314 on Discord) with any questions or issues.</div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=Wazebot&diff=160809
Wazebot
2017-09-28T17:50:35Z
<p>Vaindil: </p>
<hr />
<div>Wazebot is an automated chat bot for use in the Waze Discord servers and Google Hangouts chats. <br />
This is not to be confused with "WazeBot" which is part of the "Feed the Waze" project.<br />
<br />
'''This page discusses the details for the Discord version of the bot. For more details on the Google Hangouts bot, see the [https://vaindil.com/wazebot Wazebot] external page.'''<br />
<br />
== Features ==<br />
<br />
==== Role Syncing ====<br />
Wazebot can sync your roles across the regional Discord servers. A limited number of roles are set by the bot for security reasons; others must be set manually and are not synced automatically. The table below gives the available roles and the permission required to set them. For example, the L6 role can only be given by champs, and only when the command is used in the national server.<br />
:''NOTE: Any command which includes @username in the table below cannot be used on yourself--it must be assigned by someone else with the appropriate permissions.''<br />
{| class="wikitable"<br />
!Role<br />
!Bot Command<br />
!Role Required<br />
|-<br />
|Country Manager (CM)<br />
|!cm @username<br />
|CM or above<br />
|-<br />
|State Manager (SM)<br />
|!sm @username<br />
|SM or above<br />
|-<br />
|Large Area Manager (LAM)<!-- The LAM role is applied in those regions that use LAMs. In other regions, the bot will assign the AM role. --><br />
|!lam @username<br />
|SM or above<br />
|-<br />
|Area Manager (AM)<br />
|!am @username<br />
|SM or above<br />
|-<br />
|Mentor<br />
|!mentor @username<br />
|SM or above<br />
|-<br />
|Region-specific<br />
|!region @username<br />
|SM or above<br />
|-<br />
|Level 6 (L6)<br />
|!l6 @username<br />
|Champ in national server<br />
|-<br />
|Level 5 (L5)<br />
|!l5 @username<br />
|SM or above<br />
|-<br />
|Level 4 (L4)<br />
|!l4 @username<br />
|SM or above<br />
|-<br />
|Level 3 (L3)<br />
|!l3 @username<br />
|SM or above<br />
|-<br />
|Level 3 (L3)<br />
|!l3<br />
|Anyone (role is assigned to command user)<br />
|-<br />
|Level 2 (L2)<br />
|!l2 @username<br />
|SM or above<br />
|-<br />
|Level 2 (L2)<br />
|!l2<br />
|Anyone (role is assigned to command user)<br />
|-<br />
|Level 1 (L1)<br />
|!l1 @username<br />
|SM or above<br />
|-<br />
|Level 1 (L1)<br />
|!l1<br />
|Anyone (role is assigned to command user)<br />
|}<br />
<br />
== Commands ==<br />
<br />
=== Glossary ===<br />
You can search for glossary terms with the command <code>!glossary</code>, using the format <code>!glossary search term</code>.<br />
<br />
=== Lookup ===<br />
Some channels may have a linked Google Spreadsheet. If your channel does, you can search it using <code>!lookup</code>. An example command is <code>!lookup search term</code>.<br />
<br />
=== Autoreplies ===<br />
An autoreply is a message that the bot will reply with automatically when a certain phrase is said in chat. Autoreplies can be created at the channel, server, or global levels. The syntax is by nature somewhat convoluted due to the features provided. To trigger an autoreply, the keyword is sent preceded by an exclamation mark <code>!</code>.<br />
<br />
Channel and server autoreplies can be set by SM+, and global autoreplies can be set only in the national server by champs.<br />
<br />
The base command is <Code>!autoreplies</code>, by itself this will bring up a list of available autoreplies for the area it is used in. To add or remove autoreplies, send the command from the server, and/or channel you want it to apply to. The command is made of four parts; '''base + action + area + trigger term + autoreply text'''.<br /><br />
'''base''' = <code>!autoreplies</code><br /><br />
'''action''' = <code>add</code> or <code>remove</code><br /><br />
'''area''' = <code>global</code>, <code>server</code>, or <code>channel</code><br /><br />
'''trigger term''' = the keyword that when typed will trigger this response. Do not include the preceding exclamation mark.<br /><br />
'''autoreply text''' = the full formatted text that should be return when the trigger term sent.<br />
<br />
Here's an example command:<br />
<br />
<code>!autoreplies add server testing This is a test.</code><br />
<br />
<code>!autoreplies remove global anothertest</code><br />
<br />
====Available autoreplies====<br />
Below is a list of some of the global autoreplies which have been set.<br />
{|class="wikitable sortable"<br />
!Trigger !! Response Text<br />
|-<br />
|!help || Link to this page<br />
|-<br />
|!copyright<br>!sources<br>!externalsources || Information about using external sources and © content<br />
|-<br />
|!nickname || Instructions to set up a proper nickname on Discord<br />
|-<br />
|!ping<br>!status || Check if bot is working<br />
|-<br />
|!source || Link to source code for the bot<br />
|-<br />
|!soon || 🔜 parody<br />
|}<br />
<br />
=== Keyword Subscriptions ===<br />
You can subscribe to keywords and the bot will message you whenever one is used in a channel that you're in. The commands are somewhat complicated because of the functionality available.<br />
<br />
==== Notes ====<br />
Keywords must be at least 2 characters long. Keywords are not case-sensitive, but regex special characters such as <code>\W</code> are respected.<br />
<br />
==== Base command ====<br />
The base command to use is <code>!keyword</code> or <code>!subscription</code>, or variants of these.<br />
<br />
==== Regular Expressions ====<br />
Regular expression keywords are supported. To use them, create a keyword as normal but wrap your regex in <code>/</code>. For example, <code>!keyword add /.*/</code>. Note that regex keywords are case-insensitive by default. Special regex identifiers like <code>\W</code> will retain their meaning, but matches will ignore case. To make them case-sensitive, you can add a keyword with the normal regex format but append <code>s</code> to the end: <code>!keyword add /.*/s</code>.<br />
<br />
==== List keywords ====<br />
Your existing keywords can be listed using <code>!keyword list</code>.<br />
<br />
==== Add a keyword ====<br />
To add a keyword, use <code>!keyword add keywordhere</code>. You can use multiple words, but note that you will only be messaged if the entire phrase you use is a match. To add multiple separate keywords, you need to use the command multiple times in individual messages.<br />
<br />
==== Remove a keyword ====<br />
Remove keywords using <code>!keyword remove keywordhere</code>. The keyword must exactly match one of your existing keywords or the command will fail.<br />
<br />
==== Ignoring keywords in servers or channels ====<br />
By default, the bot will message you if a keyword matches in any channel that you're in. You can ignore specific keywords in certain servers or channels with these commands. To find the server or channel ID, see the Getting IDs section below.<br />
<br />
===== Ignore a keyword in a server =====<br />
To ignore a server: <code>!keyword ignore server serverid keywordhere</code>. For example, you could ignore the keyword "testing" in the national server by using <code>!keyword ignore server 300471946494214146 testing</code>.<br />
<br />
===== Ignore a keyword in a channel =====<br />
Ignoring a channel uses the same syntax as ignoring a server, except the word "channel" is used instead of "server": <code>!keyword ignore channel channelid keywordhere</code>. For example, to ignore the keyword "testing" in the GLR channel on the national server, you would use <code>!keyword ignore channel 300568375900504074 testing</code>.<br />
<br />
===== Unignore a server or channel =====<br />
Unignoring a server or channel uses the same syntax as ignoring, but with the word "unignore" instead of "ignore". For example: <code>!keyword unignore server 300471946494214146 testing</code>.<br />
<br />
==== Mute servers or channels ====<br />
You can mute all keywords from a given server or channel using these commands.<br />
<br />
===== Mute a server =====<br />
Mute a server using <code>!keywords mute server serverid</code>. For example, <code>!keyword mute server 300471946494214146</code>.<br />
<br />
===== Mute a channel =====<br />
Mute a channel using <code>!keyword mute channel channelid</code>. For example, <code>!keyword mute channel 300568375900504074</code>.<br />
<br />
===== Unmute a server or channel =====<br />
Unmute a server or channel using the same commands as above, except using <code>unmute</code> instead of <code>mute</code>.<br />
<br />
== Getting IDs ==<br />
Several bot commands use either channel or server IDs to identify those channels or servers. Getting these IDs is relatively straightforward. Navigate to the channel or server that you want the ID for, and look at the URL of the page. For example, the #michigan channel in the GLR server has this URL:<br />
<br />
<code><nowiki>https://discordapp.com/channels/299563059695976451/299567520652853248</nowiki></code><br />
<br />
In all URLs, the first large number is the server ID and the second number is the channel ID. In this example, the server ID is <code>299563059695976451</code>, and the channel ID is <code>299567520652853248</code>.<br />
<br />
Alternatively, you can use the command <code>!whereami</code> and the bot will give you these IDs.<br />
<br />
'''Note that the server and channel IDs may be the same!'''<br />
<br />
== Technical ==<br />
The bot's identifier is WazeBot#1984, and its internal ID is 299667737368592385. It is written in C# and runs on .NET Core. Source code is available on [https://github.com/vaindil/wazebot-discord GitHub]. Core functionality is provided by [https://github.com/RogueException/Discord.Net Discord.Net]. Contact vaindil (vaindil#2314 on Discord) with any questions or issues.</div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=Wazebot&diff=160808
Wazebot
2017-09-28T17:50:10Z
<p>Vaindil: </p>
<hr />
<div>Wazebot is an automated chat bot for use in the Waze Discord servers and Google Hangouts chats. <br />
This is not to be confused with "WazeBot" which is part of the "Feed the Waze" project.<br />
<br />
'''This page discusses the details for the Discord version of the bot. For more details on the Google Hangouts bot, see the [https://vaindil.com/wazebot Wazebot] external page.'''<br />
<br />
== Features ==<br />
<br />
==== Role Syncing ====<br />
Wazebot can sync your roles across the regional Discord servers. A limited number of roles are set by the bot for security reasons; others must be set manually and are not synced automatically. The table below gives the available roles and the permission required to set them. For example, the L6 role can only be given by champs, and only when the command is used in the national server.<br />
:''NOTE: Any command which includes @username in the table below cannot be used on yourself--it must be assigned by someone else with the appropriate permissions.''<br />
{| class="wikitable"<br />
!Role<br />
!Bot Command<br />
!Role Required<br />
|-<br />
|Country Manager (CM)<br />
|!cm @username<br />
|CM or above<br />
|-<br />
|State Manager (SM)<br />
|!sm @username<br />
|SM or above<br />
|-<br />
|Large Area Manager (LAM)<!-- The LAM role is applied in those regions that use LAMs. In other regions, the bot will assign the AM role. --><br />
|!lam @username<br />
|SM or above<br />
|-<br />
|Area Manager (AM)<br />
|!am @username<br />
|SM or above<br />
|-<br />
|Mentor<br />
|!mentor @username<br />
|SM or above<br />
|-<br />
|Region-specific<br />
|!region @username<br />
|SM or above<br />
|-<br />
|Level 6 (L6)<br />
|!l6 @username<br />
|Champ in national server<br />
|-<br />
|Level 5 (L5)<br />
|!l5 @username<br />
|SM or above<br />
|-<br />
|Level 4 (L4)<br />
|!l4 @username<br />
|SM or above<br />
|-<br />
|Level 3 (L3)<br />
|!l3 @username<br />
|SM or above<br />
|-<br />
|Level 3 (L3)<br />
|!l3<br />
|Anyone (role is assigned to command user)<br />
|-<br />
|Level 2 (L2)<br />
|!l2 @username<br />
|SM or above<br />
|-<br />
|Level 2 (L2)<br />
|!l2<br />
|Anyone (role is assigned to command user)<br />
|-<br />
|Level 1 (L1)<br />
|!l1 @username<br />
|SM or above<br />
|-<br />
|Level 1 (L1)<br />
|!l1<br />
|Anyone (role is assigned to command user)<br />
|}<br />
<br />
== Commands ==<br />
<br />
=== Glossary ===<br />
You can search for glossary terms with the command <code>!glossary</code>, using the format <code>!glossary search term</code>.<br />
<br />
=== Lookup ===<br />
Some channels may have a linked Google Spreadsheet. If your channel does, you can search it using <code>!lookup</code>. An example command is <code>!lookup search term</code>.<br />
<br />
=== Autoreplies ===<br />
An autoreply is a message that the bot will reply with automatically when a certain phrase is said in chat. Autoreplies can be created at the channel, server, or global levels. The syntax is by nature somewhat convoluted due to the features provided. To trigger an autoreply, the keyword is sent preceded by an exclamation mark <code>!</code>.<br />
<br />
Channel and server autoreplies can be set by SM+, and global autoreplies can be set only in the national server by champs.<br />
<br />
The base command is <Code>!autoreplies</code>, by itself this will bring up a list of available autoreplies for the area it is used in. To add or remove autoreplies, send the command from the server, and/or channel you want it to apply to. The command is made of four parts; '''base + action + area + trigger term + autoreply text'''.<br /><br />
'''base''' = <code>!autoreplies</code><br /><br />
'''action''' = <code>add</code> or <code>remove</code><br /><br />
'''area''' = <code>global</code>, <code>server</code>, or <code>channel</code><br /><br />
'''trigger term''' = the keyword that when typed will trigger this response. Do not include the preceding exclamation mark.<br /><br />
'''autoreply text''' = the full formatted text that should be return when the trigger term sent.<br />
<br />
Here's an example command:<br />
<br />
<code>!autoreplies add server testing This is a test.</code><br />
<br />
<code>!autoreplies remove global anothertest This is another test.</code><br />
<br />
====Available autoreplies====<br />
Below is a list of some of the global autoreplies which have been set.<br />
{|class="wikitable sortable"<br />
!Trigger !! Response Text<br />
|-<br />
|!help || Link to this page<br />
|-<br />
|!copyright<br>!sources<br>!externalsources || Information about using external sources and © content<br />
|-<br />
|!nickname || Instructions to set up a proper nickname on Discord<br />
|-<br />
|!ping<br>!status || Check if bot is working<br />
|-<br />
|!source || Link to source code for the bot<br />
|-<br />
|!soon || 🔜 parody<br />
|}<br />
<br />
=== Keyword Subscriptions ===<br />
You can subscribe to keywords and the bot will message you whenever one is used in a channel that you're in. The commands are somewhat complicated because of the functionality available.<br />
<br />
==== Notes ====<br />
Keywords must be at least 2 characters long. Keywords are not case-sensitive, but regex special characters such as <code>\W</code> are respected.<br />
<br />
==== Base command ====<br />
The base command to use is <code>!keyword</code> or <code>!subscription</code>, or variants of these.<br />
<br />
==== Regular Expressions ====<br />
Regular expression keywords are supported. To use them, create a keyword as normal but wrap your regex in <code>/</code>. For example, <code>!keyword add /.*/</code>. Note that regex keywords are case-insensitive by default. Special regex identifiers like <code>\W</code> will retain their meaning, but matches will ignore case. To make them case-sensitive, you can add a keyword with the normal regex format but append <code>s</code> to the end: <code>!keyword add /.*/s</code>.<br />
<br />
==== List keywords ====<br />
Your existing keywords can be listed using <code>!keyword list</code>.<br />
<br />
==== Add a keyword ====<br />
To add a keyword, use <code>!keyword add keywordhere</code>. You can use multiple words, but note that you will only be messaged if the entire phrase you use is a match. To add multiple separate keywords, you need to use the command multiple times in individual messages.<br />
<br />
==== Remove a keyword ====<br />
Remove keywords using <code>!keyword remove keywordhere</code>. The keyword must exactly match one of your existing keywords or the command will fail.<br />
<br />
==== Ignoring keywords in servers or channels ====<br />
By default, the bot will message you if a keyword matches in any channel that you're in. You can ignore specific keywords in certain servers or channels with these commands. To find the server or channel ID, see the Getting IDs section below.<br />
<br />
===== Ignore a keyword in a server =====<br />
To ignore a server: <code>!keyword ignore server serverid keywordhere</code>. For example, you could ignore the keyword "testing" in the national server by using <code>!keyword ignore server 300471946494214146 testing</code>.<br />
<br />
===== Ignore a keyword in a channel =====<br />
Ignoring a channel uses the same syntax as ignoring a server, except the word "channel" is used instead of "server": <code>!keyword ignore channel channelid keywordhere</code>. For example, to ignore the keyword "testing" in the GLR channel on the national server, you would use <code>!keyword ignore channel 300568375900504074 testing</code>.<br />
<br />
===== Unignore a server or channel =====<br />
Unignoring a server or channel uses the same syntax as ignoring, but with the word "unignore" instead of "ignore". For example: <code>!keyword unignore server 300471946494214146 testing</code>.<br />
<br />
==== Mute servers or channels ====<br />
You can mute all keywords from a given server or channel using these commands.<br />
<br />
===== Mute a server =====<br />
Mute a server using <code>!keywords mute server serverid</code>. For example, <code>!keyword mute server 300471946494214146</code>.<br />
<br />
===== Mute a channel =====<br />
Mute a channel using <code>!keyword mute channel channelid</code>. For example, <code>!keyword mute channel 300568375900504074</code>.<br />
<br />
===== Unmute a server or channel =====<br />
Unmute a server or channel using the same commands as above, except using <code>unmute</code> instead of <code>mute</code>.<br />
<br />
== Getting IDs ==<br />
Several bot commands use either channel or server IDs to identify those channels or servers. Getting these IDs is relatively straightforward. Navigate to the channel or server that you want the ID for, and look at the URL of the page. For example, the #michigan channel in the GLR server has this URL:<br />
<br />
<code><nowiki>https://discordapp.com/channels/299563059695976451/299567520652853248</nowiki></code><br />
<br />
In all URLs, the first large number is the server ID and the second number is the channel ID. In this example, the server ID is <code>299563059695976451</code>, and the channel ID is <code>299567520652853248</code>.<br />
<br />
Alternatively, you can use the command <code>!whereami</code> and the bot will give you these IDs.<br />
<br />
'''Note that the server and channel IDs may be the same!'''<br />
<br />
== Technical ==<br />
The bot's identifier is WazeBot#1984, and its internal ID is 299667737368592385. It is written in C# and runs on .NET Core. Source code is available on [https://github.com/vaindil/wazebot-discord GitHub]. Core functionality is provided by [https://github.com/RogueException/Discord.Net Discord.Net]. Contact vaindil (vaindil#2314 on Discord) with any questions or issues.</div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=Wazebot&diff=159758
Wazebot
2017-08-21T23:18:16Z
<p>Vaindil: </p>
<hr />
<div>Wazebot is an automated chat bot for use in the Waze Discord servers and Google Hangouts chats. <br />
This is not to be confused with "WazeBot" which is part of the "Feed the Waze" project.<br />
<br />
'''This page discusses the details for the Discord version of the bot. For more details on the Google Hangouts bot, see the [https://vaindil.com/wazebot Wazebot] external page.'''<br />
<br />
== Features ==<br />
<br />
==== Role Syncing ====<br />
Wazebot can sync your roles across the regional Discord servers. A limited number of roles are set by the bot for security reasons; others must be set manually and are not synced automatically. The table below gives the available roles and the permission required to set them. For example, the L6 role can only be given by champs, and only when the command is used in the national server.<br />
:''NOTE: Any command which includes @username in the table below cannot be used on yourself--it must be assigned by someone else with the appropriate permissions.''<br />
{| class="wikitable"<br />
!Role<br />
!Bot Command<br />
!Role Required<br />
|-<br />
|Country Manager (CM)<br />
|!cm @username<br />
|CM or above<br />
|-<br />
|State Manager (SM)<br />
|!sm @username<br />
|SM or above<br />
|-<br />
|Large Area Manager (LAM)<!-- The LAM role is applied in those regions that use LAMs. In other regions, the bot will assign the AM role. --><br />
|!lam @username<br />
|SM or above<br />
|-<br />
|Area Manager (AM)<br />
|!am @username<br />
|SM or above<br />
|-<br />
|Mentor<br />
|!mentor @username<br />
|SM or above<br />
|-<br />
|Region-specific<br />
|!region @username<br />
|SM or above<br />
|-<br />
|Level 6 (L6)<br />
|!l6 @username<br />
|Champ in national server<br />
|-<br />
|Level 5 (L5)<br />
|!l5 @username<br />
|SM or above<br />
|-<br />
|Level 4 (L4)<br />
|!l4 @username<br />
|SM or above<br />
|-<br />
|Level 3 (L3)<br />
|!l3 @username<br />
|SM or above<br />
|-<br />
|Level 3 (L3)<br />
|!l3<br />
|Anyone (role is assigned to command user)<br />
|-<br />
|Level 2 (L2)<br />
|!l2 @username<br />
|SM or above<br />
|-<br />
|Level 2 (L2)<br />
|!l2<br />
|Anyone (role is assigned to command user)<br />
|-<br />
|Level 1 (L1)<br />
|!l1 @username<br />
|SM or above<br />
|-<br />
|Level 1 (L1)<br />
|!l1<br />
|Anyone (role is assigned to command user)<br />
|}<br />
<br />
== Commands ==<br />
<br />
=== Glossary ===<br />
You can search for glossary terms with the command <code>!glossary</code>, using the format <code>!glossary search term</code>.<br />
<br />
=== Lookup ===<br />
Some channels may have a linked Google Spreadsheet. If your channel does, you can search it using <code>!lookup</code>. An example command is <code>!lookup search term</code>.<br />
<br />
=== Autoreplies ===<br />
An autoreply is a message that the bot will reply with automatically when a certain phrase is said in chat. Autoreplies can be created at the channel, server, or global levels. The syntax is by nature somewhat convoluted due to the features provided. To trigger an autoreply, the keyword is sent preceded by an exclamation mark <code>!</code>.<br />
<br />
Channel and server autoreplies can be set by SM+, and global autoreplies can be set only in the national server by champs.<br />
<br />
The base command is <Code>!autoreplies</code>, by itself this will bring up a list of available autoreplies for the area it is used in. To add or remove autoreplies, send the command from the server, and/or channel you want it to apply to. The command is made of four parts; '''base + action + area + trigger term + autoreply text'''.<br /><br />
'''base''' = <code>!autoreplies</code><br /><br />
'''action''' = <code>add</code> or <code>remove</code><br /><br />
'''area''' = <code>global</code>, <code>server</code>, or <code>channel</code><br /><br />
'''trigger term''' = the keyword that when typed will trigger this response. Do not include the preceding exclamation mark.<br /><br />
'''autoreply text''' = the full formatted text that should be return when the trigger term sent.<br />
<br />
Here's an example command:<br />
<br />
<code>!autoreplies add server testing This is a test.</code><br />
<br />
<code>!autoreplies remove global anothertest This is another test.</code><br />
<br />
====Available autoreplies====<br />
Below is a list of some of the global autoreplies which have been set.<br />
{|class="wikitable sortable"<br />
!Trigger !! Response Text<br />
|-<br />
|!help || Link to this page<br />
|-<br />
|!copyright<br>!sources<br>!externalsources || Information about using external sources and © content<br />
|-<br />
|!nickname || Instructions to set up a proper nickname on Discord<br />
|-<br />
|!ping<br>!status || Check if bot is working<br />
|-<br />
|!source || Link to source code for the bot<br />
|-<br />
|!soon || 🔜 parody<br />
|}<br />
<br />
=== Keyword Subscriptions ===<br />
You can subscribe to keywords and the bot will message you whenever one is used in a channel that you're in. The commands are somewhat complicated because of the functionality available.<br />
<br />
==== Notes ====<br />
Keywords must be at least 2 characters long. Keywords are not case-sensitive, but regex special characters such as <code>\W</code> are respected.<br />
<br />
==== Base command ====<br />
The base command to use is <code>!keyword</code> or <code>!subscription</code>, or variants of these.<br />
<br />
==== Regular Expressions ====<br />
Regular expression keywords are supported. To use them, create a keyword as normal but wrap your regex in <code>/</code>. For example, <code>!keyword add /.*/</code>.<br />
<br />
==== List keywords ====<br />
Your existing keywords can be listed using <code>!keyword list</code>.<br />
<br />
==== Add a keyword ====<br />
To add a keyword, use <code>!keyword add keywordhere</code>. You can use multiple words, but note that you will only be messaged if the entire phrase you use is a match. To add multiple separate keywords, you need to use the command multiple times in individual messages.<br />
<br />
==== Remove a keyword ====<br />
Remove keywords using <code>!keyword remove keywordhere</code>. The keyword must exactly match one of your existing keywords or the command will fail.<br />
<br />
==== Ignoring keywords in servers or channels ====<br />
By default, the bot will message you if a keyword matches in any channel that you're in. You can ignore specific keywords in certain servers or channels with these commands. To find the server or channel ID, see the Getting IDs section below.<br />
<br />
===== Ignore a keyword in a server =====<br />
To ignore a server: <code>!keyword ignore server serverid keywordhere</code>. For example, you could ignore the keyword "testing" in the national server by using <code>!keyword ignore server 300471946494214146 testing</code>.<br />
<br />
===== Ignore a keyword in a channel =====<br />
Ignoring a channel uses the same syntax as ignoring a server, except the word "channel" is used instead of "server": <code>!keyword ignore channel channelid keywordhere</code>. For example, to ignore the keyword "testing" in the GLR channel on the national server, you would use <code>!keyword ignore channel 300568375900504074 testing</code>.<br />
<br />
===== Unignore a server or channel =====<br />
Unignoring a server or channel uses the same syntax as ignoring, but with the word "unignore" instead of "ignore". For example: <code>!keyword unignore server 300471946494214146 testing</code>.<br />
<br />
==== Mute servers or channels ====<br />
You can mute all keywords from a given server or channel using these commands.<br />
<br />
===== Mute a server =====<br />
Mute a server using <code>!keywords mute server serverid</code>. For example, <code>!keyword mute server 300471946494214146</code>.<br />
<br />
===== Mute a channel =====<br />
Mute a channel using <code>!keyword mute channel channelid</code>. For example, <code>!keyword mute channel 300568375900504074</code>.<br />
<br />
===== Unmute a server or channel =====<br />
Unmute a server or channel using the same commands as above, except using <code>unmute</code> instead of <code>mute</code>.<br />
<br />
== Getting IDs ==<br />
Several bot commands use either channel or server IDs to identify those channels or servers. Getting these IDs is relatively straightforward. Navigate to the channel or server that you want the ID for, and look at the URL of the page. For example, the #michigan channel in the GLR server has this URL:<br />
<br />
<code><nowiki>https://discordapp.com/channels/299563059695976451/299567520652853248</nowiki></code><br />
<br />
In all URLs, the first large number is the server ID and the second number is the channel ID. In this example, the server ID is <code>299563059695976451</code>, and the channel ID is <code>299567520652853248</code>.<br />
<br />
Alternatively, you can use the command <code>!whereami</code> and the bot will give you these IDs.<br />
<br />
'''Note that the server and channel IDs may be the same!'''<br />
<br />
== Technical ==<br />
The bot's identifier is WazeBot#1984, and its internal ID is 299667737368592385. It is written in C# and runs on .NET Core. Source code is available on [https://github.com/vaindil/wazebot-discord GitHub]. Core functionality is provided by [https://github.com/RogueException/Discord.Net Discord.Net]. Contact vaindil (vaindil#2314 on Discord) with any questions or issues.</div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=Wazebot&diff=159703
Wazebot
2017-08-18T17:54:14Z
<p>Vaindil: </p>
<hr />
<div>Wazebot is an automated chat bot for use in the Waze Discord servers and Google Hangouts chats. <br />
This is not to be confused with "WazeBot" which is part of the "Feed the Waze" project.<br />
<br />
'''This page discusses the details for the Discord version of the bot. For more details on the Google Hangouts bot, see the [https://vaindil.com/wazebot Wazebot] external page.'''<br />
<br />
== Features ==<br />
<br />
==== Role Syncing ====<br />
Wazebot can sync your roles across the regional Discord servers. A limited number of roles are set by the bot for security reasons; others must be set manually and are not synced automatically. The table below gives the available roles and the permission required to set them. For example, the L6 role can only be given by champs, and only when the command is used in the national server.<br />
:''NOTE: Any command which includes @username can not be used for yourself, it must be assigned by someone else.''<br />
{| class="wikitable"<br />
!Role<br />
!Bot Command<br />
!Role Required<br />
|-<br />
|Country Manager (CM)<br />
|!cm @username<br />
|CM or above<br />
|-<br />
|State Manager (SM)<br />
|!sm @username<br />
|SM or above<br />
|-<br />
|Large Area Manager (LAM)<!-- The LAM role is applied in those regions that use LAMs. In other regions, the bot will assign the AM role. --><br />
|!lam @username<br />
|SM or above<br />
|-<br />
|Area Manager (AM)<br />
|!am @username<br />
|SM or above<br />
|-<br />
|Mentor<br />
|!mentor @username<br />
|SM or above<br />
|-<br />
|Region-specific<br />
|!region @username<br />
|SM or above<br />
|-<br />
|Level 6 (L6)<br />
|!l6 @username<br />
|Champ in national server<br />
|-<br />
|Level 5 (L5)<br />
|!l5 @username<br />
|SM or above<br />
|-<br />
|Level 4 (L4)<br />
|!l4 @username<br />
|SM or above<br />
|-<br />
|Level 3 (L3)<br />
|!l3<br />
|Anyone (role is assigned to command user)<br />
|-<br />
|Level 2 (L2)<br />
|!l2<br />
|Anyone (role is assigned to command user)<br />
|-<br />
|Level 1 (L1)<br />
|!l1<br />
|Anyone (role is assigned to command user)<br />
|}<br />
<br />
== Commands ==<br />
<br />
=== Glossary ===<br />
You can search for glossary terms with the command <code>!glossary</code>, using the format <code>!glossary search term</code>.<br />
<br />
=== Lookup ===<br />
Some channels may have a linked Google Spreadsheet. If your channel does, you can search it using <code>!lookup</code>. An example command is <code>!lookup search term</code>.<br />
<br />
=== Autoreplies ===<br />
An autoreply is a message that the bot will reply with automatically when a certain phrase is said in chat. Autoreplies can be created at the channel, server, or global levels. The syntax is by nature somewhat convoluted due to the features provided. To trigger an autoreply, the keyword is sent preceded by an exclamation mark <code>!</code>.<br />
<br />
Channel and server autoreplies can be set by SM+, and global autoreplies can be set only in the national server by champs.<br />
<br />
The base command is <Code>!autoreplies</code>, by itself this will bring up a list of available autoreplies for the area it is used in. To add or remove autoreplies, send the command from the server, and/or channel you want it to apply to. The command is made of four parts; '''base + action + area + trigger term + autoreply text'''.<br /><br />
'''base''' = <code>!autoreplies</code><br /><br />
'''action''' = <code>add</code> or <code>remove</code><br /><br />
'''area''' = <code>global</code>, <code>server</code>, or <code>channel</code><br /><br />
'''trigger term''' = the keyword that when typed will trigger this response. Do not include the preceding exclamation mark.<br /><br />
'''autoreply text''' = the full formatted text that should be return when the trigger term sent.<br />
<br />
Here's an example command:<br />
<br />
<code>!autoreplies add server testing This is a test.</code><br />
<br />
<code>!autoreplies remove global anothertest This is another test.</code><br />
<br />
====Available autoreplies====<br />
Below is a list of some of the global autoreplies which have been set.<br />
{|class="wikitable sortable"<br />
!Trigger !! Response Text<br />
|-<br />
|!help || Link to this page<br />
|-<br />
|!copyright<br>!sources<br>!externalsources || Information about using external sources and © content<br />
|-<br />
|!nickname || Instructions to set up a proper nickname on Discord<br />
|-<br />
|!ping<br>!status || Check if bot is working<br />
|-<br />
|!source || Link to source code for the bot<br />
|-<br />
|!soon || 🔜 parody<br />
|}<br />
<br />
=== Keyword Subscriptions ===<br />
You can subscribe to keywords and the bot will message you whenever one is used in a channel that you're in. The commands are somewhat complicated because of the functionality available.<br />
<br />
==== Notes ====<br />
Keywords must be at least 2 characters long. Keywords are not case-sensitive, but regex special characters such as <code>\W</code> are respected.<br />
<br />
==== Base command ====<br />
The base command to use is <code>!keyword</code> or <code>!subscription</code>, or variants of these.<br />
<br />
==== Regular Expressions ====<br />
Regular expression keywords are supported. To use them, create a keyword as normal but wrap your regex in <code>/</code>. For example, <code>!keyword add /.*/</code>.<br />
<br />
==== List keywords ====<br />
Your existing keywords can be listed using <code>!keyword list</code>.<br />
<br />
==== Add a keyword ====<br />
To add a keyword, use <code>!keyword add keywordhere</code>. You can use multiple words, but note that you will only be messaged if the entire phrase you use is a match. To add multiple separate keywords, you need to use the command multiple times in individual messages.<br />
<br />
==== Remove a keyword ====<br />
Remove keywords using <code>!keyword remove keywordhere</code>. The keyword must exactly match one of your existing keywords or the command will fail.<br />
<br />
==== Ignoring keywords in servers or channels ====<br />
By default, the bot will message you if a keyword matches in any channel that you're in. You can ignore specific keywords in certain servers or channels with these commands. To find the server or channel ID, see the Getting IDs section below.<br />
<br />
===== Ignore a keyword in a server =====<br />
To ignore a server: <code>!keyword ignore server serverid keywordhere</code>. For example, you could ignore the keyword "testing" in the national server by using <code>!keyword ignore server 300471946494214146 testing</code>.<br />
<br />
===== Ignore a keyword in a channel =====<br />
Ignoring a channel uses the same syntax as ignoring a server, except the word "channel" is used instead of "server": <code>!keyword ignore channel channelid keywordhere</code>. For example, to ignore the keyword "testing" in the GLR channel on the national server, you would use <code>!keyword ignore channel 300568375900504074 testing</code>.<br />
<br />
===== Unignore a server or channel =====<br />
Unignoring a server or channel uses the same syntax as ignoring, but with the word "unignore" instead of "ignore". For example: <code>!keyword unignore server 300471946494214146 testing</code>.<br />
<br />
==== Mute servers or channels ====<br />
You can mute all keywords from a given server or channel using these commands.<br />
<br />
===== Mute a server =====<br />
Mute a server using <code>!keywords mute server serverid</code>. For example, <code>!keyword mute server 300471946494214146</code>.<br />
<br />
===== Mute a channel =====<br />
Mute a channel using <code>!keyword mute channel channelid</code>. For example, <code>!keyword mute channel 300568375900504074</code>.<br />
<br />
===== Unmute a server or channel =====<br />
Unmute a server or channel using the same commands as above, except using <code>unmute</code> instead of <code>mute</code>.<br />
<br />
== Getting IDs ==<br />
Several bot commands use either channel or server IDs to identify those channels or servers. Getting these IDs is relatively straightforward. Navigate to the channel or server that you want the ID for, and look at the URL of the page. For example, the #michigan channel in the GLR server has this URL:<br />
<br />
<code><nowiki>https://discordapp.com/channels/299563059695976451/299567520652853248</nowiki></code><br />
<br />
In all URLs, the first large number is the server ID and the second number is the channel ID. In this example, the server ID is <code>299563059695976451</code>, and the channel ID is <code>299567520652853248</code>.<br />
<br />
Alternatively, you can use the command <code>!whereami</code> and the bot will give you these IDs.<br />
<br />
'''Note that the server and channel IDs may be the same!'''<br />
<br />
== Technical ==<br />
The bot's identifier is WazeBot#1984, and its internal ID is 299667737368592385. It is written in C# and runs on .NET Core. Source code is available on [https://github.com/vaindil/wazebot-discord GitHub]. Core functionality is provided by [https://github.com/RogueException/Discord.Net Discord.Net]. Contact vaindil (vaindil#2314 on Discord) with any questions or issues.</div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=Wazebot&diff=159229
Wazebot
2017-07-23T18:42:31Z
<p>Vaindil: </p>
<hr />
<div>Wazebot is an automated chat bot for use in the Waze Discord servers and Google Hangouts chats. <br />
This is not to be confused with "WazeBot" which is part of the "Feed the Waze" project.<br />
<br />
'''This page discusses the details for the Discord version of the bot. For more details on the Google Hangouts bot, see the [https://vaindil.com/wazebot Wazebot] external page.'''<br />
<br />
== Features ==<br />
<br />
==== Role Syncing ====<br />
Wazebot can sync your roles across the regional Discord servers. A limited number of roles are set by the bot for security reasons; others must be set manually and are not synced automatically. The table below gives the available roles and the permission required to set them. For example, the L6 role can only be given by champs, and only when the command is used in the national server.<br />
{| class="wikitable"<br />
!Role<br />
!Bot Command<br />
!Role Required<br />
|-<br />
|Country Manager (CM)<br />
|!cm @username<br />
|CM or above<br />
|-<br />
|State Manager (SM)<br />
|!sm @username<br />
|SM or above<br />
|-<br />
|Large Area Manager (LAM)<!-- The LAM role is applied in those regions that use LAMs. In other regions, the bot will assign the AM role. --><br />
|!lam @username<br />
|SM or above<br />
|-<br />
|Area Manager (AM)<br />
|!am @username<br />
|SM or above<br />
|-<br />
|Mentor<br />
|!mentor @username<br />
|SM or above<br />
|-<br />
|Region-specific<br />
|!region @username<br />
|SM or above<br />
|-<br />
|Level 6 (L6)<br />
|!l6 @username<br />
|Champ in national server<br />
|-<br />
|Level 5 (L5)<br />
|!l5 @username<br />
|SM or above<br />
|-<br />
|Level 4 (L4)<br />
|!l4 @username<br />
|SM or above<br />
|-<br />
|Level 3 (L3)<br />
|!l3<br />
|Anyone (role is assigned to command user)<br />
|-<br />
|Level 2 (L2)<br />
|!l2<br />
|Anyone (role is assigned to command user)<br />
|-<br />
|Level 1 (L1)<br />
|!l1<br />
|Anyone (role is assigned to command user)<br />
|}<br />
<br />
== Commands ==<br />
<br />
=== Glossary ===<br />
You can search for glossary terms with the command <code>!glossary</code>, using the format <code>!glossary search term</code>.<br />
<br />
=== Lookup ===<br />
Some channels may have a linked Google Spreadsheet. If your channel does, you can search it using <code>!lookup</code>. An example command is <code>!lookup search term</code>.<br />
<br />
=== Autoreplies ===<br />
An autoreply is a message that the bot will reply with automatically when a certain phrase is said in chat. Autoreplies can be created at the channel, server, or global levels. The syntax is by nature somewhat convoluted due to the features provided. To trigger an autoreply, the keyword is sent preceded by an exclamation mark <code>!</code>.<br />
<br />
Channel and server autoreplies can be set by SM+, and global autoreplies can be set only in the national server by champs.<br />
<br />
The base command is <Code>!autoreplies</code>, by itself this will bring up a list of available autoreplies for the area it is used in. To add or remove autoreplies, send the command from the server, and/or channel you want it to apply to. The command is made of four parts; '''base + action + area + trigger term + autoreply text'''.<br /><br />
'''base''' = <code>!autoreplies</code><br /><br />
'''action''' = <code>add</code> or <code>remove</code><br /><br />
'''area''' = <code>global</code>, <code>server</code>, or <code>channel</code><br /><br />
'''trigger term''' = the keyword that when typed will trigger this response. Do not include the preceding exclamation mark.<br /><br />
'''autoreply text''' = the full formatted text that should be return when the trigger term sent.<br />
<br />
Here's an example command:<br />
<br />
<code>!autoreplies add server testing This is a test.</code><br />
<br />
<code>!autoreplies remove global anothertest This is another test.</code><br />
<br />
====Available autoreplies====<br />
Below is a list of some of the global autoreplies which have been set.<br />
{|class="wikitable sortable"<br />
!Trigger !! Response Text<br />
|-<br />
|!help || Link to this page<br />
|-<br />
|!copyright<br>!sources<br>!externalsources || Information about using external sources and © content<br />
|-<br />
|!source || Link to source code for the bot<br />
|-<br />
|!soon || 🔜 parody<br />
|}<br />
<br />
=== Keyword Subscriptions ===<br />
You can subscribe to keywords and the bot will message you whenever one is used in a channel that you're in. The commands are somewhat complicated because of the functionality available.<br />
<br />
==== Notes ====<br />
Keywords must be at least 3 characters long and are not case-sensitive.<br />
<br />
==== Base command ====<br />
The base command to use is <code>!keyword</code> or <code>!subscription</code>, or variants of these.<br />
<br />
==== Regular Expressions ====<br />
Regular expression keywords are supported. To use them, create a keyword as normal but wrap your regex in <code>/</code>. For example, <code>!keyword add /.*/</code>.<br />
<br />
==== List keywords ====<br />
Your existing keywords can be listed using <code>!keyword list</code>.<br />
<br />
==== Add a keyword ====<br />
To add a keyword, use <code>!keyword add keywordhere</code>. You can use multiple words, but note that you will only be messaged if the entire phrase you use is a match. To add multiple separate keywords, you need to use the command multiple times in individual messages.<br />
<br />
==== Remove a keyword ====<br />
Remove keywords using <code>!keyword remove keywordhere</code>. The keyword must exactly match one of your existing keywords or the command will fail.<br />
<br />
==== Ignoring keywords in servers or channels ====<br />
By default, the bot will message you if a keyword matches in any channel that you're in. You can ignore specific keywords in certain servers or channels with these commands. To find the server or channel ID, see the Getting IDs section below.<br />
<br />
===== Ignore a keyword in a server =====<br />
To ignore a server: <code>!keyword ignore server serverid keywordhere</code>. For example, you could ignore the keyword "testing" in the national server by using <code>!keyword ignore server 300471946494214146 testing</code>.<br />
<br />
===== Ignore a keyword in a channel =====<br />
Ignoring a channel uses the same syntax as ignoring a server, except the word "channel" is used instead of "server": <code>!keyword ignore channel channelid keywordhere</code>. For example, to ignore the keyword "testing" in the GLR channel on the national server, you would use <code>!keyword ignore channel 300568375900504074 testing</code>.<br />
<br />
===== Unignore a server or channel =====<br />
Unignoring a server or channel uses the same syntax as ignoring, but with the word "unignore" instead of "ignore". For example: <code>!keyword unignore server 300471946494214146 testing</code>.<br />
<br />
==== Mute servers or channels ====<br />
You can mute all keywords from a given server or channel using these commands.<br />
<br />
===== Mute a server =====<br />
Mute a server using <code>!keywords mute server serverid</code>. For example, <code>!keyword mute server 300471946494214146</code>.<br />
<br />
===== Mute a channel =====<br />
Mute a channel using <code>!keyword mute channel channelid</code>. For example, <code>!keyword mute channel 300568375900504074</code>.<br />
<br />
===== Unmute a server or channel =====<br />
Unmute a server or channel using the same commands as above, except using <code>unmute</code> instead of <code>mute</code>.<br />
<br />
== Getting IDs ==<br />
Several bot commands use either channel or server IDs to identify those channels or servers. Getting these IDs is relatively straightforward. Navigate to the channel or server that you want the ID for, and look at the URL of the page. For example, the #michigan channel in the GLR server has this URL:<br />
<br />
<code><nowiki>https://discordapp.com/channels/299563059695976451/299567520652853248</nowiki></code><br />
<br />
In all URLs, the first large number is the server ID and the second number is the channel ID. In this example, the server ID is <code>299563059695976451</code>, and the channel ID is <code>299567520652853248</code>.<br />
<br />
Alternatively, you can use the command <code>!whereami</code> and the bot will give you these IDs.<br />
<br />
'''Note that the server and channel IDs may be the same!'''<br />
<br />
== Technical ==<br />
The bot's identifier is WazeBot#1984, and its internal ID is 299667737368592385. It is written in C# and runs on .NET Core. Source code is available on [https://github.com/vaindil/wazebot-discord GitHub]. Core functionality is provided by [https://github.com/RogueException/Discord.Net Discord.Net]. Contact vaindil (vaindil#2314 on Discord) with any questions or issues.</div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=Wazebot&diff=159222
Wazebot
2017-07-22T21:07:25Z
<p>Vaindil: </p>
<hr />
<div>Wazebot is an automated chat bot for use in the Waze Discord servers and Google Hangouts chats. <br />
This is not to be confused with "WazeBot" which is part of the "Feed the Waze" project.<br />
<br />
'''This page discusses the details for the Discord version of the bot. For more details on the Google Hangouts bot, see the [https://vaindil.com/wazebot Wazebot] external page.'''<br />
<br />
== Features ==<br />
<br />
==== Role Syncing ====<br />
Wazebot can sync your roles across the regional Discord servers. A limited number of roles are set by the bot for security reasons; others must be set manually and are not synced automatically. The table below gives the available roles and the permission required to set them. For example, the L6 role can only be given by champs, and only when the command is used in the national server.<br />
{| class="wikitable"<br />
!Role<br />
!Bot Command<br />
!Role Required<br />
|-<br />
|Country Manager (CM)<br />
|!cm @username<br />
|CM or above<br />
|-<br />
|State Manager (SM)<br />
|!sm @username<br />
|SM or above<br />
|-<br />
|Large Area Manager (LAM)<!-- The LAM role is applied in those regions that use LAMs. In other regions, the bot will assign the AM role. --><br />
|!lam @username<br />
|SM or above<br />
|-<br />
|Area Manager (AM)<br />
|!am @username<br />
|SM or above<br />
|-<br />
|Mentor<br />
|!mentor @username<br />
|SM or above<br />
|-<br />
|Region-specific<br />
|!region @username<br />
|SM or above<br />
|-<br />
|Level 6 (L6)<br />
|!l6 @username<br />
|Champ in national server<br />
|-<br />
|Level 5 (L5)<br />
|!l5 @username<br />
|SM or above<br />
|-<br />
|Level 4 (L4)<br />
|!l4 @username<br />
|SM or above<br />
|-<br />
|Level 3 (L3)<br />
|!l3<br />
|Anyone (role is assigned to command user)<br />
|-<br />
|Level 2 (L2)<br />
|!l2<br />
|Anyone (role is assigned to command user)<br />
|-<br />
|Level 1 (L1)<br />
|!l1<br />
|Anyone (role is assigned to command user)<br />
|}<br />
<br />
== Commands ==<br />
<br />
=== Glossary ===<br />
You can search for glossary terms with the command <code>!glossary</code>, using the format <code>!glossary search term</code>.<br />
<br />
=== Lookup ===<br />
Some channels may have a linked Google Spreadsheet. If your channel does, you can search it using <code>!lookup</code>. An example command is <code>!lookup search term</code>.<br />
<br />
=== Autoreplies ===<br />
An autoreply is a message that the bot will reply with automatically when a certain phrase is said in chat. Autoreplies can be created at the channel, server, or global levels. The syntax is by nature somewhat convoluted due to the features provided. To trigger an autoreply, the keyword is sent preceded by an exclamation mark <code>!</code>.<br />
<br />
Channel and server autoreplies can be set by SM+, and global autoreplies can be set only in the national server by champs.<br />
<br />
The base command is <Code>!autoreplies</code>, by itself this will bring up a list of available autoreplies for the area it is used in. To add or remove autoreplies, send the command from the server, and/or channel you want it to apply to. The command is made of four parts; '''base + action + area + trigger term + autoreply text'''.<br /><br />
'''base''' = <code>!autoreplies</code><br /><br />
'''action''' = <code>add</code> or <code>remove</code><br /><br />
'''area''' = <code>global</code>, <code>server</code>, or <code>channel</code><br /><br />
'''trigger term''' = the keyword that when typed will trigger this response. Do not include the preceding exclamation mark.<br /><br />
'''autoreply text''' = the full formatted text that should be return when the trigger term sent.<br />
<br />
Here's an example command:<br />
<br />
<code>!autoreplies add server testing This is a test.</code><br />
<br />
<code>!autoreplies remove global anothertest This is another test.</code><br />
<br />
===Available autoreplies===<br />
Below is a list of some of the global autoreplies which have been set.<br />
{|class="wikitable sortable"<br />
!Trigger !! Response Text<br />
|-<br />
|!help || Link to this page<br />
|-<br />
|!copyright<br>!sources<br>!externalsources || Information about using external sources and © content<br />
|-<br />
|!source || Link to source code for the bot<br />
|-<br />
|!soon || 🔜 parody<br />
|}<br />
<br />
=== Keyword Subscriptions ===<br />
You can subscribe to keywords and the bot will message you whenever one is used in a channel that you're in. The commands are somewhat complicated because of the functionality available.<br />
<br />
==== Notes ====<br />
Keywords must be at least 3 characters long and are not case-sensitive.<br />
<br />
==== Base command ====<br />
The base command to use is <code>!keyword</code> or <code>!subscription</code>, or variants of these.<br />
<br />
==== List keywords ====<br />
Your existing keywords can be listed using <code>!keyword list</code>.<br />
<br />
==== Add a keyword ====<br />
To add a keyword, use <code>!keyword add keywordhere</code>. You can use multiple words, but note that you will only be messaged if the entire phrase you use is a match. To add multiple separate keywords, you need to use the command multiple times in individual messages.<br />
<br />
==== Remove a keyword ====<br />
Remove keywords using <code>!keyword remove keywordhere</code>. The keyword must exactly match one of your existing keywords or the command will fail.<br />
<br />
==== Ignoring keywords in servers or channels ====<br />
By default, the bot will message you if a keyword matches in any channel that you're in. You can ignore specific keywords in certain servers or channels with these commands. To find the server or channel ID, see the Getting IDs section below.<br />
<br />
===== Ignore a keyword in a server =====<br />
To ignore a server: <code>!keyword ignore server serverid keywordhere</code>. For example, you could ignore the keyword "testing" in the national server by using <code>!keyword ignore server 300471946494214146 testing</code>.<br />
<br />
===== Ignore a keyword in a channel =====<br />
Ignoring a channel uses the same syntax as ignoring a server, except the word "channel" is used instead of "server": <code>!keyword ignore channel channelid keywordhere</code>. For example, to ignore the keyword "testing" in the GLR channel on the national server, you would use <code>!keyword ignore channel 300568375900504074 testing</code>.<br />
<br />
===== Unignore a server or channel =====<br />
Unignoring a server or channel uses the same syntax as ignoring, but with the word "unignore" instead of "ignore". For example: <code>!keyword unignore server 300471946494214146 testing</code>.<br />
<br />
==== Mute servers or channels ====<br />
You can mute all keywords from a given server or channel using these commands.<br />
<br />
===== Mute a server =====<br />
Mute a server using <code>!keywords mute server serverid</code>. For example, <code>!keyword mute server 300471946494214146</code>.<br />
<br />
===== Mute a channel =====<br />
Mute a channel using <code>!keyword mute channel channelid</code>. For example, <code>!keyword mute channel 300568375900504074</code>.<br />
<br />
===== Unmute a server or channel =====<br />
Unmute a server or channel using the same commands as above, except using <code>unmute</code> instead of <code>mute</code>.<br />
<br />
== Getting IDs ==<br />
Several bot commands use either channel or server IDs to identify those channels or servers. Getting these IDs is relatively straightforward. Navigate to the channel or server that you want the ID for, and look at the URL of the page. For example, the #michigan channel in the GLR server has this URL:<br />
<br />
<code><nowiki>https://discordapp.com/channels/299563059695976451/299567520652853248</nowiki></code><br />
<br />
In all URLs, the first large number is the server ID and the second number is the channel ID. In this example, the server ID is <code>299563059695976451</code>, and the channel ID is <code>299567520652853248</code>.<br />
<br />
Alternatively, you can use the command <code>!whereami</code> and the bot will give you these IDs.<br />
<br />
'''Note that the server and channel IDs may be the same!'''<br />
<br />
== Technical ==<br />
The bot's identifier is WazeBot#1984, and its internal ID is 299667737368592385. It is written in C# and runs on .NET Core. Source code is available on [https://github.com/vaindil/wazebot-discord GitHub]. Core functionality is provided by [https://github.com/RogueException/Discord.Net Discord.Net]. Contact vaindil (vaindil#2314 on Discord) with any questions or issues.</div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=Wazebot&diff=159040
Wazebot
2017-07-08T18:30:04Z
<p>Vaindil: </p>
<hr />
<div>Wazebot is an automated chat bot for use in the Waze Discord servers and Google Hangouts chats. <br />
This is not to be confused with "WazeBot" which is part of the "Feed the Waze" project.<br />
<br />
'''This page discusses the details for the Discord version of the bot. For more details on the Google Hangouts bot, see the [https://vaindil.com/wazebot Wazebot] external page.'''<br />
<br />
== Features ==<br />
<br />
==== Role Syncing ====<br />
Wazebot can sync your roles across the regional Discord servers. A limited number of roles are set by the bot for security reasons; others must be set manually and are not synced automatically. The table below gives the available roles and the permission required to set them. For example, the L6 role can only be given by champs, and only when the command is used in the national server.<br />
{| class="wikitable"<br />
!Role<br />
!Bot Command<br />
!Role Required<br />
|-<br />
|Country Manager (CM)<br />
|!cm @username<br />
|CM or above<br />
|-<br />
|State Manager (SM)<br />
|!sm @username<br />
|SM or above<br />
|-<br />
|Large Area Manager (LAM)<!-- The LAM role is applied in those regions that use LAMs. In other regions, the bot will assign the AM role. --><br />
|!lam @username<br />
|SM or above<br />
|-<br />
|Area Manager (AM)<br />
|!am @username<br />
|SM or above<br />
|-<br />
|Mentor<br />
|!mentor @username<br />
|SM or above<br />
|-<br />
|Region-specific<br />
|!region @username<br />
|SM or above<br />
|-<br />
|Level 6 (L6)<br />
|!l6 @username<br />
|Champ in national server<br />
|-<br />
|Level 5 (L5)<br />
|!l5 @username<br />
|SM or above<br />
|-<br />
|Level 4 (L4)<br />
|!l4 @username<br />
|SM or above<br />
|-<br />
|Level 3 (L3)<br />
|!l3<br />
|Anyone (role is assigned to command user)<br />
|-<br />
|Level 2 (L2)<br />
|!l2<br />
|Anyone (role is assigned to command user)<br />
|-<br />
|Level 1 (L1)<br />
|!l1<br />
|Anyone (role is assigned to command user)<br />
|}<br />
<br />
== Commands ==<br />
<br />
=== Glossary ===<br />
You can search for glossary terms with the command <code>!glossary</code>, using the format <code>!glossary search term</code>.<br />
<br />
=== Lookup ===<br />
Some channels may have a linked Google Spreadsheet. If your channel does, you can search it using <code>!lookup</code>. An example command is <code>!lookup search term</code>.<br />
<br />
=== Autoreplies ===<br />
An autoreply is a message that the bot will reply with automatically when a certain phrase is said in chat. Autoreplies can be created at the channel, server, or global levels. The syntax is by nature somewhat convoluted due to the features provided.<br />
<br />
Channel and server autoreplies can be set by SM+, and global autoreplies can be set in the national server by champs.<br />
<br />
Here's an example command:<br />
<br />
<code>!autoreplies add server testing This is a test.</code><br />
<br />
<code>!autoreplies remove global anothertest This is another test.</code><br />
<br />
=== Keyword Subscriptions ===<br />
You can subscribe to keywords and the bot will message you whenever one is used in a channel that you're in. The commands are somewhat complicated because of the functionality available.<br />
<br />
==== Notes ====<br />
Keywords must be at least 3 characters long and are not case-sensitive.<br />
<br />
==== Base command ====<br />
The base command to use is <code>!keyword</code> or <code>!subscription</code>, or variants of these.<br />
<br />
==== List keywords ====<br />
Your existing keywords can be listed using <code>!keyword list</code>.<br />
<br />
==== Add a keyword ====<br />
To add a keyword, use <code>!keyword add keywordhere</code>. You can use multiple words, but note that you will only be messaged if the entire phrase you use is a match. To add multiple separate keywords, you need to use the command multiple times in individual messages.<br />
<br />
==== Remove a keyword ====<br />
Remove keywords using <code>!keyword remove keywordhere</code>. The keyword must exactly match one of your existing keywords or the command will fail.<br />
<br />
==== Ignoring servers or channels ====<br />
By default, the bot will message you if a keyword matches in any channel that you're in. You can ignore certain servers or channels with the command below. To find the server or channel ID, see the Getting IDs section below.<br />
<br />
===== Ignore a server =====<br />
To ignore a server: <code>!keyword ignore server serverid keywordhere</code>. For example, you could ignore the keyword "testing" in the national server by using <code>!keyword ignore server 300471946494214146 testing</code>.<br />
<br />
===== Ignore a channel =====<br />
Ignoring a channel uses the same syntax as ignoring a server, except the word "channel" is used instead of "server": <code>!keyword ignore channel channelid keywordhere</code>. For example, to ignore the keyword "testing" in the GLR channel on the national server, you would use <code>!keyword ignore channel 300568375900504074 testing</code>.<br />
<br />
===== Unignore a server or channel =====<br />
Unignoring a server or channel uses the same syntax as ignoring, but with the word "unignore" instead of "ignore". For example: <code>!keyword unignore server 300471946494214146 testing</code>.<br />
<br />
== Getting IDs ==<br />
Several bot commands use either channel or server IDs to identify those channels or servers. Getting these IDs is relatively straightforward. Navigate to the channel or server that you want the ID for, and look at the URL of the page. For example, the #michigan channel in the GLR server has this URL:<br />
<br />
<code><nowiki>https://discordapp.com/channels/299563059695976451/299567520652853248</nowiki></code><br />
<br />
In all URLs, the first large number is the server ID and the second number is the channel ID. In this example, the server ID is <code>299563059695976451</code>, and the channel ID is <code>299567520652853248</code>.<br />
<br />
Alternatively, you can use the command <code>!whereami</code> and the bot will give you these IDs.<br />
<br />
'''Note that the server and channel IDs may be the same!'''<br />
<br />
== Technical ==<br />
The bot's identifier is WazeBot#1984, and its internal ID is 299667737368592385. It is written in C# and runs on .NET Core. Source code is available on [https://github.com/vaindil/wazebot-discord GitHub]. Core functionality is provided by [https://github.com/RogueException/Discord.Net Discord.Net]. Contact vaindil (vaindil#2314 on Discord) with any questions or issues.</div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=Wazebot&diff=155590
Wazebot
2017-06-25T19:47:48Z
<p>Vaindil: </p>
<hr />
<div>Wazebot is an automated chat bot for use in the Waze Discord servers and Google Hangouts chats. <br />
This is not to be confused with "WazeBot" which is part of the "Feed the Waze" project.<br />
<br />
'''This page discusses the details for the Discord version of the bot. For more details on the Google Hangouts bot, see the [https://vaindil.com/wazebot Wazebot] external page.'''<br />
<br />
== Features ==<br />
<br />
==== Role Syncing ====<br />
Wazebot can sync your roles across the regional Discord servers. A limited number of roles are set by the bot for security reasons; others must be set manually and are not synced automatically. The table below gives the available roles and the permission required to set them. For example, the L6 role can only be given by champs, and only when the command is used in the national server.<br />
{| class="wikitable"<br />
!Role<br />
!Bot Command<br />
!Role Required<br />
|-<br />
|Country Manager (CM)<br />
|!cm @username<br />
|CM or above<br />
|-<br />
|State Manager (SM)<br />
|!sm @username<br />
|SM or above<br />
|-<br />
|Large Area Manager (LAM)<!-- The LAM role is applied in those regions that use LAMs. In other regions, the bot will assign the AM role. --><br />
|!lam @username<br />
|SM or above<br />
|-<br />
|Area Manager (AM)<br />
|!am @username<br />
|SM or above<br />
|-<br />
|Mentor<br />
|!mentor @username<br />
|SM or above<br />
|-<br />
|Region-specific<br />
|!region @username<br />
|SM or above<br />
|-<br />
|Level 6 (L6)<br />
|!l6 @username<br />
|Champ in national server<br />
|-<br />
|Level 5 (L5)<br />
|!l5 @username<br />
|SM or above<br />
|-<br />
|Level 4 (L4)<br />
|!l4 @username<br />
|SM or above<br />
|-<br />
|Level 3 (L3)<br />
|!l3<br />
|Anyone (role is assigned to command user)<br />
|-<br />
|Level 2 (L2)<br />
|!l2<br />
|Anyone (role is assigned to command user)<br />
|-<br />
|Level 1 (L1)<br />
|!l1<br />
|Anyone (role is assigned to command user)<br />
|}<br />
<br />
== Commands ==<br />
<br />
=== Glossary ===<br />
You can search for glossary terms with the command <code>!glossary</code>, using the format <code>!glossary search term</code>.<br />
<br />
=== Lookup ===<br />
Some channels may have a linked Google Spreadsheet. If your channel does, you can search it using <code>!lookup</code>. An example command is <code>!lookup search term</code>.<br />
<br />
=== Autoreplies ===<br />
An autoreply is a message that the bot will reply with automatically when a certain phrase is said in chat. Autoreplies can be created at the channel, server, or global levels. The syntax is by nature somewhat convoluted due to the features provided.<br />
<br />
Channel and server autoreplies can be set by SM+, and global autoreplies can be set in the national server by champs.<br />
<br />
Here's an example command:<br />
<br />
<code>!autoreplies add guild testing This is a test.</code><br />
<br />
== Getting IDs ==<br />
Several bot commands use either channel or server IDs to identify those channels or servers. Getting these IDs is relatively straightforward. Navigate to the channel or server that you want the ID for, and look at the URL of the page. For example, the #michigan channel in the GLR server has this URL:<br />
<br />
<code><nowiki>https://discordapp.com/channels/299563059695976451/299567520652853248</nowiki></code><br />
<br />
In all URLs, the first large number is the server ID and the second number is the channel ID. In this example, the server ID is <code>299563059695976451</code>, and the channel ID is <code>299567520652853248</code>.<br />
<br />
Alternatively, you can use the command <code>!whereami</code> and the bot will give you these IDs.<br />
<br />
== Technical ==<br />
The bot's identifier is WazeBot#1984, and its internal ID is 299667737368592385. It is written in C# and runs on .NET Core. Source code is available on [https://github.com/vaindil/wazebot-discord GitHub]. Core functionality is provided by [https://github.com/RogueException/Discord.Net Discord.Net]. Contact vaindil (vaindil#2314 on Discord) with any questions or issues.</div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=Wazebot&diff=155589
Wazebot
2017-06-25T18:08:46Z
<p>Vaindil: </p>
<hr />
<div>Wazebot is an automated chat bot for use in the Waze Discord servers and Google Hangouts chats. <br />
This is not to be confused with "WazeBot" which is part of the "Feed the Waze" project.<br />
<br />
'''This page discusses the details for the Discord version of the bot. For more details on the Google Hangouts bot, see the [https://vaindil.com/wazebot Wazebot] external page.'''<br />
<br />
== Features ==<br />
<br />
==== Role Syncing ====<br />
Wazebot can sync your roles across the regional Discord servers. A limited number of roles are set by the bot for security reasons; others must be set manually and are not synced automatically. The table below gives the available roles and the permission required to set them. For example, the L6 role can only be given by champs, and only when the command is used in the national server.<br />
{| class="wikitable"<br />
!Role<br />
!Bot Command<br />
!Role Required<br />
|-<br />
|Country Manager (CM)<br />
|!cm @username<br />
|CM or above<br />
|-<br />
|State Manager (SM)<br />
|!sm @username<br />
|SM or above<br />
|-<br />
|Large Area Manager (LAM)<!-- The LAM role is applied in those regions that use LAMs. In other regions, the bot will assign the AM role. --><br />
|!lam @username<br />
|SM or above<br />
|-<br />
|Area Manager (AM)<br />
|!am @username<br />
|SM or above<br />
|-<br />
|Mentor<br />
|!mentor @username<br />
|SM or above<br />
|-<br />
|Region-specific<br />
|!region @username<br />
|SM or above<br />
|-<br />
|Level 6 (L6)<br />
|!l6 @username<br />
|Champ in national server<br />
|-<br />
|Level 5 (L5)<br />
|!l5 @username<br />
|SM or above<br />
|-<br />
|Level 4 (L4)<br />
|!l4 @username<br />
|SM or above<br />
|-<br />
|Level 3 (L3)<br />
|!l3<br />
|Anyone (role is assigned to command user)<br />
|-<br />
|Level 2 (L2)<br />
|!l2<br />
|Anyone (role is assigned to command user)<br />
|-<br />
|Level 1 (L1)<br />
|!l1<br />
|Anyone (role is assigned to command user)<br />
|}<br />
<br />
== Commands ==<br />
<br />
=== Glossary ===<br />
You can search for glossary terms with the command <code>!glossary</code>, using the format <code>!glossary search term</code>.<br />
<br />
=== Lookup ===<br />
Some channels may have a linked Google Spreadsheet. If your channel does, you can search it using <code>!lookup</code>. An example command is <code>!lookup search term</code>.<br />
<br />
=== Autoreplies ===<br />
An autoreply is a message that the bot will reply with automatically when a certain phrase is said in chat. Autoreplies can be created at the channel, server, or global levels. The syntax is by nature somewhat convoluted due to the features provided.<br />
<br />
== Getting IDs ==<br />
Several bot commands use either channel or server IDs to identify those channels or servers. Getting these IDs is relatively straightforward. Navigate to the channel or server that you want the ID for, and look at the URL of the page. For example, the #general channel on the national server has the URL below.<br />
<br />
<code><nowiki>https://discordapp.com/channels/300471946494214146/300471946494214146</nowiki></code><br />
<br />
In all URLs, the first large number is the server ID and the second number is the channel ID. So, in this example, the server ID is <code>300471946494214146</code>, and the channel ID is <code>300471946494214146</code>.<br />
<br />
Alternatively, you can use the command <code>!whereami</code> and the bot will give you these IDs.<br />
<br />
== Technical ==<br />
The bot's identifier is WazeBot#1984, and its internal ID is 299667737368592385. It is written in C# and runs on .NET Core. Source code is available on [https://github.com/vaindil/wazebot-discord GitHub]. Core functionality is provided by [https://github.com/RogueException/Discord.Net Discord.Net]. Contact vaindil (vaindil#2314 on Discord) with any questions or issues.</div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=Wazebot&diff=155547
Wazebot
2017-06-20T23:50:24Z
<p>Vaindil: </p>
<hr />
<div>Wazebot is an automated chat bot for use in the Waze Discord servers and Google Hangouts chats. <br />
This is not to be confused with "WazeBot" which is part of the "Feed the Waze" project.<br />
<br />
'''This page discusses the details for the Discord version of the bot. For more details on the Google Hangouts bot, see the [https://vaindil.com/wazebot Wazebot] external page.'''<br />
<br />
== Features ==<br />
<br />
==== Role Syncing ====<br />
Wazebot can sync your roles across the regional Discord servers. A limited number of roles are set by the bot for security reasons; others must be set manually and are not synced automatically. The table below gives the available roles and the permission required to set them. For example, the L6 role can only be given by champs, and only when the command is used in the national server.<br />
{| class="wikitable"<br />
!Role<br />
!Bot Command<br />
!Role Required<br />
|-<br />
|Country Manager (CM)<br />
|!cm @username<br />
|CM or above<br />
|-<br />
|State Manager (SM)<br />
|!sm @username<br />
|SM or above<br />
|-<br />
|Large Area Manager (LAM)<!-- The LAM role is applied in those regions that use LAMs. In other regions, the bot will assign the AM role. --><br />
|!lam @username<br />
|SM or above<br />
|-<br />
|Area Manager (AM)<br />
|!am @username<br />
|SM or above<br />
|-<br />
|Mentor<br />
|!mentor @username<br />
|SM or above<br />
|-<br />
|Level 6 (L6)<br />
|!l6 @username<br />
|Champ in national server<br />
|-<br />
|Level 5 (L5)<br />
|!l5 @username<br />
|SM or above<br />
|-<br />
|Level 4 (L4)<br />
|!l4 @username<br />
|SM or above<br />
|-<br />
|Level 3 (L3)<br />
|!l3<br />
|Anyone (role is assigned to command user)<br />
|-<br />
|Level 2 (L2)<br />
|!l2<br />
|Anyone (role is assigned to command user)<br />
|-<br />
|Level 1 (L1)<br />
|!l1<br />
|Anyone (role is assigned to command user)<br />
|}<br />
<br />
== Commands ==<br />
<br />
== Technical ==<br />
The bot's identifier is WazeBot#1984, and its internal ID is 299667737368592385. It is written in C# and runs on .NET Core. Source code is available on [https://github.com/vaindil/wazebot-discord GitHub]. Core functionality is provided by [https://github.com/RogueException/Discord.Net Discord.Net]. Contact vaindil (vaindil#2314 on Discord) with any questions or issues.</div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=Wazebot&diff=155546
Wazebot
2017-06-20T23:00:21Z
<p>Vaindil: </p>
<hr />
<div>Wazebot is an automated chat bot for use in the Waze Discord servers and Google Hangouts chats. <br />
This is not to be confused with "WazeBot" which is part of the "Feed the Waze" project.<br />
<br />
'''This page discusses the details for the Discord version of the bot. For more details on the Google Hangouts bot, see the [https://vaindil.com/wazebot Wazebot] external page.'''<br />
<br />
== Features ==<br />
<br />
==== Role Syncing ====<br />
Wazebot can sync your roles across the regional Discord servers. A limited number of roles are set by the bot for security reasons; others must be set manually and are not synced automatically. The table below gives the available roles and the permission required to set them. For example, the L6 role can only be given by champs, and only when the command is used in the national server.<br />
{| class="wikitable"<br />
!Role<br />
!Bot Command<br />
!Role Required<br />
|-<br />
|Country Manager (CM)<br />
|!cm @username<br />
|CM or above<br />
|-<br />
|State Manager (SM)<br />
|!sm @username<br />
|SM or above<br />
|-<br />
|Large Area Manager (LAM)<br />
|!lam @username<br />
|SM or above<br />
|-<br />
|Area Manager (AM)<br />
|!am @username<br />
|SM or above<br />
|-<br />
|Mentor<br />
|!mentor @username<br />
|SM or above<br />
|-<br />
|Level 6 (L6)<br />
|!l6 @username<br />
|Champ in national server<br />
|-<br />
|Level 5 (L5)<br />
|!l5 @username<br />
|SM or above<br />
|-<br />
|Level 4 (L4)<br />
|!l4 @username<br />
|SM or above<br />
|-<br />
|Level 3 (L3)<br />
|!l3<br />
|Anyone (set on command user)<br />
|-<br />
|Level 2 (L2)<br />
|!l2<br />
|Anyone (set on command user)<br />
|-<br />
|Level 1 (L1)<br />
|!l1<br />
|Anyone (set on command user)<br />
|}<br />
<br />
== Commands ==<br />
<br />
== Technical ==<br />
The bot's identifier is WazeBot#1984, and its internal ID is 299667737368592385. It is written in C# and runs on .NET Core. Source code is available on [https://github.com/vaindil/wazebot-discord GitHub]. Core functionality is provided by [https://github.com/RogueException/Discord.Net Discord.Net]. Contact vaindil (vaindil#2314 on Discord) with any questions or issues.</div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=Michigan/Resources/Main&diff=150112
Michigan/Resources/Main
2016-11-06T19:16:32Z
<p>Vaindil: /*Resources/Main*/ add BM: Open WME in Mi Drive</p>
<hr />
<div><!-- This page is only transcluded into (displayed on) the main page for this state. See more detailed instructions below. --><noinclude>{{:USA/CommonState/ReturnPurge|{{SubPage2}}}}<br/></noinclude><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
<br />
====Statewide====<br />
*[http://mdotcf.state.mi.us/public/maps_nfc/ MDOT NFC Maps] - MDOT National Functional Classification (NFC) maps by county and urban area. An effort was started in late 2013 to convert metro Detroit and other major cities to their corresponding NFC road classifications.<br />
*[http://www.michigan.gov/mdot/0,4616,7-151-11151---,00.html MDOT maps]<br />
*[http://www2.census.gov/geo/pvs/bas/annexation/26/ Boundary and Annexation Survey Maps] from [http://www.census.gov/ US Census Bureau]<br />
*[http://www.census.gov/geo/maps-data/maps/2010ref/st26_tract.html Michigan Census Designated Places] from US Census.<br />
*[http://tigerweb.geo.census.gov/tigerweb/ TIGERweb] from [http://www.census.gov/ US Census Bureau]<br />
*[http://www.mcgi.state.mi.us/prfinder/mapBasic.aspx MDOT Physical Road (PR) Finder] (also see the [http://www.mcgi.state.mi.us/prfinder/MCGI.aspx PR Finder Home page])<br />
*[http://www.michigan.gov/mdot/0,4616,7-151-9621_11008---,00.html MDOT's Major Road Projects]<br />
*[http://mdotnetpublic.state.mi.us/drive/Default.aspx MDOT's MiDrive] live traffic cameras, accident reports, construction zones<br />
<br />
====County====<br />
*[http://www.micountyroads.org/crcs.php Directory of county road commissions], many of which maintain a list of planned improvements or current projects<br />
*[http://wiki.waze.com/wiki/Michigan/GIS Listing] of all counties in Michigan and available GIS maps.<br />
<br />
====City====<br />
*[http://www.auburnhills.org/community/2015roadprojects/index.php Auburn Hills Road Projects]<br />
*[http://www.detroitmi.gov/2015-Construction-Projects Detroit Construction Projects]<br />
*[http://m-1rail.com/construction/construction-schedule/ Detroit M-1 Rail Project]<br />
*[http://grcity.us/engineering-department/Construction-Updates/Pages/default.aspx Grand Rapids construction updates]<br />
*[http://ww3.rochesterhills.org/constructionmap/ Rochester & Rochester Hills construction map]<br />
<br />
====Recommended WME UI Enhancements====<br />
*[https://www.waze.com/forum/viewtopic.php?f=819&t=164962 WME Place Harmonizer]<br />
*[https://www.waze.com/forum/viewtopic.php?f=819&t=40705 WME Color Highlights]<br />
*[https://www.waze.com/forum/viewtopic.php?f=819&t=108055 WME Toolbox]<br />
*[https://www.waze.com/forum/viewtopic.php?f=819&t=76488 WME Validator]<br />
*[https://greasyfork.org/en/scripts/8749-wme-validator-localization-for-michigan Michigan localized enhancement of Validator]<br />
*[https://www.waze.com/forum/viewtopic.php?f=819&t=61926 WME Junction Angle Info]<br />
*[https://www.waze.com/forum/viewtopic.php?f=819&t=95038 WME Chat addon]<br />
*[https://greasyfork.org/en/scripts/5592-wme-ur-comments-stable WME UR Comments]<br />
*[https://greasyfork.org/en/scripts/6236-wme-urcomments-custom-list WME URComments Custom List]<br />
*[https://greasyfork.org/en/scripts/1952-uroverview-plus-uro UROverview Plus (URO+)]<br />
*[https://greasyfork.org/en/scripts/1776-wme-ur-mp-tracking WME UR-MP tracking]<br />
*[https://greasyfork.org/en/scripts/8693-wme-closest-segment WME Closest Segment]<br />
*[https://www.waze.com/forum/viewtopic.php?f=819&p=1194011#p1194011 WME HN Tool]<br />
*[https://chrome.google.com/webstore/detail/wme-michigan/kifcfnegjfalmmhileloeabpmbamakim WME Michigan]<br />
*[https://greasyfork.org/en/scripts/11453-wme-counties-michigan-census-2014 Michigan County Overlay]<br />
*[https://gist.github.com/vaindil/bd53205a938f3dc93375a14bbd727339 Open WME in Mi Drive] ''([[Bookmarklets|bookmarklet]] to open the current WME view in [http://mdotnetpublic.state.mi.us/drive/Default.aspx Mi Drive])''<br />
<br />
====Forms to Address Mapping/Navigation Issues====<br />
*[https://support.google.com/waze/contact/search_issues?hl=en Waze App Search Issues]<br />
*[https://docs.google.com/forms/d/1OJUjSL_rHybThnQ9pFTXCOUwCahxoakf9o3lt8KFnd0/viewform?hl=en Stale Trafficast reports]<br />
*[https://docs.google.com/forms/d/1bZ_fVDTpX99-DdW1MVMyWz8nbu5FhTk24YdVp_6jegQ/viewform City Merge Form]<br />
*[https://docs.google.com/forms/d/1B3bvjTYsO1r5GOxaXB1x9nN0AG5bY7OZFv_6WJ12wm0/viewform?c=0&w=1 Mentor Request Form]<br />
*[https://docs.google.com/forms/d/1rs5NIxmFifY0VYS4MJZFSucu8DgrcvJSXsawm3eTqOE/viewform?c=0&w=1 Michigan Waze Advertised Place Problems]<br />
<br />
<br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Resources|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Resources]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=Michigan/Resources/Main&diff=142512
Michigan/Resources/Main
2016-04-16T20:33:16Z
<p>Vaindil: /*Resources/Main*/</p>
<hr />
<div><!-- This page is only transcluded into (displayed on) the main page for this state. See more detailed instructions below. --><noinclude>{{:USA/CommonState/ReturnPurge|{{SubPage2}}}}<br/></noinclude><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
<br />
====Statewide====<br />
*[http://mdotcf.state.mi.us/public/maps_nfc/ MDOT NFC Maps] - MDOT National Functional Classification (NFC) maps by county and urban area. An effort was started in late 2013 to convert metro Detroit and other major cities to their corresponding NFC road classifications.<br />
*[http://www.michigan.gov/mdot/0,4616,7-151-11151---,00.html MDOT maps]<br />
*[http://www2.census.gov/geo/pvs/bas/annexation/26/ Boundary and Annexation Survey Maps] from [http://www.census.gov/ US Census Bureau]<br />
*[http://www.census.gov/geo/maps-data/maps/2010ref/st26_tract.html Michigan Census Designated Places] from US Census.<br />
*[http://tigerweb.geo.census.gov/tigerweb/ TIGERweb] from [http://www.census.gov/ US Census Bureau]<br />
*[http://www.mcgi.state.mi.us/prfinder/mapBasic.aspx MDOT Physical Road (PR) Finder] (also see the [http://www.mcgi.state.mi.us/prfinder/MCGI.aspx PR Finder Home page])<br />
*[http://www.michigan.gov/mdot/0,4616,7-151-9621_11008---,00.html MDOT's Major Road Projects]<br />
*[http://mdotnetpublic.state.mi.us/drive/Default.aspx MDOT's MiDrive] live traffic cameras, accident reports, construction zones<br />
<br />
====County====<br />
*[http://www.micountyroads.org/crcs.php Directory of county road commissions], many of which maintain a list of planned improvements or current projects<br />
*[http://wiki.waze.com/wiki/Michigan/GIS Listing] of all counties in Michigan and available GIS maps.<br />
<br />
====City====<br />
*[http://www.auburnhills.org/community/2015roadprojects/index.php Auburn Hills Road Projects]<br />
*[http://www.detroitmi.gov/2015-Construction-Projects Detroit Construction Projects]<br />
*[http://m-1rail.com/construction/construction-schedule/ Detroit M-1 Rail Project]<br />
*[http://grcity.us/engineering-department/Construction-Updates/Pages/default.aspx Grand Rapids construction updates]<br />
*[http://ww3.rochesterhills.org/constructionmap/ Rochester & Rochester Hills construction map]<br />
<br />
====Recommended WME UI Enhancements====<br />
*[https://www.waze.com/forum/viewtopic.php?f=819&t=40705 WME Color Highlights]<br />
*[https://www.waze.com/forum/viewtopic.php?f=819&t=108055 WME Toolbox]<br />
*[https://www.waze.com/forum/viewtopic.php?f=819&t=76488 WME Validator]<br />
*[https://greasyfork.org/en/scripts/8749-wme-validator-localization-for-michigan Michigan localised enhancement of Validator]<br />
*[https://www.waze.com/forum/viewtopic.php?f=819&t=61926 WME Junction Angle Info]<br />
*[https://www.waze.com/forum/viewtopic.php?f=819&t=95038 WME Chat addon]<br />
*[https://greasyfork.org/en/scripts/5592-wme-ur-comments-stable WME UR Comments]<br />
*[https://greasyfork.org/en/scripts/6236-wme-urcomments-custom-list WME URComments Custom List]<br />
*[https://greasyfork.org/en/scripts/1952-uroverview-plus-uro UROverview Plus (URO+)]<br />
*[https://greasyfork.org/en/scripts/1776-wme-ur-mp-tracking WME UR-MP tracking]<br />
*[https://greasyfork.org/en/scripts/8693-wme-closest-segment WME Closest Segment]<br />
*[https://www.waze.com/forum/viewtopic.php?f=819&p=1194011#p1194011 WME HN Tool]<br />
*[https://chrome.google.com/webstore/detail/wme-michigan/kifcfnegjfalmmhileloeabpmbamakim WME Michigan]<br />
*[https://greasyfork.org/en/scripts/11453-wme-counties-michigan-census-2014 Michigan County Overlay]<br />
*[https://greasyfork.org/en/scripts/15672-mi-drive-total-closures-only Mi Drive Total Closures Only] ''(hides everything except total closures and current accidents on [http://mdotnetpublic.state.mi.us/drive/Default.aspx Mi Drive])''<br />
<br />
====Forms to Address Mapping/Navigation Issues====<br />
*[https://support.google.com/waze/contact/search_issues?hl=en Waze App Search Issues]<br />
*[https://docs.google.com/forms/d/1OJUjSL_rHybThnQ9pFTXCOUwCahxoakf9o3lt8KFnd0/viewform?hl=en Stale Trafficast reports]<br />
*[https://docs.google.com/forms/d/1bZ_fVDTpX99-DdW1MVMyWz8nbu5FhTk24YdVp_6jegQ/viewform City Merge Form]<br />
<br />
<br />
<br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Resources|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Resources]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=Michigan/AM/Editor/Area&diff=141961
Michigan/AM/Editor/Area
2016-04-10T15:26:40Z
<p>Vaindil: update vaindil rank</p>
<hr />
<div><!---------------------- DO NOT MODIFY THIS TOP CODE ------------------------------<br />
------------------------ SCROLL DOWN FOR INSTRUCTIONS -----------------------------<br />
-----------------------------------------------------------------------------------><noinclude><!--Keep hard coded due to unique page address--><div class="center"><span class="noprint plainlinks purgelink" style="{{Road/style}}background-color:#93c4d3">[{{FULLURL:{{#titleparts:{{PAGENAME}}|-3}}|action=purge}}#Area_Managers <span title="Return to the Area Manager table">&nbsp;Press here to return to the Area Managers table to see your changes&nbsp;</span>]</span></div></noinclude><includeonly><!--<br />
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ------------------------------------- INSTRUCTIONS - START READING HERE ------------------------------------- --------------------<br />
-------------------------------------------------------------------------------------<br />
-- Country/State Managers: Cancel this edit and use the link at the top of the table.<br />
<br />
-------------------------------------------------------------------------------------<br />
<br />
-- Editors: To add yourself to this Area Manager table, copy and paste the following<br />
<br />
-- template into the space below with the other {{AM/Editor|...}} templates. Add<br />
-- yourself into rank order (higher at top)then alphabetical order by user name (A-Z)<br />
-------------------------------------------------------------------------------------<br />
{{AM/Editor|YOUR_USER_NAME|YOUR_RANK#|YOUR_AREA|ANY_COMMENT}}<br />
-------------------------------------------------------------------------------------<br />
-- then in the Summary field enter "Added YOUR_USER_NAME" and press "Save page"<br />
-------------------------------------------------------------------------------------<br />
------------------- DO NOT MODIFY CONTENT ABOVE THE EQUAL SIGN ----------------------<br />
================================================================================-->|-<br />
<br />
{{AM/Editor|jdeyoung|6|West Michigan|Indiana State Manager}}<br />
{{AM/Editor|hitfactor|5|Southern Lower Michigan|badge1=am}}<br />
{{AM/Editor|lelehman|5|Mid-Michigan, Tri-Cities|Bay, Clinton, Eaton, Genessee, Gratiot, Ingham, Isabella, Livingston, Midland, Saginaw, and Shiawassee counties}}<br />
{{AM/Editor|zohar760|5|Central/Southern Oakland/Macomb, Wayne, and all of Detroit|badge1=am|Home area: Sterling Heights, editable area stretches throughout North Macomb, East Oakland, and Wayne County/Downtown Detroit|gho=zohar760|pic=File:Avatar-zohar760.jpg}}<br />
{{AM/Editor|BuzzardJoe|4|Rochester Hills|Likes to wiki}}<br />
{{AM/Editor|captnkeegs|4|Grand Rapids Area|Mostly working Kent & Barry county some Ottawa & Allegan county area}}<br />
{{AM/Editor|JB15TM|4|Shiawassee, Genesee, Lapeer, Northern Oakland / Livingston|AM for lower Westchester NY|badge1=AM|badge2=mr||gho=John|pic=File:JB15TM.png}}<br />
{{AM/Editor|SuperMari0O|4|Upper Peninsula|}}<br />
{{AM/Editor|vaindil|4|Traverse City and surrounding areas|badge1=am|gho=vaindil|pic=File:avatar-vaindil.png}}<br />
{{AM/Editor|falco_sparverius|3|Kalamazoo/Battle Creek Area, and Presque Isle County|badge1=am|gho=Kestrel|pic=File:Falco_sparverius-avatar.png}}<br />
{{AM/Editor|Gazoo4U|3|SE Luce county near Newberry|}}<br />
{{AM/Editor|PedroskiPR|3|Walker/West Grand Rapids|badge1=am}}<br />
{{AM/Editor|miked_64|3|SW Lower MI|GR, Kzoo and surrounding areas|badge1=am}}<br />
{{AM/Editor|trukkurt|3|Muskegon Area|badge1=am}}<br />
{{AM/Editor|tythesly|3|Saginaw|}}<br />
<br />
<br />
<!--+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<br />
------------------- DO NOT MODIFY CONTENT BELOW THE PLUS SIGN -----------------------<br />
-------------------------------------------------------------------------------------<br />
-------------------------------------------------------------------------------------<br />
--></includeonly></div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=File:Jct_transition_90.png&diff=138592
File:Jct transition 90.png
2016-02-26T18:55:12Z
<p>Vaindil: Vaindil uploaded a new version of &quot;File:Jct transition 90.png&quot;</p>
<hr />
<div>Transition junction, 90 degrees</div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=File:Jct_transition.png&diff=138591
File:Jct transition.png
2016-02-26T18:53:07Z
<p>Vaindil: Vaindil uploaded a new version of &quot;File:Jct transition.png&quot;</p>
<hr />
<div>Transition junction</div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=File:Jct_transition.png&diff=138590
File:Jct transition.png
2016-02-26T18:51:25Z
<p>Vaindil: Vaindil uploaded a new version of &quot;File:Jct transition.png&quot;</p>
<hr />
<div>Transition junction</div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=File:Jct_at_grade_keep.png&diff=138588
File:Jct at grade keep.png
2016-02-26T18:49:54Z
<p>Vaindil: Vaindil uploaded a new version of &quot;File:Jct at grade keep.png&quot;</p>
<hr />
<div>At grade connector, keep instruction</div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=File:Jct_at_grade_keep.png&diff=138587
File:Jct at grade keep.png
2016-02-26T18:48:59Z
<p>Vaindil: Vaindil uploaded a new version of &quot;File:Jct at grade keep.png&quot;</p>
<hr />
<div>At grade connector, keep instruction</div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=File:Jct_at_grade_keep.png&diff=138586
File:Jct at grade keep.png
2016-02-26T18:47:17Z
<p>Vaindil: Vaindil uploaded a new version of &quot;File:Jct at grade keep.png&quot;</p>
<hr />
<div>At grade connector, keep instruction</div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=File:Jct_roundabout.png&diff=138585
File:Jct roundabout.png
2016-02-26T18:43:46Z
<p>Vaindil: Vaindil uploaded a new version of &quot;File:Jct roundabout.png&quot;</p>
<hr />
<div>Basic roundabout</div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=Junction_Style_Guide&diff=138339
Junction Style Guide
2016-02-23T18:04:27Z
<p>Vaindil: adjust size of loop image for new file</p>
<hr />
<div><!--if the section parameter is defined, do not place the visible banner, only as the code block for the top of a section-->{{GlobalMark/visible}}<br />
<!--<br />
#####-----#####-----#####-----#####-----#####-----#####-----#####-----#####-----<br />
#### This page has been curated ####<br />
#### to be included in the new ####<br />
#### Wazeopedia - GLOBAL Wiki. ####<br />
#### Please do not make any ####<br />
#### edits on this page without ####<br />
#### PRIOR CONSENSUS in the Wiki ####<br />
#### Updates and Discussions ####<br />
#### forum thread for this page. ####<br />
#### If a specific forum thread ####<br />
#### for this page doesn't exist ####<br />
#### please start one. ####<br />
#### www.waze.com/forum/ ####<br />
#### viewforum.php?f=276 ####<br />
#####-----#####-----#####-----#####-----#####-----#####-----#####-----#####--><br />
<br />
<!--Editorial Reminders--><!--To Do - U-Turn Solutions for "Road not connected" error --><br />
{{construction<br />
| contact = http://www.waze.com/forum/viewtopic.php?f=276&t=86666<br />
| contacttype = forum<br />
| draft = no<br />
| open = no<br />
| revision = yes<br />
| talk = yes<br />
}}<br />
<br />
The following article contains key information on properly creating junctions and the roadways between them. Be sure to review it in its entirety before editing the map.<br />
<br />
== Simple is better ==<br />
<br />
When representing junctions, intersections, interchanges, cross roads, corners, etc., the Waze map does not need to perfectly match the road layouts it represents. The primary goal is to represent the real world as simply as possible in the maps and only introduce complexity in the maps to address complex issues.<br />
<br />
== The basics ==<br />
This guide requires a complete understanding of editing the maps with [[Waze Map Editor]] (WME).<br />
<br />
=== Map editing 101 ===<br />
Although it is highly recommended to read the [[editing manual]] before touching the map, it is required that you do not continue with this guide until you have read the following:<br />
* [[Map Editing Quick-start Guide|Map Editing Quick-start Guide]]<br />
* [[Creating and editing road segments#Junctions|Moving and removing junctions]]<br />
<br />
=== Junction definition ===<br />
{| class="Wikitable floatright"<br />
| [[Image:Junction_selected.png|50px|border]]<br />
| [[Image:Uneditable_junction.png|50px|border]]<br />
| [[Image:junction_unsaved.png|50px|border]]<br />
|}<br />
The [[Glossary#Junction or Junction Point|Glossary on Junctions]] provides details on how junctions can appear differently in the editor depending on its state or condition.<br />
<br />
A junction is made up of three things:<br />
# Two or more road [[Creating and editing road segments|segments]]<br />
# One point where all the segments meet (the [[junction point]] itself)<br />
# [[Map Editing Quick-start Guide#Turn restrictions .28allowed turns.29|Turns allowed or restricted]] when traveling from one segment to another through that junction point<br />
{{clear}}<br />
<br />
== Controlling Turn Instructions ==<br />
{| class="Wikitable floatright" cellpadding="5" border="1" style="text-align:center; border: 1px solid darkgray;"<br />
|-<br />
| Keep Right || Keep Left<br />
|-<br />
| Turn Right || Turn Left<br />
|-<br />
| Exit Right || Exit Left<br />
|}<br />
Turn instructions are critical for proper client navigation. They are controlled by:<br />
* The angle set between segments at junctions.<br />
* The road names.<br />
* The road types.<br />
<br />
Review the article [[Junction Style Guide/Controlling turn instructions|controlling turn instructions]] for a complete understanding of the requirements and issues surrounding this topic.<br />
<br />
== Surface Streets ==<br />
<br />
=== Intersections ===<br />
{| class="Wikitable floatright"<br />
| [[File:Jct 3 90.png|x100px|border]]<br />
| [[File:Jct 4 90.png|x100px|border]]<br />
| [[File:Jct ramp no geo.png|x100px|border]]<br />
|-<br />
| colspan="3"|[[File:Jct bowtie.png|x100px|center|border]]<br />
|}<br />
The most basic junctions form three-way and four-way intersections. Some variations resemble bow ties.<br />
<br />
In all cases it is important to configure these intersections properly. Detailed information is covered in the [[Junction Style Guide/Intersections|Intersections]] article.<br />
{{clear}}<br />
<br />
<br />
=== No Outlet Roads ===<br />
<br />
Roads which only have one way in and one way out can present challenges to the routing server, although they seem simple to our minds.<br />
<br />
==== Dead Ends ====<br />
<br />
Dead Ends (a.k.a. No Exit, Closed, No Through Road, No Outlet) are road segments that simply end, with no continuation or connections at one end. In some areas, a Dead End may be synonymous with a [[#Cul-de-sacs|Cul-de-sac]]. In the US, a "No Outlet" sign may be used to indicate a road which itself is not a dead end, but it only connects to other dead end roads. It can also be used as a "friendlier" alternative to the typical Dead End sign.<br />
<br />
Within the Map Editor it is possible to represent a dead end road with multiple segments if there are private driveways or parking lot roads mapped and connected. In that case, only the very last segment is considered the dead end segment.<br />
<br />
[[File:Jct dead end.png|left|border]]<br />
Make sure that there is a junction indicator (the small blue dot, not just a geometry node) at the very end of the segment. While this one segment does not actually constitute a junction, the small blue dot is a visual indicator to the editor that the end of this segment is properly set up. This is necessary to ensure proper routing out of the segment. See the Cul-de-sac section below on when and how to fix this.<br />
<br />
[[File:Jct dead end ex.png|right|border|200px]]<br />
This final junction indicator must be located near the end of the road, but it should be located where there is still pavement as not to negatively impact client routes. Waze only considers the road fully traversed if both ends of the segment are fully crossed. If the junction indicator at the end of the segment happens to be at the edge of the pavement (or off of the road surface if aerials are not exactly aligned), it will be very difficult for a driver to cross that junction. A good rule of thumb is to have the end of the segment the same distance from the end of the pavement as it is from each side of the road.<br />
<br />
With such a placement, the driver is given a chance to cross that junction indicator for that segment. Also check for the proper u-turn setting as covered in the [[Map Editing Quick-start Guide#U-Turns at the end of dead-end-streets|best practices article on u-turns]].<br />
<br />
==== Cul-de-sacs ====<br />
<br />
''See also: [http://en.wikipedia.org/wiki/Cul-de-sac Cul-de-sac article on Wikipedia]''<br />
<br />
A Cul-de-sac (a.k.a. Court in the US) is a common treatment of a dead end street in a residential neighborhood.<br />
<br />
In almost every situation, a cul-de-sac should be treated exactly as a dead end street, with the final junction indicator in the center of the bulb of the cul-de-sac. Be sure the free end of the final road segment has small blue dot displayed at the tip (when not editing or selecting the segment). If there is no blue dot, please correct it by following the steps for [[Creating and editing road segments#Fix the end-node on cul-de-sacs and dead-ends|fixing dead ends]].<br />
<br />
[[Image:Jct_cul-de-sac_ex.png|left|border]]<br />
The junction indicator should be located close to the middle of the bulb and NOT near the outer edges. If the end of the segment is positioned along the perimeter of the bulb, there may be difficulty in processing client routes. Waze only considers the road fully traversed if both ends of a segment are crossed. If the end of the segment happens to be on the curb (or off of the road surface if aerials are not exactly aligned), it will be very difficult for a driver to cross the end of the road segment. With the junction in the middle of the visual road, we give a driver a good chance to cross the end of the segment no matter where they drive within the bulb. The exception to this guidance is given in the next example.<br />
{{clear}}<br />
<br />
{| class="Wikitable floatright"<br />
| [[Image:Jct_cul-de-sac_island_ex.png|200px|border]]<br />
| [[Image:Jct_cul-de-sac_island_ex_road.png|border|200px]]<br />
|}<br />
This cul-de-sac, with a small island, should be treated as a basic dead end with no loop. The island can be ignored, as there is no significant routing question for the driver once they get to the cul-de-sac.<br />
<br />
As for placement of the final junction indicator, here we may get better results by moving the junction out from the true center and over to the outer perimeter of the central island. The shift ensures that the driver has a good opportunity to cross the end of the segment.<br />
{{clear}}<br />
<br />
However, if the cul-de-sac has a very large bulb with a large island in the middle, it may better be treated as a [[#Loops|Loop]]. A good rule of thumb is if you were standing at the end of the cul-de-sac, can you tell that it is just a cul-de-sac? Or does it look like two different roads? If you see an island, but are not sure if it is significant, leave the Loop out. If "Missing Road" errors occur on the road, then add a Loop.<br />
<br />
=== Loops ===<br />
<gallery mode=packed-hover><br />
File:U-shaped Road.jpg|U-shaped road<br />
File:Jct loop bulb.png|terminal or dead-end loop<br />
</gallery><br />
Road segments form a loop when you can trace a path from a starting point around to the same point without retracing any portion of the traced path.<br />
<br />
==== Every loop must be made up of three or more segments ====<br />
[[File:Loop_3-part_6.jpg|right|150px]]Any loop that does not follow this rule can cause problems for the Waze routing server. If there is no side-street, you must [[Map Editing Quick-start Guide#Splitting a segment|insert an extra junction node]] along the loop. Many new editors will see the extra junction node(s), assume they are not needed, and delete them. Please educate new editors.<br />
<br />
====Two-segment loops====<br />
Two-segment loops create a situation called "same endpoint drivable segments" or "same connection segments". There are two or more ways to get from one junction node to another without going through any other nodes. They can cause a problem for the Waze app because the routing server gives your mobile app a list of node ids, but the app needs to tell you which segments to drive on. If there are two ways to get from one node to the next without going through any other nodes, then the Waze app might just have to guess. It might guess a detour off the highway through a gas station or scenic overlook. Please save Waze from this silliness. Correct two-segment loops.<br />
<br />
====One-segment loops====<br />
{{anchor|Loop_save_errors}}<br />
[[File:Dead end loop.png|thumb|right]] One-segment or self-connected loops are often found in basemap areas. It is difficult for Waze editors to create one-segment loops. Depending on the situation, these should be converted to three-segment loops or simple dead-end roads. For more on loops on dead-end roads, please see [[Cul-de-sac#Cul-de-sacs|cul-de-sac]]. It is important to preserve house number data on these segments.<br />
===== Fixing one-segment loops=====<br />
If you try to edit a one-segment loop, but then cannot save the changes, undo your changes and then try one of the following to fix it:<br />
<br />
*If the loop and the road leading to it have the '''same''' name<br />
*#Select the loop and the road.<br />
*#Click the bridge icon that appears (one end of the loop will disconnect from the other)<br />
*#Move the now free end of the loop so it is slightly separated<br />
*#Save<br />
*If the loop and the road leading to it have '''different''' names<br />
*#Draw a new road segment that connects to the loop/road junction<br />
*#Give that new road the same exact name as the loop<br />
*#Select the loop and the new road segment<br />
*#Click the bridge icon that appears (one end of the loop will disconnect from the other)<br />
*#Move the now free end of the loop so it is slightly separated<br />
*#Save<br />
*Create a dead end road or a three-segment dead-end loop as appropriate.<br />
*Fix elevations.<br />
*Confirm turns.<br />
<br />
Here is a [http://www.youtube.com/watch?v=a7yAzG7HElw video on YouTube showing the second method].<br />
{{#widget:YouTube|id=a7yAzG7HElw}}<br />
<br />
[[Image:Jct_roundabout.png|frameless|right]]<br />
<br />
===Roundabouts and traffic circles===<br />
It may be tempting to use the roundabout feature to create a loop shape. Do not do this unless the loop is a roundabout or traffic circle. Roundabouts give special routing instructions, and must not be used for other purposes. To learn more, please see the [[Roundabout]] page.<br />
<br />
=== At-grade connectors ===<br />
<br />
: [[Image:Jct_at_grade_keep.png]]<br />
<br />
With exceptions, don't set these segments as ramps! Watch out for all of the turns you need to restrict. For a more detailed discussion, see the full [[At-grade connectors]] article.<br />
<br />
== Interchanges and ramps ==<br />
<br />
An '''interchange''' is a road junction where two roads are connected by dedicated roadways, called '''ramps'''. The roads connected by an interchange do not intersect one another directly, and if they cross, the crossing is grade-separated.<br />
<br />
=== When to use ramps ===<br />
<br />
Use of the {{Ramp}} type is governed by the following rules:<br />
* [[Road types/USA]]<br />
* [[At-grade connectors]]<br />
<br />
=== Ramp and interchange style ===<br />
<br />
For guidance on the proper configuration of ramps, interchanges and wayfinders, see [[Junction Style Guide/Interchanges]].<br />
<br />
== Special Cases ==<br />
=== Transitions ===<br />
{| class="Wikitable floatright"<br />
| [[Image:Jct_transition.png|x150px|border]]<br />
| [[Image:Jct_transition_90.png|x150px|border]]<br />
|}<br />
A transition is a non-junction depicted using a junction node.<br />
<br />
Valid examples of where to use a Transition node include:<br />
# Road name changes<br />
# City Limits<br />
# Road Direction changes<br />
# Part of a [[#Loops|Loop Road]]<br />
# Speed Limit Change<br />
<br />
Before the current house numbering system came into use, transition nodes were used to aid in house numbering, but that is no longer required.<br />
<br />
There may be existing transition nodes on the map for other reasons like remaining after a connecting road is deleted, inherited from to the original base map import when rivers and streams created junctions, etc.<br />
<br />
As long as you are '''certain''' it is not a valid transition node, a superfluous junction node may be [[Map Editing Quick-start Guide#Delete a Junction|deleted]]. Doing so will simplify the map, eliminate turn restrictions to maintain, and reduce computing resource needs. Also consider removing the [[Creating and editing road segments#Adjusting road geometry .28nodes.29|geometry node]] which will replace the junction node you delete, if that geometry node is not needed.<br />
<br />
=== Roads to Nowhere ===<br />
In certain situations it may be necessary to add road segments that are un-drivable in order to provide accurate navigation instructions.<br />
<br />
==== Actual ====<br />
A valid use of this technique is at the temporary end of a freeway. As a freeway is built, it is often opened in sections, up to a certain exit. If we map this as a regular freeway segment leading to a ramp segment, no announcement will be made for that final exit, no matter what we name the exit ramp.<br />
<br />
This can be confusing if the ramp is set up as a properly signed and numbered exit, especially if a driver is traveling a long distance on this freeway. Imagine traveling down a freeway and seeing your next instruction is "turn left at Main St." You would probably wonder if there was a map error since you shouldn't be making a left turn off of a freeway.<br />
<br />
If we map even just a little of the future path of the freeway, this gives the routing engine a junction which will generate an "exit" instruction at the end of the freeway, thus eliminating any confusion.<br />
<br />
Conversely, if we do NOT want an exit instruction at the end of a freeway, ensure there are no road segments extending past the final exit, to ensure the final exit is the only path out of the final freeway segment.<br />
<br />
==== Fake ====<br />
''(coming soon)''<br />
<br />
=== Offset Roads ===<br />
[[Image:Jct_4_offset.png|left|x150px|border]]<br />
Sometimes you will find two roads which cross, where one does not quite line up with the other.<br />
<br />
There are a few things we need to look at in this situation.<br />
{{clear}}<br />
:* Do the roads actually line up in reality? If so we need to modify the junction to be a basic 4-way junction.<br />
{| class="Wikitable floatright"<br />
|[[Image:Jct_4_offset_align.png|x150px|border]]<br />
|[[Image:Jct_4_offset_align_ex.png|x150px|border]]<br />
|}<br />
:* Do the roads ALMOST line up in reality? If you were giving instructions to a person and would tell them to go straight with no mention of any slight turn or jog, then we want to make it into a 4-way junction. You may need to "split the difference" and not follow the centerline of either road to achieve this. The angles are exaggerated in this next example to show how the junction is forced to be close to 90 degrees, then we taper to the true centerlines of the roads. In practice this can be much more gradual and/or done while zoomed in very close.<br />
[[Image:Jct_4_offset_ex.png|right|x150px|border]]<br />
:* Finally, is there a true separation between the roads? Would you need to say for example "turn left then make an immediate right"? If so then we will want to leave the junction such that the two sides do not align.<br />
{{clear}}<br />
<br />
[[Image:Jct_4_offset_sep_ex.png|left|x150px|border]]<br />
Since we want to avoid very short segments of road (the GPS chips in consumer devices can be very inaccurate which may make it seem that a driver skipped right over a short segment. This will result in [[Map Problems in Waze Map Editor|automated map errors]] and possible route recalculations in the client,) it may be wise to shift the side roads as far apart from each other as possible with them still in the proper location (along the far curb lines for a residential street for example). This will maximize the length of the short segment between the side roads.<br />
<br />
[[Category:Style Guides]]<br />
[[Category:Table examples]]</div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=File:Loop_3-part_6.jpg&diff=138338
File:Loop 3-part 6.jpg
2016-02-23T18:01:53Z
<p>Vaindil: Vaindil uploaded a new version of &quot;File:Loop 3-part 6.jpg&quot;</p>
<hr />
<div></div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=File:Jct_loop_bulb.png&diff=138337
File:Jct loop bulb.png
2016-02-23T17:43:50Z
<p>Vaindil: Vaindil uploaded a new version of &quot;File:Jct loop bulb.png&quot;</p>
<hr />
<div>Loop road (simple bulb) example</div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=File:U-shaped_Road.jpg&diff=138336
File:U-shaped Road.jpg
2016-02-23T17:37:35Z
<p>Vaindil: Vaindil uploaded a new version of &quot;File:U-shaped Road.jpg&quot;</p>
<hr />
<div>Three segments. OK.</div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=Junction_Style_Guide&diff=138205
Junction Style Guide
2016-02-22T17:56:14Z
<p>Vaindil: adjust image dimensions</p>
<hr />
<div><!--if the section parameter is defined, do not place the visible banner, only as the code block for the top of a section-->{{GlobalMark/visible}}<br />
<!--<br />
#####-----#####-----#####-----#####-----#####-----#####-----#####-----#####-----<br />
#### This page has been curated ####<br />
#### to be included in the new ####<br />
#### Wazeopedia - GLOBAL Wiki. ####<br />
#### Please do not make any ####<br />
#### edits on this page without ####<br />
#### PRIOR CONSENSUS in the Wiki ####<br />
#### Updates and Discussions ####<br />
#### forum thread for this page. ####<br />
#### If a specific forum thread ####<br />
#### for this page doesn't exist ####<br />
#### please start one. ####<br />
#### www.waze.com/forum/ ####<br />
#### viewforum.php?f=276 ####<br />
#####-----#####-----#####-----#####-----#####-----#####-----#####-----#####--><br />
<br />
<!--Editorial Reminders--><!--To Do - U-Turn Solutions for "Road not connected" error --><br />
{{construction<br />
| contact = http://www.waze.com/forum/viewtopic.php?f=276&t=86666<br />
| contacttype = forum<br />
| draft = no<br />
| open = no<br />
| revision = yes<br />
| talk = yes<br />
}}<br />
<br />
The following article contains key information on properly creating junctions and the roadways between them. Be sure to review it in its entirety before editing the map.<br />
<br />
== Simple is better ==<br />
<br />
When representing junctions, intersections, interchanges, cross roads, corners, etc., the Waze map does not need to perfectly match the road layouts it represents. The primary goal is to represent the real world as simply as possible in the maps and only introduce complexity in the maps to address complex issues.<br />
<br />
== The basics ==<br />
This guide requires a complete understanding of editing the maps with [[Waze Map Editor]] (WME).<br />
<br />
=== Map editing 101 ===<br />
Although it is highly recommended to read the [[editing manual]] before touching the map, it is required that you do not continue with this guide until you have read the following:<br />
* [[Map Editing Quick-start Guide|Map Editing Quick-start Guide]]<br />
* [[Creating and editing road segments#Junctions|Moving and removing junctions]]<br />
<br />
=== Junction definition ===<br />
{| class="Wikitable floatright"<br />
| [[Image:Junction_selected.png|50px|border]]<br />
| [[Image:Uneditable_junction.png|50px|border]]<br />
| [[Image:junction_unsaved.png|50px|border]]<br />
|}<br />
The [[Glossary#Junction or Junction Point|Glossary on Junctions]] provides details on how junctions can appear differently in the editor depending on its state or condition.<br />
<br />
A junction is made up of three things:<br />
# Two or more road [[Creating and editing road segments|segments]]<br />
# One point where all the segments meet (the [[junction point]] itself)<br />
# [[Map Editing Quick-start Guide#Turn restrictions .28allowed turns.29|Turns allowed or restricted]] when traveling from one segment to another through that junction point<br />
{{clear}}<br />
<br />
== Controlling Turn Instructions ==<br />
{| class="Wikitable floatright" cellpadding="5" border="1" style="text-align:center; border: 1px solid darkgray;"<br />
|-<br />
| Keep Right || Keep Left<br />
|-<br />
| Turn Right || Turn Left<br />
|-<br />
| Exit Right || Exit Left<br />
|}<br />
Turn instructions are critical for proper client navigation. They are controlled by:<br />
* The angle set between segments at junctions.<br />
* The road names.<br />
* The road types.<br />
<br />
Review the article [[Junction Style Guide/Controlling turn instructions|controlling turn instructions]] for a complete understanding of the requirements and issues surrounding this topic.<br />
<br />
== Surface Streets ==<br />
<br />
=== Intersections ===<br />
{| class="Wikitable floatright"<br />
| [[File:Jct 3 90.png|x100px|border]]<br />
| [[File:Jct 4 90.png|x100px|border]]<br />
| [[File:Jct ramp no geo.png|x100px|border]]<br />
|-<br />
| colspan="3"|[[File:Jct bowtie.png|x100px|center|border]]<br />
|}<br />
The most basic junctions form three-way and four-way intersections. Some variations resemble bow ties.<br />
<br />
In all cases it is important to configure these intersections properly. Detailed information is covered in the [[Junction Style Guide/Intersections|Intersections]] article.<br />
{{clear}}<br />
<br />
<br />
=== No Outlet Roads ===<br />
<br />
Roads which only have one way in and one way out can present challenges to the routing server, although they seem simple to our minds.<br />
<br />
==== Dead Ends ====<br />
<br />
Dead Ends (a.k.a. No Exit, Closed, No Through Road, No Outlet) are road segments that simply end, with no continuation or connections at one end. In some areas, a Dead End may be synonymous with a [[#Cul-de-sacs|Cul-de-sac]]. In the US, a "No Outlet" sign may be used to indicate a road which itself is not a dead end, but it only connects to other dead end roads. It can also be used as a "friendlier" alternative to the typical Dead End sign.<br />
<br />
Within the Map Editor it is possible to represent a dead end road with multiple segments if there are private driveways or parking lot roads mapped and connected. In that case, only the very last segment is considered the dead end segment.<br />
<br />
[[File:Jct dead end.png|left|border]]<br />
Make sure that there is a junction indicator (the small blue dot, not just a geometry node) at the very end of the segment. While this one segment does not actually constitute a junction, the small blue dot is a visual indicator to the editor that the end of this segment is properly set up. This is necessary to ensure proper routing out of the segment. See the Cul-de-sac section below on when and how to fix this.<br />
<br />
[[File:Jct dead end ex.png|right|border|200px]]<br />
This final junction indicator must be located near the end of the road, but it should be located where there is still pavement as not to negatively impact client routes. Waze only considers the road fully traversed if both ends of the segment are fully crossed. If the junction indicator at the end of the segment happens to be at the edge of the pavement (or off of the road surface if aerials are not exactly aligned), it will be very difficult for a driver to cross that junction. A good rule of thumb is to have the end of the segment the same distance from the end of the pavement as it is from each side of the road.<br />
<br />
With such a placement, the driver is given a chance to cross that junction indicator for that segment. Also check for the proper u-turn setting as covered in the [[Map Editing Quick-start Guide#U-Turns at the end of dead-end-streets|best practices article on u-turns]].<br />
<br />
==== Cul-de-sacs ====<br />
<br />
''See also: [http://en.wikipedia.org/wiki/Cul-de-sac Cul-de-sac article on Wikipedia]''<br />
<br />
A Cul-de-sac (a.k.a. Court in the US) is a common treatment of a dead end street in a residential neighborhood.<br />
<br />
In almost every situation, a cul-de-sac should be treated exactly as a dead end street, with the final junction indicator in the center of the bulb of the cul-de-sac. Be sure the free end of the final road segment has small blue dot displayed at the tip (when not editing or selecting the segment). If there is no blue dot, please correct it by following the steps for [[Creating and editing road segments#Fix the end-node on cul-de-sacs and dead-ends|fixing dead ends]].<br />
<br />
[[Image:Jct_cul-de-sac_ex.png|left|border]]<br />
The junction indicator should be located close to the middle of the bulb and NOT near the outer edges. If the end of the segment is positioned along the perimeter of the bulb, there may be difficulty in processing client routes. Waze only considers the road fully traversed if both ends of a segment are crossed. If the end of the segment happens to be on the curb (or off of the road surface if aerials are not exactly aligned), it will be very difficult for a driver to cross the end of the road segment. With the junction in the middle of the visual road, we give a driver a good chance to cross the end of the segment no matter where they drive within the bulb. The exception to this guidance is given in the next example.<br />
{{clear}}<br />
<br />
{| class="Wikitable floatright"<br />
| [[Image:Jct_cul-de-sac_island_ex.png|200px|border]]<br />
| [[Image:Jct_cul-de-sac_island_ex_road.png|border|200px]]<br />
|}<br />
This cul-de-sac, with a small island, should be treated as a basic dead end with no loop. The island can be ignored, as there is no significant routing question for the driver once they get to the cul-de-sac.<br />
<br />
As for placement of the final junction indicator, here we may get better results by moving the junction out from the true center and over to the outer perimeter of the central island. The shift ensures that the driver has a good opportunity to cross the end of the segment.<br />
{{clear}}<br />
<br />
However, if the cul-de-sac has a very large bulb with a large island in the middle, it may better be treated as a [[#Loops|Loop]]. A good rule of thumb is if you were standing at the end of the cul-de-sac, can you tell that it is just a cul-de-sac? Or does it look like two different roads? If you see an island, but are not sure if it is significant, leave the Loop out. If "Missing Road" errors occur on the road, then add a Loop.<br />
<br />
=== Loops ===<br />
<gallery mode=packed-hover><br />
File:U-shaped Road.jpg|U-shaped road<br />
File:Jct loop bulb.png|terminal or dead-end loop<br />
</gallery><br />
Road segments form a loop when you can trace a path from a starting point around to the same point without retracing any portion of the traced path.<br />
<br />
==== Every loop must be made up of three or more segments ====<br />
[[File:Loop_3-part_6.jpg|right]]Any loop that does not follow this rule can cause problems for the Waze routing server. If there is no side-street, you must [[Map Editing Quick-start Guide#Splitting a segment|insert an extra junction node]] along the loop. Many new editors will see the extra junction node(s), assume they are not needed, and delete them. Please educate new editors.<br />
<br />
====Two-segment loops====<br />
Two-segment loops create a situation called "same endpoint drivable segments" or "same connection segments". There are two or more ways to get from one junction node to another without going through any other nodes. They can cause a problem for the Waze app because the routing server gives your mobile app a list of node ids, but the app needs to tell you which segments to drive on. If there are two ways to get from one node to the next without going through any other nodes, then the Waze app might just have to guess. It might guess a detour off the highway through a gas station or scenic overlook. Please save Waze from this silliness. Correct two-segment loops.<br />
<br />
====One-segment loops====<br />
{{anchor|Loop_save_errors}}<br />
[[File:Dead end loop.png|thumb|right]] One-segment or self-connected loops are often found in basemap areas. It is difficult for Waze editors to create one-segment loops. Depending on the situation, these should be converted to three-segment loops or simple dead-end roads. For more on loops on dead-end roads, please see [[Cul-de-sac#Cul-de-sacs|cul-de-sac]]. It is important to preserve house number data on these segments.<br />
===== Fixing one-segment loops=====<br />
If you try to edit a one-segment loop, but then cannot save the changes, undo your changes and then try one of the following to fix it:<br />
<br />
*If the loop and the road leading to it have the '''same''' name<br />
*#Select the loop and the road.<br />
*#Click the bridge icon that appears (one end of the loop will disconnect from the other)<br />
*#Move the now free end of the loop so it is slightly separated<br />
*#Save<br />
*If the loop and the road leading to it have '''different''' names<br />
*#Draw a new road segment that connects to the loop/road junction<br />
*#Give that new road the same exact name as the loop<br />
*#Select the loop and the new road segment<br />
*#Click the bridge icon that appears (one end of the loop will disconnect from the other)<br />
*#Move the now free end of the loop so it is slightly separated<br />
*#Save<br />
*Create a dead end road or a three-segment dead-end loop as appropriate.<br />
*Fix elevations.<br />
*Confirm turns.<br />
<br />
Here is a [http://www.youtube.com/watch?v=a7yAzG7HElw video on YouTube showing the second method].<br />
{{#widget:YouTube|id=a7yAzG7HElw}}<br />
<br />
[[Image:Jct_roundabout.png|frameless|right]]<br />
<br />
===Roundabouts and traffic circles===<br />
It may be tempting to use the roundabout feature to create a loop shape. Do not do this unless the loop is a roundabout or traffic circle. Roundabouts give special routing instructions, and must not be used for other purposes. To learn more, please see the [[Roundabout]] page.<br />
<br />
=== At-grade connectors ===<br />
<br />
: [[Image:Jct_at_grade_keep.png]]<br />
<br />
With exceptions, don't set these segments as ramps! Watch out for all of the turns you need to restrict. For a more detailed discussion, see the full [[At-grade connectors]] article.<br />
<br />
== Interchanges and ramps ==<br />
<br />
An '''interchange''' is a road junction where two roads are connected by dedicated roadways, called '''ramps'''. The roads connected by an interchange do not intersect one another directly, and if they cross, the crossing is grade-separated.<br />
<br />
=== When to use ramps ===<br />
<br />
Use of the {{Ramp}} type is governed by the following rules:<br />
* [[Road types/USA]]<br />
* [[At-grade connectors]]<br />
<br />
=== Ramp and interchange style ===<br />
<br />
For guidance on the proper configuration of ramps, interchanges and wayfinders, see [[Junction Style Guide/Interchanges]].<br />
<br />
== Special Cases ==<br />
=== Transitions ===<br />
{| class="Wikitable floatright"<br />
| [[Image:Jct_transition.png|x150px|border]]<br />
| [[Image:Jct_transition_90.png|x150px|border]]<br />
|}<br />
A transition is a non-junction depicted using a junction node.<br />
<br />
Valid examples of where to use a Transition node include:<br />
# Road name changes<br />
# City Limits<br />
# Road Direction changes<br />
# Part of a [[#Loops|Loop Road]]<br />
# Speed Limit Change<br />
<br />
Before the current house numbering system came into use, transition nodes were used to aid in house numbering, but that is no longer required.<br />
<br />
There may be existing transition nodes on the map for other reasons like remaining after a connecting road is deleted, inherited from to the original base map import when rivers and streams created junctions, etc.<br />
<br />
As long as you are '''certain''' it is not a valid transition node, a superfluous junction node may be [[Map Editing Quick-start Guide#Delete a Junction|deleted]]. Doing so will simplify the map, eliminate turn restrictions to maintain, and reduce computing resource needs. Also consider removing the [[Creating and editing road segments#Adjusting road geometry .28nodes.29|geometry node]] which will replace the junction node you delete, if that geometry node is not needed.<br />
<br />
=== Roads to Nowhere ===<br />
In certain situations it may be necessary to add road segments that are un-drivable in order to provide accurate navigation instructions.<br />
<br />
==== Actual ====<br />
A valid use of this technique is at the temporary end of a freeway. As a freeway is built, it is often opened in sections, up to a certain exit. If we map this as a regular freeway segment leading to a ramp segment, no announcement will be made for that final exit, no matter what we name the exit ramp.<br />
<br />
This can be confusing if the ramp is set up as a properly signed and numbered exit, especially if a driver is traveling a long distance on this freeway. Imagine traveling down a freeway and seeing your next instruction is "turn left at Main St." You would probably wonder if there was a map error since you shouldn't be making a left turn off of a freeway.<br />
<br />
If we map even just a little of the future path of the freeway, this gives the routing engine a junction which will generate an "exit" instruction at the end of the freeway, thus eliminating any confusion.<br />
<br />
Conversely, if we do NOT want an exit instruction at the end of a freeway, ensure there are no road segments extending past the final exit, to ensure the final exit is the only path out of the final freeway segment.<br />
<br />
==== Fake ====<br />
''(coming soon)''<br />
<br />
=== Offset Roads ===<br />
[[Image:Jct_4_offset.png|left|x150px|border]]<br />
Sometimes you will find two roads which cross, where one does not quite line up with the other.<br />
<br />
There are a few things we need to look at in this situation.<br />
{{clear}}<br />
:* Do the roads actually line up in reality? If so we need to modify the junction to be a basic 4-way junction.<br />
{| class="Wikitable floatright"<br />
|[[Image:Jct_4_offset_align.png|x150px|border]]<br />
|[[Image:Jct_4_offset_align_ex.png|x150px|border]]<br />
|}<br />
:* Do the roads ALMOST line up in reality? If you were giving instructions to a person and would tell them to go straight with no mention of any slight turn or jog, then we want to make it into a 4-way junction. You may need to "split the difference" and not follow the centerline of either road to achieve this. The angles are exaggerated in this next example to show how the junction is forced to be close to 90 degrees, then we taper to the true centerlines of the roads. In practice this can be much more gradual and/or done while zoomed in very close.<br />
[[Image:Jct_4_offset_ex.png|right|x150px|border]]<br />
:* Finally, is there a true separation between the roads? Would you need to say for example "turn left then make an immediate right"? If so then we will want to leave the junction such that the two sides do not align.<br />
{{clear}}<br />
<br />
[[Image:Jct_4_offset_sep_ex.png|left|x150px|border]]<br />
Since we want to avoid very short segments of road (the GPS chips in consumer devices can be very inaccurate which may make it seem that a driver skipped right over a short segment. This will result in [[Map Problems in Waze Map Editor|automated map errors]] and possible route recalculations in the client,) it may be wise to shift the side roads as far apart from each other as possible with them still in the proper location (along the far curb lines for a residential street for example). This will maximize the length of the short segment between the side roads.<br />
<br />
[[Category:Style Guides]]<br />
[[Category:Table examples]]</div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=File:Jct_dead_end_ex.png&diff=138204
File:Jct dead end ex.png
2016-02-22T17:54:37Z
<p>Vaindil: Vaindil uploaded a new version of &quot;File:Jct dead end ex.png&quot;</p>
<hr />
<div>Dead end junction placement example</div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=File:Jct_dead_end.png&diff=138198
File:Jct dead end.png
2016-02-22T17:36:43Z
<p>Vaindil: Vaindil uploaded a new version of &quot;File:Jct dead end.png&quot;</p>
<hr />
<div>Dead end junction</div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=File:Jct_3_90.png&diff=138195
File:Jct 3 90.png
2016-02-22T17:27:00Z
<p>Vaindil: Vaindil uploaded a new version of &quot;File:Jct 3 90.png&quot;</p>
<hr />
<div>3 way, 90 degree junction<br />
<br />
[[Category:WME]]<br />
[[Category:New Road Layer]]<br />
[[Category:Junction]]</div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=File:Jct_ramp_no_geo.png&diff=138184
File:Jct ramp no geo.png
2016-02-22T16:20:56Z
<p>Vaindil: Vaindil uploaded a new version of &quot;File:Jct ramp no geo.png&quot;</p>
<hr />
<div>diverging ramp, no geometry tweak</div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=File:Jct_4_90.png&diff=138182
File:Jct 4 90.png
2016-02-22T16:14:25Z
<p>Vaindil: Vaindil uploaded a new version of &quot;File:Jct 4 90.png&quot;</p>
<hr />
<div>4 way, 90 degree junction</div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=Michigan/Area_Managers/Main&diff=135507
Michigan/Area Managers/Main
2016-01-27T16:34:01Z
<p>Vaindil: */Area manager table update*/</p>
<hr />
<div><!---------------------- DO NOT MODIFY THIS TOP CODE -------------------------------<br />
------------------------------------------------------------------------------------<br />
--><noinclude>{{:USA/CommonState/ReturnPurge|{{#titleparts:{{PAGENAME}}|-1|-2}}}}</noinclude><includeonly><!--<br />
------------------------------------------------------------------------------------<br />
---- Area Managers: Cancel edit and use link on table next to "Area Managers". -----<br />
---- Other Area Editors: Cancel edit and use link on table next to "Other Area<br />
---- Editors". If does not exist, that section can be added from talk page.---- Country/State Managers: Continue.<br />
------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this <br />
---- state. When first setting up this page, remove the example users for Country<br />
---- and State managers. Area Managers are changed in a different section as noted<br />
---- above. When adding a new user, use the following template: <br />
{{AM/Editor|Username|Area Managed|Other Comment}}<br />
---- If any fields are skipped, ensure all three the pipe "|" characters are present.<br />
---- Note the badge1, badge2, badge3 entries are only what is defined under:{{AM/Badge}}<br />
---- This link can be reached from http://wiki.waze.com/wiki/Template:AM/Badge or<br />
---- search the Wiki for:<br />
Template:AM/Badge<br />
<br />
---- When adding a new user, place the new template based on Rank (highest first)<br />
---- and then alphabetical order in that rank.<br />
------------------------------------------------------------------------------------<br />
--------------------- AREA MANAGER TABLE BEGINS BELOW ------------------------------<br />
---------------------------- EDIT BELOW LINE ---------------------------------------<br />
-----------------------------------------------------------------------------------><br />
Area managers may also add their managed polygon to [http://mapsengine.google.com/map/u/0/edit?mid=ziFWFU1Jd4Vg.kNeUGPOnDl5o this Google map]. Just send a [http://www.waze.com/forum/ucp.php?i=pm&mode=compose&subject=MI%20Resource%20Wiki:&username=lelehman PM to user lelehman] for access.<br />
<br />
<br />
{{AM/Top}}<!-- Top of the table --><br />
{{AM/Country}}<!-- Defines the start of the country manager section --><br />
{{AM/Editor|GizmoGuy411|6|Statewide|Regional Coordinator|badge1=rc|badge2=gc|badge3=mgc}}<br />
{{AM/Editor|SkiDooGuy|6|Statewide|Asst Regional Coordinator|badge1=rc|badge2=lc|badge3=mlc|}}<br />
{{AM/Editor|Sketch|6|Statewide|Detroit Enthusiast|badge1=gc|badge2=mgc}}<br />
{{AM/Editor|TerryPurdue|5|Statewide|Country Manager|badge1=cm|badge2=m}}<br />
{{AM/State}}<!-- Defines the start of the state manager section --><br />
{{AM/Editor|Doryphore_6|5|Statewide|MI State Manager, AM of GLR|badge1=SM|badge2=AM}}<br />
{{AM/AreaLink}}<!-- Defines the start of the area manager section --><br />
{{#ifexist: {{BasePage2}}/AM/Editor/Area |<!--<br />
-->{{:{{BasePage2}}/AM/Editor/Area}}<!-- Area managers are edited through the main page link accessed from within the table itself. Do not add them here.--><br />
}}<!-- End ifexist --><br />
{{AM/Bottom}}<!-- Bottom of the table; must be the last line of table. -------------<br />
------------------------------------------------------------------------------------<br />
<br />
-->{{#ifexist: {{BasePage2}}/AM/Editor/Area2 <!-- If other table exists --><br />
| {{AM/Area2Link}}<!--then display Other Table, or skip --><br />
}}<!-- End ifexist --></includeonly><br />
<!-----------------------------------------------------------------------------------><br />
<!------------------------ DO NOT ADD CODE BELOW THE TABLE --------------------------></div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=Michigan/AM/Editor/Area&diff=135505
Michigan/AM/Editor/Area
2016-01-27T16:22:36Z
<p>Vaindil: </p>
<hr />
<div><!---------------------- DO NOT MODIFY THIS TOP CODE ------------------------------<br />
------------------------ SCROLL DOWN FOR INSTRUCTIONS -----------------------------<br />
-----------------------------------------------------------------------------------><noinclude><!--Keep hard coded due to unique page address--><div class="center"><span class="noprint plainlinks purgelink" style="{{Road/style}}background-color:#93c4d3">[{{FULLURL:{{#titleparts:{{PAGENAME}}|-3}}|action=purge}}#Area_Managers <span title="Return to the Area Manager table">&nbsp;Press here to return to the Area Managers table to see your changes&nbsp;</span>]</span></div></noinclude><includeonly><!--<br />
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ------------------------------------- INSTRUCTIONS - START READING HERE ------------------------------------- --------------------<br />
-------------------------------------------------------------------------------------<br />
-- Country/State Managers: Cancel this edit and use the link at the top of the table.<br />
<br />
-------------------------------------------------------------------------------------<br />
<br />
-- Editors: To add yourself to this Area Manager table, copy and paste the following<br />
<br />
-- template into the space below with the other {{AM/Editor|...}} templates. Add<br />
-- yourself into rank order (higher at top)then alphabetical order by user name (A-Z)<br />
-------------------------------------------------------------------------------------<br />
{{AM/Editor|YOUR_USER_NAME|YOUR_RANK#|YOUR_AREA|ANY_COMMENT}}<br />
-------------------------------------------------------------------------------------<br />
-- then in the Summary field enter "Added YOUR_USER_NAME" and press "Save page"<br />
-------------------------------------------------------------------------------------<br />
------------------- DO NOT MODIFY CONTENT ABOVE THE EQUAL SIGN ----------------------<br />
================================================================================-->|-<br />
<br />
{{AM/Editor|jdeyoung|6|West Michigan|Indiana State Manager}}<br />
{{AM/Editor|hitfactor|5|Southern Lower Michigan}}<br />
{{AM/Editor|lelehman|5|Mid-Michigan, Tri-Cities|Bay, Clinton, Eaton, Genessee, Gratiot, Ingham, Isabella, Livingston, Midland, Saginaw, and Shiawassee counties}}<br />
{{AM/Editor|zohar760|5|Central/Southern Oakland/Macomb, Wayne, and all of Detroit|Home area: Sterling Heights, editable area stretches throughout North Macomb, East Oakland, and Wayne County/Downtown Detroit}}<br />
{{AM/Editor|captnkeegs|4|Grand Rapids Area|Mostly working Kent & Barry county some Ottawa & Allegan county area}}<br />
{{AM/Editor|SuperMari0O|4|Upper Peninsula|}}<br />
{{AM/Editor|BuzzardJoe|3|Rochester Hills|Likes to wiki}}<br />
{{AM/Editor|falco_sparverius|3|Kalamazoo/Battle Creek Area, and Presque Isle County|}}<br />
{{AM/Editor|Gazoo4U|3|SE Luce county near Newberry|}}<br />
{{AM/Editor|JB15TM|3|Shiawassee / Genesee Counties|}}<br />
{{AM/Editor|miked_64|3|SW Lower MI|GR, Kzoo and surrounding areas}}<br />
{{AM/Editor|trukkurt|3|Muskegon Area|}}<br />
{{AM/Editor|vaindil|3|Traverse City and surrounding areas|}}<br />
<br />
<br />
<!--+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<br />
------------------- DO NOT MODIFY CONTENT BELOW THE PLUS SIGN -----------------------<br />
-------------------------------------------------------------------------------------<br />
-------------------------------------------------------------------------------------<br />
--></includeonly></div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=Michigan/AM/Editor/Area&diff=135504
Michigan/AM/Editor/Area
2016-01-27T16:22:08Z
<p>Vaindil: update zohar760 rank</p>
<hr />
<div><!---------------------- DO NOT MODIFY THIS TOP CODE ------------------------------<br />
------------------------ SCROLL DOWN FOR INSTRUCTIONS -----------------------------<br />
-----------------------------------------------------------------------------------><noinclude><!--Keep hard coded due to unique page address--><div class="center"><span class="noprint plainlinks purgelink" style="{{Road/style}}background-color:#93c4d3">[{{FULLURL:{{#titleparts:{{PAGENAME}}|-3}}|action=purge}}#Area_Managers <span title="Return to the Area Manager table">&nbsp;Press here to return to the Area Managers table to see your changes&nbsp;</span>]</span></div></noinclude><includeonly><!--<br />
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ------------------------------------- INSTRUCTIONS - START READING HERE ------------------------------------- --------------------<br />
-------------------------------------------------------------------------------------<br />
-- Country/State Managers: Cancel this edit and use the link at the top of the table.<br />
<br />
-------------------------------------------------------------------------------------<br />
<br />
-- Editors: To add yourself to this Area Manager table, copy and paste the following<br />
<br />
-- template into the space below with the other {{AM/Editor|...}} templates. Add<br />
-- yourself into rank order (higher at top)then alphabetical order by user name (A-Z)<br />
-------------------------------------------------------------------------------------<br />
{{AM/Editor|YOUR_USER_NAME|YOUR_RANK#|YOUR_AREA|ANY_COMMENT}}<br />
-------------------------------------------------------------------------------------<br />
-- then in the Summary field enter "Added YOUR_USER_NAME" and press "Save page"<br />
-------------------------------------------------------------------------------------<br />
------------------- DO NOT MODIFY CONTENT ABOVE THE EQUAL SIGN ----------------------<br />
================================================================================-->|-<br />
<br />
{{AM/Editor|jdeyoung|6|West Michigan|Indiana State Manager}}<br />
{{AM/Editor|hitfactor|5|Southern Lower Michigan}}<br />
{{AM/Editor|lelehman|5|Mid-Michigan, Tri-Cities|Bay, Clinton, Eaton, Genessee, Gratiot, Ingham, Isabella, Livingston, Midland, Saginaw, and Shiawassee counties}}<br />
{{AM/Editor|captnkeegs|4|Grand Rapids Area|Mostly working Kent & Barry county some Ottawa & Allegan county area}}<br />
{{AM/Editor|SuperMari0O|4|Upper Peninsula|}}<br />
{{AM/Editor|zohar760|5|Central/Southern Oakland/Macomb, Wayne, and all of Detroit|Home area: Sterling Heights, editable area stretches throughout North Macomb, East Oakland, and Wayne County/Downtown Detroit}}<br />
{{AM/Editor|BuzzardJoe|3|Rochester Hills|Likes to wiki}}<br />
{{AM/Editor|falco_sparverius|3|Kalamazoo/Battle Creek Area, and Presque Isle County|}}<br />
{{AM/Editor|Gazoo4U|3|SE Luce county near Newberry|}}<br />
{{AM/Editor|JB15TM|3|Shiawassee / Genesee Counties|}}<br />
{{AM/Editor|miked_64|3|SW Lower MI|GR, Kzoo and surrounding areas}}<br />
{{AM/Editor|trukkurt|3|Muskegon Area|}}<br />
{{AM/Editor|vaindil|3|Traverse City and surrounding areas|}}<br />
<br />
<br />
<!--+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<br />
------------------- DO NOT MODIFY CONTENT BELOW THE PLUS SIGN -----------------------<br />
-------------------------------------------------------------------------------------<br />
-------------------------------------------------------------------------------------<br />
--></includeonly></div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=Michigan/Resources/Main&diff=134973
Michigan/Resources/Main
2016-01-22T14:13:04Z
<p>Vaindil: added Mi Drive script</p>
<hr />
<div><!-- This page is only transcluded into (displayed on) the main page for this state. See more detailed instructions below. --><noinclude>{{:USA/CommonState/ReturnPurge|{{SubPage2}}}}<br/></noinclude><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
<br />
====Statewide====<br />
*[http://mdotcf.state.mi.us/public/maps_nfc/ MDOT NFC Maps] - MDOT National Functional Classification (NFC) maps by county and urban area. An effort was started in late 2013 to convert metro Detroit and other major cities to their corresponding NFC road classifications.<br />
*[http://www.michigan.gov/mdot/0,4616,7-151-11151---,00.html MDOT maps]<br />
*[http://www2.census.gov/geo/pvs/bas/annexation/26/ Boundary and Annexation Survey Maps] from [http://www.census.gov/ US Census Bureau]<br />
*[http://www.census.gov/geo/maps-data/maps/2010ref/st26_tract.html Michigan Census Designated Places] from US Census.<br />
*[http://tigerweb.geo.census.gov/tigerweb/ TIGERweb] from [http://www.census.gov/ US Census Bureau]<br />
*[http://www.mcgi.state.mi.us/prfinder/mapBasic.aspx MDOT Physical Road (PR) Finder] (also see the [http://www.mcgi.state.mi.us/prfinder/MCGI.aspx PR Finder Home page])<br />
*[http://www.michigan.gov/mdot/0,4616,7-151-9621_11008---,00.html MDOT's Major Road Projects]<br />
*[http://mdotnetpublic.state.mi.us/drive/Default.aspx MDOT's MiDrive] live traffic cameras, accident reports, construction zones<br />
<br />
====County====<br />
*[http://www.micountyroads.org/crcs.php Directory of county road commissions], many of which maintain a list of planned improvements or current projects<br />
*[http://wiki.waze.com/wiki/Michigan/GIS Listing] of all counties in Michigan and available GIS maps.<br />
<br />
====City====<br />
*[http://www.auburnhills.org/community/2015roadprojects/index.php Auburn Hills Road Projects]<br />
*[http://www.detroitmi.gov/2015-Construction-Projects Detroit Construction Projects]<br />
*[http://m-1rail.com/construction/construction-schedule/ Detroit M-1 Rail Project]<br />
*[http://grcity.us/engineering-department/Construction-Updates/Pages/default.aspx Grand Rapids construction updates]<br />
*[http://ww3.rochesterhills.org/constructionmap/ Rochester & Rochester Hills construction map]<br />
<br />
====Recommended WME UI Enhancements====<br />
*[https://www.waze.com/forum/viewtopic.php?f=819&t=40705 WME Color Highlights]<br />
*[https://www.waze.com/forum/viewtopic.php?f=819&t=108055 WME Toolbox]<br />
*[https://www.waze.com/forum/viewtopic.php?f=819&t=76488 WME Validator]<br />
*[https://greasyfork.org/en/scripts/8749-wme-validator-localization-for-michigan Michigan localised enhancement of Validator]<br />
*[https://www.waze.com/forum/viewtopic.php?f=819&t=61926 WME Junction Angle Info]<br />
*[https://www.waze.com/forum/viewtopic.php?f=819&t=95038 WME Chat addon]<br />
*[https://greasyfork.org/en/scripts/5592-wme-ur-comments-stable WME UR Comments]<br />
*[https://greasyfork.org/en/scripts/6236-wme-urcomments-custom-list WME URComments Custom List]<br />
*[https://greasyfork.org/en/scripts/1952-uroverview-plus-uro UROverview Plus (URO+)]<br />
*[https://greasyfork.org/en/scripts/1776-wme-ur-mp-tracking WME UR-MP tracking]<br />
*[https://greasyfork.org/en/scripts/8693-wme-closest-segment WME Closest Segment]<br />
*[https://www.waze.com/forum/viewtopic.php?f=819&p=1194011#p1194011 WME HN Tool]<br />
*[https://chrome.google.com/webstore/detail/wme-michigan/klbifhgolgcgpcnmdpcmkpkgpfmjpalm WME Michigan]<br />
*[https://greasyfork.org/en/scripts/11453-wme-counties-michigan-census-2014 Michigan County Overlay]<br />
*[https://greasyfork.org/en/scripts/15672-mi-drive-total-closures-only Mi Drive Total Closures Only] ''(hides everything except total closures and current accidents on [http://mdotnetpublic.state.mi.us/drive/Default.aspx Mi Drive])''<br />
<br />
====Forms to Address Mapping/Navigation Issues====<br />
*[https://support.google.com/waze/contact/search_issues?hl=en Waze App Search Issues]<br />
<br />
<br />
<br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Resources|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Resources]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=User:Vaindil&diff=134962
User:Vaindil
2016-01-22T13:40:59Z
<p>Vaindil: changed dumb winky face to a normal smiley face</p>
<hr />
<div>I wrote this so my username would stop appearing red on the wiki. Nothing to see here. :)</div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=Michigan/Closures/Main&diff=126217
Michigan/Closures/Main
2015-11-16T03:26:21Z
<p>Vaindil: /*Closures/Main*/ Added link to GR closures page</p>
<hr />
<div><!-- This page is only transcluded into (displayed on) the main page for this state. See more detailed instructions below. --><noinclude>{{:USA/CommonState/ReturnPurge|{{SubPage2}}}}<br/></noinclude><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
The following are resources run by the Michigan DOT:<br />
*[http://mi.gov/drive/ MDOT MiDrive (Traffic, Construction, etc.)]<br />
*[http://twitter.com/MichiganDOT MDot Twitter feed]<br />
<br />
Local Resources:<br />
County Resources<br />
* [http://www.wcroads.org/Roads/MajorRoadWork Washtenaw County Road Work]<br />
City Resources<br />
* [http://www.a2gov.org/departments/engineering/traffic/pages/road-and-lane-closure.aspx Ann Arbor closures]<br />
* [http://grcity.us/enterprise-services/Lights-Signals-and-Signs/Pages/Road-Closures.aspx Grand Rapids closures]<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Closures|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Closures]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=User_talk:Vaindil&diff=126216
User talk:Vaindil
2015-11-16T03:23:06Z
<p>Vaindil: Created page with "~~~~ Oh look, a talk page."</p>
<hr />
<div>[[User:Vaindil|Vaindil]] ([[User talk:Vaindil|talk]]) 03:23, 16 November 2015 (UTC)<br />
Oh look, a talk page.</div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=User:Vaindil&diff=126215
User:Vaindil
2015-11-16T03:22:27Z
<p>Vaindil: Created page with "I wrote this so my username would stop appearing red on the wiki. Nothing to see here. ;)"</p>
<hr />
<div>I wrote this so my username would stop appearing red on the wiki. Nothing to see here. ;)</div>
Vaindil
https://www.waze.com/wiki/USA/index.php?title=Michigan/AM/Editor/Area&diff=124877
Michigan/AM/Editor/Area
2015-11-06T14:20:07Z
<p>Vaindil: AM table update</p>
<hr />
<div><!---------------------- DO NOT MODIFY THIS TOP CODE ------------------------------<br />
------------------------ SCROLL DOWN FOR INSTRUCTIONS -----------------------------<br />
-----------------------------------------------------------------------------------><noinclude><!--Keep hard coded due to unique page address--><div class="center"><span class="noprint plainlinks purgelink" style="{{Road/style}}background-color:#93c4d3">[{{FULLURL:{{#titleparts:{{PAGENAME}}|-3}}|action=purge}}#Area_Managers <span title="Return to the Area Manager table">&nbsp;Press here to return to the Area Managers table to see your changes&nbsp;</span>]</span></div></noinclude><includeonly><!--<br />
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ------------------------------------- INSTRUCTIONS - START READING HERE ------------------------------------- --------------------<br />
-------------------------------------------------------------------------------------<br />
-- Country/State Managers: Cancel this edit and use the link at the top of the table.<br />
<br />
-------------------------------------------------------------------------------------<br />
<br />
-- Editors: To add yourself to this Area Manager table, copy and paste the following<br />
<br />
-- template into the space below with the other {{AM/Editor|...}} templates. Add<br />
-- yourself into rank order (higher at top)then alphabetical order by user name (A-Z)<br />
-------------------------------------------------------------------------------------<br />
{{AM/Editor|YOUR_USER_NAME|YOUR_RANK#|YOUR_AREA|ANY_COMMENT}}<br />
-------------------------------------------------------------------------------------<br />
-- then in the Summary field enter "Added YOUR_USER_NAME" and press "Save page"<br />
-------------------------------------------------------------------------------------<br />
------------------- DO NOT MODIFY CONTENT ABOVE THE EQUAL SIGN ----------------------<br />
================================================================================-->|-<br />
<br />
{{AM/Editor|jdeyoung|6|West Michigan|Indiana State Manager}}<br />
{{AM/Editor|hitfactor|5|Southern Lower Michigan}}<br />
{{AM/Editor|lelehman|5|Mid-Michigan, Tri-Cities|Bay, Clinton, Eaton, Genessee, Gratiot, Ingham, Isabella, Livingston, Midland, Saginaw, and Shiawassee counties}}<br />
{{AM/Editor|captnkeegs|4|Grand Rapids Area|Mostly working Kent & Barry county some Ottawa & Allegan county area}}<br />
{{AM/Editor|SuperMari0O|4|Upper Peninsula|}}<br />
{{AM/Editor|zohar760|4|Central/Southern Oakland/Macomb, Wayne, and all of Detroit|Home area: Sterling Heights, editable area stretches throughout North Macomb, East Oakland, and Wayne County/Downtown Detroit}}<br />
{{AM/Editor|BuzzardJoe|3|Rochester Hills|Likes to wiki}}<br />
{{AM/Editor|falco_sparverius|3|Kalamazoo and Battle Creek|}}<br />
{{AM/Editor|Gazoo4U|3|SE Luce county near Newberry|}}<br />
{{AM/Editor|JB15TM|3|Shiawassee / Genesee Counties|}}<br />
{{AM/Editor|miked_64|3|SW Lower MI|GR, Kzoo and surrounding areas}}<br />
{{AM/Editor|trukkurt|3|Muskegon Area|}}<br />
{{AM/Editor|vaindil|3|Traverse City and surrounding areas|}}<br />
<br />
<br />
<!--+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<br />
------------------- DO NOT MODIFY CONTENT BELOW THE PLUS SIGN -----------------------<br />
-------------------------------------------------------------------------------------<br />
-------------------------------------------------------------------------------------<br />
--></includeonly></div>
Vaindil