Difference between revisions of "Closures/nl"

From Wazeopedia

Closures/nl

m (Text replacement - "[[Waze Closures Bot" to "[[Closures Bot")
(Updating to match new version of source page)
 
Line 14: Line 14:
 
__TOC__
 
__TOC__
  
==When to use (and when not)==
+
=={{@|When to use (and when not)}}==
 
RTCs are used for closing off as well as opening up all traffic flow on certain road segments in real time. It can only be used when a road is completely closed in one or both directions, for all vehicles normally allowed.  
 
RTCs are used for closing off as well as opening up all traffic flow on certain road segments in real time. It can only be used when a road is completely closed in one or both directions, for all vehicles normally allowed.  
  
Line 23: Line 23:
 
Permanent changes closing off a route, such as a road that changes to one-way driving direction, map it as such, and don't use any kind of closure.
 
Permanent changes closing off a route, such as a road that changes to one-way driving direction, map it as such, and don't use any kind of closure.
  
==Requests for closures==
+
=={{@|Requests for closures}}==
 
If you need to set or remove an RTC but the road segment is above your level or outside your editable area, you can always file a request. Requests for RTCs are welcome in the Slack closure channels: [https://waze-belux.slack.com/archives/CF511LUBA #30-vl_closures], [https://waze-belux.slack.com/archives/CCKLS7C4B #30-fr_fermetures], [https://waze-belux.slack.com/archives/CF5UQ07V3 #30-bl_closures-bxl]. With the  script [[Tools#Send_to_Slack|Send to Slack]] you can do this directly from WME. Non-Slack users may request closures on the [https://www.waze.com/forum/viewforum.php?f=718 forum].  
 
If you need to set or remove an RTC but the road segment is above your level or outside your editable area, you can always file a request. Requests for RTCs are welcome in the Slack closure channels: [https://waze-belux.slack.com/archives/CF511LUBA #30-vl_closures], [https://waze-belux.slack.com/archives/CCKLS7C4B #30-fr_fermetures], [https://waze-belux.slack.com/archives/CF5UQ07V3 #30-bl_closures-bxl]. With the  script [[Tools#Send_to_Slack|Send to Slack]] you can do this directly from WME. Non-Slack users may request closures on the [https://www.waze.com/forum/viewforum.php?f=718 forum].  
  
Line 36: Line 36:
 
{{BackToc{{#translation:}}}}
 
{{BackToc{{#translation:}}}}
  
==Closures set in App==
+
=={{@|Closures set in App}}==
 
Drivers can mark an unexpected road closure while driving. Reliable requests become immediately active on the Waze map as an RTC . However, App closures are almost always defined in one-way direction with a limited duration, and they often need modification.
 
Drivers can mark an unexpected road closure while driving. Reliable requests become immediately active on the Waze map as an RTC . However, App closures are almost always defined in one-way direction with a limited duration, and they often need modification.
  
Line 42: Line 42:
 
The date a closure is marked from the App is also the start date of the closure. To change the end date of an App closure: delete the App closure and create of a new one. More info on how to follow up these closures is described on the page about the  [[Closures Bot|closures bot]].
 
The date a closure is marked from the App is also the start date of the closure. To change the end date of an App closure: delete the App closure and create of a new one. More info on how to follow up these closures is described on the page about the  [[Closures Bot|closures bot]].
  
==Multiple Closures for Events==
+
==Updating closed segments==
 +
It is not possible to modify some attributes of a closed segment. 
 +
 
 +
The logical workaround (removing the closure and closing again after the update) will frequently fail, read next section.
 +
==Closing recently created/updated segments==
 +
It is not possible to close a recently created segment, until the segment is fully created by a map update.
 +
 
 +
Some recent changes do not allow closing a segment, or closing one direction of a segment, until the change is fully applied by a map update. 
 +
In such a case, it is sometimes possible to create "short term" closures, expiring within the next 48 hours.
 +
As an example, after changing a two ways street into a one way street, it is possible to immediately close the forbidden direction, if the closure expires within the next 48 hours.
 +
Such “short term” closures can be extended later if necessary, if the end time remains within the next 48 hours.
 +
 
 +
It is not possible to close a deleted segment: it is not possible to apply closures from the "Current live map" view of the WME.
 +
 
 +
=={{@|Multiple Closures for Events}}==
 
[[File:Closures-example.png|500px|right]]
 
[[File:Closures-example.png|500px|right]]
 
<br>
 
<br>
Line 56: Line 70:
 
{{BackToc{{#translation:}}}}
 
{{BackToc{{#translation:}}}}
  
== Closing junctions==
+
== {{@|Closing junctions}}==
 
When adding an RTC to consecutive segments, all junction nodes in between those segments will be closed too. The nodes on the edges remain open.  
 
When adding an RTC to consecutive segments, all junction nodes in between those segments will be closed too. The nodes on the edges remain open.  
  
Line 62: Line 76:
  
 
[[File:Be-Closure-Nodes-En.PNG|right|230px]]<!--Nl and fr version also available!-->
 
[[File:Be-Closure-Nodes-En.PNG|right|230px]]<!--Nl and fr version also available!-->
=== How to work with node closures ===
+
=== {{@|How to work with node closures}} ===
 
# Select the segments to be closed and fill in the details
 
# Select the segments to be closed and fill in the details
 
# Review the list of involved nodes at the bottom of the closure menu. Hoover over a node's cross-street name in the list of junction nodes in order to highlight that node on the map. When a node is closed, a symbol [[File:Closed node.PNG]] will appear on the map at that junction.
 
# Review the list of involved nodes at the bottom of the closure menu. Hoover over a node's cross-street name in the list of junction nodes in order to highlight that node on the map. When a node is closed, a symbol [[File:Closed node.PNG]] will appear on the map at that junction.
Line 68: Line 82:
 
# Save the closures.
 
# Save the closures.
  
===Remarks===
+
==={{@|Remarks}}===
 
* When closing two consecutive segments, the junction node in between will be closed too. This means that the entire junction will be closed for traffic. If you can cross that junction for any other route, make sure to remove the closure from the node. An open junction is shown as [[File:Open node.PNG]]
 
* When closing two consecutive segments, the junction node in between will be closed too. This means that the entire junction will be closed for traffic. If you can cross that junction for any other route, make sure to remove the closure from the node. An open junction is shown as [[File:Open node.PNG]]
 
* If you close two-way segments in just one direction, you will not be able to close the junction node.
 
* If you close two-way segments in just one direction, you will not be able to close the junction node.
Line 78: Line 92:
 
{{BackToc{{#translation:}}}}
 
{{BackToc{{#translation:}}}}
  
==Tools==
+
=={{@|Tools}}==
 
* <b>Send to Slack script</b> This script can be used to request closures above your level directly from WME to Slack. Can also be used for openings, (down)Locks, and Validation of changes.
 
* <b>Send to Slack script</b> This script can be used to request closures above your level directly from WME to Slack. Can also be used for openings, (down)Locks, and Validation of changes.
 
: - [https://gitlab.com/WMEScripts/wme-send-to-slack-public/raw/master/WME-send-to-slack.user.js Install]
 
: - [https://gitlab.com/WMEScripts/wme-send-to-slack-public/raw/master/WME-send-to-slack.user.js Install]
Line 91: Line 105:
 
: - The [https://wazeopedia.waze.com/wiki/Netherlands/WME_Advanced_Closures wiki from the Netherlands] provides an explanation with pictures
 
: - The [https://wazeopedia.waze.com/wiki/Netherlands/WME_Advanced_Closures wiki from the Netherlands] provides an explanation with pictures
  
==Further reading==
+
=={{@|Further reading}}==
 
* The [[Closures Bot|Waze Closures Bot ]] publishes RTCs reported via the app in the Slack BeLux Closure channels. Editors can easily use this data for modifying and implementing closures. <!-- <Information from GIPOD is used to provide information on closures in Flanders> add to that page, together with info how to deal with the posts in Slack-->
 
* The [[Closures Bot|Waze Closures Bot ]] publishes RTCs reported via the app in the Slack BeLux Closure channels. Editors can easily use this data for modifying and implementing closures. <!-- <Information from GIPOD is used to provide information on closures in Flanders> add to that page, together with info how to deal with the posts in Slack-->
 
* See also the page about [[Restrictions]], for partial closures.
 
* See also the page about [[Restrictions]], for partial closures.

Latest revision as of 13:10, 9 April 2021

Mbox information.png
We are currently updating the pages to include all regionally different guidelines. If you find inconsistencies, please refer to the English page. Thank you!
Other languages:
English • ‎Nederlands • ‎français
Real Time Closures (RTCs)

If a road is closed, we can map it using Real Time Closures or Partial Restrictions. A Real Time Closure (RTC) may be used when a segment is completely closed temporarily in one or both directions to all wazers. Examples are closures due to an accident, during an event, or to enable road works. RTCs are visible to the driver and can be removed in real time as well. For roads that have a structural and partial closure, such as during specific times or for specific vehicle types, we use Restrictions. Changes in restrictions need a map update and are not visible to the driver. This page deals with Real Time Closures (RTCs).

Rtc-luxembourg.png

RTCs are used when a road is temporarily unavailable. From the moment an RTC is added, routing through these segments is prevented. Users are notified in real-time: active closures are immediately visible in the app and the Live map with alerts and candy stripes on the closed segments. WME shows RTCs with a red (active) or grey (planned) icon.

RTCs can be set by editors with Level 3 and above. The start date should be within the next 365 days, the end date and duration are unlimited.

When to use (and when not) link to this section

RTCs are used for closing off as well as opening up all traffic flow on certain road segments in real time. It can only be used when a road is completely closed in one or both directions, for all vehicles normally allowed.

If only one lane of a multi-lane road is closed, but traffic can still go in this direction using other lanes, RTCs should not be used. Waze will calculate the average traffic speed and automatically adjust its routing if possible.

For structurally closed segments with partial conditions, like during specific hours or for specific vehicles, RTCs should not be used. Instead, use Restrictions. Examples are closed routes during rush hours, or a route that is only suitable for motorcycles.

Permanent changes closing off a route, such as a road that changes to one-way driving direction, map it as such, and don't use any kind of closure.

Requests for closures link to this section

If you need to set or remove an RTC but the road segment is above your level or outside your editable area, you can always file a request. Requests for RTCs are welcome in the Slack closure channels: #30-vl_closures, #30-fr_fermetures, #30-bl_closures-bxl. With the script Send to Slack you can do this directly from WME. Non-Slack users may request closures on the forum.

Please provide following details in your request:

Example closure request

- Editor level
- City and optionally Street name
- Starting date and time / End date and time
- Closure reason / description
- A permalink of the segment to close
- Source of the closure information

Closures set in App link to this section

Drivers can mark an unexpected road closure while driving. Reliable requests become immediately active on the Waze map as an RTC . However, App closures are almost always defined in one-way direction with a limited duration, and they often need modification.

App-closure.png

Therefore, closures from the App, together with information from several sources are automatically send to the relevant Slack-channels.

The date a closure is marked from the App is also the start date of the closure. To change the end date of an App closure: delete the App closure and create of a new one. More info on how to follow up these closures is described on the page about the closures bot.

Updating closed segments

It is not possible to modify some attributes of a closed segment.

The logical workaround (removing the closure and closing again after the update) will frequently fail, read next section.

Closing recently created/updated segments

It is not possible to close a recently created segment, until the segment is fully created by a map update.

Some recent changes do not allow closing a segment, or closing one direction of a segment, until the change is fully applied by a map update. In such a case, it is sometimes possible to create "short term" closures, expiring within the next 48 hours. As an example, after changing a two ways street into a one way street, it is possible to immediately close the forbidden direction, if the closure expires within the next 48 hours. Such “short term” closures can be extended later if necessary, if the end time remains within the next 48 hours.

It is not possible to close a deleted segment: it is not possible to apply closures from the "Current live map" view of the WME.

Multiple Closures for Events link to this section

Closures-example.png


For defining special events with multiple closures, see the Major Traffic Events page. Major Traffic Events, or MTE’s can be sport events (marathons, triathlons, etc), festivals, parades, significant construction works or even (natural) disasters like flooding, VIP visits, etc.

Verkeer door een afsluiting

Hov-service-road.png
Als er een zekere hoeveelheid verkeer door een actieve afsluiting passeert, kan de afsluiting verdwijenen. Dit wordt elke 10 minuten gecheckt. Als er geen verkeer meer passeert zal de afsluiting terug actief worden tot de eind datum. Deze functie kan worden uitgeschakeld door Naastliggende carpoolstrook/serviceweg te selecteren.

If the segment is paralleling another road in use, or needs to remain closed at all times until the given end time, even if movement is detected, mark the check box at HOV/Service Road adjacent (see picture).

Closing junctions link to this section

When adding an RTC to consecutive segments, all junction nodes in between those segments will be closed too. The nodes on the edges remain open.

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

Be-Closure-Nodes-En.PNG

How to work with node closures link to this section

  1. Select the segments to be closed and fill in the details
  2. Review the list of involved nodes at the bottom of the closure menu. Hoover over a node's cross-street name in the list of junction nodes in order to highlight that node on the map. When a node is closed, a symbol Closed node.PNG will appear on the map at that junction.
  3. Enable and disable node closures as necessary, by flipping the switch.
  4. Save the closures.

Remarks link to this section

  • When closing two consecutive segments, the junction node in between will be closed too. This means that the entire junction will be closed for traffic. If you can cross that junction for any other route, make sure to remove the closure from the node. An open junction is shown as Open node.PNG
  • If you close two-way segments in just one direction, you will not be able to close the junction node.
  • When removing an RTC from a segment that is connected to adjacent closed segments, the junction node will remain closed. You will then still see the closed node icon Closed node.PNG on the map. Traffic in any direction through this junction won't be possible. The same happens if you flip the switch on only one of the consecutive segments.

The above is also presented in this video tutorial made at the introduction of this feature.

Note: Prior to the introduction of node closures, the only way to prevent traffic crossing a closed street was to apply closures on the side streets as well. With the node closures feature, editing is more intuitive and easier and you'll have a better overview of the closed nodes.

Tools link to this section

  • Send to Slack script This script can be used to request closures above your level directly from WME to Slack. Can also be used for openings, (down)Locks, and Validation of changes.
- Install
- Documentation
  • WME Closure Details Scripts that adds the description and also some additional data in a tooltip, such as the origin of the (WME or app), closure creator, closure creation timestamp, closure updater and last closure update timestamp. Can also be used to view Closure details outside your editable area.
- Install
- Description and discussion on the forum
  • WME Advanced Closures Script that handles recurrent and imported Closures.
- Install
- Description and discussion on the forum
- The wiki from the Netherlands provides an explanation with pictures

Further reading link to this section

  • The Waze Closures Bot publishes RTCs reported via the app in the Slack BeLux Closure channels. Editors can easily use this data for modifying and implementing closures.
  • See also the page about Restrictions, for partial closures.




  Hoofdpagina | Index