[Page Revision] Traffic Events

[JasonN899]

Updated Major Traffic events page to the new name of Traffic Events.

Updated steps and language to meet current WME. Added new pictures

Added Duplication of TE’s (not originally in the wiki).

DRAFT - Traffic Events

Please let me know your thoughts, and if I missed a conversion of MTE → TE

Thanks

[kndcajun]

Thank you @JasonN899.

For the Duplicate Events section, it might be helpful to add the behavior of duplicating closures WRT the event:

Note that [Include road closures] will duplicate closures from the original event to the new one. The new closure start times will reflect any change in the event start time; and the closure end times will reflect any changes in the event end time.

Example:

Original event start/stop:	12:00 - 18:00		New event start/stop:	11:00 - 20:00
Closure 1 start/stop:	12:00 - 18:00		New closure 1:	11:00 - 20:00
Closure 2 start/stop:	13:00 - 16:00		New closure 2:	12:00 - 18;00

[JasonN899]

Added

[kndcajun]

@JasonN899 , thanks for making the update.

I’m thinking the statement The duplicated new closures start and end time will **match the date and time** you put in for the new event. is not accurate enough, however. Please see the example in the table I drafted above; as well as the wording I proposed above.

[JasonN899]

I’m sorry, but what is not accurate about it? The duplicated new closures start and end time will match the date and time you put in for the new event .

Your statement is not fully correct. The closures will only update once when you are duplicating the event the very first time. It updated the closures to the new date/times of the event that you have on there. Your statement said “The new closure start times will reflect any change in the event start time; and the closure end times will reflect any changes in the event end time.” They dont change with “any change”, they only update the one time.

Also, your statement doesnt include the date anywhere, which is a large part of this. The new date comes along with the new time.

i guess i could make it a little more wordy, i was trying to keep it clean…

The duplicated new closures dates, along with start and end times, will match the dates and times you put in for the New Event .

[kndcajun]

OK sorry I guess my examples weren’t clear. Let me elaborate:

In the table above I mention an event scheduled for 6 hours (12:00 to 18:00). Below it are two closures associated with the event. Closure 1 matches the event times (12:00 to 18:00). Closure 2 is a shorter closure - it starts 1 hour after the event does, and finishes 2 hours earlier than the event (from 13:00 to 16:00).

In the new event (intended for a different date that I did not specify), I’ve adjusted the start/stop times to a longer timespan (9 hours) which starts 1 hour earlier than the original, and finishes 2 hours later.

The feature I’m trying to demonstrate is that the duplicated closure start/stop times will adjust automatically based on the new event start/stop times. For closure 1, which originally matched the event start/stop time, the duplicated closure 1 will also match the new event start/stop times. But here’s the kicker: Closure 2 will be adjusted to start 1 hour after the event start (just like the original), and will end 2 hours before the event ends (again, just like the original). Hence my wording of “…closure start [or end] time will reflect any change in the event start [or end] stop time.”

To say they will “match” the date and time of the event is masking the full capability we are now provided (and not entirely accurate).

Regarding dates - you’re correct. The dates will also carry forward from the duplicated event to the duplicated closures. I just didn’t get into that part.

[kndcajun]

I agree my use of the word “any” might be confusing. We can change that to something like:

The new closure start times will reflect the change in the event start time; and the closure end times will reflect the change in the event end time.

To incorporate date into the statement, we could tweak it again:

The new closure start date/time will reflect the change in the event start date/time; and the closure end date/time will reflect the change in the event end date/time.

… or something to that effect

[JasonN899]

how about this?

2. Checking the Include road closures box will duplicate closures from the original event into the new event. The dates and times on any of the duplicated closures will be adjusted accordingly to the dates and times of new event you are creating.
   1. If the start or end time of any of the closures that are duplicated were different (ex. start time an hour later) than the event start/end time. These times will be adjusted accordingly inside of the new event times you added.

[ojlaw]

