Wow!
[ img ]
Of course, by this post, I've ruined it. Sorry!
Moderators: Unholy, bextein, Glodenox, JustinS83
turbomkt wrote:Here's why Waze can get confused - regardless of whether turn restrictions are set or they are one way segments, Waze can choose either segment to route across if it's a two segment loop. I have seen this first hand and will never leave a two segment loop - Waze routed the wrong way on a one way segment.
jm6087 wrote:In addition to my previous point, we have to remember that Waze goes from node to node, not segments. Using your example:
You have the WB segment (ID 365705604) with Node A 287525221 and Node B 287452950
You have the EB segment (ID 365705605) with Node A 287452950 and Node B 287525221
Since Waze goes node to node, If I have heading WB and I reach Node 287525221 and the app is trying to get me to Node 287452950, how does it know which segment to take? It is my understanding that it is not actually looking at which direction a one-way segment is going, it only knows that you can go from Node 287525221 to Node 287452950. It is possible that it will take you down the wrong one-way segment to complete your trip.
In reality, by having the 2 segment loop with one-way segments, you are creating 2 two-way segments by mistake.
vince1612 wrote:I'm more than familiar with it, thus why I gave you my first response. It also says that "every loop must be made up of three or more segments" and to "correct two-segment loops".
IMDashti wrote:jm6087 wrote:In addition to my previous point, we have to remember that Waze goes from node to node, not segments. Using your example:
You have the WB segment (ID 365705604) with Node A 287525221 and Node B 287452950
You have the EB segment (ID 365705605) with Node A 287452950 and Node B 287525221
Since Waze goes node to node, If I have heading WB and I reach Node 287525221 and the app is trying to get me to Node 287452950, how does it know which segment to take? It is my understanding that it is not actually looking at which direction a one-way segment is going, it only knows that you can go from Node 287525221 to Node 287452950. It is possible that it will take you down the wrong one-way segment to complete your trip.
In reality, by having the 2 segment loop with one-way segments, you are creating 2 two-way segments by mistake.
I was okay with you until you asked "how does it know which segment to take?" After that, your answer seems very confusing in regard to the situation presented. If it got to Node 287525221, there's only one way to get to Node 287452950, how can Waze get confused?! How is it possible that it will take me to the wrong one-way segment if there's only one-way to go?!! In other words, I see one option for Waze to route me from Node 287525221 to Node 287452950, which is through the WB one-segment. What is the other routing option for Waze that will make it confused?!
And when you say "you are creating 2 two-way segments by mistake", I don't get it!! Excuse me for not understanding, but please explain how is that?!!
IMDashti wrote:If turn is enabled for one direction to only one segment, how can Waze route through another segment?!!
...
when segment direction and turn arrows are put in consideration, there's no loop. Show me the loop!!
vince1612 wrote:That is a 2-segments loop, loops should never be less than 3 segments (minimum). Red/green arrows or the segments' directions don't matter. The editor who contacted you is right.
iainhouse wrote:Waze can get confused because the client does not know if the segments are one way, or if the turns are disabled.
The route given by the routing server to the client is a list of nodes. If part of that route includes 2 consecutive nodes that have more than one segment connecting them, there is no way to be sure (from our point of view) which segment will be chosen. Turn arrows are irrelevant - the client doesn't do the routing (as long as the network connection is up), the routing server does. The client does what it's told and doesn't double-check to see if the route it is given is valid. After all, by definition, the server will be more up-to-date than cached client map data.
This can lead to the client directing the user along the "wrong" segment. It can even lead to the audible instructions saying to take one route, whilst the display on-screen shows the other route. This has been reported by users.
It can also, if the client makes a report, lead to a UR in which the route follows one course whilst the instructions displayed for the route are for the other course.
It's really not worth a lot of argument.2-segment loops have demonstrably caused problems in the past. Toolbox highlights them for that reason. Adding an extra node certainly does no harm whatsoever. If you really don't want to add an extra node, then don't. Sooner or later, someone else using Toolbox will come along and do so.
ditchi56 wrote:Toolbox not appearing at all on current WME Beta
Not too worried about the Beta itself, but presumably whatever new Beta feature is messing it up may appear in main WME.
Return to Addons, Extensions, and Scripts
Users browsing this forum: G_W1Z, Google [Bot], Google Feedfetcher, ldriveskier, Leorenaud