Difference between revisions of "Translations:Closures/1/en"

From Wazeopedia
(Importing a new version from external source)
(Importing a new version from external source)
 
Line 11: Line 11:
 
The date an App closure is entered is used as startdate of the closure. App closures are almost always one-way closures.<br />To change the end date of an App closure: delete the App closure and create of a new one.<br />
 
The date an App closure is entered is used as startdate of the closure. App closures are almost always one-way closures.<br />To change the end date of an App closure: delete the App closure and create of a new one.<br />
 
<br />
 
<br />
Requests for closures within one or two days are welcome in these channels, others can be requested on [http://bit.ly/NLforum_closures Dutch forum closures] and [https://www.waze.com/forum/viewforum.php?f=718 Belgium forum closures].<br />
+
Closures can be set by editors with [[Editor level|Level 3]] and above and by the members of the <i>Closure team</i>.
 +
<br />
 +
Requests for closures within one or two days are welcome in the Slack closure channels, others can be requested on our [[Forum|forums]]: [http://bit.ly/NLforum_closures Dutch forum closures] and [https://www.waze.com/forum/viewforum.php?f=718 Belgium forum closures].<br />
 +
<small>
 +
Please enter your requests as follows: [[File:Slack-closure-request.png|right|600px|Example closure request]]
 +
* [[Editor level|Level]] 
 +
* City and optionally Street name
 +
* Starting date and time / End date and time
 +
* Closure reason / description
 +
* A [[PL|permalink]] of the segment to close
 +
* Source of the closure information
 +
</small>
 
<br />
 
<br />
 
For defining special events for sets of closures see the [[Major Traffic Events]] page. <br />
 
For defining special events for sets of closures see the [[Major Traffic Events]] page. <br />

Latest revision as of 21:50, 23 August 2019

Information about message (contribute)
This message has no documentation. If you know where or how this message is used, you can help other translators by adding documentation to this message.
Message definition (Closures)
==Closures==
Real Time Closures (RTC) should be used when a road is temporarily unavailable. Users are notified of the closures in real-time, from the moment the closure is added routing through these segments is prevented. Active closures are made visible in the [[Waze app|app]] and [[Live map]] with alerts and candy stripes on the closed segments. <br />
<br />
Duration of an closure is maximum 6 months. It is possible to add an additional closure for another period following on a previous closure.<br />
<br />
The script [[WME Closure Details]] can be used to view Closure details on closures outside the [[Editable area|editable area]]. The script [[WME Advanced Closures]] handles recurrent and imported closures in the [[Waze Map Editor]].
<br />
[[File:Rtc-luxembourg.png|right|450px]]
[[File:App-closure.png|left|200px]]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 <i>RTC</i> and automatically shared, via the [[Waze Closures Bot|closures bot]] with editors in the relevant Slack-channels: [https://wazebenelux.slack.com/messages/C037BDXMG #closures-be], [https://wazebenelux.slack.com/messages/C037KV8KM #closures-be-fr], [https://wazebenelux.slack.com/messages/C04CBAYGB #closures-nederland] and [https://wazebenelux.slack.com/messages/C0E3F7PSB #closures-lux]. <br />
<br />
The date an App closure is entered is used as startdate of the closure. App closures are almost always one-way closures.<br />To change the end date of an App closure: delete the App closure and create of a new one.<br />
<br />
Closures can be set by editors with [[Editor level|Level 3]] and above and by the members of the <i>Closure team</i>.
<br />
Requests for closures within one or two days are welcome in the Slack closure channels, others can be requested on our [[Forum|forums]]: [http://bit.ly/NLforum_closures Dutch forum closures] and [https://www.waze.com/forum/viewforum.php?f=718 Belgium forum closures].<br />
<small>
Please enter your requests as follows: [[File:Slack-closure-request.png|right|600px|Example closure request]]
* [[Editor level|Level]]  
* City and optionally Street name
* Starting date and time / End date and time 
* Closure reason / description
* A [[PL|permalink]] of the segment to close
* Source of the closure information
</small>
<br />
For defining special events for sets of closures see the [[Major Traffic Events]] page. <br />
<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 />
In some areas Security Regions manage RTCs.<br />
<br />
For more information see the global page [https://wazeopedia.waze.com/wiki/Global/Real_time_closures Real time closures].
<br />
Translation==Closures==
Real Time Closures (RTC) should be used when a road is temporarily unavailable. Users are notified of the closures in real-time, from the moment the closure is added routing through these segments is prevented. Active closures are made visible in the [[Waze app|app]] and [[Live map]] with alerts and candy stripes on the closed segments. <br />
<br />
Duration of an closure is maximum 6 months. It is possible to add an additional closure for another period following on a previous closure.<br />
<br />
The script [[WME Closure Details]] can be used to view Closure details on closures outside the [[Editable area|editable area]]. The script [[WME Advanced Closures]] handles recurrent and imported closures in the [[Waze Map Editor]].
<br />
[[File:Rtc-luxembourg.png|right|450px]]
[[File:App-closure.png|left|200px]]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 <i>RTC</i> and automatically shared, via the [[Waze Closures Bot|closures bot]] with editors in the relevant Slack-channels: [https://wazebenelux.slack.com/messages/C037BDXMG #closures-be], [https://wazebenelux.slack.com/messages/C037KV8KM #closures-be-fr], [https://wazebenelux.slack.com/messages/C04CBAYGB #closures-nederland] and [https://wazebenelux.slack.com/messages/C0E3F7PSB #closures-lux]. <br />
<br />
The date an App closure is entered is used as startdate of the closure. App closures are almost always one-way closures.<br />To change the end date of an App closure: delete the App closure and create of a new one.<br />
<br />
Closures can be set by editors with [[Editor level|Level 3]] and above and by the members of the <i>Closure team</i>.
<br />
Requests for closures within one or two days are welcome in the Slack closure channels, others can be requested on our [[Forum|forums]]: [http://bit.ly/NLforum_closures Dutch forum closures] and [https://www.waze.com/forum/viewforum.php?f=718 Belgium forum closures].<br />
<small>
Please enter your requests as follows: [[File:Slack-closure-request.png|right|600px|Example closure request]]
* [[Editor level|Level]]  
* City and optionally Street name
* Starting date and time / End date and time 
* Closure reason / description
* A [[PL|permalink]] of the segment to close
* Source of the closure information
</small>
<br />
For defining special events for sets of closures see the [[Major Traffic Events]] page. <br />
<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 />
In some areas Security Regions manage RTCs.<br />
<br />
For more information see the global page [https://wazeopedia.waze.com/wiki/Global/Real_time_closures Real time closures].
<br />

Closures

Real Time Closures (RTC) should be used when a road is temporarily unavailable. Users are notified of the closures in real-time, from the moment the closure is added routing through these segments is prevented. Active closures are made visible in the app and Live map with alerts and candy stripes on the closed segments.

Duration of an closure is maximum 6 months. It is possible to add an additional closure for another period following on a previous closure.

The script WME Closure Details can be used to view Closure details on closures outside the editable area. The script WME Advanced Closures handles recurrent and imported closures in the Waze Map Editor.

Rtc-luxembourg.png
App-closure.png
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, via the closures bot with editors in the relevant Slack-channels: #closures-be, #closures-be-fr, #closures-nederland and #closures-lux.


The date an App closure is entered is used as startdate of the closure. App closures are almost always one-way closures.
To change the end date of an App closure: delete the App closure and create of a new one.

Closures can be set by editors with Level 3 and above and by the members of the Closure team.
Requests for closures within one or two days are welcome in the Slack closure channels, others can be requested on our forums: Dutch forum closures and Belgium forum closures.

Please enter your requests as follows:
Example closure request
  • 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


For defining special events for sets of closures see the Major Traffic Events page.

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.