This isn’t really an unlock request, but more of an I’m at my wit’s end request and could use some extra eyes and some help here. Don’t worry about the major highway next to the freeway, that’s something different and I don’t think that it the issue (it was a minor highway for awhile), but in this link, there are two URs complaining about the same thing. There is one more further south all saying that Waze wants them to exit the freeway (which is tolled), drive on the major highway (free), then get back onto the freeway. The freeway is brand new just opened about this time last year, while the major highway has been there for eons. I remember seeing a few URs when the freeway first opened, and I contributed those to being a new road that Waze hadn’t learned yet. Fast forward to now and Waze is still not getting it right. I’ve check all of the nodes, I’ve checked for double layers, I can’t find anything wrong.
Is there an algorithm problem here? Do I need to kick this higher up the Waze chain and have them look at it? This is the only highway in the US with the 85mph speed limit, so I know it’s not a matter of speed between the two highways.
Forgive the ignorance of a novice here, but I assume you’ve ruled out the obvious error of a user selecting the option to avoid tolls and then driving on a toll road. I could see how WAZE could easily get “confused” about whether the user was on the highway or the freeway and ask them to exit occasionally when the two roads gap, and it is more apparent the users is on the toll road.
I would assume that ,if it didn’t route them back onto the highway. The entire freeway is marked as a toll road. It’s not sectioned out between toll and non-tolled. It’s been like that since the beginning.
Is it strictly a southbound issue? The permalink given is at a specific southbound (SB) off ramp from 130 to 183, is that one of the problem areas? As dumb as it sounds, I do see the SB 130 road switches from A->B to B->A through there, but it’s all still southbound. One other thought… Does the system use the order of road placement or joining in the algorithm calculations? In other words, would it be worth deleting all ramps in the questionable sections, re-drawing the toll road, then adding the ramps anew? I know I’ve read about junction or joins corruptions in other areas.
Looking at your permalink, pepperidge, I see the similar scenario as txemt. The prior southbound section is oneway (B->A), the Ramp is the same oneway (B->A), but the SH-45 section is oneway (A->B). Yes both are still southbound based on the direction they were placed, but is it possible that given the option of two southbound paths, it takes the most similar?
If I select a segment of sh-45 and Select Entire Street, I only get a few more sections and it indicates Multiple Directions, yet it is a oneway freeway.
Quite frankly, I’m a little confused why there are options for both oneway (A->B) and oneway (B->A). Seems like flow would ALWAYS be A->B, unless its two-way, and the cartographer (editor) should draw it accordingly.
Just some thoughts from the novice, as I learn more WAZE to the truth.