Ohio/new editors: Difference between revisions Discussion View history

(updates for Discord, downlock/uplock requests)
Line 62: Line 62:
----->
----->


=== Other Recommended Scripts ===
Other Recommended Scripts
 
# If you are working on User Reports (UR), install [https://www.waze.com/forum/viewtopic.php?f=819&t=122776 UrComments] . UR Comments is a script designed to streamline the process of responding to Update Requests. It can autofill the comment box based on UR type, or you can manually choose from the list of responses, depending on your preference.
# If you are working on User Reports (UR), install [https://www.waze.com/forum/viewtopic.php?f=819&t=122776 UrComments] . UR Comments is a script designed to streamline the process of responding to Update Requests. It can autofill the comment box based on UR type, or you can manually choose from the list of responses, depending on your preference.
# If you are working on places, install [https://www.waze.com/forum/viewtopic.php?f=819&t=133650&start=60#p1548089 WME Closest Segment] . It helps you determine the closest segment to the navigation stop point of a place. A line is drawn from a selected place (for point places) or its navigation point (for area places) to the nearest segment.
# If you are working on places, install [https://www.waze.com/forum/viewtopic.php?f=819&t=133650&start=60#p1548089 WME Closest Segment] . It helps you determine the closest segment to the navigation stop point of a place. A line is drawn from a selected place (for point places) or its navigation point (for area places) to the nearest segment.
Line 72: Line 71:
# [https://www.waze.com/forum/viewforum.php?f=819 Additional Scripts]. Feel free to browse the Waze Forum for additional scripts. The list above is not by all means complete, just ones that will get you started.  
# [https://www.waze.com/forum/viewforum.php?f=819 Additional Scripts]. Feel free to browse the Waze Forum for additional scripts. The list above is not by all means complete, just ones that will get you started.  


== The Bot ==
== The Waze CommunityBot ==
 
Once you join the Ohio GHO, Type ''!wb help'' in the GHO. This will get you started with Wazebot (wb); Wazebot will send you some help. In a DM (Direct Message or conversation) with the wazebot, type the following to set up your notifications by name and/or nickname. Wazebot will send you the instructions.
 
# !mentions
# !nickname
 
If some of the abbreviations and terms used are not clear, you can also use the wazebot to lookup terms for you. In a DM with wazebot, type '''!wb glossary [''word'']''' and the bot will send you some definitions.
 
If the notifications on your phone or computer get to be too much, in the GHO you can select the “3 dots” (by the blue arrow), Select “Options” and turn off notifications if you do not want to be disturbed; just uncheck the box.
 
'''Please do not modify/change any of the other options; they affect everyone.'''


