Changes

From Wazeopedia

Real time closures

7,709 bytes added, 2 years ago
m
1 revision imported: Second import of transfer package
<!--if the section parameter is defined, do not place the visible banner, only as the code block for the top of a section-->{{ReturnToEditingManualGlobalMark/visible}}<!-- #####-----#####-----#####-----#####-----#####-----#####-----#####-----#####----- #### This page has been curated #### #### to be included in the new #### #### Wazeopedia - GLOBAL Wiki. #### #### Please do not make any #### #### edits on this page without #### #### PRIOR CONSENSUS in the Wiki #### #### Updates and Discussions #### #### forum thread for this page. #### #### If a specific forum thread #### #### for this page doesn't exist #### #### please start one. #### #### www.waze.com/forum/ #### #### viewforum.php?f=276 #### #####-----#####-----#####-----#####-----#####-----#####-----#####-----#####--> {{ReturnTo | Editing manual | the editing manual}}
Oftentimes roads Roads on the map often need to be closed for a variety of reasons ; ranging from planned construction or a large-scale event , to emergency closures for accidents or natural disasters. These are called Real-Time Closures, and will be discussed in detail on this page.
There are several mechanisms to prevent Waze from routing traffic over specific roads. The method used depends on the reason traffic flow needs to be prevented. Here is a brief overview of the various mechanisms available for controlling traffic flow on specific roads. For specific details on any of these mechanisms, please see the corresponding wiki pages linked below.
* [[File:Closure arrow in WME.png|right]][[File:Closure_report_button_in_client.png|right|60px]]'''{{#ifeq:{{SUBPAGENAME}}|Real time closures|[[#Real time closures|Real time closures]] (this page)|[[Real time closures]]}} —''' Should be used when a road is temporarily unusable, but does not need modification (including turn restrictions). These display in the client and Livemap with alerts and candy stripes on the segments to notify users of the closures in real-time (no wait for tile updates), and prevents prevent routing during the closure time on these segments. '''Due to its' safety (protecting the map), and its visibility (in the client and Livemap), this is the preferred method of closing a road.''' <br />Real-Time Closures can be submitted in a variety of methods , discussed in detail further on this page:** Add a [[#Closure WME closure feature in the waze map editor|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 Waze app|Report a closure in the client]] as you drive by them.
* [[File:Restriction_arrow_yellow_mouseover.gif|right]]'''[[Partial restrictions]] (AKA Scheduled or Time-Based Restrictions)''' - Used when turns or roadways are restricted at certain times of day, days of the week, vehicle types, etc. These have the ability to only restrict during a specific date range, but should NOT be used in place of Mega Traffic Events or Real-Time Road Closures.
* '''[[Road types and names|Road types]] —''' Certain road types (Private, Parking Lot Road, Dirt Road/4X4 Trail) will automatically prevent routing and should be used when appropriate for permanent situationsituations.
* '''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 ==
*[[#Report a closure in the waze client app|Report a Closure in the Waze client app]]
*[[#Major traffic events|Major Traffic Events (MTEs)]]
*[[#Temporary closures in wmeWME_closure_feature|Temporary Closures in WME]]
*[[#Closure sheets|Closure Sheets]]
As mentioned above, if the closure is part of an event which will be impacting a large number of people in your area (i.e. - major highway closed, city-wide marathon, natural disaster) please be sure to [[#Major traffic events|submit the MTE form]] first.
 
=== Connected Citizens Program ===
 
Through the [[Connected Citizens Program]] Waze shares and received 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]].
This slideshow was prepared by Waze staff to show how to add a closure in WME. It contains information on which segments to select as part of a closure as well. The information in this slide show is also presented throughout this page in text.
{{#widget:Iframe
|url=https://docs.google.com/presentation/d/12TrGVZsJRTR1tBb3Cg8Ewu_rx7yuPxGMCTy4FIoAb-ia-MMdaYPF8A1cBOUoQr0uKf5L52C_MZ1CY33ukYFtM8/embed?start=false&loop=false&delayms=30000
|border=0
|width=700
Whenever entering a '''time''', it should be using the 24 hour clock, in the format of '''HH:MM:SS'''. ''The HH is the two digit hour, MM is the two digit minute, and SS is the two digit seconds. The seconds may be optional depending on the feature you are using. (For example 2:53 pm will be entered as 14:53.)''
In the 24 hour clock, the first 12 hours of the day from midnight until 11:59 am, are represented as 00:00 - 11:59. The second twelve hours of the day from noon until 11:59 pm, are represented as 12:00 - 23:59. ''To make it easy to remember, any time in the AM hours, is just the same (with a leading zero for the first nine single digit hours). Any time in the PM hours, add 12 to the hour (so 2 pm becomes 14 - by doing the following: 2+12=14).
The minute of midnight can be represented both as 00:00, and as 24:00 depending on if it is connected to the previous day (24:00), or the new day just beginning (00:00). ''For example Monday 24:00 is the same minute as Tuesday 00:00.'' To prevent confusion you should avoid using 00:00, or 24:00 as a closure time, instead use 23:59, or 00:01.
{{red|'''NOTE:'''}} Temporary Closures must not be longer than 6 calendar months (183 days to be precise).
To enter a Temporary Closure longer than 6 months, split it into multiple Temporary Closures. Each Temporary Closure entered should be less than 6 months. E.g. A one year Temporary Closure from 20112014-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)
 
====== Maximum closure duration ======
 
The maximum length for a Real-Time-Closure is one year.
 
The end date for a closure can not 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 a years 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}}'''"
 
{{anchor|Report closure feature in the waze app}}
=== Report closure feature in the Waze app ===
==== App reported closures in WME ==== Any closures reported from the Waze app are visible, and can be manipulated in the Waze Map Editor. Waze app reported closures {{u|do not}} have an effect on routing until enough users report the same segment closed. However if an editor sees it in WME and edits it, the RTCs then take effect immediately. ''For all the details on the display and handling of app-reported closures in WME please see the [[#Understanding closures with an end date circa 1970|section below that explains the WME aspect of these closures]].'' {{anchor|Major_traffic_events}}=== Major traffic events Traffic Events (MTEs) ===
----
If a road closure is part of a larger event, it can be submitted to Waze as a Major Traffic event, or 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 providedor the WME Closure tool (available to editors rank 4 and above in most communities). This way Waze is able to track the closures and help spread the word. Only if  To receive further support from Waze decides not to support (website and/or push + inbox message) for an MTE closure, the event, or if you don't have at least one weeks advance notice should you submit these closures must be submitted through other methodsthe MTE submission form below.
To notify Waze of a coming event in your area, use the [http://docs.google.com/a/google.com/forms/d/1R0XIsGkHQmk8Nc0U5DDID1PwMQWqLMwmindiLDFwcjo/viewform MTE Submission Form].
*Start and End Time (if available)
All MTE submissions are posted to the [http://script.google.com/a/macros/google.com/s/AKfycbwegLpBUyCBB07OBDXHK8H5Js3ynsGkmn8YFI-NGxS_7--JDGud/exec Waze Mini Site] <small>''(if the mini site gives an error try refreshing the page)'' </small>so that other editors in your area can find the name for an event and mark the closure consistently.  The closures for each MTE are submitted in a [[#Closure sheets|unique Google Sheets spreadsheet]]. If you need access to a particular event spreadsheet, request access in the spreadsheet and it will be granted by Waze HQ.  ==== Support for Major Traffic Events ==== Once the submitted event is reviewed, the submitter receives an MTE closure sheet and further instruction on how to provide all of the information needed to properly close the affected roads.
Once the closure sheet is fully completed, the closure will be live in the app.
==== Support for major traffic 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.
If MTEs are likely to be announced on the Major Events website and/or via inbox + push message if the event effects a significant portion of the local population. For your event is going to receive further support as an MTE, or if more information is needed, Waze will be considered for inclusion in touch after the form is submitted. Waze further supports some events by providing local following weeks push notifications, /inbox messagesmessaging, social media announcements and/or website features on the [http://www.waze.com/events Major Events page] on Waze.comall closure information must be received by Wednesday prior.
If Waze notifies you that your submitted Major Traffic Event will A closure may not be supported, or appear in the app if you have less than one week advance notice of Waze is unable to obtain the closureproper information, you should submit the either through user-completed closure through one of the sheets or if other [[#Real time closures|Real-Time Closure methods]]resources cannot be found.
{{anchor|Closure feature in the waze map editor}}
=== WME closure feature ===
==== Closure feature permissions ====
This feature is restricted to rank 5 3 editors and above, unless otherwise decided by the local community. Global champs also have the ability to allow users of varioius various levels aceess access to the feaurefeature. If you would like to request access, contact a member of the community in the [http://www.waze.com/forum/viewforum.php?f=663 Waze Community Forums].  Alternatively, If you do not have the required rank to access the Closure feature in WME, you can ask a higher ranking editor to implement the closures for you. Your country may have a streamlined monitored process for this, or it can be submitted like any other unlock/update request. You can also ask a higher editor directly in a [[PM]], or [[WME Chat]]. ''In the USA the [http://docs.google.com/forms/d/1oGINt4UEkBV0Par5VCingXzTZpJq9KjG8GbZpGqbRow/viewform Road Closures Form (USA)] is used for example.''
Alternatively, If you do not have the required rank to access the Closure feature in WME, you can ask a higher ranking editor to implement the closures for you. Your country may have a streamlined monitored process for this, or it can be submitted like any other unlock/update request. You can also ask a higher ranked editor directly in a [[PM]], or [[WME Chat]]. ''In the USA the [http://docs.google.com/forms/d/1oGINt4UEkBV0Par5VCingXzTZpJq9KjG8GbZpGqbRow/viewform Road Closures Form (USA)] is used for example.''
==== Step by step instructions to add a closure ====
If you need to edit the segment, you will have to first remove the Temporary Closure ''(copy the details first)'', then modify the segment and save. Depending on the type of edit you can either replace now, otherwise you will need to wait for a tile update before being able to add a new Temporary Closure. Add a new Temporary Closure with the details you copied to the appropriate segments.
 
 
===== Understanding closures with an end date circa 1970 =====
Note: {{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 [[#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 1 January 1970. Because Waze uses the [[UTC]] time zone, this may be ±1 up to 13 hours for you.
 
In the [http://en.wikipedia.org/wiki/Unix Unix operating systems] a time is encoded as the number of seconds passed since January 1st, 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 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 Livemap 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.
 
This explains the anomalies listed above;
* Because they are from the app, they don't immediately affect routing until there are multiple identical reports.
* They can be reported by any rank user.
* There needs to be multiple reports to activate them.
* It is possible to have more than one report 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 start affecting traffic like any regular RTC immediately.
 
If there are multiple app-reported RTCs on a segment you may have to remove the duplicates before being able to save any changes to one of them, otherwise you may get an error for trying to create an overlapping closure.
=== Closure sheets ===
There are generally two types of Closure Sheets;
* Regional Closure Sheets supplied by Waze staff and shared with the community leadership of some countries.
* Supported Mega 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 here below. They still also follow all the general guidance for [[#Real time closureclosures|Real-Time Closures]] listed above.
Real-Time Closures which could just as easily be submitted using the Closure feature in the WME, shouldn't be submitted using the Regional Closure Sheets. If there is some feature of submitting them through the Regional Closure Sheet easier somehow, then it is fine to use the Regional Closure Sheets for them. The Regional Closure Sheets may also have some features not yet available in WME, closures utilizing those features should be submitted through the sheets.
 
===== 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 applicable.
 
 
Waze staff receive a alerts of certain changes to the closure sheets three times daily 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 do not receive the 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 can not be submitted through WME'',&nbsp;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, 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 th esame 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.<br />
'''Permalink -''' You have to provide a permalink which shows all the segments you wish to close selected. See the [[Waze Map Editor#Permalink|Permalink]] article for details on how to create a Permalink which has the segments selected.
There may be other elements you are asked to provide to make use of some advance features of the Closure Sheets, if this happens there . '''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 columns of sheet labeled "DO NOT EDIT" in the header row.
{{clear}}{{ReturnToEditingManualReturnTo | Editing manual | the editing manual}}