Difference between revisions of "Real time closures"

From Wazeopedia
 
(114 intermediate revisions by 9 users not shown)
Line 1: Line 1:
 
{{ReturnTo | Editing manual | the editing manual}}
 
{{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 (temporarily) in one or both directions to all public through traffic.}}
+
[[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''
  
Roads on the map often need to be closed for a variety of reasons including but not limited to planned construction, large-scale events, and emergency closures for accidents or natural disasters.  These 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 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|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 to prevent the traffic flow. 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 [[Live Map]] with alerts and candy stripes on the segments to notify users of the closures in real-time (no wait for tile updates), and prevent routing during the closure time on these segments. '''Due to its safety (protecting the map), and its visibility (in the client and Live Map), 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:
 
** Add a [[#WME closure feature|closure in WME]]
 
** 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 app]] 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 situations.
 
* '''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 ==
 
 
 
'''This is the preferred method for closing roads due to its [[#Map safety and client visibility|map safety and visibility to Wazers]].'''
 
 
 
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.
 
 
 
Real Time Closures can be added to Waze in four ways:
 
 
*[[#Report a closure in the Waze client app|Report a Closure in the Waze client app]]
 
*[[#Report a closure in the Waze client app|Report a Closure in the Waze client app]]
*[[#Major traffic events|Major Traffic Events (MTEs)]]
+
*[[#Major traffic events|Major Traffic Events (MTEs) Closure Sheets]]
*[[#WME_closure_feature|Temporary Closures in WME]]
 
*[[#Closure sheets|Closure Sheets]]
 
 
 
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.
 
 
 
 
 
=== Connected Citizens Program ===
 
 
 
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 submitted to WME directly by Waze staff. To ease the burden of teaching and submitting closures, Wazers are encouraged to [[Connected Citizens Program#How to Join|promote these relationships with their local governing entities]].
 
 
 
 
 
=== Map safety and client visibility ===
 
 
 
This feature is safer for the map 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 Live Map, and the Waze app with special alert icons, and segment highlighting. They are also visible in WME with special icons.
 
  
 +
==Real time closures in WME==
 +
{{Anchor|WME closure feature}}
  
=== General closure guidance ===
+
===How to add a real time closure===
 +
[[File:RTC Window 082020.png|right|alt=Screenshot of segment RTC properties as of 08/2020]]
  
==== Illustrated slideshow ====
+
#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:
  
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.
+
::'''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 autoselected. 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 [[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.
 +
::*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
 +
{{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.
 
{{#widget:Iframe
 
{{#widget:Iframe
 
|url=https://docs.google.com/presentation/d/1tBb3Cg8Ewu_rx7yuPxGMCTy4FIoAb-Z1CY33ukYFtM8/embed?start=false&loop=false&delayms=30000
 
|url=https://docs.google.com/presentation/d/1tBb3Cg8Ewu_rx7yuPxGMCTy4FIoAb-Z1CY33ukYFtM8/embed?start=false&loop=false&delayms=30000
Line 67: Line 128:
 
|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 canceled, 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 Live Map 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.
When adding a Real-Time Closure, consider whether any cross traffic will be blocked as well. Often in work zones and for special events (parades, marathons, festivals), cross traffic is not allowed at one or more junctions.
+
*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.
Waze will not route '''through''' a closed segment. However, it will route up to the nearest end of a closed segment to reach a destination within it. Waze will also route out of the most convenient end of a closed segment if the user starts within it. If traffic going across your Real-Time Closure must be blocked at a junction, you will need to close at least one of the cross street segments as well.
+
*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.
:* Regular cross-streets
 
::* Close '''two-way''' cross-street segments on either side of the closed intersection. Each segment should be closed in the direction traveling away from the closed junction.
 
::* Close '''one-way''' cross-street segments on the side traveling away from the closed junction.
 
:::''Closing both segments will prevent routing across the junction to reach a destination or leave a starting point, regardless of the user's position in relation to that junction.''
 
:* Median segments of closed divided roadways
 
::* When both directions of a divided roadway are closed and cross traffic is disallowed, consider closing only the median segment.
 
:::''When cross traffic between the lanes of a divided roadway is prohibited, closing the median segment will prevent routing to destinations on the far side of the divided roadway.''
 
 
 
{{Expand|
 
====== New Year's Day Parade in RTC Town ======
 
[[File:RTC-CrossStreet-010.png|400px|left|thumb|RTC Town has scheduled a parade down Main St on January 1 starting at 13:00 and ending at 14:00. Traffic must not be allowed to travel along Main St or cross at any intersection.]]
 
[[File:RTC-CrossStreet-020.png|400px|thumb|Select the parade route on Main St and set a two-way closure between 13:00 and 14:00 on January 1.]]
 
[[File:RTC-CrossStreet-030.png|400px|left|thumb|Plum Rd is a two-way cross-street, Orchard Rd, and Mulberry St are one-way cross-streets. To route traffic to the correct sides of these streets, the segments north and south of Main St should be set with one-way closures between 13:00 and 14:00 in the direction traveling away from their junction with Main St.]]
 
[[File:RTC-CrossStreet-060.png|400px|thumb|The completed set of closures in this example would look like those on the right. We’re all set to watch the parade!]]
 
{{clear}}
 
====== Divided road closed for construction ======
 
[[File:RTC-CrossStreet-100.png|400px|left|thumb|Willow St will be closed for two weeks for construction. So we set a closure for the length of both carriageways.]]
 
[[File:RTC-CrossStreet-110.png|400px|thumb|Cherry Ave crosses Willow St in a ‘H’ configuration. In this case, we need to close only the median segment to prevent traffic from being routed through the intersection or to the wrong side of Willow. Note, we set no closures on Rose St because it is a T-intersection.]]
 
|Examples|section=5
 
|nt=yes
 
|summary='''Click expand on the right side here to see Example scenarios with illustrations.'''{{anchor|New_Year.27s_Day_Parade_in_RTC_Town|Divided_road_closed_for_construction}}
 
}} <!-- End Expand -->
 
 
 
==== Lane closures and construction zones ====
 
 
 
For situations where only some lanes are closed but the road is still driveable, and general [[Road names#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 by doing the following: 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. The one minute delta from the scheduled time will not be significant enough to impact any routing issues in that area.
 
  
 +
<br />
 +
=====How we learn about closures=====
 +
The editing community can be informed about these closures by:
  
===== Start and end time settings =====
+
*URs/MPs submitted through the app
 +
*Knowledge of local happenings
 +
*Notification from the local community / Waze Major Traffic Event Team
 +
*Long-term closures
  
{{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 entered as ending on Jan 1st at 00:00 will open the road for the entire day of Jan 1st, while if it is entered as 23:59 would leave the road closed for that entire day. ''To prevent ambiguity for closure times try not to use 00:00 and instead use 00:01 for the start of a day and 23:59 for the end of a day.''}}
+
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.
  
*Real-time Closures are active for the full minute they are set for.
+
===Waze for Cities Program===
** 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.
 
  
 +
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]].
  
===== Time zone =====
+
===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.
  
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 located.
+
====={{anchor|RTC area}}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.
  
===== Setting long-term closures =====
+
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.
  
{{red|'''NOTE:'''}} Temporary Closures must not be longer than 6 calendar months (183 days to be precise).
+
=====Closing recently edited segments and nodes=====
  
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. For example, a one-year Temporary Closure from 2014-12-01 through 2015-11-30 can be entered as two individual Temporary Closures.
+
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.
# 2014-12-01 - 2015-05-31 (182 days)
 
# 2015-06-01 - 2015-11-30 (183 days)
 
  
 +
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. 
  
====== Maximum closure duration ======
+
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.
  
The maximum length for a Real-Time Closure is one year.
+
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.
  
The end date for a closure cannot be set for more than one year from the current date. Even if the closure is less than 6 months long, it must end before one year from the current date. Otherwise, you will get an error from the server. "'''{{red|(!) end time is too far in the future for road closure -103}}'''"
+
=====Editing segments with closures=====
  
{{anchor|Report closure feature in the waze app}}
+
{{Red|'''NOTE:'''}} If a segment has a closure on it in WME, it cannot be directly modified by any editors - regardless of rank. This is by design, to prevent any changes to segment IDs which will corrupt the closure. Turns and house numbers associated with the segment can be edited normally.
  
=== Report closure feature in the Waze app ===
+
If you need to edit the segment, 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.
----
+
=====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.
  
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.
+
=====Segment direction for one-way closures=====
  
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].
+
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.)
 
 
==== App reported closures in WME ====
 
 
 
Any closures reported from the Waze app are visible and can be manipulated in the Waze Map Editor. Waze app reported closures {{u|do not}} have an effect on routing until enough users report the same segment closed. However, if an editor sees it in WME and edits it, the RTCs then take effect immediately. ''For all the details on the display and handling of app-reported closures in WME, please see the [[#Understanding closures with an end date circa 1970|section below that explains the WME aspect of these closures]].''
 
  
 +
==Major Traffic Event (MTE)==
 +
{{anchor|Major Traffic Event (MTE) closure sheets}}
 
{{anchor|Major_traffic_events}}
 
{{anchor|Major_traffic_events}}
 +
{{Anchor|Closure_sheets}}
  
=== Major Traffic Events (MTEs) ===
+
There are two ways to create [[Major Traffic Event|Major Traffic Events]] in Waze.
----
 
 
 
If a road closure is part of a larger event, it can be submitted to Waze as a Major Traffic Event (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 or the WME Closure tool (available to editors rank {{rank|closure}} and above). This way Waze is able to track the closures and help spread the word.
 
 
 
To receive further support from Waze (website and/or push + inbox message) for an MTE closure, the event must be submitted through the MTE submission form below. 
 
 
 
To notify Waze of an upcoming 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 affected (not required)
 
*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 ====
 
 
 
Once the submitted event is reviewed, the submitter receives an MTE closure sheet and further instruction on how to provide all of the information needed to properly close the affected roads. 
 
 
 
Once the closure sheet is fully completed, the closure will be live in the app. 
 
 
 
Waze further supports some MTEs 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. 
 
 
 
MTEs are likely to be announced on the Major Events website and/or via inbox + push message if the event affects a significant portion of the local population.  For your event to be considered for inclusion in the following week's push/inbox messaging, all closure information must be received by the Wednesday prior to the event.
 
 
 
A closure may not appear in the app if Waze is unable to obtain the proper information, either through user-completed closure sheets or if other resources cannot be found.
 
 
 
{{anchor|Closure feature in the waze map editor}}
 
 
 
=== WME closure feature ===
 
----
 
 
 
'''This is the preferred method for closing roads due to its map safety and visibility to Wazers.'''
 
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 Live Map. It is displayed prominently on the map as a closure alert, and with red and white candy stripe lines along the closed segments.
 
 
 
 
 
==== {{anchor|RTC area}}Closure feature permissions ====
 
 
 
This feature is restricted to rank {{rank|closure}} editors and above. Under special circumstances, your [[RC]] (or a state or territory manager in your area), has the ability to grant an '''RTC area''' to users of various ranks so they can access the feature. Contact your local RC if you believe you require such access.
 
 
 
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. It can be submitted like any other unlock/update request in the [http://docs.google.com/forms/d/1oGINt4UEkBV0Par5VCingXzTZpJq9KjG8GbZpGqbRow/viewform Road Closures Form]. You can also ask a higher ranked editor directly in a [[PM]], or [[WME Chat]].
 
 
 
==== Step by step instructions to add a closure ====
 
 
 
# Select the segments you want to close.
 
# 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 viewable in both the client app and the Live Map. 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 the area of the map you are editing.  Time is entered in 24-hour format and date uses the YYYY-MM-DD format. '''{{red|NOTE:}} End date can not be more than 183 days after the start date.''' (see the section [[#Start and end time settings|Start and end time settings]] for more information.)
 
 
 
[[File:Add closure details.png|center]]
 
 
 
 
 
==== Saving your work ====
 
 
 
'''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.
 
 
 
Inactive closures will appear with gray closure icons in WME only. They do not appear at all in Live Map or the Waze app.
 
 
 
A closure cannot be entered along with any other saves (similar to saving with House Numbers). If you have any edits pending a save and try to add a Temporary Closure you will get an error. Be sure to save before trying to add a Temporary Closure.
 
 
 
 
 
==== WME closure feature guidance ====
 
 
 
===== Closing recently edited segments =====
 
 
 
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.
 
 
 
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.
 
 
 
 
 
===== Closing multiple segments =====
 
 
 
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. If the edit did not alter the segment or junction node IDs, you can immediately replace the Temporary 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 Temporary Closure.
 
 
 
 
 
===== Understanding closures with a start date circa 1970 =====
 
{{anchor|Understanding closures with an end date circa 1970}}
 
Note: {{as of|2017}} App reported closures show this style date as the start date, while end dates can set by choosing a duration in the client. {{as of|2015|May}} Waze has recently changed the user interface, so you should not see these anymore. You will instead see the closure marked as end date "Not set" (see the [[#Closure date NOT SET|next section]]). It is possible that there are some existing closures that use the old format described in this section, or that not all servers have been updated to use the new interface described in the next section.
 
 
 
When a mobile user [[#Report closure feature in the Waze app|submits a Closure Report through the app report menu]], Waze puts it on the map as a closure, similar to a manually-entered closure. Unlike WME-entered reports, the app supports submitting closures without indicating an end date/time. These are recorded with a "null" date time, which in Unix, by convention (as described below), is midnight of January 1,1970. Because Waze uses the [[UTC]] time zone, this may be ±1-13 hours different from your local time.
 
 
 
In the [http://en.wikipedia.org/wiki/Unix Unix operating systems] a time is encoded as the number of seconds passed since January 1, 1970. A "null" date will be zero seconds passed and show a date time of 1970-01-01T00:00 UTC. Adjusted for time zones, and you could have a date-time anywhere from 1969-12-31T12:00, to 1970-01-01T12:00, or one hour more when adjusted for Daylight Saving (Summer) Time.
 
  
 +
#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.
  
{{Anchor|Closure date NOT SET}}
+
===Submitting directly to Waze===
 
+
{{anchor|More on closure sheets}}
===== Closures with end date "Not set" =====
 
 
 
You may occasionally see an RTC in WME with an end date of "Not set" (or set in 1969-1970 in the older style [[#Understanding closures with an end date circa 1970|described above]]).
 
*These may not be actively affecting routing in Live Map or the Waze app.
 
*They may be submitted by any rank user, even if the user is below the rank to have [[#closure feature permissions|RTC permission]].
 
*There may be more than one of this type of closure overlapping for the same segment and direction.
 
 
 
''These are [[#Report closure feature in the Waze app|Closures reported from within the Waze app]]''.
 
 
 
A Closure reported from the Waze app does not include an end date in it. These closures are therefore reported to WME with no assigned end date.
 
 
 
The closure anomalies listed above are a result of the following:
 
* Closures reported from the client app don't immediately affect routing until there are multiple identical reports.
 
* They can be reported by any rank user.
 
* Multiple reports are required to activate them.
 
* More than one report can exist on the same segment.
 
 
 
These closures are editable by editors in WME who have permission to use the RTC feature. If you do edit and/or delete one of these app-reported RTCs, the effects are seen immediately. If you change the end date, the RTC will immediately start affecting traffic like any regular RTC.
 
 
 
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. You will need to locate the duplicate entry or entries and remove them before being able to save changes to the one entry.
 
 
 
=== 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.
 
* Supported Major 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 below. They still also follow all the general guidance for [[#Real time closures|Real-Time Closures]] listed above.
 
 
 
 
 
==== Closure sheets vs closure feature in WME ====
 
 
 
Real-Time Closures which could just as easily be submitted using the Closure feature in 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.
 
 
 
 
 
===== Closure sheets upload schedule =====
 
 
 
Real-time closures submitted through WME are processed and go live immediately. Closures submitted through a regional sheet are manually uploaded by Waze staff on a daily schedule. This is another benefit of submitting RTCs through WME instead when possible.
 
 
 
Waze staff receive an alert of certain changes to the closure sheets three times per day at the following hours:
 
*05:00 UTC
 
*13:30 UTC
 
*17:00 UTC
 
If there have been no qualifying changes to the sheet, Waze staff will not receive the scheduled alert.
 
Closures submitted to the spreadsheet 5 min after they upload them, will not be seen by Waze staff until the next alert.
 
 
 
The alert is generated when changes are made to the currently active sheet (tab) in the workbook. This is usually the sheet on the left (for regional spreadsheets this is the sheet named for the current month). Changes that trigger the alert are setting the cell in the status column to one of the following:
 
*'''"Ready for upload"'''
 
*'''"Canceled event"'''
 
*'''"Updated Details"'''
 
 
 
For '''urgent closures''' which must be uploaded or changed immediately, ''and cannot be submitted through WME'', you can "add a comment" to it in the sheet and write "URGENT", or any other descriptive text so they know to handle immediately.
 
 
 
When you add a comment by right-clicking on a cell in the sheet, Waze staff get a separate alert with the text of the comment after a few minutes.
 
 
 
Closures are not uploaded the minute the alert is received by Waze staff, but they do try. There may be delays because this is a manual process. If something is urgent, be sure to add the comment as mentioned above for priority handling.
 
 
 
==== How to submit a closure using a sheet ====
 
 
 
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 the same 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.
 
:'''Permalink -''' You have to provide a permalink which selects all the segments you wish to close. 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 advanced features of the Closure Sheets. '''There will usually be some instructions and guidelines included somewhere in the 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
  
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 in the columns of the sheet labeled "DO NOT EDIT" in the header row.
 
  
==== Closures not displayed on the map ====
+
Some pointers when submitting events directly to Waze Closure staff:
  
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.  
+
*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.
  
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.
+
==Report closure feature in the Waze app==
 +
{{anchor|Report closure feature in the waze app}}{{anchor|Closure feature in the waze map editor}}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].
  
 +
*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.
  
{{clear}}{{ReturnTo | Editing manual | the editing manual}}
+
====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
  
[[Category:Community Administration]]
+
*These closures can be deleted or edited by any rank {{Rank|closure}}+ editor
[[Category:Waze Map 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 02:35, 7 September 2020

Livemap closure alert.png

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
Arrow Red-2.png
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.
Closure arrow in WME.png

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 can be added to Waze in three ways:

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 autoselected. 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
Closure nodes English.png

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
Livemap closure alert.png

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, it cannot be directly modified by any editors - regardless of rank. This is by design, to prevent any changes to segment IDs which will corrupt the closure. Turns and house numbers associated with the segment can be edited normally.

If you need to edit the segment, 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.

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.