Difference between revisions of "User:PesachZ/SyncScratch"

From Wazeopedia
m (Copying text of wiki page for coparison with the "Places/Parking lot/USA" page)
m (Copying text of wiki page for coparison with the "New York/Closures/Major" page)
 
Line 1: Line 1:
{{mbox|text=New Parking features are being rolled out to the display of PLAs in the client app. It is now encouraged to convert point places to area places. New parking lot point places can no longer be created.
+
<!-- ========================
 +
    ↓  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/>
  
Waze is also importing Parking Lot Areas. Do not delete them unless instructed to do so. Use the guidance here to improve their name, data, shape, and placement.  '''Current guidance is to add PLAs to the map, since the client is being updated.''' Initially we should focus on adding large and/or popular lots, but ''all'' lots should eventually be added.}}
+
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.
[[File:Parking_sign.png|300px|thumb|right]]
 
  
The '''Parking Lot Area (PLA)''' Place marks a well-defined area constructed for off-street public or private parking, including parking structures and garages as well as at-grade lots. The parking lot feature in the app will recommend parking lots to Wazers navigating to a nearby destination. Waze will recommend lots within ⅔ mile of a Wazer's destination. As the feature matures, Waze will recommend the 'most popular' lots that other Wazers have chosen when navigating to the same destination.
 
  
== {{@|Area or point}} ==
+
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 (=).
{{Anchor|Area or Point}}Parking lots can ONLY be added as an area as of August 1st, 2016. They are a special place category; you cannot add other categories to a parking lot place, or convert/add a parking lot category to another kind of place.
 
  
=== {{@|Parking lot point places}} ===
+
==Accepted parameters:==
{{Anchor|The Parking-Lot Point Place}}As of this writing, you can no longer add Parking Lots as a point place.
 
  
Existing point places should be evaluated for inclusion and either converted to an area if applicable or deleted to solve the [[Map Problems in Waze Map Editor#Parking lot input as point|Map Problem]] (MP) report.
+
*<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.
  
== {{@|Scope}} ==
 
{{Anchor|Principles|General Public Use|General Purpose Use|Distinctive and Significant|Interpreting_.27distinctive_and_significant.27}}At this time, parking lot areas (PLA) should be added to '''all lots''' including businesses with small parking lots (less than 10 spaces). Start by adding parking lots to event venues, shopping centers, airports, public use lots, garages, multi-use parking lots, popular lots with heavy usage or [[Glossary#UR|UR]]s, etc.
 
[[File:Waze_PLA_Mall_Example.jpg|400px|thumb|right|Shopping Center PLA Example]]
 
<u>For a mall or large shopping center</u>, break the parking lot up into multiple lots, as shown in the image to the right (use your discretion or discuss with your State Manager(s) or RC for official guidance if necessary.)
 
  
<u>If a lot is stacked</u> (underground + surface), map it as one place covering the footprint of the parking lot / garage. Future UI enhancements may allow for better modeling of these lots.
+
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 (=).  
  
<u>If a lot has different entrances</u> serving different levels of a multi-level garage and you cannot drive from one level to another to park, but rather the levels are served independently by different entrances, then they should be mapped as multiple places.
 
  
Care must be taken that stacked areas like this do not obscure each other. You do not want two areas with identical boundaries stacked on top of each other as it will be hard to notice or select the right one for editing in WME.
+
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.
  
As with all Area Places, a Parking Lot Area Place's geometry nodes should not be allowed to "snap" to adjacent road segments or junctions while being adjusted. Doing so can make the Area Place, as well as the adjacent segments or junctions, more difficult to modify.
 
  
=== {{@|On-premises parking}} ===
+
For example an Event row should look like this;
* It is important to create 2 separate places - one for the complex / place, and one for its designated parking lot.
 
* Multiple parking lots for one premise: Create separate parking lots so the best parking lot can be recommended.
 
* Valet parking - Valet is a service attribute of a place but is also an attribute for a parking lot.
 
* Multi-level lots should be created as single place with the shape of the overall parking surface outlined.
 
  
=== {{@|Underground parking lots}} ===
+
{{Tlx|Event/Item|name=''EVENT NAME''|date{{=}}14/10|in progress|username|updated{{=}}14/08}}
* It is still important to map these correctly so they can be routed to properly, and recommended appropriately in the client to users. Since the underground portion of the garage is not visible to drivers, it is not important to be displayed fully in the app.
 
* To support the internal features of the client; The polygon must include all above ground areas, and the areas where it starts to go underground. See the [[#Drawing|Drawing section]] below for more details and examples on how to draw these lots.
 
* If parking lots overlap with a Place, do not add "Parking Lot" category to a Place. Create a separate Area polygon for the parking lot.
 
  
=== {{@|Rental-car lots}} ===
 
*{{Anchor|Rental-car return|Rental-car return lots}}With the availability of the "Car Rental" Place, rental car facilities and returns, including at airports, should be marked with the Car Rental Place category for the desk and/or the building. If there is any customer parking, or return vehicle parking, then mark that area with the parking lot category.
 
  
=== {{@|Temporary lots}} ===
+
If there are multiple editors it should look like this
Temporary lots for use at festivals, parades, concerts, etc., where temporary parking is being established specifically for the event can be added and named accordingly. Taking care to ensure that any temporary lots that are added, are removed as soon as the event is complete.
 
'''On-street parking should not be added as a temporary lot.'''
 
  
== {{@|Creating and editing parking lot areas}} ==
+
{{Tlx|Event/Item|name=''EVENT NAME''|date{{=}}14/10|in progress|username1|username2|updated{{=}}14/08}}
{{Anchor|Implementation}}
 
{{mbox|type=caution|text=[[File:WME parking lots layer on.png|250px|right]]
 
When editing or creating parking lots and related URs, MPs, & PURs, please make sure you have the Parking Lots layer turned on so the existing PLAs on the map are not hidden.}}
 
[[File:Waze_PLA_Example.jpg|300px|thumb|right|Outline building footprint only]]
 
=== {{@|Drawing}} ===
 
{{Anchor|Extent}}
 
The Parking Lot Area (PLA) Place should never be attached/snapped to roads. Places snapped to roads are difficult to edit.
 
  
For planned parking features to be announced later, it's important that the shape of the polygon be drawn as close as possible to the actual shape of the parking lot, including the entry/exit location. Keeping in mind that for multi-level garages, only the footprint of the structure should be outlined.
 
  
If a lot spans both sides of a street (not counting PLRs obviously), it must be mapped so '''the polygon does not overlap the street'''. This may require drawing the lot as separate places.<br />
 
''If the lot is elevated above the street however, and the lot actually covers the street, then the PLA may overlap the street as well.''
 
  
For underground garages  it is not important to draw the polygon to match the internal perimeter since there is no GPS signal underground. It is important that the polygon includes any above ground areas, and the underground areas near any entrances or exits in a single polygon. If a lot has more than one entrance/exit the polygon must be made to connect all the entrances and exits. You may use a PLR to show multiple entrances as well, allowing the routing to choose the best route to access the lot, just as an above ground lot is drawn. It is not important however to draw the polygon to the entire footprint of the garage. The accuracy of the entry point ([[Places#Setting_the_stop_point_for_a_Place|'''Setting the stop point''']]) is very important. {{Clear}}
+
'''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.'''
<center>
+
————————————————————————————————————
{| class="wikitable"
 
| style="background: #BEDCE5;" colspan=2; align=center|'''[http://www.waze.com/editor/?env=usa&lon=-73.98899&lat=40.74062&zoom=7&venues=187433367.1874399210.3624518 Icon Parking]'''
 
|-
 
| style="background: red;"|[[File:Underground lot mapped to perimeter.png|400px|thumb|center|WRONG: Mapped to estimated underground Perimeter]]
 
| style="background: lawngreen;"|[[File:Underground lot mapped to entrance.png|350px|thumb|center|CORRECT: mapped above ground, and entry/exit areas]]
 
|-
 
| style="background: #BEDCE5;" colspan=2; align=center|'''[http://www.waze.com/editor/?env=usa&lon=-85.75334&lat=38.25737&zoom=6&venues=179700095.1797328626.3614708 Parking Garage - Yum! Center]'''
 
|-
 
| style="background: red;"|[[File:Underground lot with multiple places.png|375px|thumb|center|WRONG: Multiple access points mapped as individual places for a single underground garage.]]
 
| style="background: lawngreen;"|[[File:Underground lot with multiple access.png|350px|thumb|center|CORRECT: multiple access points included in a single polygon for an underground lot, the underground perimeter is not important.]]
 
|-
 
| style="background: #BEDCE5;" align=center|'''[http://www.waze.com/editor/?env=usa&lon=-123.03897&lat=44.94261&zoom=7&mode=0&venueFilter=2&venues=155320769.1552945550.3513573 Chemeketa Parkade]'''
 
| style="background: #BEDCE5;" align=center|'''[http://www.waze.com/editor/?env=usa&lon=-73.58783&lat=40.73257&zoom=6&venueFilter=2 Nassua Community College]'''
 
|-
 
| style="background: lawngreen;"|[[File:Elevated lot over street.png|375px|thumb|center|CORRECT: Elevated lot built above street, mapped as a single PLA overlapping the street.]]
 
| style="background: lawngreen;"|[[File:Ground level lots spanning streets mapped separate.png|375px|thumb|center|CORRECT:Ground level lots spanning streets mapped as separate PLAs. On-street parking not mapped as a PLA.]]
 
  
|}</center>
 
  
=== {{@|Naming}} ===
 
If a parking facility or area has a documented identity, such as "Beach Street Garage", "18th Avenue/Geary Lot", "Lot 7 - <Stadium name>", "Short-Term Parking - <Airport name>", "Cell Phone Lot - <Airport name>", etc., its Place should reflect that name to facilitate searches. Generic park-and-ride lots should be named consistently according to local custom, for example as "Park & Ride".
 
  
If a Parking Lot Area Place is contained within a larger Area Place, do not repeat the larger Area's full name. For example, if the Domestic Garage is contained within the "SFO San Francisco International Airport" Area Place boundaries, it need not be named "SFO San Francisco International Airport Domestic Garage"; "Domestic Garage - SFO" is sufficient.
+
''The actual contents of this page '''will only be visible''' in the [[{{BasePage2 }}/Closures|Major Events table]], or when editing this page.''
  
If a mall or shopping center has several lots which can be associated with various anchor stores in the mall/shopping center, the lots can be named for the anchor stores. For example: "Macy's Lot - Big Hill Shopping Center" 
+
==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}}
  
In rare cases, a municipality or district provides public parking distinct from any other Area Place but without any documented or signed identity. These can be named after the municipality or district, for example, "Redwood City Public Parking". Do not use completely generic names such as "Parking" or "Public Parking" for anonymous parking facilities.
+
{{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}}
  
A block range or specific address '''should not be used''' to name a lot. If the lot does not have an official and/or signed name, then leave the name blank, and be sure to add the address details in the address field. Some imported PLAs were created with the address or address block range as the name, these names should be removed accordingly. Check your local guidance for any variations.
+
{{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}}
:'''NOTE:''' It is very important if there is no name for the lot that there be a proper address in the address field. If you don't know the exact address you should at least put the street the main entrance is on, and - if you can - an approximate house number. The address is needed to be displayed in the search results, and differentiate the lot from all the others. Users can see the address displayed, know which lot it is when viewing the results list.  
 
  
==== {{@|Restricted parking}} ====
+
{{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}}
If there are posted signs restricting the lot to only one certain category of users (e.g. Customers, Residents, Staff, Attendees,  Permit Holders, Faculty, Students, etc.) ONLY, then put that restriction in the name. If the lot is restricted to more than one category of users, then put "(restricted access)" in the name. Also put the details of the restriction in the [[#description|description]].<br>
 
'''Examples:'''
 
* "Starbucks Parking (customers only)"
 
* "Macy's Lot (customers only) - Big Hill Shopping Center"
 
* Lot D (attendees only) - Cheery Stadium"
 
* "Alpha Lot (permit only) - StudyHard University" ''Parking allowed by permit only ( even if permits are available to multiple groups (eg for Students, and Faculty)''
 
* "Bravo Lot (restricted access) - StudyHard University" ''Parking allowed for Students, and Faculty ONLY''
 
* "123 Somewhere St Lot (residents only)"
 
* "345 Other St Lot (restricted access)" ''Parking allowed for resident, guests, and staff''
 
  
=== {{@|Description}} ===
+
{{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}}
Any lot which is fully restricted in some way (e.g. permit/resident/customer only), and not open to the public for general parking, must include that information as the first line of the description. If only some of the available spots are restricted, but there are some spots in the lot open to the public for general parking, then it should not be mentioned.<br>
 
'''Examples:'''
 
* "Parking by permit only."
 
* "Parking only for customers of John Doe's Supermarket"
 
* "Parking only for residents of 123 Something St, and their guests"
 
* "Parking restricted to 15 minutes or less"
 
* "Valet parking only"
 
If you know the details or times of the restrictions you may add that information in the descriptions as well for users to see. This will also help for when those features become available in WME to have the details handy for mapping.
 
  
=== {{@|Operator}} ===
+
{{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}}
When there is a recognized parking operator, select it from the list, otherwise, leave this field blank. If an Operator is missing from the list that you feel should be added, please send the information to your [[Regional Coordinator/USA|Regional Coordinator]] (RC).
 
  
=== {{@|Locking standards}} ===
+
{{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}}
Due to this major shift in editing guidelines, it is recommended that once a Parking Lot Area (PLA) has been added, that it be locked to 3 to avoid newer editors, or those not familiar with the change, from editing or deleting the PLA.
 
  
== {{@|Interface - more info}} ==
+
{{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}}
[[File:WME_PLA_UI_081016.jpg|400px|thumb|right|WME User Interface - More info tab]]
 
  
'''Opening hours''' - Hours lot is open. Set open times for the lot or select each day and the ''All day'' radio button for lots open 24 hours a day / 7 days a week.  
+
{{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}}
*''Cars can exit when lot is closed'' - Check if the lot or garage does not restrict egress after the lot is considered closed.
 
*'''Cost'''{{Anchor|Free versus paid parking}}
 
**Cost determination should be made based on parking lot fees for other similar and nearby lots for the same type of venue.
 
***Example #1: Adding / editing parking lots near an airport; terminal parking may be the most expensive at $25/day, express parking the next level down (moderate) at $15/day and remote parking the next best option at $5/day (low).
 
***Example #2: Hotel parking; on-site $50/day (expensive), self-parking garage at $30/day (moderate), and off-site parking at $15/day (low)
 
**Each lot within approximately ⅔ mile (1 km) radius should be taken into consideration for PLA cost determination where appropriate.
 
  
*'''Services '''(select services listed below)
+
{{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}}
**Reservations - Lot accepts reservations or accepts pre-paid parking passes or permits.
+
<!--- DO NOT MODIFY BELOW THIS LINE ------=====                               =====
**Disability parking - Spaces exist for handicap parking / wheelchair accessible spaces.
+
=====                                =====
**Car wash - A car wash is on premises within the parking lot (some airports and other venues have amenities such as this for those parking within the lot).
+
=====                                =====
**Security - On-site security for the specific lot exists
+
----- DO NOT MODIFY BELOW THIS LINE ----->
*'''Number of Spots'''
+
</includeonly>
**List the most accurate number of spots within the specified parking lot area polygon.
 
*'''Contact info'''
 
**A link to the specific parking lot or vendor's site (if applicable) is permissible here.
 
*'''Phone'''
 
**The phone number for the main venue to which the parking lot belongs or to the parking lot vendor is permissible here.
 
 
 
== {{@|Parking lot roads}} ==
 
Don't forget to map any necessary [[parking lot roads]], to allow for proper navigation into and out of the parking lot. The parking lot place does not substitute roads needed for actual navigation.
 
 
 
'''Parking lot roads are not required simply because a lot qualifies for a PLA.''' It is OK for small lots which do not qualify for their own PLRs to still be mapped as a PLA, the two features are independent of each other. PLRs have an effect on routing which can sometimes be detrimental. While it is important to map the ''necessary'' PLRs, please follow [[Parking lot roads|the guidance]] and do not add PLRs which are not necessary.
 
 
 
== {{@|What does not qualify as a PLA?}} ==
 
 
 
=== {{@|On-street parking}} ===
 
{{Anchor|Examples}}{{Red|On-street parking should not be added at this time.}}
 
 
 
=== Gas stations ===
 
Gas stations are already drawn on the map as an area, and typical usage includes parking to get gas. They are therefore handled specially by the servers, and '''do not require an additional PLA to be drawn on top of the gas station area'''. However if there is a significant parking area there which is worthy to be recommended to users who are navigating to nearby venues (e.g. a truck stop, etc.), then you ''may'' add a PLA there.
 
 
 
=== {{@|Valet only facility}} ===
 
Parking lots or garages accessed exclusively by valet staff, and situated away from the valet drop off point should not be added to the map. (If regular drivers are not allowed to drive up to the valet facility, and rather must drop the vehicle at a different location, and the valet drivers are the only ones driving to this facility location, then it serves no purpose being recommended ever.
 
 
 
In such cases, where the valet drop off is not near the stop point for the place it services, the valet drop off may be added as a PLA, and marked as valet only in the name.
 
 
 
If regular drivers are allowed to drop their vehicle at the valet facility, or there is mixed use of the facility where non-valet users can park as well, then a PLA '''should''' be added.
 

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