Planowe ograniczenia w ruchu: Różnice pomiędzy wersjami Wyświetl historię

Articles containing potentially dated statements from May 2016 Articles with invalid date parameter in template All articles containing potentially dated statements
WizualnieWikikod
Nie podano opisu zmian
Nie podano opisu zmian
Linia 4: Linia 4:
{{ReturnTo | Editing manual | the editing manual}}
{{ReturnTo | Editing manual | the editing manual}}


A '''partial restriction''' is entered on a segment or a turn restriction. A partial restriction is often referred to as a '''time-based restriction''' ('''TBR'''); specifically as a '''time-based segment restriction''' ('''TBSR''')  or '''time-based turn restriction''' ('''TBTR''').  They are used to allow or to restrict certain vehicle types to be routed or prevented from routing on that segment or turn. The TBSR or TBTR means the segment or turn will tell the routing algorithm that some '''vehicle type(s)''' are forbidden or allowed on a segment or turn; or some or all vehicles are forbidden at '''certain times, or on certain days or dates''', or both; that certain special types of travel are allowed.


{{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.}}
Note currently only private car, taxi, motorcycle, and electric are allowed to be selected in the app; therefore restrictions preventing trucks or buses from a segment or turn do not have any effect in the app. Setting a segment to be a bus only segment will prevent any user from being routed and is the equivalent of a prohibited all private cars and taxi restriction.