[[File:Ohghobotoptions.png|Ohio Bot Options]]
Once you join the [https://discord.me/wazeglr Ohio Discord channel], send a direct message to @communitybot & type '''!help''' and press Enter.  This will trigger an autoreply with a link to all the commands typically used in Discord, and how to set them up for your own preferences.


Additional Help for the Bot can be found [https://vaindil.com/wazebot/commands/ here].
If some of the abbreviations and terms used are not clear, you can also use the CommunityBot to lookup terms for you.  In a DM with @communitybot, type '''!glossary ['''''search term''''']''' , and CommunityBot will send you some definitions.


== Permalink (PL) ==
== Permalink (PL) ==

Revision as of 16:10, 15 July 2018

We are so glad you decided to join us in improving the Waze Map in Ohio. Here are some things that will make your Map Editing experience a little easier (and hopefully more enjoyable).

Welcome New Editors

New editors should familiarize themselves with the Ohio Wiki before doing very much editing.

To better understand how to edit the map, check out The Editing Manual and Map Editing Style Guidelines. It's also important to read about Edits to avoid before getting started.

Waze Map Editor (WME)

First thing in the Editor, Select the gear icon and enable the first two checkboxes:


Add Ins, Extensions and Scripts

New editors should be aware there are many scripts and extensions that editors use to assist with editing that not only make some jobs easier, but verifies what we do is correct. The use of these scripts is highly encouraged and those listed below are the ones you should install, at a minimum, to get started.

Toolbox

After Toolbox is installed it will add several things to the WME editor. At the top next to the Places Icon will be a picture of a toolbox. If you hover your mouse over it, a menu should open. Select the following options:

TamperMonkey / GreaseMonkey

The most common and supported browser is Chrome with Firefox a close second. Install the appropriate one for your browser. This is needed to install other scripts.

Ohio Specific Scripts

WME OH Scripts

WME OH Scripts


This script will dynamically load the Ohio specific scripts that we use to aid in editing. Install this and you can disable/remove the OH Validator Localization, OH Counties overlay, OH Cities 1 & OH Cities 2 scripts from Tampermonkey.

This will insert a OH Scripts tab to your left bar where you can toggle these scripts on/off (just like with Tampermonkey, toggling will require a hard refresh to go into effect).

In addition to loading the selected scripts, a button is provided for launching ODOT TIMS with either the County Road (CR) or Function Classification (FC) layer enabled, at the current location of the WME window.

A button is also provided for opening the current WME window location in Google Map Maker (GMM).


Other Recommended Scripts

  1. If you are working on User Reports (UR), install UrComments . UR Comments is a script designed to streamline the process of responding to Update Requests. It can autofill the comment box based on UR type, or you can manually choose from the list of responses, depending on your preference.
  2. If you are working on places, install WME Closest Segment . It helps you determine the closest segment to the navigation stop point of a place. A line is drawn from a selected place (for point places) or its navigation point (for area places) to the nearest segment.
  3. Junction Angle Info. This script helps with junction maintenance. If two connected segments are selected, it shows the turn angle, and estimates navigation instructions. Otherwise it shows the the angle between each segment.
  4. WME Simple Permalink. Shortens WME permalinks by removing any layer and filter specifications.
  5. Place Harmonizer (WMEPH). Harmonizes, formats and locks a selected place. NOTE: All Ranks can now use this script.
  6. When working with House Numbers (HN), please use this script by JustinS83. It highlights un-nudged house numbers. WME HN Tool (JustinS83 fork)
  7. Additional Scripts. Feel free to browse the Waze Forum for additional scripts. The list above is not by all means complete, just ones that will get you started.

The Waze CommunityBot

Once you join the Ohio Discord channel, send a direct message to @communitybot & type !help and press Enter. This will trigger an autoreply with a link to all the commands typically used in Discord, and how to set them up for your own preferences.

If some of the abbreviations and terms used are not clear, you can also use the CommunityBot to lookup terms for you. In a DM with @communitybot, type !glossary [search term] , and CommunityBot will send you some definitions.

Permalink (PL)

An URL, aka a browser link, (http://...) that shows the map with the same view as the user who created the Permalink (PL). Location, zoom, layers, and selected segments will be the same. You can find the icon for the PL in the lower right corner of the WME screen (two chains linked together). When the mouse is hovered over the icon, press Control-C to copy the Permalink to the clipboard (or right-click it and choose copy). You can then paste the PL into the GHO, an e-mail, or forum message so others can access and view what you are seeing.

Request A Lock Level Change

To request a Lock Level Change on a segment:

  1. Go to the OH Discord channel (you can learn more about the Waze online community here)
  2. State the lock level coming from and going to (example: L3>L1). This is called a "downlock".
  3. Then, state the area the lock is in by naming the closest city.
  4. Next, state your reason for the downlock.
  5. Paste the permalink (PL) starting on its own line.
    • You can select multiple segments in one PL by selecting the first one, holding down the CTRL key and selecting the others.
    • You can go to a new line in Discord by holding the Shift Key and then hitting Return, without sending the message.
  6. Lastly, be polite. A please and thank you go a long way!

Example: Downlock request to change turn restrictions:

Can I please have L3 > L1, Dayton area, to change turn restrictions to match local signage?

<insert PL here and on a new line>

Thank you!

When you are finished, request that the segments you were working be "uplocked" back to the previous lock level. You will have to provide a new PL in case you added a road which would cut the original segment(s), or if the other editors handling the uplock request are using their phones. Example: Uplock request to change turn restrictions:

Can I please have L1 > L3, Dayton area? Finished with turn restrictions; please review and lock when satisfied.

<insert PL here and on a new line>

Thank you!