mNo edit summary |
mNo edit summary |
||
| Line 11: | Line 11: | ||
Information from <i>GIPOD</i> is used to provide information on closures in Flanders, <br /> | Information from <i>GIPOD</i> is used to provide information on closures in Flanders, <br /> | ||
CCP-partner <i>Wegstatus</i> collects information from authorities in the Netherlands. <br /> | CCP-partner <i>Wegstatus</i> collects information from authorities in the Netherlands. <br /> | ||
In some areas Security Regions manage RTCs. | In some areas Security Regions manage RTCs.<br /> | ||
<br /> | <br /> | ||
For more information see the global page [https://wazeopedia.waze.com/wiki/Global/Real_time_closures Real time closures]. | |||
</translate> | </translate> | ||
{{Bottomline}} | {{Bottomline}} | ||
Revision as of 22:57, 16 February 2018
Closures
Real Time Closures (RTC) should be used when a road is temporarily unusable. These are visible in the client and Live map with alerts and candy stripes on the segments, to notify users of the closures in real-time, and prevent routing during the closure time on these segments.
Users in the Waze app can mark an unexpected road closure they see while driving. Reliable requests become immediately active on the Waze map as a RTC and automatically shared with editors in the relevant Slack-channels: #closures-be, #closures-be-fr, #closures-nederland and #closures-lux.
Requests for closures within a week are welcome in these channels, others can be requested on Dutch forum closures and Belgium forum closures.
Information from GIPOD is used to provide information on closures in Flanders,
CCP-partner Wegstatus collects information from authorities in the Netherlands.
In some areas Security Regions manage RTCs.
For more information see the global page Real time closures.