PesachZ wrote:
Where in the page would you recommend putting it? Do have a proposed text you would suggest?

Fredo-p wrote:How is this for starters:
from this

Overview
There are four methods to control traffic flow:

1. Mega events
2. Temporary Road Closures
3. Partial restrictions
4. Disconnect road segments

• Mega event - A major event that will typically have road closures or detours. It is usually a scheduled event with significant exposure and likely to impact an entire community. A major natural disaster can be added after it occurs if roads are going to be rerouted for many days.
• Temporary road closures - 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 a few days. Currently this feature is only available in the client application and requires multiple users be at the location to enter the same road closure information on the map before it will be seen by other drivers. Once this feature is available in WME it will have more use.
• Scheduled restrictions - A new feature recently added to WME. Used when turns or roadways are restricted for certain times of day, days of the week, vehicle types, etc. It has the ability to only restrict during a specific date range, so it can be used in place of mega events or temporary road closures if necessary.
• Disconnect road segments - In general it is not recommended to disconnect road segments unless roads are permanently being disconnected. However, this method has been used for longer term construction projects while waiting for the scheduled restrictions feature.

to this:

Overview
There are five methods to control traffic flow:

1. Mega events
2. Temporary Road Closures
3. Partial restrictions
4. Disconnect road segments
5. Using the road closures form

• Mega event - A major event that will typically have road closures or detours. It is usually a scheduled event with significant exposure and likely to impact an entire community. A major natural disaster can be added after it occurs if roads are going to be rerouted for many days.
• Temporary road closures - 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 a few days. Currently this feature is only available in the client application and requires multiple users be at the location to enter the same road closure information on the map before it will be seen by other drivers. Once this feature is available in WME it will have more use.
• Scheduled restrictions - A new feature recently added to WME. Used when turns or roadways are restricted for certain times of day, days of the week, vehicle types, etc. It has the ability to only restrict during a specific date range, so it can be used in place of mega events or temporary road closures if necessary.
• Disconnect road segments - In general it is not recommended to disconnect road segments unless roads are permanently being disconnected. However, this method has been used for longer term construction projects while waiting for the scheduled restrictions feature.
• Road Closures form - The road closures form is to be filled for closures related to construction, work closures and emergency closures.This form is to be used by all editors who do NOT have direct access to the Waze Road Closure system. US Champs and State Managers will review requests entered and will be submitted to Waze if approved.

• It is the preferred method by Waze staff for editors to enter closures.
• It is available for all editors to use
• It's more accurate
• It displays the closure and description on the client map
• It has less potential for abuse and neglect, being that every closure must be confirmed by a SM, RC, or champ.
• It automatically express at a set date reinstating the roads, preventing roads accidentally being left closed indefinitely because they've been forgotten about.

old text wrote: Disconnect road segments - In general it is not recommended to disconnect road segments unless roads are permanently being disconnected. However, this method has been used for longer term construction projects while waiting for the scheduled restrictions feature.

suggested new text wrote: {{S|Disconnect road segments}} - It is no longer recommended to disconnect road segments, unless the roads are permanently being deconstructed or closed. However, this method has been used in the past for longer term construction projects while waiting for the scheduled restrictions feature.

kentsmith9 wrote:

PesachZ wrote: I would also change the text of the disconnect bullet (to be placed as number 5) as follows:

old text wrote: Disconnect road segments - In general it is not recommended to disconnect road segments unless roads are permanently being disconnected. However, this method has been used for longer term construction projects while waiting for the scheduled restrictions feature.

To this

suggested new text wrote: {{S|Disconnect road segments}} - It is no longer recommended to disconnect road segments, unless the roads are permanently being deconstructed or closed. However, this method has been used in the past for longer term construction projects while waiting for the scheduled restrictions feature.

I recommend a slight adjustment on this suggestion since there is still a use for this situation.

suggested new text alteration wrote: Disconnect road segments - Road segments should only be physically disconnected if the road is no longer intended to connect or is being permanently removed. In the past, this method was used for longer term construction projects, but now the Road Closure form should be used.

