User:PesachZ/SyncScratch View history

m (Copying text of wiki page for coparison with the "Ohio/new editors" page)
m (Copying text of wiki page for coparison with the "New York/Closures/Major" page)
 
(273 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{AddCode|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).}}
<!-- ========================
    ↓  EDITS TO THIS TABLE ARE MADE BELOW THE INSTRUCTIONS    ↓
==============================
This page is only viewed directly in the Major Events table on the Closures subpage.--><noinclude>[[Category:{{RootPage2}}]]
[{{fullurl:{{BasePage2}}/Closures|action{{=}}purge}} {{u|Click here to return to the {{RootPage2}}/Closures Subpage}}]<br/>


== Welcome New Editors ==
These rows fill the major Event table, and are modified using the template {{tl|Event/Item}}. If you are working on a Major Event in {{RootPage2}}, please add add that event to this table. If the event is already listed, please add your username to the row, preceded by a pipe (|), and change the date to today's date in the <code>updated=</code> parameter.
New editors should familiarize themselves with the [https://wiki.waze.com/wiki/Ohio Ohio Wiki] before doing very much editing.


To better understand how to edit the map, check out [[Editing_manual|The Editing Manual and Map Editing Style Guidelines]]. It's also important to read about [[Edits_to_avoid_(USA)|Edits To Avoid]] before getting started. 


== Waze Map Editor (WME) ==
This template accepts many parameters which must be separated from each other using pipe characters (|), but can be placed in any order and will automatically  the correct parts of the table. To use a parameter you must keep the name of parameter (the part before the equals sign (=) identical to this list, and only modify what goes after the equals sign (=).


First thing in the Editor, Select the ''gear'' icon and enable the first two checkboxes:
==Accepted parameters:==


[[File:WME_options.png]]
*<code>name=</code> The name of the event.
*<code>area=</code> The county or are the event takes place in.
*<code>date=</code> The estimated date(s) this event happens on.
*<code>road=</code> The main road(s) affected by this event.
*<code>pl=</code> A [[permalink]] to the affected road(s), or a link to documenting listing all the affected roads (usually a Waze event closure document).
*<code>source=</code> A link to an official information source for this event, a government website, the hosting organizations webpage, etc.
*<code>status=</code> Whether this event has been submitted to Waze yet for this season. It accepts the following options spelled only exactly as listed here in order to correctly change the color of the row, filled with anything else will display with a white background
**<code>not submitted</code> produces a red background
**<code>submitted</code> produces a light green background
**<code>in progress</code> produces an orange background.
*Up to six editors can be listed in the table for any event. These can be the editors who are working to get it submitted, maintain the segments, or just have special knowledge of the event/area. They are entered as unnamed parameters. Meaning they are to be entered between two pipe (|) characters of the adjacent parameters. Each editors name (without any spaces) should be separated with a pipe (|).
*<code>updated=</code> the date this event was last updated in this table. This is used to keep the table current, and identify stale entries.




== Add Ins, Extensions and Scripts ==
The updated parameter (<code>|updated=YY/MM(/DD)|</code>) should be updated any time you update a row. Put the date you are modifying the row after the equals sign (=).


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 ===
The <code>|date=|</code>, and <code>|updated=|</code> parameters should use the format YY/MM/DD. The day of the month is optional. Using this format will make it easier to sort the list by updated date. This will help ensure the information on the list is current, and make it easy to find stale rows which may need to be adopted by other editors.


* [https://chrome.google.com/webstore/detail/wme-toolbox/ihebciailciabdiknfomleeccodkdejn?hl=en For Chrome]
* [http://gitlab.com/doctorkb/wme-toolbox-public/raw/master/Dist/Firefox/wmetoolbox.xpi For Firefox]


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.
For example an Event row should look like this;
If you hover your mouse over it, a menu should open.  Select the following options:


[[File:Ron-Toolbox-settings.jpg]]
{{Tlx|Event/Item|name=''EVENT NAME''|date{{=}}14/10|in progress|username|updated{{=}}14/08}}


=== 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.
If there are multiple editors it should look like this


* [https://chrome.google.com/webstore/detail/tampermonkey/dhdgffkkebhmkfjojejmpbldmpobfkfo?hl=en TamperMonkey (Chrome)]
{{Tlx|Event/Item|name=''EVENT NAME''|date{{=}}14/10|in progress|username1|username2|updated{{=}}14/08}}
* [https://addons.mozilla.org/en-US/firefox/addon/greasemonkey/ GreaseMonkey (Firefox)]


=== Ohio Specific Scripts ===


==== WME OH Scripts ====


[https://greasyfork.org/en/scripts/23799-wme-oh-scripts WME OH Scripts]
'''Whenever you edit this table, please be sure to include the name of the event you are editing in the summary field under the edit box.'''
————————————————————————————————————




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).
''The actual contents of this page '''will only be visible''' in the [[{{BasePage2 }}/Closures|Major Events table]], or when editing this page.''


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.
==TO EDIT THIS TABLE CLICK HERE >> ==
</noinclude><includeonly><!--
------ DO NOT MODIFY ABOVE THIS LINE -----
======                              ======
======                              ======
======                              ======
====== DO NOT MODIFY ABOVE THIS LINE ====-->
{{Event/Item|name=New Years Celebration|area=NYC|road=Times Sq/Coney Island|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1716991474|date=12/31-01/01 annual|status=submitted|Rfrsw101|jdelosa|johnsninja58|PesachZ|updated=2017/02/08}}


A button is also provided for opening the current WME window location in Google Map Maker (GMM).
{{Event/Item|name=NYC 1/2 Marathon & St. Patricks' Day Parade|date=03 annual|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=339510355|area=NYC|road=5 Boroughs|status=submitted|updated=2017/02/09|Rfrsw101|jdelosa|johnsninja58|PesachZ}}


<!-----
{{Event/Item|name=July 4th Celebration|area=NYC|status=submitted|updated=2017/02/12|Rfrsw101|jdelosa|johnsninja58|PesachZ|road=FDR Dr|date=07/04 annual|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1864894199|source=http://www.nyc.gov/html/dot/html/motorist/wkndtraf.shtml}}


==== WME US Government Boundaries ====
{{Event/Item|name=Summer Streets|road=Park Ave|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1984749524|source=http://www.nyc.gov/html/dot/summerstreets/html/home/home.shtml|date=08 First 3 Sundays|area=NYC|status=submitted|updated=2017/02/10|Rfrsw101|jdelosa|johnsninja58|PesachZ}}


[https://greasyfork.org/en/scripts/25631-wme-us-government-boundaries WME US Government Boundaries]
{{Event/Item|name=West Indian Day Parade|date=09 Labor Day annual|area=Kings|road=Eastern Pkwy, Classon-Rochester St Johns-Empire|source=http://maps.nyc.gov/streetclosure/|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1605830763|status=submitted|Rfrsw101|jdelosa|johnsninja58|PesachZ|updated=2017/02/10}}


Currently only displays approximate ZIP code "tabulation areas"*. The zip code at the center of the map view will be displayed in the black header bar. Click the ZIP code there to open a USPS ZIP code-to-city conversion web page.
{{Event/Item|name=TD 5 Boro Bike Tour|area=NYC|date=05 First Sunday annual|road=5 Boroughs|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=790135118|Rfrsw101|jdelosa|johnsninja58|PesachZ|status=submitted|updated=2017/02/08}}


*ZIP codes don't have true boundaries. See the following for more information on "tabulation areas":
{{Event/Item|name=NYC TCS Marathon|area=NYC|date=11 First Weekend annual|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=0|road=5 Boroughs|source=http://www.tcsnycmarathon.org/race-day/course|Rfrsw101|jdelosa|johnsninja58|PesachZ|status=submitted|updated=2017/02/07}}
https://www.census.gov/geo/reference/zctas.html


----->
{{Event/Item|name=UN General Assembly|area=NYC|road=East Midtown|date=09 Last Two Weeks Annual|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1895099030|Rfrsw101|jdelosa|johnsninja58|PesachZ|status=submitted|updated=2017/02/08}}


=== Other Recommended Scripts ===
{{Event/Item|name=Macy's Thanksgiving Day Parade|area=NYC|road=Herald Square|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1774745119|date=11 Last Thursday Annual|source=http://social.macys.com/parade/#route|status=submitted|Rfrsw101|jdelosa|johnsninja58|PesachZ|updated=2017/02/08}}


# 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.
{{Event/Item|name=Chinese New Year Parades|date=01 or 02 annual|pl=https://docs.google.com/spreadsheets/d/1Ira6IdyS3x3YtAlTqoXbU1Muw4ANl8rq7af2zKLcCtM/edit#gid=1190958434|area=NYC|road=Chinatown/8th Avenue/Flushing|status=submitted|updated=2017/02/08|Rfrsw101|jdelosa|johnsninja58|PesachZ}}
# 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.
<!--- DO NOT MODIFY BELOW THIS LINE ------=====                                =====
# [https://chrome.google.com/webstore/detail/wme-junctionangle/cfcpfikgmfoghjfpfepmklballeagadf 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.
=====                                =====
# [https://greasyfork.org/en/scripts/18089-wme-simple-permalink-from-wme-keepmylayers WME Simple Permalink]. Shortens WME permalinks by removing any layer and filter specifications.
=====                                =====
# [https://github.com/WazeUSA/WME-Place-Harmonizer/raw/master/WME-Place-Harmonizer.user.js Place Harmonizer (WMEPH)]. Harmonizes, formats and locks a selected place. '''NOTE: All Ranks can now use this script.'''
----- DO NOT MODIFY BELOW THIS LINE ----->
# When working with House Numbers (HN), please use this script by '''JustinS83'''. It highlights un-nudged house numbers. [https://greasyfork.org/en/scripts/21779-wme-hn-tool-justins83-fork WME HN Tool (JustinS83 fork)]
</includeonly>
# [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 ==
 
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]]
 
Additional Help for the Bot can be found [https://vaindil.com/wazebot/commands/ here].
 
== 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 Change on a segment, go to the OH GHO, state the level coming from and going to and then state the area it is in by naming the closest city.  Next would be your reason, why are you requesting the lock level to change and lastly be polite.  A please and thank you go a long way. 
 
Paste the 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 goto a new line in the GHO by holding the Shift Key and then hitting Return, without sending the message.
 
'''To request a DownLock to change turn restrictions would be formatted like this:'''
 
''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 to the previous 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 are using their phones.
 
''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!''

Latest revision as of 05:15, 19 February 2017

Click here to return to the PesachZ/Closures Subpage

These rows fill the major Event table, and are modified using the template {{Event/Item}}. If you are working on a Major Event in PesachZ, please add add that event to this table. If the event is already listed, please add your username to the row, preceded by a pipe (|), and change the date to today's date in the updated= parameter.


This template accepts many parameters which must be separated from each other using pipe characters (|), but can be placed in any order and will automatically the correct parts of the table. To use a parameter you must keep the name of parameter (the part before the equals sign (=) identical to this list, and only modify what goes after the equals sign (=).

Accepted parameters:

  • name= The name of the event.
  • area= The county or are the event takes place in.
  • date= The estimated date(s) this event happens on.
  • road= The main road(s) affected by this event.
  • pl= A permalink to the affected road(s), or a link to documenting listing all the affected roads (usually a Waze event closure document).
  • source= A link to an official information source for this event, a government website, the hosting organizations webpage, etc.
  • status= Whether this event has been submitted to Waze yet for this season. It accepts the following options spelled only exactly as listed here in order to correctly change the color of the row, filled with anything else will display with a white background
    • not submitted produces a red background
    • submitted produces a light green background
    • in progress produces an orange background.
  • Up to six editors can be listed in the table for any event. These can be the editors who are working to get it submitted, maintain the segments, or just have special knowledge of the event/area. They are entered as unnamed parameters. Meaning they are to be entered between two pipe (|) characters of the adjacent parameters. Each editors name (without any spaces) should be separated with a pipe (|).
  • updated= the date this event was last updated in this table. This is used to keep the table current, and identify stale entries.


The updated parameter (|updated=YY/MM(/DD)|) should be updated any time you update a row. Put the date you are modifying the row after the equals sign (=).


The |date=|, and |updated=| parameters should use the format YY/MM/DD. The day of the month is optional. Using this format will make it easier to sort the list by updated date. This will help ensure the information on the list is current, and make it easy to find stale rows which may need to be adopted by other editors.


For example an Event row should look like this;

{{Event/Item|date=14/10|in progress|username|updated=14/08}}


If there are multiple editors it should look like this

{{Event/Item|date=14/10|in progress|username1|username2|updated=14/08}}


Whenever you edit this table, please be sure to include the name of the event you are editing in the summary field under the edit box. ————————————————————————————————————


The actual contents of this page will only be visible in the Major Events table, or when editing this page.

TO EDIT THIS TABLE CLICK HERE >>