Sometimes I’m a little slow and visual examples may help. Maybe take some screenshots of a few events that were duplicated with different hours so editors can see the impact. Example sections can be made collapsible so they don’t take up a ton of real estate on the page.

[JasonN899]

added, used @kndcajun table example

[fuji2086]

Thank you for the work on this. I quickly reviewed it and it looks good.

[nzahn1]

Revisions pushed to the Public wiki:

Traffic Events (TE)

Traffic Events, or TEs, (formerly Major Traffic Event or MTEs) are events that have impact to the roads associated within them. Regularly, they can include Real time closures but it is not a requirement. TEs can be sporting events (marathons, triathlons, etc), festivals, parades, significant construction works, VIP visits or even (natural) disasters like flooding. Reporting TEs ensures that your local community is informed about closures and congestion due to relevant events nearby. This page will provide further details on how to create events and add associated road closures within WME. Before you start To submit a TE you need to have permission to add road closures or to work together with an editor that has this permission. In this phase of the tool, you will be able to create events and upload closures through WME. A web page is automatically created at the Waze events website upon event submission. This page includes the name, dates, description, planned road closures, overview map, and other related information. A push message will be sent to Wazers affected by the TE. This means anyone that lives in the area selected or regularly travels to, or through, that area. If the event you are creating is a crisis or emergency with a widespread impact, use the crisis category and inform your Regional Coordinator. This allows for coordination among editors and staff for assistance in mapping shelters, adding closures, removing closures, monitoring hazards, etc. Creation [Screenshot 2025-09-25 105204aa] Open WME. Mouse over to the tab on the left pane labelled Events. Create a new event by clicking Create Event. You will be presented with the displayed event editor panel (pictured above). Select the category of the event. Select the Impacted area. You can choose Specific Area, to draw a polygon on the map (this is preferred), or choose the city. If you select city the notification will be sent to anyone related to that city name, and will most likely be sent to too many people that may not be affected by the event. Reminder, when drawing the polygon, it will show up on the app so please make it neat. Also, cover all areas impacted by the event, even detour routes. Add start and end times for the event. Note: Allow for preparation and teardown after the event’s scheduled ending. If event locations vary from day to day, such as during the Tour de France, create separate events by region/location. This allows us to send timely push/inbox notifications to users. Add the event name in English (mandatory) - the event name should be as short as possible while accurately representing the event. There is a 25-character limit. Add an event description if available. This will be visible to Wazers. Add a website for further information about the event, if available. Select a lock level for the event Make sure to save! (Note: This is our regular save button top right. There is not a save button on the event panel) Closure addition If you don’t have any closures to add, skip to Submission. Create closures as you normally would, but instead of leaving the event as “none”, choose your event in the drop down menu. Save your closures. They will now be visible on the closures tab of the event in the event editor. Submission [Screenshot_20250926_131320_Waze] Once the closures are attached to the event, return to the events tab, select your event, click the submit button and confirm the submission. This will cause a web page to be created for the event and will also start the process to generate a push message for nearby Wazers. You will be able to view your event via the URL provided, or via the Events Page. Email As an alternative to submitting in WME, a traffic event can be submitted to waze-closures@google.com with the following details: The event name in English and in the Local Language All street names closed during the event Intersecting street where each closure begins and ends Start and end time for each closed road Start and end date for each closed road Indicate if the whole road is closed or just one direction is closed Some pointers when submitting events directly to Waze Closure staff: Check your email; find out who will be working with you on these closures, when they are available to upload closures. Make sure you have time to double-check closures before the event begins. Waze staff might not publish the TE to their [www.waze.com/events Events] page, until shortly before the event. Make sure to communicate with them so you can verify the details. Closures will go live as soon as they are uploaded (within their specified time frames). Closure Sheets are obsolete, and are no longer used to input Real Time Closures, or to generate an TE. Duplicating TE’s [Screenshot 2025-09-29 142036] Navigate to the events tab and filter your results to show the previous event that you want to duplicate. Once your Past Event is located, use the 3 vertical dots to locate the Duplicate button. This will p…