User:PesachZ/SyncScratch View history

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.

@@ Line 1: / Line 1: @@
-<!-- This page is only viewed directly through a link from the state's "unique portion" page. Content on this page will be viewed in its entirety.--><noinclude>{{:USA/CommonState/ReturnPurge|{{SubPage2}}}}<br/></noinclude><!--
+<!-- ========================
------- DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------>
+     ↓   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/>
-{{AddCode|We are so glad you decided to join us in improving the Waze Map in West Virginia. Here are some things that will make your Map Editing experience a little easier (and hopefully more enjoyable). [http://www.youtube.com/watch?v{{=}}UHKdgZmVYN0&feature{{=}}youtu.be Click here for a recent Webinar Intro to Map Editing]}}
+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.
-=== Introduction to Map Editing Webinar ===
-Click here for an [http://www.youtube.com/watch?v=UHKdgZmVYN0&feature=youtu.be Introduction to Map Editing Webinar]
-=== WV GHO ===
+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 (=).
-[[File:Wazebot.png]]
+==Accepted parameters:==
-We have created a Google Hangout (GHO) just for West Virginia. The GHO is where you can go to interact and chat with fellow editors along with your Area and State Managers. It will give you good insight into the best practices and policies in regard to map editing plus give an easy, convenient way for editors to stay in touch, ask questions (any questions, we all started at Rank #1 at some point), request downlocks or review of your work and get Peer-to-Peer Mentoring.
+*<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.
-If you are editing in West Virginia and have not done so; please join us on the WV Editor Hangout. You can join easily with [http://docs.google.com/forms/d/e/1FAIpQLSdGds9PsBtOEfvtdFGVEgTxHaS7-sQZ2_XiXcvX869MKq5SAA/viewform this link].
-=== Waze Bot ===
+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 (=).
-Once you join, Type ''!wb help'' in the WV GHO. This will get you started with Wazebot (wb); Wazebot will send you some help. In a DM (Direct Message or conversation) window with the wazebot overlord:
-: Say hello to the WazeBot. Then back in the WV GHO, type hello @xxxxx (where xxxx is your username. This procedure is necessary to let the bot know you're alive ;P No seriously, the above steps are required to authorize two-way communication between the bot and your own account.
-Also you should set up the following:
+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.
-: !wb setnickname xxxxxx
-: !wb subscribe yyyyyyy
-:: You can subscribe to multiple keywords, names, etc.
-For example, if your waze editor name is ''pittsburgsteelersfaninwv'', you can set your nickname to be '''SteelersFan''' by using '''!wb setnickname SteelersFan'''. Then people can ping you by using @SteelersFan.
+For example an Event row should look like this;
-If your real name is ''Marcus Aurelius'', you can use '''!wb subscribe Marc''' and people can ping you by just using the work "Marc" and won't have to use the @ preface. You can also subscribe to other keywords such as downlock, mapraid, etc. Just continue to subscribe to the bot.
+{{Tlx|Event/Item|name=''EVENT NAME''|date{{=}}14/10|in progress|username|updated{{=}}14/08}}
-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 WV GHO you can select the “3 dots” (circled in Blue), Select “Options” and turn off notifications if you do not want to be disturbed; Just uncheck the box.
+If there are multiple editors it should look like this
-'''Please do not modify/change any of the other options; they affect everyone.'''
+{{Tlx|Event/Item|name=''EVENT NAME''|date{{=}}14/10|in progress|username1|username2|updated{{=}}14/08}}
-[[File:GHO options.png]]
-=== WME (Waze Map Editor) Settings ===
-First thing in the Editor, Select the “gear” icon and enable the first two checkboxes:
+'''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.'''
+————————————————————————————————————
-[[File:WME options.png]]
-=== Add Ins and Scripts ===
-The Waze Community has created extensions and scripts to make editing a little easier and to help spot errors. The following should be installed. Chrome is the recommended browser but FireFox works as well.
+''The actual contents of this page '''will only be visible''' in the [[{{BasePage2 }}/Closures|Major Events table]], or when editing this page.''
-==== Toolbox ====
+==TO EDIT THIS TABLE CLICK HERE >> ==
-This script will highlight some errors that are very common, especially with new editors. Go here to install: [[Scripts/WME_Toolbox|Toolbox]]
+</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}}
-Once you have installed Toolbox, press the Toolbox Icon and select the following options:
+{{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}}
-[[File:Tb options.JPG]]
+{{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}}
-==== TamperMonkey (Chrome) and GreaseMonkey (Firefox) ====
+{{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}}
-You will need this to install the additional scripts. [[Scripts#General_installation_instructions|Install TamperMonkey or GreaseMonkey]]
+{{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}}
-==== Validator ====
+{{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}}
-Tool for highlighting additional errors. Please see [http://www.waze.com/forum/viewtopic.php?t=76488 Validator] for installation information for Chrome or Firefox users.
-===== Temporary Fix to Get Validator Working =====
+{{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}}
-Once you have installed Validator, you will need to do the following to make it work properly:
+{{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}}
-) Go To '''Tampermonkey Dashboard'''
+{{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}}
-) Click '''Utilities''' Tab
+{{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}}
+<!--- DO NOT MODIFY BELOW THIS LINE ------=====                                =====
-) Paste in the URL Box the following URL:
+=====                                =====
-<pre>http://dbcm.github.io/waze/valfix/valfix.js</pre>
+=====                                =====
+----- DO NOT MODIFY BELOW THIS LINE ----->
-) Click '''Import'''
+</includeonly>
-) Click '''Install'''
-) Click '''Installed Userscripts''' Tab
-) Click On '''Waze Map Editor - Validator Fix'''
-) Click On '''Settings'''
-) '''Set Position to #1'''
-) Hard Refresh in WME
-) Install WV Scripts (below) to get the WV Localization File.
-==== WV Scripts ====
-: [https://greasyfork.org/en/scripts/26683-wme-wv-scripts WV Scripts] Allows you to toggle the  County, City, Town, and Census Designated Place (CDP) in the Waze Map Editor (WME) (original script by Rickzabel). Also the WV Validator Localization File (original script by XanderB). And links to WV Forum, MAR Forum and WV Wiki Pages. Script by '''JustinS83''' with many thanks!
-==== WME US Government Boundaries ====
-: [https://greasyfork.org/en/scripts/25631-wme-us-government-boundaries WME US Government Boundaries] This script by '''MapOMatic''' will display the USPS Boundaries for use in adding alt names to segments to aid in address searches.
-==== Additional Scripts ====
-Not required but highly recommended. Some are restricted by Rank, so be aware they may not work initially. These are the ones we have found to be most useful for new editors; there are others you can browse and decide for yourself. Remember, you have to install TamperMonkey or GreaseMonkey first prior to installing these scripts.
-===== General =====
-: [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.
-===== User Reports =====
-: 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.
-===== Places =====
-: [https://github.com/WazeUSA/WME-Place-Harmonizer/raw/master/WME-Place-Harmonizer.user.js Place Harmonizer (WMEPH)]. Harmonizes, formats and locks a selected place. Also for Chains, please Submit New Chain Data for any that are not in the database. '''NOTE: Now is available for all editors, regardless of Rank.'''
-: [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.
-===== Roads/Segments =====
-: [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.
-: 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)]
-===== More Scripts =====
-More scripts and installation instructions for various browsers can be found here: [[Scripts]].
-There is also a forum for discussion of the [http://www.waze.com/forum/viewforum.php?f=819 Add-ons, Extensions, and Scripts]
-=== Wiki Pages ===
-Map editing may seem intimidating at first; it's not and everyone here started at the same point you are. The Waze community has come up with guidelines and put them into a Wiki. These are some that will get you started; as you edit, there will be more of these to review.
-* [[Waze_Map_Editor/Welcome|Welcome]]
-* [[Edits_to_avoid_(USA)|Map Edits to Avoid]]
-* [[Best_map_editing_practice|Best Map Editing Practice]]
-* [[Places]]
-* [[Road_types/USA|Road Types]]
-* [[Glossary|Waze Glossary]]
-* [[West_Virginia|West Virginia Wiki]]
-=== 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.
-'''Formatting the Permalink (PL)'''
-Zoom In! Selecting a PL at the widest extent (Zoom=0) will not enable the editor who may grant your request to select anything. Setting a zoom level = 3 or higher is generally effective in generating the view required for a senior editor to select the segments. If necessary, break up your PL into multiple requests.
-=== Downlock and Uplock Requests ===
-You will find as a beginning editor that some segments or roads are "locked" above your Rank. In order to work on those, you will need to request a "downlock" to your rank. A downlock request can made in the WV GHO. Be patient as Senior Editors are often in dozens of different GHOs, handling issues for dozens of fellow editors. The request, in order to set a good example for other editors and not spread bad habits to newer editors, shall be constructed as follows:
-Dnlock Lx-Ly, "Location", "Reason", PL
-Lx = Current Lock Level
-Ly = Proposed Lock Level
-Location = Closest City or County or other location description for where the request is being requested. Such as Morgantown, Raleigh County, I-77 etc.
-Reason = Whatever Reason for the request. Examples include Speed Limits (SL), Elevation, Geometry, etc.
-PL = Permalink to the segment(s) that you need downlocked.
-''Be Patient and say Please!''
-'''Finished Example:'''
-Dnlock Please L5-L2. Huntington. SLs, Elevation. http://www.waze.com/editor/?env=usa&lon=-82.42197&lat=38.39253&zoom=5&segments=65476746
-'''Uplock Requests'''
-Upon finishing your editing, create another PL with the segments needed to Uplock to the '''[[West_Virginia#MAR_Minimum_Road_Lock_Standard|Minimum Lock Standard]]'''. Use the format ''Uplock Lx-Ly "PL"''. This needs to be done because the senior editor who will perform the uplock may be using a mobile device, is reviewing multiple requests, and/or is in multiple GHOs or it's a different senior editor. Furthermore, if you add a junction node for a speed limit, add a Parking Lot Road (PLR), or merge segments, it may/will create new segment IDs and those will not be the same as the original downlock request.
-If you have different lock levels; for example freeway (FW) at L5, ramps at L4 and Minor Highway (mh) at L3, break your uplock request into separate PLs for each lock level needed.
-If for any reason the original lock level was higher than the Minimum Lock Standard (for example: a mH at L5 instead of the minimum level, L3), ask in the GHO if they still need to be uplocked back to that original higher level or can be set to the minimums before you request the uplocks. There are a multitude of reasons for this to occur and it's your responsibility to reset those back to the desired levels.

Search

User:PesachZ/SyncScratch View history

Latest revision as of 05:15, 19 February 2017

Accepted parameters:

TO EDIT THIS TABLE CLICK HERE >>