Partial restrictions are often used for bus lanes, turns that are forbidden during rush hour, segments that change direction for morning and evening rush hour, bridges and ferries that are only available during the day, and roads that are closed in winter.


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.
If a turn is forbidden on all days, dates, and times, then use [[Turn_restriction#Turn_restrictions_.28allowed_turns.29|turn restriction]] or if the segment never allows travel in that direction then [[Set_one-way_road#Set_Road_Type.2C_Direction.2C_and_Elevation|one-way road]] instead. If no traffic will ever be allowed to travel through an intersection, it should be disconnected. If no traffic will ever be allowed to travel on a segment, the segment should not be added to the map.


In some cases, the turn (typically left-hand) may simply be difficult to make at certain times of the day due to uncontrolled intersections during heavy traffic periods. The difficult turn should not be installed where there is a traffic light or a dedicated left turn lane.


== Controlling traffic flow ==
For big road-closing events such as marathons and parades, please see [[Mega events]] For construction-related traffic closures, please see [[Real time closures]].


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.
== Overview ==
* [[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 article covers how to create scheduled restrictions and vehicle type restrictions. Collectively, these can be termed ''Partial restrictions.''


'''This is the preferred method for closing roads due to its [[#Map safety and client visibility|map safety and visibility to Wazers]].'''
Partial restrictions can be based on:
# An entire segment controlling traffic flow for one or both directions '''TBSR'''
# Specific turns from one segment to another '''TBTR'''


The editing community can be informed about these closures by:  
Each of these restrictions can be further restricted based on combinations of:
* URs/MPs submitted through the app
# Vehicle type (trucks, buses, hazardous materials, etc.)
* Knowledge of local happenings
# Time of day, day of week, and date range.
* 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
Examples:
which method is used there are additional guidance and instructions in the corresponding unique subsections below.
* No left turn 7a-9a and 4p-6p weekdays
* HOV lanes eastbound 5a-11a, westbound 3p-10p
* Flexible capacity lanes which are a single roadway, but run a different direction for morning and evening commutes (frequently found on congested freeways and some primary streets, sometimes with limited exit or turn options to create express traffic routes)
* Interstate truck-only ramp (not used in app at this time)
* No trucks allowed between 9a-3p weekends (not used in app at this time)
* Vehicle towing a trailer (not used in app at this time)


Real Time Closures can be added to Waze in four ways:
While this is a very flexible system, it can be a complex interface to manage the many combinations possible. It is certainly very important that any changes made to any current scheduled restrictions on the map be done with extreme caution so as not to destroy hours of work by prior map editors. Therefore be sure to only make changes to scheduled restrictions with careful consideration and patience.
*[[#Report a closure in the Waze client app|Report a Closure in the Waze client app]]
*[[#Major traffic events|Major Traffic Events (MTEs)]]
*[[#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.
== Segments ==


===Segment restrictions===
The segment restriction method changed in 2017. Some attributes changed location in the editor and some new ones were added.
====Selecting a segment====[[File:Add_restriction1.PNG‎|thumb|right|50px]]
#Select a segment so that the name appears to the left of the map editor.
#Select the yellow '''Add restrictions''' radio button (Time Based Segment Restrictions) on the left panel when the segment is selected.
#It will be '''Edit restrictions(#)''' if there is already a restriction(s) on the segment.[[File:Edit Restrictions1.PNG‎|thumb|right|50px]]
#First restriction pop-up window appears[[File:Restriction_first_popup.PNG‎|center|200px|border]]


=== Connected Citizens Program ===
===First pop-up window===


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]].
====Toll====
There are two ways to mark toll:
# Toll attribute in bottom left corner of the first TBSR popup window
# Toll free restriction is enabled in second TBSR popup window


=====Toll attribute check box=====
The toll attribute check box has moved to the first pop-up window of a segment restriction. It used to be under the segment's road type.
[[File:Toll_attribute_box_checked.PNG‎|center|300px|border]]
#Check the toll road attribute in the bottom left corner of the popup box[[File:New Toll2.PNG|right|150px|border]]
#Mark a road segment as a toll segment only if the segment has a toll booth, transponder reader, or other tolling device and if no vehicles travel as toll free on that segment.
#Once a segment is marked as a toll segment then the toll attribute is displayed under the road segment name.  You have to go to the TBSR to deselect the attribute.
#Designating a segment as toll will prevent setting any vehicle type as toll free.
#Designating a two way segment with the toll attribute will designate both directions as a toll road. Designating a one way segment with the toll attribute will designate that direction as a toll road.


=== Map safety and client visibility ===
=====Toll by default (toll free designation)=====
#If there are any vehicle types that are designated toll free on the segment, then any allowed vehicle that is not designated as toll free is assumed to pay a toll.[[File:Toll-free designation.PNG ‎|center|300px|border]]
#Note the toll free vehicle must also be listed in the allowed restrictions too.[[File:Allowed private vehicles.PNG ‎|center|300px|border]]


This feature is safer for the map than other methods of controlling traffic flow for a number of reasons.
If a vehicle type is not listed in the allowed section then Waze assumes it is prohibited and will not check for the vehicle’s toll free designation. In short Waze thinks the vehicle type is prohibited and it can't be routed there as a toll free vehicle since it is prohibited. In the example above only private vehicles are allowed on the road segment as a toll road. Private vehicles that the user designates as HOV-2+ will be allowed to use the road toll free. All other vehicle types are prohibited.
* 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.


If a vehicle type is designated as toll free why doesn't Waze just recognize that they are allowed? There are notes in the restriction popup windows that impart this knowledge.
#Hover over the small blue lower case i in the toll free restriction and a black box pop-up appears that says "Vehciles must also meet all of the "Allowed" restrictions".[[File:Must_be_in_allowable.PNG|center|200px|border]]
#Orange note in bottom left of '''Allowable''' restriction says "Other vehicles are restricted" (i.e. prohibited)[[File:Other_vehicles_prohibited.PNG|center|300px|border]]


=== General closure guidance ===
====Selection of direction====
[[File:Restriction_first_popup.PNG‎|right|150px|border]]
#First restriction pop-up window has three main items:
#* A > B
#* B > A
#* Two way
#Restrictions have three main '''Types'''[[File:Restriction Types.PNG|right|150px|border]]
#*'''Allowable'''
#*'''Toll free'''
#*'''Prohibited'''
#Restriction '''Types''' are added as '''Lines''' under the applicable direction(s) of travel.[[File:Restriction Lines.PNG|right|200px|border]]
#*The picture to the right has three '''Lines''' of restrictions; one each of Allowed, Toll free, and Prohibited
#Restriction '''Lines''' contain '''Rules''' which are partially displayed in the Summary; rules are fully described below
#Click the grey '''Add new''' box under the appropriate direction for the restriction to be entered
#Second restriction pop-up window appears[[File:Restriction second pop up window.PNG|center|200px|border]]


==== Illustrated slideshow ====
Note
#Each restriction '''Type''' on the first pop-up window is compared to other Types as an '''AND''' statement.
#Each restriction '''Line''' on the second pop-up window (within the restriction Type) is compared to other lines in that restriction line as an '''OR''' statement.
#Each restriction '''Rule''' within a single restriction '''Line''' is compared to other rules as an '''OR''' statement
So for the three restriction lines in this photo:[[File:Restriction Lines.PNG|right|200px|border]]
#* a) All Private vehicles are allowed as tolled vehicles
#* b) Private vehicles that are HOV-2+ are allowed as toll free vehicles
#* c) All vehicles are prohibited from 00-02
#* d) Since HOV-2+ is a subset of private vehicles, it does not have to added as a separate allowable restriction; the allowable restriction for all private vehicles includes private vehicles and HOV-2+


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.
A vehicle is allowed as toll free, if it is a) a private vehicle AND b) a private vehicle with HOV-2+ AND c) Not being routed 00-02.  
{{#widget:Iframe
A vehicle is allowed as tolled, if it is a) a private vehicle AND b) Not being routed 00-02.
|url=https://docs.google.com/presentation/d/1tBb3Cg8Ewu_rx7yuPxGMCTy4FIoAb-Z1CY33ukYFtM8/embed?start=false&loop=false&delayms=30000
All vehicles are not allowed if it is 00-02.
|border=0
|width=700
|height=415
}}


Because the restrictions only include private vehicles, any user that has selected another vehicle type, ex taxi, will not be routed on the segment. Taxis are not part of the allowed vehicles so they are assumed to be prohibited. Remember the Orange note in bottom left of Allowable restriction says "Other vehicles are restricted"? This is how that note affects routing.


==== Real time closures vs. partial restrictions ====
A user that selects avoid toll roads will not get routed here unless they signify that they are HOV-2+ (once HOV is pushed to production).  They have selected to avoid toll roads, but the road is toll free if they have HOV-2+.


Many major roads have ongoing restrictions, which are based on day of the week or time of day. Some examples include:
===Second pop-up window===
*No Left Turn between 12:00pm-6:00pm
The second pop-up window has the label of '''Add restriction''' in the top left corner.
*No passenger cars on weekdays


For these types of restrictions, please see the [[Partial restrictions|Partial Restrictions page]] on the Wiki.
====Second pop-up window attributes====
[[File:I-66E_AM_HOV.PNG‎|right|200px|border]]
The second line will display '''Driving both ways (N/E/S/W/NE/SE/SW/NW if one way)  on [name of segment] is restricted on'''. There are several attributes that can be selected for the restriction:
#Applies to
#Days
#Hours
#Applies
#Restriction '''Type'''
#Additional information text box


'''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.)''


=====Applies to=====
[[File:Driving is.PNG‎|right|200px|border]]
This section has two selections portion of the segment and type of special routing.
#Portion of segment selections are:
#* a) Entire segment
#* b)  Left lane
#* c)  Middle lane
#* d) Right lane


==== Usernames and closures ====
Select the appropriate portion of the segment. Note Waze can differentiate the speed difference between the lanes on a segment for the Bus/Express/FAST/HOT/HOV lanes that are separated by a dashed line from regular lanes. This does not work for the individual lanes on a road to tell you which lane is fastest when they are all the same type of road.


[[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.
=====Specialty road type=====
[[File:Specialty road type.PNG‎|right|200px|border]]
This attribute is used to distinguish regular (none) road segments from
#Specialty road type selections are:
#* a) None
#* b)  Bus
#* c)  Express
#* d) Fast
#* e) HOT
#* f) HOV
#'''None''' is the designation for the vast majority of roads; if a road does not have a specialty designation then it is a regular road and should have '''None''' selected.
#The other designations of '''Bus''', '''Express''', '''Fast''', '''Express''', '''HOT''', '''HOV''' are used based on the local usage. The specialty road type has to be selected to get the proper routing for that type of road. As of October 2017 there is no difference in the designations, but there will eventually be different voice prompts for the various types; therefore set the road up with a consistent usage based on what the locals call the road type. 
#For the special designations '''EVERY RESTRICTION LINE''' on the segment should have the same specialty road type designation. If you have an HOV road that has one segment in the middle that is selected as '''None''' then the algorithm will not work properly.
#When multiple segments have different orientations of A>B and B>A in one selection, they may have the restrictions saved in opposite directions. This is a bug that developers are working to fix. Till it is fixed then you should carefully check each segment to ensure the restriction is in the proper direction. For one way road segments if the restriction is in the opposite direction the light orange dotted road will not be displayed; unfortunately two way road segments or one way road segments with multiple restrictions do not have a simple way to see that a restriction is in the reverse orientation.


=====Days (of week)=====
[[File:Days selection.PNG‎|right|300px|border]]Select the applicable days of the week that the restriction will be active. Use the '''Select all''' or '''Select none''' link to more quickly change all the check boxes. The default is all days of the week. Your display order for the days will depend upon your country settings in your browser and may not exactly match the image above. '''Mon-Fri''' and '''Every day''' are the most common restriction groupings in USA.


==== Junctions and cross traffic ====
=====Hours (of day)=====
[[File:Clock entry.PNG|right|300px|border]]Select the applicable hours of the day that the restriction will be active. For restrictions that apply all day long, use the default setting of '''All day'''. If the restriction is for only certain periods of time during the day, then deselect the '''All day''' radio button to allow the time to be changed. You can click the hours or minutes fields to enter times directly, or click the clock icon next to the time to enable input panels. The schedule uses a 24-hour notation. The restriction will start at the beginning of the minute designated in the start block. The restriction will go till the 59th second of the minute designated; so if you state an end time of 08:00 it goes till 08:00:59. So if a posted restriction ends at 08:00 it is advisable to end the waze restriction at 07:59; this will have the 08:00 time enacted vice carrying the restriction over for an additional minute. If the end time is selected after 23:59 then the restriction will carry over till the next day.


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.
{{:24-hour format}}


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.
For example, a schedule of 10:00 AM to 3:00 PM is entered as 10:00 to 15:00; a schedule of midnight to noon (12:00 AM to 12:00 PM) is entered as 0:00 to 12:00. A schedule of 3:00 PM to 5:00 AM is entered as 15:00 to 05:00.
:* 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|
The time that should be entered is the local time of the road as on the local signs. The Waze server knows the local time zone and will schedule the restriction correctly.
====== 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 ====
Daylight savings time is automatically accounted for as long as the Waze client app is properly set to the correct local time.


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.
======Entering midnight======


'''DO NOT use Real-Time Closures for roads which only have some lanes closed.'''
If a scheduled restriction is between 8:00 PM and Midnight, then enter "20:00 - 23:59". Technically if you enter "20:00 - 00:00" it will go to 00:00:59 but is more or less an equivalent result.


======Crossing midnight======


=== Web based closure guidance ===
If a restriction occurs only during nighttime hours and opens in the morning, e.g., restricted between 10 PM and 5 AM, then enter the From time as 22:00 and the To time as 05:00. You will notice an information box that says the restriction will end of the following day. If this restriction is only on a certain day of the week, e.g., Saturday night and Sunday night, then select the day of the week for Sat and Sun matching the ''start'' of the restriction. There is no need to include Monday because it is automatically covered. Including the Monday check box would add a third day starting at 10 PM Monday.


==== Dates and times ====
=====Applies (to dates)=====
[[File:Date selection.PNG‎|right|300px|border]]The default setting is '''Every week''' meaning there is no limit to the date range so as soon as you add the restriction it will be active every week until it is removed. Optionally you can select the radio button for '''Range''' of dates to limit the restriction to a certain number of days. Press the button displaying the date to display two calendars. The one one the left shows the start date and the calendar on the right shows the end date of the restriction. Note these date are inclusive meaning the restriction will include both dates (and all the ones in between) when determining the restriction. When you have selected the date range press the green '''Apply''' button. The date range is displayed in '''DD/MM/YYYY''' format. To remove the date range, simply select the '''Every week''' radio button again.


'''All Real-Time Closures are set using the [http://wikipedia.org/wiki/ISO_8601 ISO-8601 ''"extended format"''].'''
Remember that the end date will consider the entire day based on any time settings also configured. If the time crosses midnight, the next day will automatically be included for that time period and so that the restriction ends at the appropriate time.


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.)''
=====Restriction types (Allowed/Toll free/Prohibited)=====
This is where the three main '''Types''' of restrictions are selected that appear on the first pop-up window.[[File:Restriction Types.PNG|right|150px|border]]
#The three Restriction '''Types''' are:
#*'''Allowable'''
#*'''Toll free'''
#*'''Prohibited'''
#Restriction '''Types''' are added as '''Lines''' under the applicable direction(s) of travel.[[File:Restriction Lines.PNG|right|200px|border]]
#Restriction '''Lines''' contain '''Rules''' which are constructed here on the second pop-up window
#Allowable restrictions have green backgrounds
#Toll free restrictions have blue backgrounds
#Prohibited restrictions have red backgrounds
#Restriction '''Rules''' combine the type of vehicle, number of passengers required, and toll transponder/pass required
#Remember
#* a) Each restriction '''Type''' on the first pop-up window is compared to other Types as an '''AND''' statement.
#* b) Each restriction '''Line''' on the second pop-up window (within the restriction Type) is compared to other lines in that restriction line as an '''OR''' statement.
#* c) Each restriction '''Rule''' within a single restriction '''Line''' is compared to other rules as an '''OR''' statement
#Will use a toll free restriction to go over the various '''Rule''' types
# Select '''toll free''' if there are vehicles that can travel without paying a toll '''and''' there are some vehicles that have to pay a toll. If no vehicle type has to pay a toll then it is assumed that all vehicles are toll free and do not select toll free.
#Note that the restriction's background color should change to blue[[File:Driving_is_allowed_for_toll_free.PNG|center|500px|border]]
#There are three categories to choose from for making a '''Rule'''
#* a) '''Vehicle type'''
#* b) '''Minimum passengers'''
#* c) '''Requires a pass'''
#The categories can be selected in any order
#Select the applicable '''Vehicle type''' by clicking on the '''+'''[[File:Toll free plus drop down.PNG|center|500px|border]]
#'''Private car''' is added to the restriction '''Line'''[[File:Toll free plus drop down.PNG|center|500px|border]]
#The vehicle type can be changed by clicking on '''Private car''' bubble[[File:HOV vehicle type drop down.PNG|center|250px|border]]
#Only one vehicle type can be selected per Restriction '''Rule'''
#If no vehicle type is selected then Waze defaults to have the restriction applicable to all vehicles
#If there is more than one vehicle type that needs a restriction then clilck '''Add a new rule''' and then the '''+''' and '''Vehicle type''' till all applicable vehicles are added as a separate '''Rule''' in the one Restriction '''Line'''[[File:Three HOV rules.PNG|center|500px|border]]
#Select '''Minimum passengers''' by clicking the '''+''' on the blue add restriction banner and a drop down menu will appear[[File:Toll_Free_initial_drop_down.PNG|center|500px|border]]
#'''At least 2 passengers''' is added[[File:Toll_Free_Min_Pass_initial.PNG|center|500px|border]]
#Select number of passengers required by clicking the '''At least 2 passengers''' and a drop down menu will appear with selections for '''At least 3 (4) passengers'''[[File:HOV min passenger drop down.PNG|center|500px|border]]
#If no minimum passenger restriction is selected then Waze defaults to have the restriction applicable to vehicles with any number of occupants
# Click the '''+''' again while remaining on the same restriction as the number of passengers to  select '''Requires a pass'''
# '''Alabama Freedom Pass''' is added to the restriction line[[File:HOV Ala Pass.PNG|center|500px|border]]
# Click the '''Alabama Freedom Pass''' area and a drop down menu will appear with available companies[[File:Toll free Transponder Pass.PNG|center|200px|border]]
# Select the applicable transponder/pass
#If no transponder/pass is selected then Waze defaults to have the restriction applicable to all vehicles even if no transponder/pass is selected in the Navigation settings
# Click '''Add''' button in bottom right corner of the second pop-up window
# Click '''Apply''' button in bottom right corner of the first pop-up window
# Click '''Save''' icon on the grey Waze bar
#Remember for '''Toll free''' restrictions, the vehicles listed as toll free much be covered by the '''Allowable''' restrictions to have proper routing.
#'''Allowable''' restrictions are set up similarly to '''Toll free''' restrictions; '''Allowable''' restrictions will have a green background[[File:Driving_is_allowed_for.PNG|center|500px|border]]
#'''Prohibited''' restrictions can only select the '''Vehicle type'''[[File:Prohibited restriction.PNG|center|500px|border]]
#'''Prohibited''' restrictions have a red background
#'''Prohibited''' restrictions default to '''All vehicles'''
#Select '''Only''' to be able to pick what vehicle type(s) will be prohibited
#Note '''DO NOT''' select conflicting restrictions. For example selecting a segment as a toll road with an allowable restriction line of any vehicle with Sunpass and a prohibited restriction line for any taxi will not preform properly since there is no prioritization of restrictions. A user that has designated the vehicle is a taxi with Sunpass will meet both the allowable restriction and the prohibited restriction. Until the programming has prioritization this restriction should be written as a toll road with an allowable restriction line of any private car with Sunpass. Since the taxi is not an allowable restriction then all taxis will not be routed on the toll road. This means it does not matter whether the taxi has designated Sunpass is in the vehicle or not.


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.)''
====Understanding Restriction '''Line''' and '''Rule''' affects====
#If there is more than one vehicle type that needs a restriction then clilck '''Add a new rule''' and then the '''+''' and '''Vehicle type''' till all applicable vehicles are added as a separate '''Rule''' in the one Restriction '''Line'''[[File:Three HOV rules.PNG|center|500px|border]]
#In the above picture the '''Rules''' are treated as '''OR''' statements; therefore read this restriction as to be toll free on this segment you must be either "Private car" OR "Taxi" OR "Motorcycle". So any of the three vehicle types will meet the restriction. The first pop-up window looks like this:[[File:Three_HOV_rules_summary.PNG|center|500px|border]]
#If you made three separate Restriction '''Lines''' with each having one '''Rule''' for "Private car"/"Taxi"/"Motorcycle], #*then you will have three separate HOV Restriction '''Lines'''. Below is a picture of one Restriction '''Line'''[[File:‎Single HOV restriction vehicle type.PNG|center|500px|border]]
#In the above situation the '''Lines''' are treated as '''AND''' statements;  therfore read these restrictions as to be toll free on this segment you must be "Private car" AND "Taxi" AND "Motorcycle". The user must be '''ALL THREE VEHICLE TYPES''' simultaneously; since only one vehicle type can be selected at a time it is impossible to ever meet this criteria.The first pop-up window looks like this:[[File:Improper HOV Restriction Lines.PNG‎|center|500px|border]]
#Please take a second and look at the last two examples to see how the '''OR''' and '''AND''' statements are aligned for '''Rules''' and '''Lines''' respectively.


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).
====Multiple segments====
Multiple segments can be selected at once for batch editing of restrictions. Selecting multiple segments is done by clicking the segments while holding the Ctrl button (or Cmd on Mac computers).  


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.
A few things to note when editing multiple segments:
* Note the directionality of the segments - two neighboring segments can be with different A->B directionality. In one of them the A->B direction can be eastbound and in the other it can be westbound at the same time.
* When multiple segments are selected with different restrictions set on them, they will appear in a different section of the panel under the title: 'These restrictions only apply to some of the segments selected:' Click the ‘Apply to all’ link to the right of the restriction line to propagate the restriction to all the selected segments.
* There is a bug that the developers are working on where when several segments are selected that have a mix of A>B and B>A segments then one way restrictions may not be entered properly. This occurs on both one way and two way segments. So be very careful that they are saved properly. For one way segments, if the restriction is entered in the opposite direction of the road then the restriction coloration will not show on the segment. It will be saved in the reverse direction and can be removed and then properly entered. This occurs when copying restrictions to multiple segments or when entering new restrictions.


== Turns ==


===== Start and end time settings =====
Time Based Turn Restrictions (TBTRs) are used when only certain turns are partially restricted from one segment to another. If the turn is always restricted then use a red turn restriction; TBTR are not to be set to 24/7.


{{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 turning traffic restricted at all times ===


*Real-time Closures are active for the full minute they are set for.
Turns that are restricted to all traffic (all vehicle types) are set with '''turn arrows'''—the arrows that appear at the end of a selected segment. A restricted turn is indicated by a red arrow with a red ''do not'' sign next to it (lower left arrow in picture below). A turn that is open (not restricted) '''to all traffic''' is indicated by a green arrow. A TBTR is indicated by the yellow arrow with a yellow "do not" sign next to it (upper right arrow in picture below)[[Global/Map_Editing_Quick-start_Guide#Junction_arrows|Turns]]
** 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.


[[Image:Lotsa turns.jpg]]


===== Time zone =====


All times entered are in the '''local time zone of the segment being closed'''. If you are in one time zone, and are submitting a closure for a segment in another time zone, use the start and end times in the time zone where the segment is located.
=== Scheduled turn restrictions ===


When not all times, days, dates, or vehicles are restricted from turning, you can set a scheduled turn restriction from one segment to another. Turns that are restricted to all traffic during certain times of the day are "time based turn restrictions".


===== Setting long-term closures =====
[[File:DC TBTR example.PNG|center|150px|border]]


{{red|'''NOTE:'''}} Temporary Closures must not be longer than 6 calendar months (183 days to be precise).
[[File:TBTR hover3.PNG‎|right|150px|border]]
To enter a TBTR:
# Select one segment
# Hover over a '''GREEN''' or '''Yellow''' turn restriction arrow
# Two icons appear
#* a) A clock for a TBTR
#* b) A speaker for a [[Turn_instruction_override|Turn override instruction]]
# Click the clock icon and the first TBTR popup window appears
[[File:TBTR first pop up window.PNG|center|300px|border]]
# Note the Difficult turn (DT) attribute box in the lower left corner; the  [[Partial_restrictions#Difficult_turn|Difficult Turn]] is described below
# Click on the '''Add new''' radio button under the description of the turn, the second popup window appears
[[File:TBTR second pop up window.PNG|center|150px|border]]


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.
# 2014-12-01 - 2015-05-31 (182 days)
# 2015-06-01 - 2015-11-30 (183 days)


====Second pop-up window attributes====
[[File:I-66E_AM_HOV.PNG‎|right|200px|border]]
The second line will display '''Turning from [original segment] to [destination segment] is restricted on'''. There are several attributes that can be selected for the restriction:
#Days
#Hours
#Applies
#Restriction '''Type'''
#Additional information text box


====== Maximum closure duration ======
=====Days (of week)=====
[[File:Days selection.PNG‎|right|300px|border]]Select the applicable days of the week that the restriction will be active. Use the '''Select all''' or '''Select none''' link to more quickly change all the check boxes. The default is all days of the week. Your display order for the days will depend upon your country settings in your browser and may not exactly match the image above. '''Mon-Fri''' and '''Every day''' are the most common restriction groupings in USA.


The maximum length for a Real-Time Closure is one year.
=====Hours (of day)=====
[[File:Clock entry.PNG|right|300px|border]]Select the applicable hours of the day that the restriction will be active. For restrictions that apply all day long, use the default setting of '''All day'''. If the restriction is for only certain periods of time during the day, then deselect the '''All day''' radio button to allow the time to be changed. You can click the hours or minutes fields to enter times directly, or click the clock icon next to the time to enable input panels. The schedule uses a 24-hour notation. The restriction will start at the beginning of the minute designated in the start block. The restriction will go till the 59th second of the minute designated; so if you state an end time of 08:00 it goes till 08:00:59. So if a posted restriction ends at 08:00 it is advisable to end the waze restriction at 07:59; this will have the 08:00 time enacted vice carrying the restriction over for an additional minute. If the end time is selected after 23:59 then the restriction will carry over till the next day.


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}}'''"
{{:24-hour format}}


{{anchor|Report closure feature in the waze app}}
For example, a schedule of 10:00 AM to 3:00 PM is entered as 10:00 to 15:00; a schedule of midnight to noon (12:00 AM to 12:00 PM) is entered as 0:00 to 12:00. A schedule of 3:00 PM to 5:00 AM is entered as 15:00 to 05:00.


=== Report closure feature in the Waze app ===
The time that should be entered is the local time of the road as on the local signs. The Waze server knows the local time zone and will schedule the restriction correctly.
----


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.
Daylight savings time is automatically accounted for as long as the Waze client app is properly set to the correct local time.  


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].
======Entering midnight======


==== App reported closures in WME ====
If a scheduled restriction is between 8:00 PM and Midnight, then enter "20:00 - 23:59". Technically if you enter "20:00 - 00:00" it will go to 00:00:59 but is more or less an equivalent result.


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 affect 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. ''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]].''
======Crossing midnight======


{{anchor|Major_traffic_events}}
If a restriction occurs only during nighttime hours and opens in the morning, e.g., restricted between 10 PM and 5 AM, then enter the From time as 22:00 and the To time as 05:00. You will notice an information box that says the restriction will end of the following day. If this restriction is only on a certain day of the week, e.g., Saturday night and Sunday night, then select the day of the week for Sat and Sun matching the ''start'' of the restriction. There is no need to include Monday because it is automatically covered. Including the Monday check box would add a third day starting at 10 PM Monday.


=== Major Traffic Events (MTEs) ===
=====Applies (to dates)=====
----
[[File:Date selection.PNG‎|right|300px|border]]The default setting is '''Every week''' meaning there is no limit to the date range so as soon as you add the restriction it will be active every week until it is removed. Optionally you can select the radio button for '''Range''' of dates to limit the restriction to a certain number of days. Press the button displaying the date to display two calendars. The one one the left shows the start date and the calendar on the right shows the end date of the restriction. Note these date are inclusive meaning the restriction will include both dates (and all the ones in between) when determining the restriction. When you have selected the date range press the green '''Apply''' button. The date range is displayed in '''DD/MM/YYYY''' format. To remove the date range, simply select the '''Every week''' radio button again.


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.  
Remember that the end date will consider the entire day based on any time settings also configured. If the time crosses midnight, the next day will automatically be included for that time period and so that the restriction ends at the appropriate time.


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.
=====Restriction types (Allowed/Prohibited)=====
This is where the two main '''Types''' of restrictions are selected that appear on the first pop-up window. Since only Allowable and Prohibited are used, Toll free is not selectable.[[File:Restriction Types.PNG|right|150px|border]]
#The three Restriction '''Types''' displayed are:
#*'''Allowable'''
#*'''Toll free''' (not selectable)
#*'''Prohibited'''
#Restriction '''Types''' are added as '''Lines''' under the applicable direction of turning.[[File:TBTR lines.PNG|right|200px|border]]
#Restriction '''Lines''' contain '''Rules''' which are constructed here on the second pop-up window
#Allowable restrictions have green backgrounds
#Prohibited restrictions have red backgrounds
#Restriction '''Rules''' combine the vehicle type allowed and/or prohibited
#Allowable and Prohibited rules have different ways of selecting vehicle types; most editors will use one or the other restriction type but not both.
#Remember
#* a) Each restriction '''Type''' on the first pop-up window is compared to other Types as an '''AND''' statement.
#* b) Each restriction '''Rule''' on the second pop-up window (within the '''Allowable''' restriction Type) is compared to other vehicle type(s) in that restriction line as an '''OR''' statement.
#Note that the restriction's background color should change to red for prohibited and green for allowed
#Select the applicable Allowed '''Vehicle type''' by clicking on the '''+'''[[File:TBTR allowable drop down.PNG|center|500px|border]]
#'''Private car''' is added to the restriction '''Line'''[[File:TBTR allowable private car.PNG|center|500px|border]]
#The vehicle type can be changed by clicking on '''Private car''' bubble[[File:TBTR allowable private car drop down.PNG|center|250px|border]]
#Only one vehicle type can be selected per Restriction '''Rule'''
#If no vehicle type is selected then Waze defaults to have the restriction applicable to all vehicles
#If there is more than one vehicle type that needs a restriction then clilck '''Add a new rule''' and then the '''+''' and '''Vehicle type''' till all applicable vehicles are added as a separate '''Rule''' in the one Restriction '''Line'''[[File:TBTR allowable two veh types.PNG|center|500px|border]]
# Click '''Add''' button in bottom right corner of the second pop-up window
# For '''Prohibited''' restrictions you get to enter one '''Rule''' and mark all the prohibited vehicle types at the same time in the same rule.[[File:TBTR prohibited.PNG|center|500px|border]]
#'''Prohibited''' restrictions default to '''All vehicles'''
#Select '''Only''' to be able to pick what vehicle type(s) will be prohibited
#Note '''DO NOT''' select conflicting restrictions. There is no prioritization of the restrictions which is why it is advisable to only use Allowed '''OR''' Prohibited TBTRs but not both together on the same turn.
# Click '''Add''' button in bottom right corner of the second pop-up window
# Click '''Apply''' button in bottom right corner of the first pop-up window
# Click '''Save''' icon on the grey Waze bar


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]. 
=== Difficult turn ===
Helpful information to have for submissions are as follows:
Note the Difficult turn (DT) attribute box in the lower left corner of the first TBTR popup window
*Name of Event
[[File:TBTR first pop up window.PNG|center|150px|border]]
*Website for event
This setting tells the routing server to add a [[routing penalty]] to the turn, meaning when calculating the time to reach the destination, this turn will include extra time so that other routes are more likely to be selected if this turn is only marginally better than another nearby route.
*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.
A turn can be considered difficult for many reasons including but not limited to the following:<br />
:'''Heavy traffic'''
:* Turn left across traffic that may be continuously flowing or fully stopped and into traffic that may also be continuously flowing or stopped.
:* Turn right into traffic that may be continuously flowing or fully stopped.
:'''Poor visibility'''
:* Turn (left or right) into quickly moving traffic with poor visibility from:
::* a crest in the road
::* a sharp corner
::* an obstacle


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.
A turn can be identified as difficult by ''''multiple'''' drivers submitting [[URs]] or by the direct knowledge of the editor.


 
Do not put a DT in for the following situations:
==== Support for Major Traffic Events ====
#If the poor visibility turn is the only valid way into the segment (The DT will not affect routing and should be omitted)
 
#A left/right turn at a traffic light
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. 
#A left/right turn where there are stop signs at all paths of travel
 
#A left turn where there is a dedicated left turn lane even if left turn lane is not an at-grade connector (AGC) (car is protected and if time to turn is long algorithm will pick up)
Once the closure sheet is fully completed, the closure will be live in the app. 
{{mbox|type=caution|text={{As of|May 2016}}, the difficult turn box is a 24 hour every day setting and not related to any other time-based restriction. That may be something available in the future but not at this time.}}
 
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.
 
 
{{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 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:
* 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 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 ====
 
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.
 
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.
 
 
{{clear}}{{ReturnTo | Editing manual | the editing manual}}
 
[[Category:Community Administration]]
[[Category:Waze Map Editor]]

Wersja z 09:29, 5 lut 2018

Home HomeAplikacja AplikacjaEdytowanie EdytowanieSpołeczność SpołecznośćPomoc Pomoc

Szybka Nawigacja do...

Edytowanie
Poradnik edytowania Updated Editing Guidelines ● Edycja Map - szybki start
Edytor Map Waze Zastrzeżone funkcje edytora map ● Ochrona mapy ● Interfejs i kontrolki Edytora Map
Drogi Kategorie dróg w Polsce ● Tworzenie i edycja segmentów dróg
Ograniczenia prędkości Przewodnik po ograniczeniach prędkości ●
Nazewnictwo Wzorce nazywania dróg ● Nazywanie ulic ● Tabela skrótów ● Miejscowości o takich samych nazwach
Pierwsze kroki w edytowaniu Najlepsze Praktyki ● Editing Basics ● Editing Bridges and Tunnels
Połączenia Skrzyżowania ● Ronda ● Niepotwierdzone i potwierdzone skręty
Problemy i Błędy Zgłoszenia użytkowników (UR) ● Problemy mapy (MP)
Wszystko o Miejscach Przewodnik po miejscach ● Standaryzacja nazw ● Zgłoszenia aktualizacji miejsc (PUR) ● Miejsca wjazdu/wyjazdu
Ograniczenia i blokady Planowe ograniczenia w ruchu ● Zamknięcia w czasie rzeczywistym
Routing i Nawigacja Oblicznie trasy ● Navigation Instructions
Wydarzenia MapRaid ● WoW


Szablon:ReturnTo

A partial restriction is entered on a segment or a turn restriction. A partial restriction is often referred to as a time-based restriction (TBR); specifically as a time-based segment restriction (TBSR) or time-based turn restriction (TBTR). They are used to allow or to restrict certain vehicle types to be routed or prevented from routing on that segment or turn. The TBSR or TBTR means the segment or turn will tell the routing algorithm that some vehicle type(s) are forbidden or allowed on a segment or turn; or some or all vehicles are forbidden at certain times, or on certain days or dates, or both; that certain special types of travel are allowed.

Note currently only private car, taxi, motorcycle, and electric are allowed to be selected in the app; therefore restrictions preventing trucks or buses from a segment or turn do not have any effect in the app. Setting a segment to be a bus only segment will prevent any user from being routed and is the equivalent of a prohibited all private cars and taxi restriction.

Partial restrictions are often used for bus lanes, turns that are forbidden during rush hour, segments that change direction for morning and evening rush hour, bridges and ferries that are only available during the day, and roads that are closed in winter.

If a turn is forbidden on all days, dates, and times, then use turn restriction or if the segment never allows travel in that direction then one-way road instead. If no traffic will ever be allowed to travel through an intersection, it should be disconnected. If no traffic will ever be allowed to travel on a segment, the segment should not be added to the map.

In some cases, the turn (typically left-hand) may simply be difficult to make at certain times of the day due to uncontrolled intersections during heavy traffic periods. The difficult turn should not be installed where there is a traffic light or a dedicated left turn lane.

For big road-closing events such as marathons and parades, please see Mega events For construction-related traffic closures, please see Real time closures.

Overview

This article covers how to create scheduled restrictions and vehicle type restrictions. Collectively, these can be termed Partial restrictions.

Partial restrictions can be based on:

  1. An entire segment controlling traffic flow for one or both directions TBSR
  2. Specific turns from one segment to another TBTR

Each of these restrictions can be further restricted based on combinations of:

  1. Vehicle type (trucks, buses, hazardous materials, etc.)
  2. Time of day, day of week, and date range.

Examples:

  • No left turn 7a-9a and 4p-6p weekdays
  • HOV lanes eastbound 5a-11a, westbound 3p-10p
  • Flexible capacity lanes which are a single roadway, but run a different direction for morning and evening commutes (frequently found on congested freeways and some primary streets, sometimes with limited exit or turn options to create express traffic routes)
  • Interstate truck-only ramp (not used in app at this time)
  • No trucks allowed between 9a-3p weekends (not used in app at this time)
  • Vehicle towing a trailer (not used in app at this time)

While this is a very flexible system, it can be a complex interface to manage the many combinations possible. It is certainly very important that any changes made to any current scheduled restrictions on the map be done with extreme caution so as not to destroy hours of work by prior map editors. Therefore be sure to only make changes to scheduled restrictions with careful consideration and patience.

Segments

Segment restrictions

The segment restriction method changed in 2017. Some attributes changed location in the editor and some new ones were added.

====Selecting a segment====
  1. Select a segment so that the name appears to the left of the map editor.
  2. Select the yellow Add restrictions radio button (Time Based Segment Restrictions) on the left panel when the segment is selected.
  3. It will be Edit restrictions(#) if there is already a restriction(s) on the segment.
  4. First restriction pop-up window appears

First pop-up window

Toll

There are two ways to mark toll:

  1. Toll attribute in bottom left corner of the first TBSR popup window
  2. Toll free restriction is enabled in second TBSR popup window
Toll attribute check box

The toll attribute check box has moved to the first pop-up window of a segment restriction. It used to be under the segment's road type.

  1. Check the toll road attribute in the bottom left corner of the popup box
  2. Mark a road segment as a toll segment only if the segment has a toll booth, transponder reader, or other tolling device and if no vehicles travel as toll free on that segment.
  3. Once a segment is marked as a toll segment then the toll attribute is displayed under the road segment name. You have to go to the TBSR to deselect the attribute.
  4. Designating a segment as toll will prevent setting any vehicle type as toll free.
  5. Designating a two way segment with the toll attribute will designate both directions as a toll road. Designating a one way segment with the toll attribute will designate that direction as a toll road.
Toll by default (toll free designation)
  1. If there are any vehicle types that are designated toll free on the segment, then any allowed vehicle that is not designated as toll free is assumed to pay a toll.
  2. Note the toll free vehicle must also be listed in the allowed restrictions too.

If a vehicle type is not listed in the allowed section then Waze assumes it is prohibited and will not check for the vehicle’s toll free designation. In short Waze thinks the vehicle type is prohibited and it can't be routed there as a toll free vehicle since it is prohibited. In the example above only private vehicles are allowed on the road segment as a toll road. Private vehicles that the user designates as HOV-2+ will be allowed to use the road toll free. All other vehicle types are prohibited.

If a vehicle type is designated as toll free why doesn't Waze just recognize that they are allowed? There are notes in the restriction popup windows that impart this knowledge.

  1. Hover over the small blue lower case i in the toll free restriction and a black box pop-up appears that says "Vehciles must also meet all of the "Allowed" restrictions".
  2. Orange note in bottom left of Allowable restriction says "Other vehicles are restricted" (i.e. prohibited)

Selection of direction

  1. First restriction pop-up window has three main items:
    • A > B
    • B > A
    • Two way
  2. Restrictions have three main Types
    • Allowable
    • Toll free
    • Prohibited
  3. Restriction Types are added as Lines under the applicable direction(s) of travel.
    • The picture to the right has three Lines of restrictions; one each of Allowed, Toll free, and Prohibited
  4. Restriction Lines contain Rules which are partially displayed in the Summary; rules are fully described below
  5. Click the grey Add new box under the appropriate direction for the restriction to be entered
  6. Second restriction pop-up window appears

Note

  1. Each restriction Type on the first pop-up window is compared to other Types as an AND statement.
  2. Each restriction Line on the second pop-up window (within the restriction Type) is compared to other lines in that restriction line as an OR statement.
  3. Each restriction Rule within a single restriction Line is compared to other rules as an OR statement
So for the three restriction lines in this photo:
    • a) All Private vehicles are allowed as tolled vehicles
    • b) Private vehicles that are HOV-2+ are allowed as toll free vehicles
    • c) All vehicles are prohibited from 00-02
    • d) Since HOV-2+ is a subset of private vehicles, it does not have to added as a separate allowable restriction; the allowable restriction for all private vehicles includes private vehicles and HOV-2+

A vehicle is allowed as toll free, if it is a) a private vehicle AND b) a private vehicle with HOV-2+ AND c) Not being routed 00-02. A vehicle is allowed as tolled, if it is a) a private vehicle AND b) Not being routed 00-02. All vehicles are not allowed if it is 00-02.

Because the restrictions only include private vehicles, any user that has selected another vehicle type, ex taxi, will not be routed on the segment. Taxis are not part of the allowed vehicles so they are assumed to be prohibited. Remember the Orange note in bottom left of Allowable restriction says "Other vehicles are restricted"? This is how that note affects routing.

A user that selects avoid toll roads will not get routed here unless they signify that they are HOV-2+ (once HOV is pushed to production). They have selected to avoid toll roads, but the road is toll free if they have HOV-2+.

Second pop-up window

The second pop-up window has the label of Add restriction in the top left corner.

Second pop-up window attributes

The second line will display Driving both ways (N/E/S/W/NE/SE/SW/NW if one way) on [name of segment] is restricted on. There are several attributes that can be selected for the restriction:

  1. Applies to
  2. Days
  3. Hours
  4. Applies
  5. Restriction Type
  6. Additional information text box


Applies to

This section has two selections portion of the segment and type of special routing.

  1. Portion of segment selections are:
    • a) Entire segment
    • b) Left lane
    • c) Middle lane
    • d) Right lane

Select the appropriate portion of the segment. Note Waze can differentiate the speed difference between the lanes on a segment for the Bus/Express/FAST/HOT/HOV lanes that are separated by a dashed line from regular lanes. This does not work for the individual lanes on a road to tell you which lane is fastest when they are all the same type of road.

Specialty road type

This attribute is used to distinguish regular (none) road segments from

  1. Specialty road type selections are:
    • a) None
    • b) Bus
    • c) Express
    • d) Fast
    • e) HOT
    • f) HOV
  2. None is the designation for the vast majority of roads; if a road does not have a specialty designation then it is a regular road and should have None selected.
  3. The other designations of Bus, Express, Fast, Express, HOT, HOV are used based on the local usage. The specialty road type has to be selected to get the proper routing for that type of road. As of October 2017 there is no difference in the designations, but there will eventually be different voice prompts for the various types; therefore set the road up with a consistent usage based on what the locals call the road type.
  4. For the special designations EVERY RESTRICTION LINE on the segment should have the same specialty road type designation. If you have an HOV road that has one segment in the middle that is selected as None then the algorithm will not work properly.
  5. When multiple segments have different orientations of A>B and B>A in one selection, they may have the restrictions saved in opposite directions. This is a bug that developers are working to fix. Till it is fixed then you should carefully check each segment to ensure the restriction is in the proper direction. For one way road segments if the restriction is in the opposite direction the light orange dotted road will not be displayed; unfortunately two way road segments or one way road segments with multiple restrictions do not have a simple way to see that a restriction is in the reverse orientation.
Days (of week)
Select the applicable days of the week that the restriction will be active. Use the Select all or Select none link to more quickly change all the check boxes. The default is all days of the week. Your display order for the days will depend upon your country settings in your browser and may not exactly match the image above. Mon-Fri and Every day are the most common restriction groupings in USA.
Hours (of day)
Select the applicable hours of the day that the restriction will be active. For restrictions that apply all day long, use the default setting of All day. If the restriction is for only certain periods of time during the day, then deselect the All day radio button to allow the time to be changed. You can click the hours or minutes fields to enter times directly, or click the clock icon next to the time to enable input panels. The schedule uses a 24-hour notation. The restriction will start at the beginning of the minute designated in the start block. The restriction will go till the 59th second of the minute designated; so if you state an end time of 08:00 it goes till 08:00:59. So if a posted restriction ends at 08:00 it is advisable to end the waze restriction at 07:59; this will have the 08:00 time enacted vice carrying the restriction over for an additional minute. If the end time is selected after 23:59 then the restriction will carry over till the next day.

24-hour format

For example, a schedule of 10:00 AM to 3:00 PM is entered as 10:00 to 15:00; a schedule of midnight to noon (12:00 AM to 12:00 PM) is entered as 0:00 to 12:00. A schedule of 3:00 PM to 5:00 AM is entered as 15:00 to 05:00.

The time that should be entered is the local time of the road as on the local signs. The Waze server knows the local time zone and will schedule the restriction correctly.

Daylight savings time is automatically accounted for as long as the Waze client app is properly set to the correct local time.

Entering midnight

If a scheduled restriction is between 8:00 PM and Midnight, then enter "20:00 - 23:59". Technically if you enter "20:00 - 00:00" it will go to 00:00:59 but is more or less an equivalent result.

Crossing midnight

If a restriction occurs only during nighttime hours and opens in the morning, e.g., restricted between 10 PM and 5 AM, then enter the From time as 22:00 and the To time as 05:00. You will notice an information box that says the restriction will end of the following day. If this restriction is only on a certain day of the week, e.g., Saturday night and Sunday night, then select the day of the week for Sat and Sun matching the start of the restriction. There is no need to include Monday because it is automatically covered. Including the Monday check box would add a third day starting at 10 PM Monday.

Applies (to dates)
The default setting is Every week meaning there is no limit to the date range so as soon as you add the restriction it will be active every week until it is removed. Optionally you can select the radio button for Range of dates to limit the restriction to a certain number of days. Press the button displaying the date to display two calendars. The one one the left shows the start date and the calendar on the right shows the end date of the restriction. Note these date are inclusive meaning the restriction will include both dates (and all the ones in between) when determining the restriction. When you have selected the date range press the green Apply button. The date range is displayed in DD/MM/YYYY format. To remove the date range, simply select the Every week radio button again.

Remember that the end date will consider the entire day based on any time settings also configured. If the time crosses midnight, the next day will automatically be included for that time period and so that the restriction ends at the appropriate time.

Restriction types (Allowed/Toll free/Prohibited)
This is where the three main Types of restrictions are selected that appear on the first pop-up window.
  1. The three Restriction Types are:
    • Allowable
    • Toll free
    • Prohibited
  2. Restriction Types are added as Lines under the applicable direction(s) of travel.
  3. Restriction Lines contain Rules which are constructed here on the second pop-up window
  4. Allowable restrictions have green backgrounds
  5. Toll free restrictions have blue backgrounds
  6. Prohibited restrictions have red backgrounds
  7. Restriction Rules combine the type of vehicle, number of passengers required, and toll transponder/pass required
  8. Remember
    • a) Each restriction Type on the first pop-up window is compared to other Types as an AND statement.
    • b) Each restriction Line on the second pop-up window (within the restriction Type) is compared to other lines in that restriction line as an OR statement.
    • c) Each restriction Rule within a single restriction Line is compared to other rules as an OR statement
  9. Will use a toll free restriction to go over the various Rule types
  10. Select toll free if there are vehicles that can travel without paying a toll and there are some vehicles that have to pay a toll. If no vehicle type has to pay a toll then it is assumed that all vehicles are toll free and do not select toll free.
  11. Note that the restriction's background color should change to blue
  12. There are three categories to choose from for making a Rule
    • a) Vehicle type
    • b) Minimum passengers
    • c) Requires a pass
  13. The categories can be selected in any order
  14. Select the applicable Vehicle type by clicking on the +
  15. Private car is added to the restriction Line
  16. The vehicle type can be changed by clicking on Private car bubble
  17. Only one vehicle type can be selected per Restriction Rule
  18. If no vehicle type is selected then Waze defaults to have the restriction applicable to all vehicles
  19. If there is more than one vehicle type that needs a restriction then clilck Add a new rule and then the + and Vehicle type till all applicable vehicles are added as a separate Rule in the one Restriction Line
  20. Select Minimum passengers by clicking the + on the blue add restriction banner and a drop down menu will appear
  21. At least 2 passengers is added
  22. Select number of passengers required by clicking the At least 2 passengers and a drop down menu will appear with selections for At least 3 (4) passengers
  23. If no minimum passenger restriction is selected then Waze defaults to have the restriction applicable to vehicles with any number of occupants
  24. Click the + again while remaining on the same restriction as the number of passengers to select Requires a pass
  25. Alabama Freedom Pass is added to the restriction line
  26. Click the Alabama Freedom Pass area and a drop down menu will appear with available companies
  27. Select the applicable transponder/pass
  28. If no transponder/pass is selected then Waze defaults to have the restriction applicable to all vehicles even if no transponder/pass is selected in the Navigation settings
  29. Click Add button in bottom right corner of the second pop-up window
  30. Click Apply button in bottom right corner of the first pop-up window
  31. Click Save icon on the grey Waze bar
  32. Remember for Toll free restrictions, the vehicles listed as toll free much be covered by the Allowable restrictions to have proper routing.
  33. Allowable restrictions are set up similarly to Toll free restrictions; Allowable restrictions will have a green background
  34. Prohibited restrictions can only select the Vehicle type
  35. Prohibited restrictions have a red background
  36. Prohibited restrictions default to All vehicles
  37. Select Only to be able to pick what vehicle type(s) will be prohibited
  38. Note DO NOT select conflicting restrictions. For example selecting a segment as a toll road with an allowable restriction line of any vehicle with Sunpass and a prohibited restriction line for any taxi will not preform properly since there is no prioritization of restrictions. A user that has designated the vehicle is a taxi with Sunpass will meet both the allowable restriction and the prohibited restriction. Until the programming has prioritization this restriction should be written as a toll road with an allowable restriction line of any private car with Sunpass. Since the taxi is not an allowable restriction then all taxis will not be routed on the toll road. This means it does not matter whether the taxi has designated Sunpass is in the vehicle or not.

Understanding Restriction Line and Rule affects

  1. If there is more than one vehicle type that needs a restriction then clilck Add a new rule and then the + and Vehicle type till all applicable vehicles are added as a separate Rule in the one Restriction Line
  2. In the above picture the Rules are treated as OR statements; therefore read this restriction as to be toll free on this segment you must be either "Private car" OR "Taxi" OR "Motorcycle". So any of the three vehicle types will meet the restriction. The first pop-up window looks like this:
  3. If you made three separate Restriction Lines with each having one Rule for "Private car"/"Taxi"/"Motorcycle], #*then you will have three separate HOV Restriction Lines. Below is a picture of one Restriction Line
  4. In the above situation the Lines are treated as AND statements; therfore read these restrictions as to be toll free on this segment you must be "Private car" AND "Taxi" AND "Motorcycle". The user must be ALL THREE VEHICLE TYPES simultaneously; since only one vehicle type can be selected at a time it is impossible to ever meet this criteria.The first pop-up window looks like this:
  5. Please take a second and look at the last two examples to see how the OR and AND statements are aligned for Rules and Lines respectively.

Multiple segments

Multiple segments can be selected at once for batch editing of restrictions. Selecting multiple segments is done by clicking the segments while holding the Ctrl button (or Cmd on Mac computers).

A few things to note when editing multiple segments:

  • Note the directionality of the segments - two neighboring segments can be with different A->B directionality. In one of them the A->B direction can be eastbound and in the other it can be westbound at the same time.
  • When multiple segments are selected with different restrictions set on them, they will appear in a different section of the panel under the title: 'These restrictions only apply to some of the segments selected:' Click the ‘Apply to all’ link to the right of the restriction line to propagate the restriction to all the selected segments.
  • There is a bug that the developers are working on where when several segments are selected that have a mix of A>B and B>A segments then one way restrictions may not be entered properly. This occurs on both one way and two way segments. So be very careful that they are saved properly. For one way segments, if the restriction is entered in the opposite direction of the road then the restriction coloration will not show on the segment. It will be saved in the reverse direction and can be removed and then properly entered. This occurs when copying restrictions to multiple segments or when entering new restrictions.

Turns

Time Based Turn Restrictions (TBTRs) are used when only certain turns are partially restricted from one segment to another. If the turn is always restricted then use a red turn restriction; TBTR are not to be set to 24/7.

All turning traffic restricted at all times

Turns that are restricted to all traffic (all vehicle types) are set with turn arrows—the arrows that appear at the end of a selected segment. A restricted turn is indicated by a red arrow with a red do not sign next to it (lower left arrow in picture below). A turn that is open (not restricted) to all traffic is indicated by a green arrow. A TBTR is indicated by the yellow arrow with a yellow "do not" sign next to it (upper right arrow in picture below)Turns


Scheduled turn restrictions

When not all times, days, dates, or vehicles are restricted from turning, you can set a scheduled turn restriction from one segment to another. Turns that are restricted to all traffic during certain times of the day are "time based turn restrictions".

To enter a TBTR:

  1. Select one segment
  2. Hover over a GREEN or Yellow turn restriction arrow
  3. Two icons appear
  4. Click the clock icon and the first TBTR popup window appears
  1. Note the Difficult turn (DT) attribute box in the lower left corner; the Difficult Turn is described below
  2. Click on the Add new radio button under the description of the turn, the second popup window appears


Second pop-up window attributes

The second line will display Turning from [original segment] to [destination segment] is restricted on. There are several attributes that can be selected for the restriction:

  1. Days
  2. Hours
  3. Applies
  4. Restriction Type
  5. Additional information text box
Days (of week)
Select the applicable days of the week that the restriction will be active. Use the Select all or Select none link to more quickly change all the check boxes. The default is all days of the week. Your display order for the days will depend upon your country settings in your browser and may not exactly match the image above. Mon-Fri and Every day are the most common restriction groupings in USA.
Hours (of day)
Select the applicable hours of the day that the restriction will be active. For restrictions that apply all day long, use the default setting of All day. If the restriction is for only certain periods of time during the day, then deselect the All day radio button to allow the time to be changed. You can click the hours or minutes fields to enter times directly, or click the clock icon next to the time to enable input panels. The schedule uses a 24-hour notation. The restriction will start at the beginning of the minute designated in the start block. The restriction will go till the 59th second of the minute designated; so if you state an end time of 08:00 it goes till 08:00:59. So if a posted restriction ends at 08:00 it is advisable to end the waze restriction at 07:59; this will have the 08:00 time enacted vice carrying the restriction over for an additional minute. If the end time is selected after 23:59 then the restriction will carry over till the next day.

24-hour format

For example, a schedule of 10:00 AM to 3:00 PM is entered as 10:00 to 15:00; a schedule of midnight to noon (12:00 AM to 12:00 PM) is entered as 0:00 to 12:00. A schedule of 3:00 PM to 5:00 AM is entered as 15:00 to 05:00.

The time that should be entered is the local time of the road as on the local signs. The Waze server knows the local time zone and will schedule the restriction correctly.

Daylight savings time is automatically accounted for as long as the Waze client app is properly set to the correct local time.

Entering midnight

If a scheduled restriction is between 8:00 PM and Midnight, then enter "20:00 - 23:59". Technically if you enter "20:00 - 00:00" it will go to 00:00:59 but is more or less an equivalent result.

Crossing midnight

If a restriction occurs only during nighttime hours and opens in the morning, e.g., restricted between 10 PM and 5 AM, then enter the From time as 22:00 and the To time as 05:00. You will notice an information box that says the restriction will end of the following day. If this restriction is only on a certain day of the week, e.g., Saturday night and Sunday night, then select the day of the week for Sat and Sun matching the start of the restriction. There is no need to include Monday because it is automatically covered. Including the Monday check box would add a third day starting at 10 PM Monday.

Applies (to dates)
The default setting is Every week meaning there is no limit to the date range so as soon as you add the restriction it will be active every week until it is removed. Optionally you can select the radio button for Range of dates to limit the restriction to a certain number of days. Press the button displaying the date to display two calendars. The one one the left shows the start date and the calendar on the right shows the end date of the restriction. Note these date are inclusive meaning the restriction will include both dates (and all the ones in between) when determining the restriction. When you have selected the date range press the green Apply button. The date range is displayed in DD/MM/YYYY format. To remove the date range, simply select the Every week radio button again.

Remember that the end date will consider the entire day based on any time settings also configured. If the time crosses midnight, the next day will automatically be included for that time period and so that the restriction ends at the appropriate time.

Restriction types (Allowed/Prohibited)
This is where the two main Types of restrictions are selected that appear on the first pop-up window. Since only Allowable and Prohibited are used, Toll free is not selectable.
  1. The three Restriction Types displayed are:
    • Allowable
    • Toll free (not selectable)
    • Prohibited
  2. Restriction Types are added as Lines under the applicable direction of turning.
  3. Restriction Lines contain Rules which are constructed here on the second pop-up window
  4. Allowable restrictions have green backgrounds
  5. Prohibited restrictions have red backgrounds
  6. Restriction Rules combine the vehicle type allowed and/or prohibited
  7. Allowable and Prohibited rules have different ways of selecting vehicle types; most editors will use one or the other restriction type but not both.
  8. Remember
    • a) Each restriction Type on the first pop-up window is compared to other Types as an AND statement.
    • b) Each restriction Rule on the second pop-up window (within the Allowable restriction Type) is compared to other vehicle type(s) in that restriction line as an OR statement.
  9. Note that the restriction's background color should change to red for prohibited and green for allowed
  10. Select the applicable Allowed Vehicle type by clicking on the +
  11. Private car is added to the restriction Line
  12. The vehicle type can be changed by clicking on Private car bubble
  13. Only one vehicle type can be selected per Restriction Rule
  14. If no vehicle type is selected then Waze defaults to have the restriction applicable to all vehicles
  15. If there is more than one vehicle type that needs a restriction then clilck Add a new rule and then the + and Vehicle type till all applicable vehicles are added as a separate Rule in the one Restriction Line
  16. Click Add button in bottom right corner of the second pop-up window
  17. For Prohibited restrictions you get to enter one Rule and mark all the prohibited vehicle types at the same time in the same rule.
  18. Prohibited restrictions default to All vehicles
  19. Select Only to be able to pick what vehicle type(s) will be prohibited
  20. Note DO NOT select conflicting restrictions. There is no prioritization of the restrictions which is why it is advisable to only use Allowed OR Prohibited TBTRs but not both together on the same turn.
  21. Click Add button in bottom right corner of the second pop-up window
  22. Click Apply button in bottom right corner of the first pop-up window
  23. Click Save icon on the grey Waze bar

Difficult turn

Note the Difficult turn (DT) attribute box in the lower left corner of the first TBTR popup window

This setting tells the routing server to add a routing penalty to the turn, meaning when calculating the time to reach the destination, this turn will include extra time so that other routes are more likely to be selected if this turn is only marginally better than another nearby route.

A turn can be considered difficult for many reasons including but not limited to the following:

Heavy traffic
  • Turn left across traffic that may be continuously flowing or fully stopped and into traffic that may also be continuously flowing or stopped.
  • Turn right into traffic that may be continuously flowing or fully stopped.
Poor visibility
  • Turn (left or right) into quickly moving traffic with poor visibility from:
  • a crest in the road
  • a sharp corner
  • an obstacle

A turn can be identified as difficult by 'multiple' drivers submitting URs or by the direct knowledge of the editor.

Do not put a DT in for the following situations:

  1. If the poor visibility turn is the only valid way into the segment (The DT will not affect routing and should be omitted)
  2. A left/right turn at a traffic light
  3. A left/right turn where there are stop signs at all paths of travel
  4. A left turn where there is a dedicated left turn lane even if left turn lane is not an at-grade connector (AGC) (car is protected and if time to turn is long algorithm will pick up)
 z May 2016, the difficult turn box is a 24 hour every day setting and not related to any other time-based restriction. That may be something available in the future but not at this time.
Źródło: „https://beta.waze.com/wiki/Poland/index.php?title=Planowe_ograniczenia_w_ruchu&oldid=11969”