Real time closures: Difference between revisions Discussion View history

m (→‎Major traffic events: closures are in sheets emphasized and linked to closure sheets section)
 
(183 intermediate revisions by 19 users not shown)
Line 1: Line 1:
{{ReturnToEditingManual}}
{{ReturnTo | Editing manual | the editing manual}}
[[File:Livemap_closure_alert.png|right]]A Real Time Closure (RTC) may be used when a segment is completely closed temporarily in one or both directions to all wazers. When the RTC is active, the affected segment will be marked with red-and-white candy stripes and Waze will not route any traffic through or onto the segment.  Only use an RTC when a road is completely closed in one or both directions. '''Do not use an RTC for lane closures, width restrictions or other cases where traffic is still allowed to move.'''


The real time closure '''is the preferred method for temporarily closing roads because it is visible to Wazers and because it helps protect the map.'''
==Deciding when to use an RTC==
{{Anchor|Controlling traffic flow}}There are several possible ways to prevent Waze from routing traffic over a segment.  The best choice depends on the situation.
{| class="wikitable"
|-
!Method
!Vehicles Affected
!Takes Effect
!Ends
!Traffic Data
!Guidance
|-
|Real time closure
|All
|Immediate
|Expires
|Kept
|Preferred option for temporary (even long term) one-way or two-way closure. Visible to drivers.  Immediate effect. Automatically removed when it expires.
|-
|Road direction change
|All
|Tile update
|Permanent
|Kept
|Use only for permanent change in direction from two-way to one-way.
|-
|[[Partial restrictions|Time-based segment restriction]]
|Some/All
|Tile update
|Optionally expires
|Kept
|Use only where the restrictions (time of day/ day of week) are permanent, or where certain vehicle types are allowed or prohibited. Example: No passenger cars on weekdays.
|-
|[[Partial restrictions|Time-based turn restriction]]
|Some/All
|Tile update
|Optionally expires
|Kept
|Use where travel on the segment is allowed, but turns onto the segment are temporarily forbidden or else permanently forbidden at certain times of day, days of week or for certain vehicle types. Example: No left turn 4:00pm-6:00pm
|-
|Permanent turn restriction
|All
|Tile update
|Permanent
|Kept
|[[File:Arrow Red-2.png|frameless|left]]Use where a turn onto the segment should be permanently forbidden for all vehicles.
|-
|Conversion to a penalized [[road types|road type]]
|All
|Tile update
|Permanent
|Kept
|Penalties make routing less likely, but are not absolute. Vehicles with a destination on the segment will be routed onto the segment. Normally {{Private Road}} is used.
|-
|Disconnection
|All
|Tile update
|Permanent
|Lost
|Use only if the disconnection is permanent. All turn data is lost.
|-
|Deletion
|All
|Tile update
|Permanent
|Lost
|Use only if the road is permanently closed. All data is lost.
|}


{{mbox|type=important|text='''Do NOT use any of the tools discussed on this page for ''lane closures'''''. These methods of controlling traffic flow are only to be used when a segment is completely closed in one or both directions to all public through traffic temporarily.}}
[[File:Closure arrow in WME.png|right]]Real time closures are the preferred way of temporarily controlling traffic for a number of reasons


