Sloppy geometry...

[failsafe]

Got it. Remember reading and following it before. For some reason, I'd thought I'd seen that was no longer necessary.

Not sure where I hallucinated that, but that is not a good thing.

Re-read everything, taking another day off for it to sink in. Do no harm...

[failsafe]

Not to belabor the point, but I see this a lot on these adjusted intersections.

https://www.waze.com/editor/?lon=-87.71 ... 4,15021643

User Report shows user intending to go south on Kimball, and then take a left onto Milwaukee, but getting routed to take the right on Woodward and then a left on Milwaukee.

Is it a coincidence?

[ArlenBystander]

I doubt the extra geometry nodes added to bring the intersecting roads closer to 90 degrees is the cause for that routing. Most likely it's Waze thinking one route is faster than the other. Either there is missing/incorrect speed data for one or both routes or there was a backup on Kimball at the time the driver travelled through there.

Both routes appear to be valid; it's just that the offered route wasn't the route the driver wanted to take. Until Waze has better data about the offered route, it will keep choosing it as long as it looks better than the alternate(s).

A possible reason for these types of reports on adjusted intersections - at least in Chicago - could be a result of less-popular routes (with no or out-of-date traffic info) being offered where angled roads such as Milwaukee cut through a mostly NSEW grid system.

[bigbear3764]

I'll have to take a look when I get to a PC.

EDIT: Ok, look to see what I did with the turn restrictions here:
https://www.waze.com/editor/?lon=-87.71 ... s=15079673

I left the turns from Milwaukee, but I restricted some left turns to increase the penalty for taking a route that Waze seems to think is faster. I have seen quite a few of these when there are 3 streets crossing to create a triangle. See if this stops this from happening, or we may need to restrict the right from Milwaukee to Woodard also. I know these turns are allowed, it's just that people generally don't take them because they know it's not the easiest way to go.


Sent from my iPhone using Tapatalk

[crazycomputingdotnet]

Just to further the point here is another example that looks like it is sloppy zoomed all the way in, but because of the angles of the roads you do not get a keep left/right instruction at this intersection. I had to add a little extra node bit and angle the other roads to get this to work. It took me a couple of months to tweak and fine tune it so you don't get a turn instruction or no instruction.

https://www.waze.com/editor/?zoom=10&lo ... TTTFTTTTFT

I drive this road every day on my way home from work and in the client you can not tell that this is here.

[jemay]

Just to further the point here is another example that looks like it is sloppy zoomed all the way in, but because of the angles of the roads you do not get a keep left/right instruction at this intersection. I had to add a little extra node bit and angle the other roads to get this to work. It took me a couple of months to tweak and fine tune it so you don't get a turn instruction or no instruction.

https://www.waze.com/editor/?zoom=10&lo ... TTTFTTTTFT

I drive this road every day on my way home from work and in the client you can not tell that this is here.

Am I missing something from your description for the landmark item.

There is a little stub under here to allow a keep left for I-44 W. ...

Do you mean right?

[crazycomputingdotnet]

Yup. Good catch. Left looking North, right going the right way on it.