sketch wrote:Rename this segment "US-131 N".

Waze has a detour prevention function that prohibits this sort of behavior, but it is not working here because the names of the two segments that bracket the detour do not have the same name. The prevention mechanism works with segments that have the same name and city name.

kodi75 wrote:Join this on-ramp segment directly to Pearl St NW at the beginning of the Scribner Ave junction and disallow traffic from the exit ramp to that on-ramp.

That's not a good idea -- then you won't get the "keep left" to get onto the freeway.

Thanks for the info, didn't know about this detour prevention mechanism in Waze, I've changed the segment so this should no longer happen.

Join this on-ramp segment directly to Pearl St NW at the beginning of the Scribner Ave junction and disallow traffic from the exit ramp to that on-ramp.

Rename this segment "US-131 N".

Waze has a detour prevention function that prohibits this sort of behavior, but it is not working here because the names of the two segments that bracket the detour do not have the same name. The prevention mechanism works with segments that have the same name and city name.

kodi75 wrote:Join this on-ramp segment directly to Pearl St NW at the beginning of the Scribner Ave junction and disallow traffic from the exit ramp to that on-ramp.

That's not a good idea -- then you won't get the "keep left" to get onto the freeway.

It's not well known, in fact, the global champs group didn't even know quite how it worked until a few days ago.

It also depends on city name—so if the freeway segments on either side of the ramp are in different cities, the prevention mechanism won't work. For that reason, some editors have been removing the city names from all freeway segments—since there aren't any addresses on freeways, the city it's in isn't really important.