*They begin to affect routing within a few minutes of being saved, without waiting for a [[tile update]].
*When the RTC is removed, proper routing can be restored immediately, without waiting for a [[tile update]].
*They allow editors to temporarily prevent routing over specific segments, without having to make any changes to, or damage those segments, and their road types, junctions, or turn restrictions.
*They preserve traffic data.
*By default (see below), a road closed with an RTC will be continually evaluated for through traffic. If enough traffic is detected driving through a closure, the closure is temporarily deactivated until the traffic is no longer detected. Therefore if an RTC is mistakenly placed on an open segment it will only affect drivers for a few minutes until the through traffic is detected, and the closure deactivated automatically.
*Real time closures are visible in Live Map and the Waze app with special alert icons and segment highlighting. They are also visible in WME with special icons.
*They can be created and commented on within the Waze app, with app creations and comments generating [[Waze Closures Bot|notifications for editors]].
*They can be associated with [https://www.waze.com/events Major Traffic Events] to get notifications sent to nearby Wazers.
*They eliminate the need for addition and removal of partial restrictions. In fact, ''partial restrictions should not be used redundantly with real time closures''


Oftentimes roads on the map need to be closed for a variety of reasons ranging from planned construction or a large-scale event to emergency closures for accidents or natural disastersThese are called Real-Time Closures, and will be discussed in detail on this page.
===Effect on routing===
[[File:RTC destination on closed segment.jpeg|thumbnail|right|Waze will not choose a closed segment as the closest segment to the destination.]]When a real time closure is active, Waze will not route through or even partway through the closed segment in the direction(s) it is closed. It will not route to a destination on the closed segment(s), even if that is the closest segment to the destinationInstead, it will pick a stop point on the next closest segment. If the closed segment is much longer than the part of the road that is actually closed to all traffic, this can result in wazers being sent to a nearby street even though they should be able to drive to the destination. For this reason, if a closure is very localized and going to go on for over a week (as for a bridge replacement) it might be worth the effort to [[#edit the closed segment|edit the closed segment]].


If the Wazer is currently located on a closed segment, waze will find a route that begins in the closed segment and find the shortest distance to a segment with no closure.


== Controlling traffic flow ==
==How real time closures are added to the map==
Real Time Closures can be added to Waze in three ways:


There are several mechanisms to prevent Waze from routing traffic over specific roads. The method used depends on the reason traffic flow needs to be prevented. Here is a brief overview of the various mechanisms available for controlling traffic flow on specific roads. For specific details on any of these mechanisms, please see the corresponding wiki pages linked below.
*[[#WME_closure_feature|Real Time Closures in WME]]
* [[File:Closure arrow in WME.png|right]][[File:Closure_report_button_in_client.png|right|60px]]'''{{#ifeq:{{SUBPAGENAME}}|Real time closures|[[#Real time closures|Real time closures]] (this page)|[[Real time closures]]}} —''' Should be used when a road is temporarily unusable, but does not need modification (including turn restrictions). These display in the client and Livemap with alerts and candy stripes on the segments to notify users of the closures in real-time (no wait for tile updates), and prevents routing during the closure time on these segments. '''Due to its' safety (protecting the map), and its visibility (in the client and Livemap), this is the preferred method of closing a road.''' <br />Real-Time Closures can be submitted in a variety of methods discussed in detail further on this page:
*[[#Report a closure in the Waze client app|Report a Closure in the Waze client app]]
** Add a [[#Closure feature in the waze map editor|closure in WME]]
*[[#Major traffic events|Major Traffic Events (MTEs) Closure Sheets]]
** Submit a [[#Major traffic events|Major Traffic Event]]
** Enter a closure using a [[#Closure sheets|regional closure sheet]]
** [[#Report closure feature in the waze app|Report a closure in the client]] as you drive by them.
* [[File:Restriction_arrow_yellow_mouseover.gif|right]]'''[[Partial restrictions]] (AKA Scheduled or Time-Based Restrictions)''' - Used when turns or roadways are restricted at certain times of day, days of the week, vehicle types, etc. These have the ability to only restrict during a specific date range, but should NOT be used in place of Mega Traffic Events or Real-Time Road Closures.
* '''[[Road types and names|Road types]] —''' Certain road types (Private, Parking Lot Road, Dirt Road/4X4 Trail) will automatically prevent routing and should be used when appropriate for permanent situation.
* '''Disconnect road segments — ''Road segments should only be physically disconnected if the road is no longer intended to connect or is being permanently removed.''''' When a road is disconnected it becomes ''absolutely unroutable'', and all stored speed data for the junctions are lost. This should be done with the support of a senior editor. In the past, this method was used for longer term construction projects, but now the Road Closure feature should be used.


==Real time closures in WME==
{{Anchor|WME closure feature}}


== Real time closures ==
===How to add a real time closure===
[[File:RTC Window 082020.png|right|alt=Screenshot of segment RTC properties as of 08/2020]]


'''This is the preferred method for closing roads due to its [[#Safety and visibility|safety and visibility to Wazers]].'''
#Save all pending edits. You will not be able to add or edit closures if there are pending edits. Note that saving an edit which changes the segment number will prevent adding the RTC.
#Select the segments you want to close.
#Click the {{key press|Closure}}  tab in the left panel.
#Click to {{key press|+ Add Closure}} and fill out the fields shown:


 
::'''Description '''- This section will be viewable in both the client app and the Live Map. Write a description of closure / event here.
The editing community can be informed about these closures by:
::'''Direction''' - If a single one-way segment is selected, then the correct direction will be auto-selected. If the segment is two way and the closure is in only one of the directions, choose that direction here. If multiple directions are selected, then the editor should choose two way for the closure then all two way segments will be closed two ways and the one ways will be closed in the appropriate direction.
* URs/MPs submitted through the app
::'''Event''' - If this closure is part of a [[Major Traffic Event]], choose it from the drop-down list. If not present then add the Event.
* Knowledge of local happenings
::'''Start/End Date & Time''' - Enter date/time the closure will remain active (the start date can be a date in the past). Enter the correct time for the closure for the local time zone of the segment being closed, regardless of where you are located while entering the closures. Time is entered in [[wikipedia:24-hour_clock|24-hour format]] and date uses the YYYY-MM-DD. The first minute of the day begins at 00:00 and the last minute of the day begins at 23:59.
* Notification from the local community / Waze Major Traffic Event Team
::*The start date cannot be great than 365 days from the current date.
* Long term closures
::*The end date (i.e. duration) for a Real-time closure is no longer limited.
 
::*Real-time closures are active for the full minute they are set for (up to 00 seconds of the next minute)
All Real-Time Closures follow the same general principles below, regardless of which method is used to submit them. Depending on
::*Do not use 24:00 as a start or end time.
which method is used there are additional guidance and instructions in the corresponding unique subsections below.
::*00:00 is the first minute of the day. Avoid using it as end time.
 
::*23:59 is the last minute of the day.  Avoid using it as a start time.
Real Time Closures can be added to Waze in four ways:
::*A closure set for Start: 03:00, End: 04:00, will actually be closed for 60 minutes and 59 seconds, from 03:00:00 - 04:00:59.
*[[#Report a closure in the waze client app|Report a Closure in the Waze client app]]
::'''Save & Check'''
*[[#Major traffic events|Major Traffic Events (MTEs)]]
::*In Live Map, active closures will appear with red closure icons in WME, and with closure alerts bubbles and red and white ''(candy stripe)'' road segment highlighting in Live Map immediately.
*[[#Temporary closures in wme|Temporary Closures in WME]]
::*May have to zoom in to see all closures in Live Map.
*[[#Closure sheets|Closure Sheets]]
::*In Event Mode, if the closures are associated with an event, to see candy stripe road segment highlighting in WME
 
::*Inactive closures do not appear at all in Live Map or the Waze app, and will appear with gray closure icons in WME only
As mentioned above, if the closure is part of an event which will be impacting a large number of people in your area (i.e. - major highway closed, city-wide marathon, natural disaster) please be sure to [[#Major traffic events|submit the MTE form]] first.  
{{Expand|This slideshow was prepared by Waze staff to show how to add a closure in WME. It contains information on which segments to select as part of a closure as well. The information in this slide show is also presented throughout this page in text.
 
 
 
=== Safety and visibility ===
 
This feature is safer than other methods of controlling traffic flow for a number of reasons.
* It allows editors to temporarily prevent routing over specific segments, without having to make any changes to, or damage those segments, and their road types, junctions, or turn restrictions.
* The history of the segment is preserved.
* When the RTC is removed, proper routing can be restored immediately, without waiting for a [[tile update]].
* A road closed with an RTC will be continually evaluated for through traffic. If enough traffic is detected driving through a closure, the closure is temporarily deactivated until the traffic is no longer detected. Therefore if an RTC is mistakenly placed on an open segment it will only affect drivers for a few minutes until the through traffic is detected, and the closure deactivated automatically.
* Real Time Closures are visible in Livemap, and the Waze app with special alert icons, and segment highlighting. They are also visible in WME with special icons.
 
 
=== General closure guidance ===
 
==== Illustrated slideshow ====
 
This slideshow was prepared by Waze staff to show how to add a closure in WME. It contains information on which segments to select as part of a closure as well. The information in this slide show is also presented throughout this page in text.
{{#widget:Iframe
{{#widget:Iframe
|url=https://docs.google.com/presentation/d/12TrGVZsJRTR-ia-MMdaYPF8A1cBOUoQr0uKf5L52C_M/embed?start=false&loop=false&delayms=30000
|url=https://docs.google.com/presentation/d/1tBb3Cg8Ewu_rx7yuPxGMCTy4FIoAb-Z1CY33ukYFtM8/embed?start=false&loop=false&delayms=30000
|border=0
|border=0
|width=700
|width=700
|height=415
|height=415
}}
|Slideshow - how to create Real Time Closures|nt=yes
|section=5
|summary='''Click expand on the right side here to see a slideshow developed by waze staff'''
}}
}}


=====HOV/Service Road adjacent checkbox=====
When checked, the HOV/Service Road adjacent checkbox will prevent the segment from being temporarily reopened by traffic detection. This includes situations where Waze might mistakenly believe that drivers on adjacent segments are driving on the closed segment, causing Waze to temporarily "reopen" the road and include it in calculated routes. The HOV/Service Road adjacent checkbox is intended to mitigate nearby HOV/Express lane and service road traffic from a closed main road segment (or vice versa), but may also apply to adjacent parallel roads or other elevations of multi-level stacked roads that could trigger traffic detection. The checkbox may also be used in other circumstances where traffic detection is undesired before the set closure end time, such as closures where local traffic is still allowed.


==== Real time closures vs. partial restrictions ====
=====Node Closure=====


Many major roads have ongoing restrictions, which are based on day of the week or time of day. Some examples include:
======Node closure - cross traffic======<!--Was: Cross streets - which segments to close-->
*No Left Turn between 12:00pm-6:00pm
[[File:Closure nodes English.png|thumb|right]]Closing segments of a road using real-time closures will prevent Waze from routing wazers down that road. '''Node closures''' prevent Waze from routing wazers across intersections along a closed road. When a [[Glossary#Node|junction node]] is closed, no traffic can pass through that node in any direction. All turns through a closed node are prohibited. There is no partial node closure function to restrict individual turns without closing the entire node. In order to close a node to traffic, at least one segment attached to the node must be closed as well.
*No passenger cars on weekdays


For these types of restrictions, please see the [[Partial restrictions|Partial Restrictions page]] on the Wiki.
When entering a real-time closure, junction nodes between selected contiguous segments will automatically be pre-selected for closure, while nodes at the ends of a single segment or multiple contiguous segments are not automatically marked for closure. Prior to applying the closure, junction node closure status can be reviewed and toggled.


'''If a road is closed with a Real Time Closure, there is no need to duplicate the Closure with an additional Partial Restriction ''(AKA Time-Based Restriction)'' for traveling across the segment, or change any turn restrictions.''' ''(This also helps preserve the map, as soon as the Temporary Closure expires, or is cancelled, the map will route as it's supposed to.)''
If all the real-time closures on segments attached to a closed node are removed, the node closure will be automatically removed as well. However, if any segment attached to a closed junction node remains closed, the node closure will also remain.


To work with node closures:


==== Usernames and closures ====
*Select the segments to be closed and add segment closure information.
*Review the list of nodes selected for closure. WME will have enabled junction nodes closures between contiguous selected segments. Mouse-over a node's cross-street name in the list of junction nodes in order to highlight that node on the map.
*Enable and disable node closures as necessary.
*Save segment and associated junction node real-time closures.


[[File:Livemap closure alert.png|250px|thumbnail|right]] Adding a Temporary Closure does not put your name as the last editor for the segment (<small>Updated By: user (#)</small>), however you can see who added a closure by looking at the alert in livemap or the client.
Prior to the introduction of node closures, the only way to prevent Waze from routing traffic "across" a closed street was to apply closures on the cross-streets. That practice is no longer recommended.[[File:Input_node_English.png|thumb|Only the node on the "input" end of a one-way closure can be closed.]]


======Node closures - what to watch out for======


==== Junctions and cross traffic ====
*If a Node closure is enabled as part of an active closure, then it will remain enabled as long as the active closures on any connected segments remain active. If it needs to be disabled, use the node closure toggle switch on any of the connected segment closures
**[[File:Closure_corner_node_English.png|thumb|When a closure turns a corner, check the state of the closure at the node]]Example: If a Freeway is closed due to weather from Mile 0 to Exit 100,  and then the eastern part of the road is opened (Exit 60-Exit 100), be sure to remove the node closure at the remaining eastern closure.  Otherwise, the closed node at the end of the entrance ramp at the Exit 60 interchange will prevent routing.
*On one-way segments closures, only the node at the inbound end can be closed. To close the other node, choose a segment closure that has this node at its inbound end and set the closure toggle switch accordingly.
*When a closure turns corner, watch out.  WME will automatically close the node between the two segments.  But traffic may be allowed between the other segments at the intersection. Check the state of the toggle switch for the node at the intersection.
*When all of the closures at a closed node have expired or been removed, the node closure will also expire. Node closure cannot be used to close an intersection unless at least one segment at the intersection is also closed.


When adding a Real-Time Closure consider whether any cross traffic will be blocked as well.
<br />
* If traffic going across your Real-Time Closure at a junction must be blocked as well, you will need to close {{u|one}} of the cross street segments as well.
=====How we learn about closures=====
** You should close the segment leading away from the main road with the Real-Time Closure.
The editing community can be informed about these closures by:  
** If the cross street is a two way street, close only the shorter segment.
*** When closing a two way cross street segment, only set the Real-Time Closure to the direction leading away from the Temporary Closure.
<center>''Click on these illustrations to see them in full size.<br />
<sup>''1.''</sup> [[File:Closure cross streets 1.png|150px]] <sup>''2.''</sup> [[File:Closure cross streets 2.png|150px]] <sup>''3.''</sup> [[File:Closure cross streets 3.png|150px]]</center>{{clear}}
 
 
==== Lane closures and construction zones ====
 
For situations where only some lanes are closed but the road is still driveable, and general [[Road names/USA#Construction zones and closed roads|road construction]] situations, refer to that article for additional specific information.
 
'''DO NOT use Real-Time Closures for roads which only have some lanes closed.'''
 
 
=== Web based closure guidance ===
 
==== Dates and times ====
 
'''All Real-Time Closures are set using the [http://wikipedia.org/wiki/ISO_8601 ISO-8601 ''"extended format"''].'''
 
Put simply this means whenever entering a '''date''', it should be in the format of '''YYYY-MM-DD'''. ''The YYYY is the four digit year, MM is the two digit month, and DD is the two digit day of the month. (For example March 15th, 2015 would be entered as 2015-03-15.)''
 
Whenever entering a '''time''', it should be using the 24 hour clock, in the format of '''HH:MM:SS'''. ''The HH is the two digit hour, MM is the two digit minute, and SS is the two digit seconds. The seconds may be optional depending on the feature you are using. (For example 2:53 pm will be entered as 14:53.)''
 
In the 24 hour clock, the first 12 hours of the day from midnight until 11:59 am, are represented as 00:00 - 11:59. The second twelve hours of the day from noon until 11:59 pm, are represented as 12:00 - 23:59. ''To make it easy to remember, any time in the AM hours, is just the same (with a leading zero for the first nine single digit hours). Any time in the PM hours, add 12 to the hour (so 2 pm becomes 14 - 2+12=14).
 
The minute of midnight can be represented both as 00:00, and as 24:00 depending on if it is connected to the previous day (24:00), or the new day just beginning (00:00). ''For example Monday 24:00 is the same minute as Tuesday 00:00.'' To prevent confusion you should avoid using 00:00, or 24:00 as a closure time, instead use 23:59, or 00:01.
 
 
===== Start and end time settings =====
 
{{mbox|image=[[File:Clock.png|40px]]|text=Be careful choosing closure times. 00:00 is the first minute of a day, 23:59 is the last minute of a day. A closure ending on Jan 1st at 00:00 will leave the road open for the entire day of Jan 1st, while 23:59 would leave the road closed for that entire day. ''To prevent ambiguity try using 00:01 instead of 00:00 as a closure time.''}}
 
*Real-time Closures are active for the full minute they are set for.
** A Closure set for Start: 03:00 - End: 03:01, will actually be closed for 119 seconds, from 03:00:00 - 03:01:59.
** A closure set for Start: 03:00, End: 04:00, will actually be closed for 60 minutes and 59 seconds, from 03:00:00 - 04:00:59.
 
 
===== Time zone =====
 
All times entered are in the '''local time zone of the segment being closed'''. If you are in one time zone, and are submitting a closure for a segment in another time zone, use the start and end times in the time zone where the segment is.
 
 
===== Setting long-term closures =====
 
{{red|'''NOTE:'''}} Temporary Closures must not be longer than 6 calendar months (183 days to be precise).
 
To enter a Temporary Closure longer than 6 months, split it into multiple Temporary Closures. Each Temporary Closure entered should be less than 6 months. E.g. A one year Temporary Closure from 2011-12-01 through 2015-11-30 can be entered as two individual Temporary Closures.
# 2014-12-01 - 2015-05-31 (182 days)
# 2015-06-01 - 2015-11-30 (183 days)
 
 
=== Report closure feature in the Waze app ===
----
 
Users in the client app can mark an unexpected road closure they see while driving. It is typically used for unexpected, short term closures of up to a few days. This feature requires multiple users to be at the location to enter the same road closure information on the map before it will be seen by other drivers.
 
Instructions on how to use this feature in the Waze app is available in the [http://support.google.com/waze/answer/6081233 Waze Help Center].
 
 
=== Major traffic events ===
----
 
If a road closure is part of a larger event, it can be submitted to Waze as a Major Traffic event, or MTE. MTEs are generally determined by the scale of the event and how many people will be impacted.  The closures should be submitted using the MTE sheets provided. This way Waze is able to track the closures and help spread the word. Only if Waze decides not to support the event, or if you don't have at least one weeks advance notice should you submit these closures through other methods.
 
To notify Waze of a coming event in your area, use the [http://docs.google.com/a/google.com/forms/d/1R0XIsGkHQmk8Nc0U5DDID1PwMQWqLMwmindiLDFwcjo/viewform MTE Submission Form]. 
Helpful information to have for submissions are as follows:
*Name of Event
*Website for event
*Roads which will be effected (not necessary)
*Location
*Start and End Date
*Start and End Time (if available)
 
All MTE submissions are posted to the [http://script.google.com/a/macros/google.com/s/AKfycbwegLpBUyCBB07OBDXHK8H5Js3ynsGkmn8YFI-NGxS_7--JDGud/exec Waze Mini Site] <small>''(if the mini site gives an error try refreshing the page)'' </small>so that other editors in your area can find the name for an event and mark the closure consistently.
 
The closures for each MTE are submitted in a [[#Closure sheets|unique Google Sheets spreadsheet]]. If you need access to a particular event spreadsheet, request access in the spreadsheet and it will be granted by Waze HQ.
 
 
==== Support for major traffic events ====


If your event is going to receive further support as an MTE, or if more information is needed, Waze will be in touch after the form is submitted. Waze further supports some events by providing local push notifications, inbox messages, social media announcements and/or website features on the [http://www.waze.com/events Major Events page] on Waze.com.
*URs/MPs submitted through the app
*Knowledge of local happenings
*Notification from the local community / Waze Major Traffic Event Team
*Long-term closures


If Waze notifies you that your submitted Major Traffic Event will not be supported, or if you have less than one week advance notice of the closure, you should submit the closure through one of the other [[#Real time closures|Real-Time Closure methods]].
All Real-Time Closures follow the same general principles below, regardless of which method is used to submit them. Depending on which method is used there are additional guidance and instructions in the corresponding unique subsections below.


=== WME closure feature ===
===Waze for Cities Program===
----


'''This is the preferred method for closing roads due to its safety and visibility to Wazers.'''
Through the [[Connected Citizens Program]], Waze shares and receives information from [[Connected Citizens Program#Who can Join|select entities]] which partner with Waze. This information can include Road Closures which are entered in WME directly by Waze Staff or the CCP's employees. Wazers are encouraged to [[Connected Citizens Program#How to Join|promote these relationships with their local governing entities]].
The feature allows editors to temporarily prevent routing over specific segments, without having to make any changes to, or damage those segments and their junctions.


With this tool, closures can be entered directly in WME, and is visible almost immediately in the client and Livemap. It is displayed prominently on the map as a closure alert, and with red and white candy stripe lines along the closed segments.  
===Closure guidance and tips===
=====Edit History=====
[[File:Livemap closure alert.png|250px|thumbnail|right]] Adding/deleting/modifying a closure creates an entry in the segment's history, but does not cause a change in the <small>Modified:</small> username showing the last editor of the segment. You can also see who added an active closure by clicking on the alert in Live Map or the client. Closure expiration does not appear in the segment's history.


====={{anchor|RTC area}}Closure feature permissions=====


==== Closure feature permissions ====
*Usual situation
**Rank: Your rank must be {{rank|closure}} or above.
**Edit permission The segment must be in your editing area, and be locked at or below your rank
*'''RTC area''' - a special-purpose area granted by your [[RC]] for the purpose of making closures. Generally granted to CCP partners
**You can apply a closure to any segment within the RTC area, no matter the lock level.


This feature is restricted to rank 5 editors and above, unless otherwise decided by the local community. Global champs also have the ability to allow users of varioius levels aceess to the feaure.  If you would like to request access, contact a member of the community in the [http://www.waze.com/forum/viewforum.php?f=663 Waze Community Forums].
If you are unable to close a segment, then contact an editor who can via [[PM]], in [[WME Chat]], or in Discord. Some regions of the US use a closure form to submit closure requests. Please check with your local community.


Alternatively, If you do not have the required rank to access the Closure feature in WME, you can ask a higher ranking editor to implement the closures for you. Your country may have a streamlined monitored process for this, or it can be submitted like any other unlock/update request. You can also ask a higher editor directly in a [[PM]], or [[WME Chat]]. ''In the USA the [http://docs.google.com/forms/d/1oGINt4UEkBV0Par5VCingXzTZpJq9KjG8GbZpGqbRow/viewform  Road Closures Form (USA)] is used for example.''
=====Closing recently edited segments and nodes=====


Road closures go live almost immediately - there is no wait for tile update. However, they can only be applied to segments that have already been uploaded to the map. You will not be able to save a closure on any segment that was cut, merged or newly drawn after the last tile update, because the new segment ID has not been uploaded. WME will display the error message '''{{red|(!) Failed to add road closure -xxx}}'''. Wait until after the changes are included in a tile build, then enter the closure again.


==== Step by step instructions to add a closure ====
If a segment is disconnected from one node, attached to a different node, or is involved in roundabout creation, even though the segment ID is preserved, it may not be possible to apply the desired closure to the segment. WME may allow application of a closure that extends no more than 48 hours into the future. When a segment has been attached to a different node (identified by its node ID), attempts to use the segment to close this "new" node may instead result in closure of the node formerly attached to the same end of the segment. 


# Select the segments you want to close.
In order  to prevent routing through a segment that also needs to be cut in two or removed completely, first place a time-based segment restriction (TBSR) on the segment, then (optionally) apply the closure to make it visible to driversAfter the next tile update, the TBSRs will be in place to prevent routing while you make other changes. Even if you delete a segment, the restrictions will persist until the next tile update. Then you can remove the closure, make segment edits, and apply any new TBSRs needed to control traffic appropriately in the new configuration. After one more tile update, all the edits will be uploaded to the map, the TBSRs can be removed, and closures can be applied to the correct section of roadFollowing this procedure will require 2 or 3 days, but will, in the end, allow you to limit a closure to just a damaged bridge, for example, instead of an entire mile-long segment of road.
# Click the {{key press|Add Closure}} button in the left panel.
# Click to {{key press|+ Add Closure}} and fill out the fields shown:
::'''Location''' - This field will auto-populate to name of affected street. If multiple streets are selected, add a general description of the area (name of the road, the interchange, or the area if several roads in a known area are being closed)This section is NOT view-able in the client app, it is only seen in the WME. 
::'''Reason''' - This section will be view-able in both the client app and the LiveMap. Write a description of closure / event here. ''Once supported, #hashtags will go here.''
::'''Direction''' - Closure direction should be noted carefully (using the A and B nodes for reference). Close one way direction on a two way road here.
::'''Event''' - This field is not currently active, please ignore.
::'''Start/End Date & Time''' - Enter date/time the closure will remain active (the start date can be a date in the past).  Enter local time for area of map you are editingFormat is 24-hour clock and YYYY-MM-DD. '''{{red|NOTE:}} End date can not be more than 183 days after the start date.''' (see [[#Start and end time settings|below]] for more information.)


[[File:Add closure details.png|center]]
To maintain closures at an intersection while drawing a new roundabout, it is possible to remove the closures, draw the roundabout, and set new closures (48 hours or less) on the incoming segments.  After the next tile update, the closures can be extended.


=====Editing segments with closures=====


==== Saving your work ====
{{Red|'''NOTE:'''}} If a segment has a closure on it in WME, certain attributes cannot be directly modified by any editors - regardless of rank. This includes changing the segment, node IDs, or anything that could affect routing. This is by design, to prevent corrupting the closure. Changing the direction of the segment cannot be made with a closure already on a segment.


'''Save & Check''' in the live map.  Active closures will appear with red closure icons in WME, and with closure alerts bubbles and red and white ''(candy stripe)'' road segment highlighting in Livemap immediately.
If you need to edit the segment causing the IDs or direction to change, you will have to first remove the closure (copy the details first), then modify the segment and save. If the edit did not alter the segment or junction node IDs, you can immediately replace the closure with the details you copied to the appropriate segments. If you altered any segment or junction node IDs, you will have to wait until after the next tile update before reentering the closure.


Inactive closures will appear with grey closure icons in WME only. They do not appear at all in Livemap or the Waze app.
Segments with a closure on it in WME can be edited in the following ways: change street and city name, change lock level, change road type, change speed limit, add, change, or remove a restriction, add, change, or remove elevation, add, change, or remove routing preference and add lane guidance.


A closure can not be entered along with any other saves, similar to House Numbers. If you have any edits pending a save, and try to add a Temporary Closure you will get an error at the end. Be sure to save before trying to add a Temporary Closure.
<br />
=====Closing multiple segments=====
When closing multiple segments at the same time, especially when they have different directions, verify that all the closures were added properly. Sometimes adding closures to segments in different directions can result in some segments not being closed, or in some segments being closed in the wrong direction.


=====Segment direction for one-way closures=====


==== WME closure feature guidance ====
If only some of the segments are one-way, or some one-way segments are in opposing direction (B-A, A-B), you can set the closure as two-way for all the segments. When you save you will see an error line for each direction of a closed segment which failed to save because the segment is one-way. You can ignore the error, and all your segments ''should'' be closed in all possible directions. (Be sure to double check them all.)


===== Closing recently edited segments =====
==Major Traffic Event (MTE)==
{{anchor|Major Traffic Event (MTE) closure sheets}}
{{anchor|Major_traffic_events}}
{{Anchor|Closure_sheets}}


Real-Time Closures entered using this feature {{u|are not subject to waiting for a [[tile update]]}}, they will go live almost immediately. However, since the Real-Time Closures are effected on the segments and nodes as they are now in the current live map, they don't work on segments and nodes which are not already included in the current tile build. If you enter a Real-Time Closure for a segment which has been modified enough (e.g. changed the segment ID, node ID, or junction location) since the last tile update, the Real-Time Closure would be corrupted and not functioning properly until after the next tile update.  
There are two ways to create [[Major Traffic Event|Major Traffic Events]] in Waze.


To protect against this, if you try to close a new or modified segment before the tiles update, the closure will not save and WME will display an error '''{{red|(!) Element Segment with ID xxxxxxxx was not found (probably deleted).}}''' Wait till after the changes are included in a tile build, and then enter the closure again and it should save fine.
#The easiest way, for editors of rank {{rank|closure}} and higher, is to create the event and the closures in the Waze Map Editor. ''See the full article for more details on creating a [[Major Traffic Event]] in the WME.''
#*Editors below rank {{rank|closure}} can reach out to their local community who will be glad to assist them in generating the MTE, and associated closures in the WME.
#Non-editors can still submit information directly to Waze Closure staff (see below) to create an MTE, and (optionally) get a message out to wazers in the area.


 
===Submitting directly to Waze===
===== Closing multiple segments =====
{{anchor|More on closure sheets}}
 
Real-Time Closures can be added to multiple segments simultaneously by selecting all the affected segments first. {{Red|Be careful}} to verify all the segments after you save that the Real-Time Closures were added properly. ''It's been reported before when multiple Real-Time Closures were added at once, that some of the segments either weren't closed, or had incorrect details in the closure (e.g. direction).''
 
 
===== Segment direction for one-way closures =====
 
If only some of the segments are one-way, or some one-way segments are in opposing direction (B-A, A-B), you can set the Closure as two-way for all the segments. When you save you will see an error line for each direction of a closed segment which failed to save because the segment is one-way. You can ignore the error, and all your segments ''should'' be closed in all possible directions. (Be sure to double check them all.)
 
 
===== Editing closed segments =====
 
{{Red|'''NOTE:'''}} If a segment is closed using this feature, the segment will not be editable by any editors - regardless of rank - while the closure is in effect. This is by design, to prevent any changes to segment and junction node IDs which will corrupt the closure.
 
If you need to edit the segment, you will have to first remove the Temporary Closure ''(copy the details first)'', then modify the segment and save. Depending on the type of edit you can either replace now, otherwise you will need to wait for a tile update before being able to add a new Temporary Closure. Add a new Temporary Closure with the details you copied to the appropriate segments.
 
=== Closure sheets ===
----
----


There are generally two types of Closure Sheets;
To submit a major traffic event, email waze-closures@google.com with the following details:
* Regional Closure Sheets supplied by Waze staff and shared with the community leadership of some countries.
* Supported Mega Traffic Events are also processed using a unique closure sheet for each MTE.
 
These Closure Sheets have some unique advantages over submitting closures directly in WME, and also have some unique guidelines listed here below. They still also follow all the general guidance for [[#Real time closure|Real-Time Closures]] listed above.
 
 
==== Closure sheets vs closure feature in the WME ====
 
Real-Time Closures which could just as easily be submitted using the Closure feature in the WME, shouldn't be submitted using the Regional Closure Sheets. If there is some feature of submitting them through the Regional Closure Sheet easier somehow, then it is fine to use the Regional Closure Sheets for them. The Regional Closure Sheets may also have some features not yet available in WME, closures utilizing those features should be submitted through the sheets.
 


==== How to submit a closure using a sheet ====
*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


Many aspects of submitting a Real-Time Closure in a sheet are the same as other forms of submission. However because the sheets are not part of the Waze ecosystem, there are some important differences. Not all Closure Sheets are identical, but they all follow th esame general principals:
'''Username -''' You must enter your exact Waze Username as it appears in WME and the Forum. This allows Waze staff and the community leadership to contact you for any updates as necessary.<br />
'''Permalink -''' You have to provide a permalink which shows all the segments you wish to close selected. See the [[Waze Map Editor#Permalink|Permalink]] article for details on how to create a Permalink which has the segments selected.


There may be other elements you are asked to provide to make use of some advance features of the Closure Sheets, if this happens there will usually be some instructions and guidelines included somewhere in the sheet.
Some pointers when submitting events directly to Waze Closure staff:


The Closure Sheets are processed by scripts and contain formulas which automatically perform functions and calculations on the data you submit. To make sure you don't break the sheets, please be careful never to type or paste anything columns of sheet labeled "DO NOT EDIT" in the header row.
*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 MTE 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 MTE.


==== Closures not displayed on the map ====
==Report closure feature in the Waze app==
{{anchor| Report a Closure in the Waze client app}}
{{anchor| Report a closure in the Waze client app}}


Real-Time Closures entered using this feature {{u|are not subject to waiting for a [[tile update]]}}, they will go live as soon as they are uploaded by Waze. However, if you enter a Real-Time Closure for a segment which has been modified enough (e.g. changed the segment ID, node ID, or junction location) since the last tile update, the Real-Time Closure will not work until the new segment changes go live.  
Users in the mobile app can mark a closed road they see while driving. Instructions on how to use this feature in the Waze app is available in the [http://support.google.com/waze/answer/6081233 Waze Help Center].


When entered through a Regional Closure Google Sheet the alert bubbles will likely show in the new location of the nodes, but the candy stripe and routing effects won't be implemented until the segment changes are live after the next tile update.
*This feature is typically used for unexpected, short-term closures of up to a few days.
*This closure will immediately show up in the reporting user's app.
*Generally, the closure will not show up for anyone else until several other users have reported the same closure.
*Editors can become "trusted" to report closures and fewer additional reports will be required to make their in-app closures go live.
*If the editor is rank 5 or higher, the in-app closure will go into effect immediately.


====App reported closures in WME====
{{Anchor|Closure date NOT SET}}{{anchor|closures with a start date 1969 or 1970}}In-app closures are also visible from within WME


{{clear}}{{ReturnToEditingManual}}
*These closures can be deleted or edited by any rank {{Rank|closure}}+ editor
*If there are multiple app-reported RTCs on a segment, an error will be generated when trying to edit and save changes to one of them. Remove duplicate entries first, and then make changes to the one remaining entry.

Latest revision as of 20:21, 14 July 2022

A Real Time Closure (RTC) may be used when a segment is completely closed temporarily in one or both directions to all wazers. When the RTC is active, the affected segment will be marked with red-and-white candy stripes and Waze will not route any traffic through or onto the segment. Only use an RTC when a road is completely closed in one or both directions. Do not use an RTC for lane closures, width restrictions or other cases where traffic is still allowed to move.

The real time closure is the preferred method for temporarily closing roads because it is visible to Wazers and because it helps protect the map.

Deciding when to use an RTC

There are several possible ways to prevent Waze from routing traffic over a segment. The best choice depends on the situation.

Method Vehicles Affected Takes Effect Ends Traffic Data Guidance
Real time closure All Immediate Expires Kept Preferred option for temporary (even long term) one-way or two-way closure. Visible to drivers. Immediate effect. Automatically removed when it expires.
Road direction change All Tile update Permanent Kept Use only for permanent change in direction from two-way to one-way.
Time-based segment restriction Some/All Tile update Optionally expires Kept Use only where the restrictions (time of day/ day of week) are permanent, or where certain vehicle types are allowed or prohibited. Example: No passenger cars on weekdays.
Time-based turn restriction Some/All Tile update Optionally expires Kept Use where travel on the segment is allowed, but turns onto the segment are temporarily forbidden or else permanently forbidden at certain times of day, days of week or for certain vehicle types. Example: No left turn 4:00pm-6:00pm
Permanent turn restriction All Tile update Permanent Kept
Use where a turn onto the segment should be permanently forbidden for all vehicles.
Conversion to a penalized road type All Tile update Permanent Kept Penalties make routing less likely, but are not absolute. Vehicles with a destination on the segment will be routed onto the segment. Normally  Private Road  is used.
Disconnection All Tile update Permanent Lost Use only if the disconnection is permanent. All turn data is lost.
Deletion All Tile update Permanent Lost Use only if the road is permanently closed. All data is lost.

Real time closures are the preferred way of temporarily controlling traffic for a number of reasons

  • They begin to affect routing within a few minutes of being saved, without waiting for a tile update.
  • When the RTC is removed, proper routing can be restored immediately, without waiting for a tile update.
  • They allow editors to temporarily prevent routing over specific segments, without having to make any changes to, or damage those segments, and their road types, junctions, or turn restrictions.
  • They preserve traffic data.
  • By default (see below), a road closed with an RTC will be continually evaluated for through traffic. If enough traffic is detected driving through a closure, the closure is temporarily deactivated until the traffic is no longer detected. Therefore if an RTC is mistakenly placed on an open segment it will only affect drivers for a few minutes until the through traffic is detected, and the closure deactivated automatically.
  • Real time closures are visible in Live Map and the Waze app with special alert icons and segment highlighting. They are also visible in WME with special icons.
  • They can be created and commented on within the Waze app, with app creations and comments generating notifications for editors.
  • They can be associated with Major Traffic Events to get notifications sent to nearby Wazers.
  • They eliminate the need for addition and removal of partial restrictions. In fact, partial restrictions should not be used redundantly with real time closures

Effect on routing

Waze will not choose a closed segment as the closest segment to the destination.

When a real time closure is active, Waze will not route through or even partway through the closed segment in the direction(s) it is closed. It will not route to a destination on the closed segment(s), even if that is the closest segment to the destination. Instead, it will pick a stop point on the next closest segment. If the closed segment is much longer than the part of the road that is actually closed to all traffic, this can result in wazers being sent to a nearby street even though they should be able to drive to the destination. For this reason, if a closure is very localized and going to go on for over a week (as for a bridge replacement) it might be worth the effort to edit the closed segment.

If the Wazer is currently located on a closed segment, waze will find a route that begins in the closed segment and find the shortest distance to a segment with no closure.

How real time closures are added to the map

Real time closures in WME

How to add a real time closure

Screenshot of segment RTC properties as of 08/2020
  1. Save all pending edits. You will not be able to add or edit closures if there are pending edits. Note that saving an edit which changes the segment number will prevent adding the RTC.
  2. Select the segments you want to close.
  3. Click the Closure tab in the left panel.
  4. Click to + Add Closure and fill out the fields shown:
Description - This section will be viewable in both the client app and the Live Map. Write a description of closure / event here.
Direction - If a single one-way segment is selected, then the correct direction will be auto-selected. If the segment is two way and the closure is in only one of the directions, choose that direction here. If multiple directions are selected, then the editor should choose two way for the closure then all two way segments will be closed two ways and the one ways will be closed in the appropriate direction.
Event - If this closure is part of a Major Traffic Event, choose it from the drop-down list. If not present then add the Event.
Start/End Date & Time - Enter date/time the closure will remain active (the start date can be a date in the past). Enter the correct time for the closure for the local time zone of the segment being closed, regardless of where you are located while entering the closures. Time is entered in 24-hour format and date uses the YYYY-MM-DD. The first minute of the day begins at 00:00 and the last minute of the day begins at 23:59.
  • The start date cannot be great than 365 days from the current date.
  • The end date (i.e. duration) for a Real-time closure is no longer limited.
  • Real-time closures are active for the full minute they are set for (up to 00 seconds of the next minute)
  • Do not use 24:00 as a start or end time.
  • 00:00 is the first minute of the day. Avoid using it as end time.
  • 23:59 is the last minute of the day. Avoid using it as a start time.
  • A closure set for Start: 03:00, End: 04:00, will actually be closed for 60 minutes and 59 seconds, from 03:00:00 - 04:00:59.
Save & Check
  • In Live Map, active closures will appear with red closure icons in WME, and with closure alerts bubbles and red and white (candy stripe) road segment highlighting in Live Map immediately.
  • May have to zoom in to see all closures in Live Map.
  • In Event Mode, if the closures are associated with an event, to see candy stripe road segment highlighting in WME
  • Inactive closures do not appear at all in Live Map or the Waze app, and will appear with gray closure icons in WME only
Slideshow - how to create Real Time Closures link to this section
Click expand on the right side here to see a slideshow developed by waze staff

This slideshow was prepared by Waze staff to show how to add a closure in WME. It contains information on which segments to select as part of a closure as well. The information in this slide show is also presented throughout this page in text.

HOV/Service Road adjacent checkbox

When checked, the HOV/Service Road adjacent checkbox will prevent the segment from being temporarily reopened by traffic detection. This includes situations where Waze might mistakenly believe that drivers on adjacent segments are driving on the closed segment, causing Waze to temporarily "reopen" the road and include it in calculated routes. The HOV/Service Road adjacent checkbox is intended to mitigate nearby HOV/Express lane and service road traffic from a closed main road segment (or vice versa), but may also apply to adjacent parallel roads or other elevations of multi-level stacked roads that could trigger traffic detection. The checkbox may also be used in other circumstances where traffic detection is undesired before the set closure end time, such as closures where local traffic is still allowed.

Node Closure
Node closure - cross traffic

Closing segments of a road using real-time closures will prevent Waze from routing wazers down that road. Node closures prevent Waze from routing wazers across intersections along a closed road. When a junction node is closed, no traffic can pass through that node in any direction. All turns through a closed node are prohibited. There is no partial node closure function to restrict individual turns without closing the entire node. In order to close a node to traffic, at least one segment attached to the node must be closed as well.

When entering a real-time closure, junction nodes between selected contiguous segments will automatically be pre-selected for closure, while nodes at the ends of a single segment or multiple contiguous segments are not automatically marked for closure. Prior to applying the closure, junction node closure status can be reviewed and toggled.

If all the real-time closures on segments attached to a closed node are removed, the node closure will be automatically removed as well. However, if any segment attached to a closed junction node remains closed, the node closure will also remain.

To work with node closures:

  • Select the segments to be closed and add segment closure information.
  • Review the list of nodes selected for closure. WME will have enabled junction nodes closures between contiguous selected segments. Mouse-over a node's cross-street name in the list of junction nodes in order to highlight that node on the map.
  • Enable and disable node closures as necessary.
  • Save segment and associated junction node real-time closures.

Prior to the introduction of node closures, the only way to prevent Waze from routing traffic "across" a closed street was to apply closures on the cross-streets. That practice is no longer recommended.

Only the node on the "input" end of a one-way closure can be closed.
Node closures - what to watch out for
  • If a Node closure is enabled as part of an active closure, then it will remain enabled as long as the active closures on any connected segments remain active. If it needs to be disabled, use the node closure toggle switch on any of the connected segment closures
    • When a closure turns a corner, check the state of the closure at the node
      Example: If a Freeway is closed due to weather from Mile 0 to Exit 100, and then the eastern part of the road is opened (Exit 60-Exit 100), be sure to remove the node closure at the remaining eastern closure. Otherwise, the closed node at the end of the entrance ramp at the Exit 60 interchange will prevent routing.
  • On one-way segments closures, only the node at the inbound end can be closed. To close the other node, choose a segment closure that has this node at its inbound end and set the closure toggle switch accordingly.
  • When a closure turns corner, watch out. WME will automatically close the node between the two segments. But traffic may be allowed between the other segments at the intersection. Check the state of the toggle switch for the node at the intersection.
  • When all of the closures at a closed node have expired or been removed, the node closure will also expire. Node closure cannot be used to close an intersection unless at least one segment at the intersection is also closed.


How we learn about closures

The editing community can be informed about these closures by:

  • URs/MPs submitted through the app
  • Knowledge of local happenings
  • Notification from the local community / Waze Major Traffic Event Team
  • Long-term closures

All Real-Time Closures follow the same general principles below, regardless of which method is used to submit them. Depending on which method is used there are additional guidance and instructions in the corresponding unique subsections below.

Waze for Cities Program

Through the Connected Citizens Program, Waze shares and receives information from select entities which partner with Waze. This information can include Road Closures which are entered in WME directly by Waze Staff or the CCP's employees. Wazers are encouraged to promote these relationships with their local governing entities.

Closure guidance and tips

Edit History

Adding/deleting/modifying a closure creates an entry in the segment's history, but does not cause a change in the Modified: username showing the last editor of the segment. You can also see who added an active closure by clicking on the alert in Live Map or the client. Closure expiration does not appear in the segment's history.

Closure feature permissions
  • Usual situation
    • Rank: Your rank must be 3 or above.
    • Edit permission The segment must be in your editing area, and be locked at or below your rank
  • RTC area - a special-purpose area granted by your RC for the purpose of making closures. Generally granted to CCP partners
    • You can apply a closure to any segment within the RTC area, no matter the lock level.

If you are unable to close a segment, then contact an editor who can via PM, in WME Chat, or in Discord. Some regions of the US use a closure form to submit closure requests. Please check with your local community.

Closing recently edited segments and nodes

Road closures go live almost immediately - there is no wait for tile update. However, they can only be applied to segments that have already been uploaded to the map. You will not be able to save a closure on any segment that was cut, merged or newly drawn after the last tile update, because the new segment ID has not been uploaded. WME will display the error message (!) Failed to add road closure -xxx. Wait until after the changes are included in a tile build, then enter the closure again.

If a segment is disconnected from one node, attached to a different node, or is involved in roundabout creation, even though the segment ID is preserved, it may not be possible to apply the desired closure to the segment. WME may allow application of a closure that extends no more than 48 hours into the future. When a segment has been attached to a different node (identified by its node ID), attempts to use the segment to close this "new" node may instead result in closure of the node formerly attached to the same end of the segment.

In order to prevent routing through a segment that also needs to be cut in two or removed completely, first place a time-based segment restriction (TBSR) on the segment, then (optionally) apply the closure to make it visible to drivers. After the next tile update, the TBSRs will be in place to prevent routing while you make other changes. Even if you delete a segment, the restrictions will persist until the next tile update. Then you can remove the closure, make segment edits, and apply any new TBSRs needed to control traffic appropriately in the new configuration. After one more tile update, all the edits will be uploaded to the map, the TBSRs can be removed, and closures can be applied to the correct section of road. Following this procedure will require 2 or 3 days, but will, in the end, allow you to limit a closure to just a damaged bridge, for example, instead of an entire mile-long segment of road.

To maintain closures at an intersection while drawing a new roundabout, it is possible to remove the closures, draw the roundabout, and set new closures (48 hours or less) on the incoming segments. After the next tile update, the closures can be extended.

Editing segments with closures

NOTE: If a segment has a closure on it in WME, certain attributes cannot be directly modified by any editors - regardless of rank. This includes changing the segment, node IDs, or anything that could affect routing. This is by design, to prevent corrupting the closure. Changing the direction of the segment cannot be made with a closure already on a segment.

If you need to edit the segment causing the IDs or direction to change, you will have to first remove the closure (copy the details first), then modify the segment and save. If the edit did not alter the segment or junction node IDs, you can immediately replace the closure with the details you copied to the appropriate segments. If you altered any segment or junction node IDs, you will have to wait until after the next tile update before reentering the closure.

Segments with a closure on it in WME can be edited in the following ways: change street and city name, change lock level, change road type, change speed limit, add, change, or remove a restriction, add, change, or remove elevation, add, change, or remove routing preference and add lane guidance.


Closing multiple segments

When closing multiple segments at the same time, especially when they have different directions, verify that all the closures were added properly. Sometimes adding closures to segments in different directions can result in some segments not being closed, or in some segments being closed in the wrong direction.

Segment direction for one-way closures

If only some of the segments are one-way, or some one-way segments are in opposing direction (B-A, A-B), you can set the closure as two-way for all the segments. When you save you will see an error line for each direction of a closed segment which failed to save because the segment is one-way. You can ignore the error, and all your segments should be closed in all possible directions. (Be sure to double check them all.)

Major Traffic Event (MTE)

There are two ways to create Major Traffic Events in Waze.

  1. The easiest way, for editors of rank 3 and higher, is to create the event and the closures in the Waze Map Editor. See the full article for more details on creating a Major Traffic Event in the WME.
    • Editors below rank 3 can reach out to their local community who will be glad to assist them in generating the MTE, and associated closures in the WME.
  2. Non-editors can still submit information directly to Waze Closure staff (see below) to create an MTE, and (optionally) get a message out to wazers in the area.

Submitting directly to Waze


To submit a major traffic event, email 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 MTE 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 MTE.

Report closure feature in the Waze app

Users in the mobile app can mark a closed road they see while driving. Instructions on how to use this feature in the Waze app is available in the Waze Help Center.

  • This feature is typically used for unexpected, short-term closures of up to a few days.
  • This closure will immediately show up in the reporting user's app.
  • Generally, the closure will not show up for anyone else until several other users have reported the same closure.
  • Editors can become "trusted" to report closures and fewer additional reports will be required to make their in-app closures go live.
  • If the editor is rank 5 or higher, the in-app closure will go into effect immediately.

App reported closures in WME

In-app closures are also visible from within WME

  • These closures can be deleted or edited by any rank 3+ editor
  • If there are multiple app-reported RTCs on a segment, an error will be generated when trying to edit and save changes to one of them. Remove duplicate entries first, and then make changes to the one remaining entry.