is now said to be obsolete. We are under the impression that waze has adjusted the routing (possibly the small detour mechanism) to prevent U-turns. So now we can enable U-turns in the editor.ottonomy wrote:First, there is no doubt that Waze does occasionally include U-turns at the ends of single two-way segments in its routing, when the turns are enabled in WME, and it has a compelling reason to do so. It seems to me almost as if there is some light penalty attached to this, because of the relative rarity of the occurrences.
If the penalties for routing U-turns when enabled in the editor are not sufficient to prevent U-turns (or if the real-time server fails implements a lesser penalty or applies no penalty) then I think we will be causing problems by enabling U-turns prior to the proper addition of a U-turn instruction to the routing instructions.ottonomy wrote:U-turns under other conditions are more frequent for me. Not common, but not exactly rare. I speculated in my previous post that Waze may assess a penalty when considering a U-turn (on an un-split road), such that the routing server will consider other options first. Let me explain what makes me think this. The likelihood that I will be given a U-turn in my route goes up exponentially with the heaviness of the traffic around me. I never get them when driving in the late evening, or in more remote, less crowded areas.
Between 4 and 6PM, there are parts of LA where streets in close proximity to the freeways become so gridlocked that it can literally take 15 to 30 minutes to traverse a single city block, and it's times and places like these when Waze is most likely to throw me a U-turn, rather than sending me around the block, like it usually would. in other words, instances which might overcome penalties.
sketch wrote:U turns should not be seen at all in routes. If it happens, staff wants to know. Staff wishes, last I heard, are that we leave U turns enabled as they should be, and to report them to staff if they are used despite the massive penalty that's supposed to make them not be given.
sketch wrote:So maybe it's a real time vs. normal routing server problem.
voludu2 wrote:stephenr1966 wrote:"normal routing server" = server that computes your route when first ask for navigation.
"real-time server" = server that (re) calculates your route due to deviations or real-time impending traffic.
It is probably actually the same server (or server farm)...but, different algorithms with different applications of the penalties.
DwarfLord wrote:There's a fair bit of discussion on it in the WME v1.6 release - (v169) release thread.
Users browsing this forum: No registered users