I recall reading some opinions on this that seemed to indicate a decision had been made, but maybe it was just wishful thinking.kentsmith9 wrote:I recall many threads discussing this, but I don't recall a final recommendation. I think this thread could spawn that decision here or in a related thread. If it was decided, I missed it in my search and I don't recall it getting into the Wiki yet. We should note that some restrictions are for commute traffic flow control and some are for other reasons. I know one road in my area is no right turn during late hours when most people are not around. Otherwise the majority of traffic is allowed. Shall we play it safe and say No turn if "ever" restricted even if only for 3 hours on a weekday?mapcat wrote:Waze does not support time based restrictions, so if it's not allowed for a specific time frame, then it's not allowed.
No, it can still happen. Check the script thread in the champs forum. Pretty sure Brian pointed out how.1. I thought Reverse Connectivity was a thing of the past that we did not have to contend with any more based on what I thought I was reading in the Known Issues list. Maybe I am wrong and we need a whole section on Map Troubleshooting with that in there. (Next topic.)
Someone else will correct this if I'm wrong, but I'm pretty sure that W alone only enables turns. Something wrong has to be disabled first. The problem of reverse connectivity goes back to the penalties. No left turn is a penalty and so is one-way. If Waze is considering routing you the wrong way down a one-way street, the one-way penalty might not be enough in every case.2. Your description of what W does on its own is a little different than what I thought Alan had previously told me. I also realize I did not include my understanding of that function. So based on what you wrote and what I thought, here is what I propose we add to the General Section with what we have already on QW:Frankly the Reverse Connectivity issue really seems like a bug in the navigation router that should be fixable. It appears to be causing very significant problems and effort to fix at the map level with millions of junctions where the routing code could do a better job at understanding what is currently "active" for that segment or junction like we see on the map. Maybe I still don't fully understand the problem in the first place.
- Pressing only the W shortcut (without the Q first) only turns any soft or hard restrictions to hard enabled turns. It does not convert any soft enabled turns to hard enabled turns. Also, with previously drawn "one-way" or "no entrance" roads using the older Cartouche map editor, there may be soft or hard enabled turns for the opposite direction of travel that are not visible on the map, but can effect traffic routing. Therefore it is best to always press Q just before using W on all segments where you are using the W shortcut. The Waze development team is considering adding this functionality to the operation of the W key to simplify matters (date TBD).
Re: Documenting Soft and Hard Turns