User:PesachZ/SyncScratch View history

PesachZ
VisualWikitext
m (Copying text of wiki page for coparison with the "Talk:Junction Box" page)
m (Copying text of wiki page for coparison with the "New York/Closures/Major" page)
 
(54 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{mbox
<!-- ========================
| type = critical
    ↓  EDITS TO THIS TABLE ARE MADE BELOW THE INSTRUCTIONS    ↓
| text = Junction boxes are currently able to be created and edited in the normal editor by Rank 5+ editors.}}<br>
==============================
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/>


[[File:Junction Box 7.png|right]]Junction boxes ''(JBs)'' are used to improve ETA calculations and routing through complicated intersections, and interchanges. Junction boxes are basically a hint editors can give the Waze routing services that “although these few segments are cut in a few places, they generally should be treated as a single point which connects traffic from several sources”. This hint helps the routing service get better ETA calculations and hence select better routes for Wazers.{{clear}}
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.


== Function ==


The junction box enables a complex intersection, or interchange composed and displayed as multiple [[Glossary#Segment|segments]] to be treated by the routing server as a single [[Glossary#Junction|junction node]] with multiple inputs and outputs. Considering a complex intersection as a single point has several beneficial properties:
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 (=).
* [[Routing_server#Turn delays|Traffic speed data]] for each path through the junction box can be collected separately.
* [[Glossary#Turn_Restriction|Turn restrictions]] can also be separately controlled for each path through the junction box.
* Additional beneficial features of a junction box will be listed here as they become available.


For [[Glossary#Estimated_Time_of_Arrival|ETA]] purposes, the [[Routing_server|routing server]] does not consider segments wholly within the junction box, but rather treats the junction box as if all the segments which enter or exit the the junction box are connected to at a single junction node.
==Accepted parameters:==


Junction boxes are considered only by the routing server. {{As of|2015|10}}, junction boxes have no effect on navigational prompts. Junction boxes have no visibility in the client or on the live map. Junction boxes do not effect the search engine; the origin or destination of route may be contained in a junction box.
*<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.


==Improving data collection==
<!-- This page, specifcally this entire section was reviewed 2015-11-10 by staff Ohad and confirmed as accurate. Staff quote "it looks really great, comprehensive and correct". -->
[[File:Junction Box 3.png|right|75px]]
Let's look at how a complex intersection can skew [[Routing_server#Turn_delays|turn delay]] transition speed data. Take the following intersection for example. It seems at first glance like a pretty simple intersection, but if it usually experiences heavy traffic this intersection could be collecting bad data.


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 (=).


[[File:Junction Box 4.png|right]]
Assume that all the roads are two-way and all turns are enabled.  Consider the drivers going from A to E, and from A to F, when there is a traffic jam for the left turn (at point D), but traffic going straight through D is flowing fine.


Without the junction box, the traffic from point A to point C is considered to be the same for both the red and the blue cars. The same statistical data is gathered and the average speed skews the ETA for everyone. The turn delay data is only different for the red and blue cars on the one segment before the turn at D, from C to D.
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.




[[File:Junction Box 5.png|right]]
For example an Event row should look like this;
The junction box solves this problem.


With the junction box, historical and real time data are collected separately for each one of the possible routes through the intersection - all 12 of them.
{{Tlx|Event/Item|name=''EVENT NAME''|date{{=}}14/10|in progress|username|updated{{=}}14/08}}
{{columns|
* A &#10145; B
* A &#10145; E
* A &#10145; F
* B &#10145; A
* B &#10145; E
* B &#10145; F
* E &#10145; A
* E &#10145; B
* E &#10145; F
* F &#10145; A
* F &#10145; B
* F &#10145; E
|4}}


Now that the paths of A to F, and A to E are being measured separately, the traffic jam for the red cars turning at D does not have a negative effect on the blue cars going straight through D. Their ETAs are being recorded separately.


If there are multiple editors it should look like this


Thus, [[Glossary#Update_Request|URs]] resulting from the inability to distinguish left turn delays from straight through traffic can be dealt with using the junction box.
{{Tlx|Event/Item|name=''EVENT NAME''|date{{=}}14/10|in progress|username1|username2|updated{{=}}14/08}}
[[File:JBRoutingExample1.png]]




=== Understanding inside a junction box ===


{{mbox|text=''There are many types of scenarios where a junction box may be indicated, this sample is used just to explain the function of a junction box, and not meant as guidance on where to use them.''}}
'''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:Junction Box A.png|right|250px|thumb]]
————————————————————————————————————
To illustrate this concept, let's take a look at this intersection. There are five segments entering/exiting the junction box (segments which are only partially inside the junction box). There are another four segments which are wholly inside the junction box. If there were no junction box at this intersection the individual [[Routing server#Turn delays|turn delay]] ''AKA the time it takes to turn from one segment to the next'' data for the outer five segments would be merged together at the inner four segments, and be distorted. The junction box here alleviates the problems with collecting accurate turn delay transition timing caused by the short segments in the middle.




==== Timing ====


If a junction box is drawn around these intersections (below left), then when considering a route that would traverse a segment within the box, the routing server treats the intersection like one large junction for the purpose of calculation transition timing ''AKA turn delays'' (below right).
''The actual contents of this page '''will only be visible''' in the [[{{BasePage2 }}/Closures|Major Events table]], or when editing this page.''


A route path from segment C to segment E is treated as a single transition, even though in actuality it traverses four segments (3 transitions).
==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}}


<center>[[File:Junction Box C.png|300px]] [[File:Junction Box B.png|300px]]</center>
{{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}}


==== Navigation instructions ====
{{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}}


However, '''junction boxes have no effect on navigational prompts''' until phase 3 will be released. {{As of|2015|10}} Junction boxes currently only have Phase 1 (transition / ETA timing), & Phase 2 (path restrictions) active.
{{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}}
{{mbox|type=speculation|text=When Phase 3 (controlling navigation instructions) is released it will likely only affect paths which are specially marked for a custom prompt.}}
Looking back at our example path, going from C to E, let's analyze how the junction box works with navigation prompts. Our path is considered for routing as one transition, and judging by the angles it would be a straight transition making it a [[best continuation]] with no navigation prompt. But as we just said 'junction boxes have no effect on navigational prompts', therefore the actual navigation prompt given for this path (C to E) will consider the three junctions and produce:
* [[File:Big_direction_left.png|25px]] Turn Left onto Idlewild Rd, and then
* [[File:Big_direction_right.png|25px]] Turn right onto Indian Trail Fairview Rd".


This is to say that the navigational prompts are still controlled by the actual names, types, and angles of the segments within a junction box.
{{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}}
{{Details|How Waze determines turn / keep / exit maneuvers|how to control navigation instructions}}


== Controlling turns ==
{{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}}


[[File:JB turn control.png|right|thumb|200px]]
{{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}}
Junction boxes permit disabling multi-segment turns that are difficult to control in complex intersections. Without a junction box, controlling complex turns may require adding artificial segments and/or reducing the intersection to a single point using a [[Bowtie#Bow_tie|bow-tie]] configuration.


Take this example of a junction between two streets with all turns allowed, but at the next junction with the highway some turns are not allowed depending on which street you originally approached from.
{{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}}


When leaving {{Street|E Briarwood Cir}} here you may turn right or left onto {{Primary Street|S Havanah St}}, but if you turn right your options are limited at the next junction. However if you were already on {{Primary Street|S Havanah St}} from before E Briarwood, at the junction with {{Major Highway|E Arapahoe RD}} you are allowed to make either turn or go straight.
{{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}}


 
{{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}}
Without a junction box here our options to reflect these restrictions on the map would require creating an artificial AGC connecting north from {{Street|E Briarwood Cir}} to the junction of the {{Major Highway|E Arapahoe RD}} layered over {{Primary Street|S Havanah St}} (which is discouraged by waze as layered segments can cause data collection problems), or creating an artificial bypass AGC on {{Primary Street|S Havanah St}} which started from south of {{Street|E Briarwood Cir}} (which can look bad on the map). These options separate the traffic flow of those vehicles approaching on {{Primary Street|S Havanah St}}, from those vehicles approaching from {{Street|E Briarwood Cir}}. In either case we are adding artificial segments which are unnecessary and difficult to maintain on the map.
<!--- DO NOT MODIFY BELOW THIS LINE ------=====                                =====
<center>[[File:JB turn control 1.png|300px]]&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[File:JB turn control 2.png|300px]]</center>
=====                                =====
 
=====                                =====
 
----- DO NOT MODIFY BELOW THIS LINE ----->
[[File:JB turn control C.png|thumb|200px]]
</includeonly>
With a junction box in place, we don't need any extra segments, we don't need to artificially alter any geometry of the segments, or to create a bow-tie. We use just the one segment of S Havanah St, and draw the junction box to include the intersection with the major highway and both approaches. We can then use the connections list in the left panel to select which paths through the junction box should be allowed, and which should be disallowed.
 
In our scenario we want to restrict the two paths starting on {{Street|E Briarwood Cir}}, going north on {{Primary Street|S Havanah St}} and then straight or left at the {{Major Highway|E Arapahoe RD}}.
 
With the junction box selected, in the left panel there will be check boxes for each of the possible paths between the segment pairs. clicking on any of these paths on the left will highlight the path in purple on the map. We then uncheck the paths we want to disallow [[File:JB turn control C1.png|75px]].
{{clear}}
<center>[[File:JB turn control 3.png|300px]]&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;[[File:JB turn control 4.png|300px]]</center>
 
=Effects In Editor=
Junction boxes can only be edited by editors of at least [[Your_Rank_and_Points#Waze_Map_Editing_Ranks|rank]] 5.  Junction boxes appear in the Waze Map Editor when the [[Map_editor_interface#Layers|Junctions layer]] {{AddCode|add layer description to [[Map_editor_interface#Layers]]}} is turned on.  Junction boxes appear as a polygon around all the junction nodes of an intersection.
[[File:Junction Box 1.jpg|center]]
All segments that enter the junction box are locked.  Selecting a segment that is part of a junction box results in a message: "You cannot edit this segment.  This segment is part of a junction and cannot be edited.  Delete the junction to edit it." 
 
Selecting the junction box causes the left pane to display the junction box properties. The properties show the editor that created the junction box and the date and editor of the last update to the junction box.  If changes are needed to the junction box or segments associated with the junction box contact the identified editor or other rank 5 editor in your area.
 
[[File:Junction Box 2.jpg|600px|center]]
Each entry to the junction box is labeled with a letter in a green circle.  Each exit from the junction box is labeled with a letter in yellow circle. Hovering the cursor over the letter circle will show the routes through the junction box that use the selected entry or exit.  The left pane shows potential entry/exit pairs with a check box ticked for each pair enabled for routing. Note that only entry/exit pair paths which are fully visible on screen are displayed. So make sure you can see the whole boundary of the JB to be sure you're getting a full list of entry/exit pair connections in the left pane.
 
Routes through the junction box that pass through a single junction node are not considered.  Such routes are controlled by turn restrictions in place when the junction box is created. Thus the route from A to G is controlled by a turn restriction and does not show in the list of entry/exit pairs. 
 
Routes through the junction box that are prohibited by turn restrictions in place when the junction box is created are not considered.  In the above example, the left turns from the southbound {{Major Highway}} use the dedicated turn lane.  The left turn from the main lanes of the southbound {{Major Highway}} to the {{Minor Highway}} is restricted by an existing turn restriction.  Thus, the junction box does not consider routes from the southbound {{Major Highway}} to exits G or H. 
 
From the southbound {{Major Highway}}, routes to exits E and F pass through only a single junction node and routes to exits G and H are prevented by a turn restriction. The junction box thus considers no routes for the traffic entering from the main lanes of the southbound {{Major Highway}}.  For this reason, this entry is not lettered.
 
=Editing=
Junction boxes are created by selecting Junction box from the [[Map_Editor_Interface_and_Controls#Draw_segments_menu|draw segments menu]] (Shortcut key {{key press|J}}). Click at one vertex of the junction box.  Continue click to at each vertex of the box until the box surrounds all the junctions nodes of the intersection.  Double click to complete the box.  The boundaries of the box cannot be changed once created.
 
Before creating a junction box at an intersection, make sure that there are no incorrect turn restrictions.  Routes through the junction box that are prevented by existing turn restrictions cannot be enabled in the junction box.
 
When a junction box is selected it can be edited.  To select a Junction Box click on it.
 
When the junction box is selected, the left pane will show the potential contention paths through the junction box as illustrated above.  Clicking the check box next to each connection path toggles between enabling or disabling routing between the indicated entry/exit pair.
The left pane includes a button to "Select included segments." Clicking this button will select all the segments with both ends in the junction box (these are the segments that are not considered for ETA routing purposes).
 
The left pane includes a name box and an address.  A name can be added to the name box and the address may be edited.  However, currently the name and address of a junction box has no effect.
 
To delete a junction box, select the junction box and click the [[Map_Editor_Interface_and_Controls#Delete_button|delete button]]&nbsp;[[File:Wme_button_delete.png|25px]] (Shortcut key {{key press|Del}}).
 
Changes to junction boxes (and adding new junction boxes) require a [[Tile_update#Updates|tile update]] to affect routing.
 
==Errors When Editing==
* '''No roundabouts''' - Junction boxes do not support [[Roundabout|roundabouts]]. Do not create junction boxes over roundabouts.
 
* '''Max size''' - The size of a junction box cannot exceed 1 kilometer. This is a linear 1 km limit north-south or east-west. If you draw an imaginary 1 km² box around the junction box, if the junction box pokes out at any point, then it's too big.
 
* '''Two junction node minimum''' - A junction box must include at least two junction nodes.  Two junction nodes within the junction box must be connected by a segment.  A junction box with only one junction node cannot be saved.
 
* '''No overlapping''' - A junction node cannot be included in multiple junction boxes.
 
* '''One connection per pair''' - A junction box must have only one connection for every entry/exit pair.  If there are multiple routes available over the segments within the junction box between an entry/exit pair, the box is invalid and cannot be saved. 
 
* '''Sixteen paths max''' - No more than 16 paths (in any direction) can pass through a single node within a junction box.  A save error stating "The highlighted node cannot have more than 16 connections" occurs if a node has more than 16 paths. Paths are connections between two points/letters in JB plus "direct" unseen connections through the junction (that are not included in JB).
 
===Eliminating entry/exit pair connections===
Entry/exit pairs may be unchecked as appropriate so that there is only one connection between an entry and an exit.
[[File:JBEE1.png|600px|center]]
 
<br>
 
[[File:JBEE2.png|300px|right]]
[[File:JBEE3.png|300px|right]]
 
For the above junction box there are two paths from entry A to exit H. In this case to save the junction box the longer path shown in the upper illustration has been unchecked.
 
Unchecking entry/pairs will also reduce the number of paths that pass through a node within the junction box.  In this case, there are fourteen entry/exit pairs that pass through the upper left junction node:
{{columns|
* A &#10145; F
* A &#10145; H
* A &#10145; I
* A &#10145; J
* B &#10145; F
* B &#10145; H
* B &#10145; I
* B &#10145; J
* C &#10145; F
* C &#10145; G
* C &#10145; J
* D &#10145; G
* E &#10145; G
* E &#10145; J
|3}}
The direct u-turns from B to G and C to H are disabled.
 
[[File:JBEE4.png]]
 
Thus, the internal routes from B to G and C to H are available. In this example these u-turns through the junction box are unchecked.  If these paths were checked there would be 16 paths through the upper left junction node and the junction box would not save.
{{clear}}
 
===Adding complexity===
Adding segments or junction nodes to an intersection to workaround the "one connection for every entry/exit pair" and "no more than 16 connections per node" limitations is not recommended. If such a workaround is required please consult with your [[Country_Manager#Coordinators|country]] or [[Regional_Coordinator|regional]] coordinator.
 
=When To Use=
Junction boxes are suitable only for specific locations where the above listed functions of junctions boxes are required.  If problems with data collection or turn restrictions are experienced then a junction box may be use to solve the problem. If problems are easily solved with other features such as [[Glossary#Turn_Restriction|turn restrictions]] or [[Routing penalties/Controlling U-turn penalties|U-turn penalties]], then a junction box should not be used.
 
Junction boxes require more space to store all the data involved. The routing server takes longer to analyse junction boxes and thus to provide routes through junction boxes.  For these reasons, junction boxes should not be used for every intersection.

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 >>

Retrieved from "https://beta.waze.com/wiki/USA/index.php?title=User:PesachZ/SyncScratch&oldid=151586"