-
Recommend changing “This feature is restricted to rank 3 editors and above.” to “This feature is restricted to rank 3 editors and above; the editor must be able to edit the applicable segment. If the segment is locked above an editor’s rank then determine the state’s/region’s policy on providing an unlock to enter the closure or having a more senior editor enter the closure. Additionally find out if there is a tracking/reminder system to restore the lock level after the closure is expired if the road segment was lowered. Additionally CCP partners can be granted to add closure to any segment within their CCP area.”
-
Road direction change. I don’t think there is a lose of data after the tile update from two way to one way. If you find someone improperly split a road that should be two way you can restore the road segments to two way and delete the new segments. The speed limit and the speed data in route speeds still appears to be saved.
-
TBSR and TBTR should be variable or selectable for vehicles affected it can be all or only designated types.
-
Not sure what you mean for the road type change affects routing for a closure. Changing from FW or MH to mH or lower affects routes for pruning based on distance of the route, but isn’t absolute for routing. If this is to change the road to a Private road (PR) segment then recommend changing for clarity. Guidance - "Changing the road type to a private road (PR) segment will prevent through routing unless the destination is on the private road segment. This is one way to do “Local Traffic Only” or “No Thru Traffic”.
-
The statement to not have a TBSR with the RTC is correct except when a road segment goes away for a long period of time or permanently. Adding a TBSR and a RTC will prevent routing immediately and then after the tile update will be able to have the RTC removed and the segment deleted. This is explained on the scheduled reconfiguration page. Also for roads that will be closed for >1 year this prevents having the RTCs expire and routing through the closed area.
-
The Roads may be temporarily renamed during construction section that you link to states that naming (Closed) or (Construction Zone) is depreciated and we don’t do that any more. Recommend deleting the last bullet under the “Deciding when to use an RTC” section.
-
How to add a real time closure section. You state to save all pending saves. Think you should state that an edit which changes the segment number prevents adding the RTC till after the next tile update. By initially stating that the editor should save all pending edits, it might prevent them from adding the RTC.
-
Step 4 Direction recommend correcting “then teh correct…” to “then the correct…”
-
For step 4 Direction, should have some description of if you select multiple directions and choose two way for the closure then all two way segments will be closed two ways and the one ways will be closed in the appropriate direction.
-
Also for step 4 Direction, if you select several two way and one way segments that are A-B and B-A direction then select a one way direction some may not have the closure added.
-
Event, state that the Event must already be generated and that the closure’s start time and end time must be within the Event’s time frame. If the RTC starts before or ends after the MTE then that event is not selectable.
-
Recommend changing “The longest duraction closure is 183 days.” to "The longest duration closure is 183 days. "
-
Step 4 Start/End Date & Time, recommend mentioning that the RTC is applicable to the time zone of the segment’s location, not the editor’s location. Therefore entering a closure in California from the East Coast will initially default to the editor’s time and have the RTC not start for 3 hours; therefore the start time should be adjusted appropriately.
-
Entering weather closures at the end of a day does not require avoiding using 23:59 as the start time. Understand your point but don’t think you need to state it in the Wazeopedia article.
-
Save and Check, you may have to zoom in to see all the closures, not all will be displayed if you are zoomed out.
-
Recommend changing “Closing both segments will prevent routing across the junction to reach a destination or leave a starting point, regardless of the user’s position in relation to that junction.” to "Closing all outbound segment(s) routing from the intersection will prevent routing across the intersection’s junction node to reach a destination or leave a starting point, regardless of the user’s position in relation to that junction node.
-
Might want to state for some parades or races people are allowed to occasionally cross the route under police direction. RTCs should not be used for these intersections if known. These are similar to alternating closures w/o a schedule and the person just has to wait for the appropriate time to cross.
-
Connected Citizens Program - Recommend changing “submitted to WME directly by Waze staff” to “entered in WME directly by Waze staff or the CCP’s employees.”
-
Usernames and closures, recommend adding that in WME you can go to edit a RTC to see who entered the closure and who the last modified the closure (if applicable). Also a segment’s history shows who entered or removed a closure.
-
Recommend changing “If you do not have the required rank to access the Closure feature in WME” to “if you do not have the required rank to access the Closure feature in WME or the road segment(s) are locked above your ability to edit”. Not the If is changed to if since it is not the beginning of the sentence.
-
Recommend removing reference to the road closures form. No one uses it anymore.
-
Recommend changing “if the node ID has been moved” to “if the segment ID has been changed; by creating a new segment, changing the road direction, or too large of an adjustment to the road’s length/geometry.”
-
Recommend changing “For this reason, if you need to remove a segment or cut a segment in two, first place a Time based segment restriction on the segment, then apply the closure. …” to
"For this reason, if you need to remove a segment, first place a Time based segment restriction on the segment, then apply the closure. After the next tile update, the segment restriction will be active in the app. You can then remove the closure and and remove the segment.
“If you need to cut a segment in two, first place a Time based segment restriction on the segment. After the next tile update, the segment restriction will be active in the app. You can then cut the segment into two (or more segments). Remove the Time based segment restrictions from the applicable segment(s) that routing is allowed on and ensure the Time based segment restriction is on the segment to remain closed. After the next tile update, remove the Time based segment restriction and add a closure. This should allow you (after 2 or more tile updates) to limit a closure to a damaged bridge rather than being forced to apply it to a mile-long segment of road.”
-
For the “Editing closed segments” section, recommend changing to “Editing segments with closures”; this refers to just segments with RTCs and eliminates segments closed by TBSR or TBTR. Also remove “and junction node” since it is preventing changing the segment ID.
-
Recommend correcting the “{{rank|closure}” format in the MTE section.
-
For the “Report closure feature in the Waze app” recommend adding that editors of Rank 5 + will have their in app closures immediately applied to the app.
-
Recommend deleting "As of May 2015 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 the next section). " and the whole next section on the not set since it appears the 1969 date is in use and May 2015 is long past.