Strange routing behavior, but cannot find a map issue

[AlanOfTheBerg]

Since the edits were long enough ago that this should be live, I'm going to suggest this is because of the 'prefer goodie munching' option. Try sending them a PM to ask if that is case and to suggest turning it off if so.

EDIT: Bah, beat me to it.

[AlanOfTheBerg]

It doesn't really matter where the goodies are. What that option appears to do is reduce or nearly eliminate routing penalties so that it takes you all over the place. It's been proven to cause the ignoring of explicitly defined turn restrictions (as opposed to the basemapped turn restrictions which haven't been edited yet) and 1-way street directionality. It really is a mess and should be removed altogether. It was useful when very few roads had been driven and verified and there were actually a lot of roads which needed to be munched. These days, in populous areas, it doesn't serve a useful purpose.

[AlanOfTheBerg]

The user that reported this error checked his munching preference setting, it was OFF.

Any chance he did have it enabled 5 days ago?

[AlanOfTheBerg]

I don't think it is a setting issue. It is reproducable on the live map.

Grrr... Well, I would do what likely isn't optimal, but sometimes must be done: delete all the segments around that intersection and rebuild it from scratch.

At the same time this segment shouldn't have the u-turn portion enabled, which is contributing to this being a valid route. To be a good-functioning intersection there, a segment of parking lot road should be added, otherwise this segment is mostly just about allowing u-turns in both directions.

[CBenson]

Other than the standard are you sure that prefer munching is turned off, I can't explain this route.

[CBenson]

I don't think it is a setting issue. It is reproducable on the live map.

[DonJ2]

I'm starting to see more cases of this strange routing behavior, personally and through URs...

In this example, a left turn from Saint Jones Pkwy to Rinehart Rd is the fastest route (see permalink), but waze tells the user to turn right, then make a u-turn to end up on Rinehart Rd travelling the desired direction.

https://www.waze.com/map-editor/?zoom=5 ... 3,61650664

I cannot find any map issues to explain this behavior, even after looking at the segment times in cartouche. Can anybody find an issue to explain this?

Thanks,
Don

[DonJ2]

Thanks guys, I'll contact the user to see if that's possibly the issue. There may actually be some goodies in the "u-turn" segment since it's not connected to any side streets.

Whenever I have personally seen such behavior, it has not been because of munching preference, I have it disabled in my client. Next time it happens to me, I'll send a map error to record it.

[DonJ2]

Well if it works like that, I hope they remove it soon. We've got enough problems to deal with, and don't need help creating even more. I like munching goodies, but I've never seen the need for this "feature", and have never used it.

Sent from my DROID RAZR using Tapatalk

[DonJ2]

The user that reported this error checked his munching preference setting, it was OFF.

Sent from my DROID RAZR using Tapatalk