Just a quick explanation of what I did here in case anybody comes across it and thinks it looks funny and needs fixing.
I connected the north one of the two ramps directly to the Fort Edmonton Park Road intersection and disabled the left turn. This is to encourage the routing engine to route people on the south ramp if they are heading for Fort Edmonton.
It looks like this new south ramp was built just for this purpose, so motorists don’t have to merge onto Fox and then cut across two lanes in less than 100 m. Although this manoeuvre is legal, it’s safer and less stressful to take the south ramp.
I think I saw that a couple weeks ago… And it was more likely to cause routing problems.
I had changed it so that it was set up exactly as it exists… Because otherwise drivers will also miss the instruction to turn on the road that goes S -> N.
Also, it’s best to let the routing engine decide what is best… If it is quickest to take the N ramp, so be it!
I don’t understand what you mean here. With the way I’ve done it, there will be “Stay to the right to Nature Centre / Fort Edmonton Pk” followed by “Make a left at 142 St.”
In most cases I would agree with you, but in this case, Waze won’t automatically learn about problems using the north ramp: If a driver has a problem cutting across the lanes, he won’t stop and wait for a gap. He’ll grumble and curse and drive straight through the intersection and look for a place to turn around. To Waze, that’s just a driver not following directions. The only data it collects is the turning time of those who cut across successfully. Waze won’t learn anything from those who fail to make the cut-across.
I just had a chance to look at what you had done… it looks ok. What I had imagined was how it was set up before – both ramps had gone directly to that intersection node… and that isn’t how the southern ramp works at all.
