Real time closures: Difference between revisions Discussion View history

(→‎Report closure feature in the Waze app: {{anchor|Closure feature in the waze map editor}})
m (→‎Deciding when to use an RTC: removed "complete" since PR is not complete prevention)
(39 intermediate revisions by 5 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 the segment.  An RTC should NOT be used for lane closures or any other traffic disruptions unless the segment is completely closed for all wazers.
[[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 due to its [[#Map safety and client visibility|map safety and visibility to Wazers]].'''
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 ==
== Deciding when to use an RTC ==
{{Anchor|Controlling traffic flow}}There are several possible ways to completely prevent waze from routing traffic over a segment.  The best choice depends on the situation.  
{{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"
{| class="wikitable"
|-
|-
!
!Method
!Vehicles Affected
!Vehicles Affected
!Takes Effect
!Takes Effect
Line 14: Line 14:
!Guidance
!Guidance
|-
|-
|Real Time Closure
|Real time closure
|All
|All
|Immediate
|Immediate
|Expires
|Expires
|Kept
|Kept
|Preferred option for Temporary (even long term) one-way or two-way closure. Visible to drivers.  Immediate effect. Automatically removed when it expires.
|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
|Road direction change
|All
|All
|Tile Update
|Tile update
|Permanent
|Permanent
|Lost
|Kept
|Only for permanent change in direction from two-way to one-way.
|Use only for permanent change in direction from two-way to one-way.
|-
|-
|[[Partial restrictions|Time-Based Segment Restriction]]
|[[Partial restrictions|Time-based segment restriction]]
|Some
|Some
|Tile Update
|Tile update
|Optionally expires
|Optionally expires
|Kept
|Kept
|Only where the restrictions (time of day/ day of week) are permanent, or where certain vehicle types are allowed or prohibited.
|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]]
|[[Partial restrictions|Time-based turn restriction]]
|Some
|Some
|Tile Update
|Tile update
|Optionally Expires
|Optionally expires
|Kept
|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 or days of week.
|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
|Permanent turn restriction
|All
|All
|Tile Update
|Tile update
|Permanent
|Permanent
|Kept
|Kept
|Use when a turn onto the segment should be permanently forbidden for all vehicles.
|[[File:Arrow Red-2.png|frameless|left]]Use where a turn onto the segment should be permanently forbidden for all vehicles.
|-
|-
|[[Road Type]]
|Conversion to a penalized [[road types|road type]]
|All
|All
|Tile Update
|Tile update
|Permanent
|Permanent
|Kept
|Kept
|Penalties make routing less likely, but are not absolute. Vehicles with a destination on the segment will be routed onto the segment.
|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.
|-
|-
|Disconnect
|Disconnection
|All
|All
|Tile Update
|Tile update
|Permanent
|Permanent
|Lost
|Lost
|Only if the disconnection is permanent. All traffic data is 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.
|}
|}


[[File:Closure arrow in WME.png|right]]Real time closures are the preferred way of temporarily controlling traffic for a number of reasons  
[[File:Closure arrow in WME.png|right]]Real time closures are the preferred way of temporarily controlling traffic 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.
* They begin to affect routing within a few minutes of being saved, without waiting for a [[tile update]].
* The history of the segment is preserved.
* When the RTC is removed, proper routing can be restored immediately, without waiting for a [[tile update]].
* 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.
* 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.
* 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 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''


===== Real time closures vs. partial restrictions =====
===Effect on routing===
Many major roads have ongoing restrictions, which are based on day of the week or time of day. Some examples include:
[[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]].
*No Left Turn between 12:00pm-6:00pm
*No passenger cars on weekdays


For these types of restrictions, please see the [[Partial restrictions|Partial Restrictions page]] on the Wiki.
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.
 
'''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.)''
 
===== 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.'''


==How real time closures are added to the map==
==How real time closures are added to the map==
Line 94: Line 96:
{{Anchor|WME closure feature}}
{{Anchor|WME closure feature}}


===== How to add a real time closure =====
=== How to add a real time closure ===
 
[[File:Add closure details.png|right]]
====== How to close a segment ======
# 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.
# Select the segments you want to close.
# Click the {{key press|Closure}}  tab in the left panel.
# Click the {{key press|Closure}}  tab in the left panel.
# Click to {{key press|+ Add Closure}} and fill out the fields shown:  
# 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. 
::'''Description '''- This section will be viewable in both the client app and the Live Map. Write a description of closure / event here.  
::'''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''' - 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.  
::'''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''' - If this closure is part of a [[Major Traffic Event]], choose it from the drop-down list. If not present then add the Event.
::'''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 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.
::'''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. '''{{red|NOTES:}} '''
::* '''End date can not be more than 183 days after the start date and no more than one year after the current date.'''  
::* '''End date can not be more than 183 days after the start date.'''  
::* Real-time closures are active for the full minute they are set for (up to 00 seconds of the next minute)
::* Real-time Closures are active for the full minute they are set for.
::* Do not use 24:00 as a start or end time.
::* A Closure set for Start: 03:00 - End: 03:01, will actually be closed for 119 seconds, from 03:00:00 - 03:01:59.
::* 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.
::* 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.
::* To prevent confusion you may avoid using 00:00, or 24:00 as a closure time, Instead use 23:59, or 00:01. The one minute difference from the scheduled time will not have a significant impact on routing issues in that area.
::* The longest duration closure is 183 days.
::* The longest duraction closure is 183 days.
::* For a 365-day closure beginning immediately, enter a 183 day closure followed by a 182 day closure.
::* For a 365-day closure beginning immediately, enter a 183 day closure followed by a 182 day closure.
::'''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.
====== Cross streets - which segments to close ======


[[File:Add closure details.png|center]]
Closing several segments of a road will prevent Waze from routing wazers down that road. But it will not prevent Waze from routing wazers across the road at the intersections. Often in work zones and for special events (parades, marathons, festivals), cross traffic should not be allowed at some or all of the junctions. 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. Waze will not route up into a closed segment to reach a destination within it, but it will route out of the "most convenient end" of a closed segment if the user starts within it. So if you need to allow wazers to reach destinations less than a block from the closed road, close the cross street segments in the direction moving away from the closed road.
 
 
====== 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.
 
====== Cross Streets - which segments to close ======
 
Junctions and cross traffic
 
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.
 
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.
:* Regular cross-streets
:* 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 '''two-way''' cross-street segments on both sides of the closed intersection. Each segment should be closed in the direction traveling away from the closed junction. ''Closing all outbound segments routing from the intersection will prevent routing across the intersection's junction node to reach a destination or leave a starting point, regardless of the user's position in relation to that junction node.''
::* Close '''one-way''' cross-street segments on the side traveling away from the closed junction.
::* If traffic at an intersection is being directed by police, then it is not necessary to apply a closure at the cross street. Waze will detect the traffic slowdown and route accordingly.
:::''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.''
::* Close '''one-way''' cross-street segments on the side traveling away from the closed junction. Closing the "way out" from the junction prevents Waze routing wazers through the junction.
:* Median segments of closed divided roadways
:* 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 both directions of a divided roadway are closed and cross traffic is disallowed, consider closing only the median segment. This is enough to prevent cross-traffic routing from either side.
:::''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.''


====== Illustrations and examples ======
==== Illustrations and examples ====
{{Expand|
{{Expand|
====== New Year's Day Parade in RTC Town ======
====== New Year's Day Parade in RTC Town ======
Line 162: Line 152:
|height=415
|height=415
}}
}}
|Slideshow - how to create Real Time Closures
|Slideshow - how to create Real Time Closures|nt=yes
|nt=yes
|section=5
|section=5
|summary='''Click expand on the right side here to see a slideshow developed by waze staff'''
|summary='''Click expand on the right side here to see a slideshow developed by waze staff'''
Line 176: Line 165:


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.
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.
=== Connected Citizens Program ===
=== 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]].
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]].








=== General closure guidance ===
=== Closure guidance and tips ===
==== Usernames and closures ====
==== Usernames and 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.
[[File:Livemap closure alert.png|250px|thumbnail|right]] Adding a closure does not put your name as the last editor for the segment (<small>Updated By: user (#)</small>), however your name does appear in the segment's history.  You can also see who added an active closure by looking at the alert in Live Map or the client.
:
:




==== {{anchor|RTC area}}Closure feature permissions ====
===== {{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.


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.
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. 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]].
===== Closing recently edited segments =====
 
==== Step by step instructions to add a closure ====
 
 
==== WME closure feature guidance ====


===== Closing recently edited segments =====
Road closures {{u|are not subject to waiting for a [[tile update]]}}; they will go live almost immediately. However, they only work on 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 will not be recognized. 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 and it will save.


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.  
For this reason, if you need to remove a segment or cut a segment in two that should not currently be routed, first place a time-based segment restriction on the segment, then apply the closure.  After the next tile update, the segment restrictions will be in place at least until the next tile update. You can then remove the closure and make the types of changes that will prevent applying the closure.  After one more tile update, you should be able to remove the time-based segment restriction (TBSR) and reapply the closure. This should allow you (after 2 or 3 days) to limit a closure to a damaged bridge rather than being forced to apply it to a mile-long segment of road, for example.  


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.
Also, certain edits like disconnection or creation of a roundabout on existing segments affect one's ability to add closures, even though they do not change the segment ID. After disconnecting a segment from another or drawing a roundabout onto it, you will only be able to save a closure on the existing segment that ends less than 48 hours in the future. If you extend it further, WME will display the error message '''{{red|(!) The highlighted segment has been modified recently and will be rebuilt.}}''' You will not immediately be able to add a closure on the new roundabout segments themselves. After a tile update, this time limitation is removed, and a longer closure can be created on the existing segments that go into or out of the roundabout, or on the new roundabout segments. This is useful for maintaining closures while drawing roundabouts at existing intersections
===== Editing segments with closures =====


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


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 =====
===== 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).''
Road 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 closuress were added properly. ''It's been reported before when multiple 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 =====
===== 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.)
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) closure sheets==
===== 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.
 
 
 
== Major Traffic Event (MTE) Closure Sheets==
{{anchor|Major_traffic_events}}
{{anchor|Major_traffic_events}}
{{Anchor|Closure_sheets}}
{{Anchor|Closure_sheets}}


There are two ways to create Major Traffic Events in Waze.
There are two ways to create [[Major Traffic Event|Major Traffic Events]] in Waze.
#<nowiki> The easiest way, for editors of rank {{rank|closure} and higher, is to create the event and the closures in the Waze Map Editor. </nowiki>
#The easiest way, for editors of rank {{rank|closure}} and higher, is to create the event and the closures in the Waze Map Editor.
# The other way is to use the [https://www.waze.com/en/events|Waze Events] page to request an MTE closure sheet. ONce the sheet is filled out with information in WME, Waze Closure staff members who will upload the closures and (optionally) get a message out to wazers in the area.
# The other way is to use the [https://www.waze.com/en/events Events] page to request an MTE closure sheet. Once the sheet is filled out with information in WME, Waze Closure staff members will upload the closures and (optionally) get a message out to wazers in the area.
=== more on closure sheets ===
=== More on closure sheets ===
----
----


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.  
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 closures listed above.  
* Real-Time Closures which could just as easily be submitted using the Closure feature in WME, shouldn't be submitted using the sheets.  
* Closures that could just as easily be submitted in WME shouldn't be submitted using the sheets.  
* 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.
* 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.
* Check the sheet for required fields (closure start and end time, permalink, road name, your username, etc). guidelines are similar to guidelines for closures entered using WME
* Check the sheet for required fields (closure start and end time, permalink, road name, your username, etc). guidelines are similar to guidelines for closures entered using WME
Line 245: Line 227:


== Report closure feature in the Waze app ==
== Report closure feature in the Waze app ==
{{anchor|Report closure feature in the waze app}}{{anchor|Closure feature in the waze map editor}}
{{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].
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.
* 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.
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].
* 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 ====
==== 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
Any closures reported from the Waze app are visible and can be manipulated in the Waze Map Editor. Waze app reported closures depend upon the rank of the editor to determine their effect on routing. RTCs from Rank 4 and below editors {{u|do not}} have an effect on routing until enough users report the same segment closed; RTC from Rank 5 and above editors go into effect immediately. Rank 4 and below app closures  are visible in WME can be edited by a Rank 3+ editor, that RTC will then take effect immediately.
* The start date will be 1969 or 1970
=====closures with a start date 1969 or 1970=====
* 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.
{{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.
 
 
{{Anchor|Closure date NOT SET}}
 
===== 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 are closures reported from the Waze App
*These may not be actively affecting routing in Live Map or the Waze app.
*They may have been submitted by any rank user,
*There may be more than one of this type of closure overlapping for the same segment and direction.
 
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.
 
 
{{clear}}{{ReturnTo | Editing manual | the editing manual}}
 
[[Category:Community Administration]]
[[Category:Waze Map Editor]]

Revision as of 12:29, 30 May 2019

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

  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.
  • End date can not be more than 183 days after the start date and no more than one year after the current date.
  • 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.
  • The longest duration closure is 183 days.
  • For a 365-day closure beginning immediately, enter a 183 day closure followed by a 182 day closure.
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.
Cross streets - which segments to close

Closing several segments of a road will prevent Waze from routing wazers down that road. But it will not prevent Waze from routing wazers across the road at the intersections. Often in work zones and for special events (parades, marathons, festivals), cross traffic should not be allowed at some or all of the junctions. 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. Waze will not route up into a closed segment to reach a destination within it, but it will route out of the "most convenient end" of a closed segment if the user starts within it. So if you need to allow wazers to reach destinations less than a block from the closed road, close the cross street segments in the direction moving away from the closed road.

  • Regular cross-streets
  • Close two-way cross-street segments on both sides of the closed intersection. Each segment should be closed in the direction traveling away from the closed junction. Closing all outbound segments routing from the intersection will prevent routing across the intersection's junction node to reach a destination or leave a starting point, regardless of the user's position in relation to that junction node.
  • If traffic at an intersection is being directed by police, then it is not necessary to apply a closure at the cross street. Waze will detect the traffic slowdown and route accordingly.
  • Close one-way cross-street segments on the side traveling away from the closed junction. Closing the "way out" from the junction prevents Waze routing wazers through the 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. This is enough to prevent cross-traffic routing from either side.

Illustrations and examples

Controlling cross traffic through a closed route link to this section
Click expand on the right side here to see Example scenarios with illustrations.
New Year's Day Parade in RTC Town
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.
Select the parade route on Main St and set a two-way closure between 13:00 and 14:00 on January 1.
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.
The completed set of closures in this example would look like those on the right. We’re all set to watch the parade!
Divided road closed for construction
Willow St will be closed for two weeks for construction. So we set a closure for the length of both carriageways.
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.
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.

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.

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

Usernames and closures

Adding a closure does not put your name as the last editor for the segment (Updated By: user (#)), however your name does appear in the segment's history. You can also see who added an active closure by looking at the alert in Live Map or the client.


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

Road closures are not subject to waiting for a tile update; they will go live almost immediately. However, they only work on 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 will not be recognized. 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 and it will save.

For this reason, if you need to remove a segment or cut a segment in two that should not currently be routed, first place a time-based segment restriction on the segment, then apply the closure. After the next tile update, the segment restrictions will be in place at least until the next tile update. You can then remove the closure and make the types of changes that will prevent applying the closure. After one more tile update, you should be able to remove the time-based segment restriction (TBSR) and reapply the closure. This should allow you (after 2 or 3 days) to limit a closure to a damaged bridge rather than being forced to apply it to a mile-long segment of road, for example.

Also, certain edits like disconnection or creation of a roundabout on existing segments affect one's ability to add closures, even though they do not change the segment ID. After disconnecting a segment from another or drawing a roundabout onto it, you will only be able to save a closure on the existing segment that ends less than 48 hours in the future. If you extend it further, WME will display the error message (!) The highlighted segment has been modified recently and will be rebuilt. You will not immediately be able to add a closure on the new roundabout segments themselves. After a tile update, this time limitation is removed, and a longer closure can be created on the existing segments that go into or out of the roundabout, or on the new roundabout segments. This is useful for maintaining closures while drawing roundabouts at existing intersections

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

Road closures can be added to multiple segments simultaneously by selecting all the affected segments first. Be careful to verify all the segments after you save that the closuress were added properly. It's been reported before when multiple 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.)

Major Traffic Event (MTE) closure sheets

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.
  2. The other way is to use the Events page to request an MTE closure sheet. Once the sheet is filled out with information in WME, Waze Closure staff members will upload the closures and (optionally) get a message out to wazers in the area.

More on closure sheets


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 closures listed above.

  • Closures that could just as easily be submitted in WME shouldn't be submitted using the sheets.
  • 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.
  • Check the sheet for required fields (closure start and end time, permalink, road name, your username, etc). guidelines are similar to guidelines for closures entered using WME
  • Once each row of the sheet has been uploaded, it will be marked as such. If any rows are not uploaded, check the sheet comments and check your email.
  • Closures will go live as soon as they are uploaded
  • It may be possible to upload a closure involving a segment ID, node ID, or node location that have moved since the last tile update; The real time closure will not become active until these segment and node changes go live.

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

  • The start date will be 1969 or 1970
  • 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.