gettingthere wrote:There is recent information from Waze staffer krankyd that may quash this so call '5 second penalty' in regards to junctions and routing. I guess it depends on how you interpret:
http://www.waze.com/forum/viewtopic.php ... 55#p141955
"Working on excessive nodes is indeed painful, but that's not the most important things to get your maps closer to perfection (an additional node has its affects, but routing is not one of them)"
He also continued to say: "There's a minor penalty for crossing a node, but when there are no other options in the node, it's null".
I assume node = junction. I think he's saying that a node connecting only 2 segments will have no penalty (null), which is good to know, but I think all other nodes/junctions that have 3 or more connected segments will still have a penalty (which I thought was 5 seconds, what does he mean by minor penalty? ).
I still think it's possible for routing to be affected by several junctions (three-or-more-segment-junctions) along a route, causing it to pick a route that is not really faster. For example, travelling up a minor highway crossing 10 junctions that have side streets would add a "minor penalty" for each junction (5 seconds each?), even if those junctions are controlled by center turn lanes and not traffic lights. So routing may take you off the highway sooner if the math through the neighborhood is better (even if by only seconds, I think).
I think it's true that from the map editor's perspective, junction delays/penalties do not really matter since there is nothing else we can do to help routing anyway, when there are correct junctions along the route (especially if extra junctions/nodes that only connect 2 segments do not introduce a penalty), but it's still frustrating because we get URs related to routing that we as map editors can not fix or influence.
I hope I'm making sense. I'm really just trying to understand what options we have as map editors to help resolve route-related user reports that seem to be caused by the routing algorithm, not map errors.