Fredo-p wrote:Haven't looked to verify this, but wouldn't the (Closed) tag and restricting "turns" to the closed segments work?

qwaletee wrote:We had a longish discussion about this on the Routing and TTS Hangout on June 23-24. There were still situations we had a consensus to disconnect.

For certain cases, especially local closures, we decided it was acceptable to use the disconnect mechanism and not file it with Waze, because they could at worst cause local problems. In addition, local closures are often not as well marked.

Also, the main reason Waze does not want disconnects is because there is a conflict between their closure system, which relies on knowing the path for the closure through a junction node to the closed segment, and the guidance to disconnect. There are other ways of phsyically disconnecting that might not conflict, but it bears some exploration.

So, modified alternative guidance for local:
* Set date-based segment and/or turn restrictions well before the closure
* Closure should occur automatically on the scheduled date
* Optionally, seal the deal AFTER the closure starts by disconnecting, in case the routing code ignores the scheduled restriction. Whether you physically disconnect should depend on your assessed: danger if routing overrides, likelihood of routing overrides, how badly the driver could get lost or lose time if routing overrides
* Set yourself a reminder for about 80% of completion time to check status of project. Fine tune end of scheduled restriction, and start checking regularly for any late changes to the construction end date.
* A few days before expected re-opening (allow a tile update cycle in between), reconnect roads, possibly fine-tune end of schedule on restriction
* Verify re-opening, then remove restriction entirely

For long term closures, instead of 80%, set yourself regular reminders to check progress against baseline dates, and adjust restriction schedule and calendar reminders accordingly.

sketch wrote:Wrong. The context was that the closure tool was not available. (Before you say anything, yes, I read through the transcript. I even copied it to a document so I don't have to waste 20 minutes scrolling to find something I already knew.)

At that time, the only way to get a proper closure was to submit a mega traffic event. The only thing I agreed would merit a disconnect was a closure on a major road if the mega traffic event was denied or reasonably expected to be denied. Anything on minor roads, time-based restrictions would do. Anything very major, a mega traffic event should be submitted.

That's no longer an issue, because we have the closure sheet, which specifically handles all closures. So we use the closure sheet for everything now, and there is no longer any reason to disconnect segments. Period.

That discussion was June 23-24; the closure sheet was created June 29.

Even then I said that disconnecting roads shouldn't be in the Wiki.

sketch wrote:

qwaletee wrote:Wrong, wrong, wrong. Mega-events use the same mechanism on the routing server, just a different interface for reporting them. This wasn't about ease of use of the reporting mechanism, it was about effectiveness and consequences. I didn't trust the mechanism until it has been proven over a longer period. Although we were arguing vociferously about it, it turned out that Marc and I had similar positions, though he was more worried about wasted miles where there are limited routes.

You did not trust the mechanism. Yes, at the time, "we had a consensus to disconnect", but only for those situations which are now covered by the closure form. That is as far as our consensus reached. We did not have a consensus that the closure tool was not to be trusted. Do not imply otherwise.

CBenson wrote:...
The issue here is that the average editor doesn't know what is submitted for closure as a event or construction road closure, but can see whether there is a scheduled restriction. I suspect many editors naturally think that they might as well add the scheduled restrictions just to be sure that the routing will be correct.

[ROADWORKS] This road has been reported closed by <editor> in the Waze Road Closure System, and will appear closed in livemap and the client from <start date / time> until <end date / time>.
<Permalink of closed segments>

PesachZ wrote:

CBenson wrote:...
The issue here is that the average editor doesn't know what is submitted for closure as a event or construction road closure, but can see whether there is a scheduled restriction. I suspect many editors naturally think that they might as well add the scheduled restrictions just to be sure that the routing will be correct.

It has been suggested that any time a closure is added to a closure sheet, the person adding the closure should place a UR through livemap directly over the closed road using the [ROADWORKS] template (to benefit editors using URO+ with that feature enabled which highlights those URs as construction related) The UR would be simple and could look like this

Code: Select all

[ROADWORKS] This road has been reported closed by <editor> in the Waze Road Closure System, and will appear closed in livemap and the client from <start date / time> until <end date / time>.
<Permalink of closed segments>