WeeeZer14 wrote:Be careful with changing things to not be ramps. In some situations a ramp is the only way to force the client to give a navigation instruction. So if you have a fork and only one is a ramp, you may only get an instruction when you go on the ramp and Waze will remain absolutely silent if you go the other way. And no, having a different name won't help.
Wajo357 wrote:WeeeZer14 wrote:Be careful with changing things to not be ramps. In some situations a ramp is the only way to force the client to give a navigation instruction. So if you have a fork and only one is a ramp, you may only get an instruction when you go on the ramp and Waze will remain absolutely silent if you go the other way. And no, having a different name won't help.
Exactly... that is why I'm trying to undo that and make sure it does give the proper voice navigation to both right & left.
WeeeZer14 wrote:8.) We should not go from ramp to street to ramp. It will break long distance routing. If the only problem is "keep right" vs. "exit right", that is too minor to worry about.
WeeeZer14 wrote:9.) I can't find the specific segment you are talking about. That segment ID isn't in the view you permalinked.
WeeeZer14 wrote:10.) I updated the split to what I know works. A few of us Champs are discussing and testing if we need to go this far to ensure instructions. In my experience, I think we do. (I also tweaked some of your geometry. It doesn't need to be perfect by any means, but your curves should be a little more smooth )
daknife wrote:The Exit right and Stay right instructions are also affected by they angle of the turn, less than 45 degrees will say "Keep right" or "Exit Right" More than 45 degrees will give a "Turn Right" command. So some of us will zoom all the way in and put a geometry node right next to the connection point to create a false 90 degree turn. I usually to this on right turn lanes to avoid ramp like instructions. It also helps avoid the keep left instructions just to go straight down the freeway. Put that micro dogleg at the beginning of the ramp and it will give the "Exit Right" command but say nothing about keeping left.
Here is an example. I'd been getting UR's about users being told to keep left when passing this interchange, so I installed a micro-dogleg and the UR's stopped. Zoom out and you can see how it looks like a normal off ramp.
Otherwise WeeeZer14 is 100% right on, but then he's been editing a few months longer than I.
Hmm... the permalink works for me. You'll see the highway split.
2) Based on my table above, your route will create a voice command of "Exit Left/Right", option C above. I believe if you look at the street view, the best approach should probably be E (as I stated above) (as these don't appear to be technically 'exits'). You can see an example of what I did with E here:
https://www.waze.com/editor/?zoom=7&lat ... TTTTTTTTFT
The regular road was named "State Rte 4" and it didn't say "Keep Left..." when I reached the fork. By changing the left name to simply "State Rte 4W", Waze sees that all 3 names are different, but the road types are the same, so it will use "Keep Left/Right". And now the voice directions are perfect when I go through those exits/splits.
Users browsing this forum: Baidu [Spider], Yahoo [Bot]