Level 5 Unlocks - Ohio

[BlazeTool]

Trying to clean up the reverse connectivity & u-turns along the I-70 interchanges between Columbus and Springfield

Hilliard-Rome Rd
US-29
US-42
Rest Area
SR-54

Thanks in advance

[bz2012]

unlocked.

[BlazeTool]

It looks like US-42 was missed in the unlocks, it remains locked at 5

The following are done and ready to be relocked at 5 (currently locked at 3)
Hilliard-Rome Rd
US-29
Rest Area
SR-54

[GizmoGuy411]

Unlocked and locked as requested.

I'm not so sure that level 5 locks were necessary, as 3 should have been sufficient, but I locked them anyway.

Thanks for being to thorough with your request too.

It makes our lives easier.

[BlazeTool]

Done with US-42 also. One node only had 16 reverse connections.

[jondrush]

There is really no need for the split road over the highway, but it should be OK. Make sure you restrict the straight across movement from off-ramp to on-ramp so Waze doesn't route people off the highway, as it sometimes does.

[jhfrontz]

There is really no need for the split road over the highway, but it should be OK. Make sure you restrict the straight across movement from off-ramp to on-ramp so Waze doesn't route people off the highway, as it sometimes does.

In this case, he didn't split it-- the segments have existed for several years.

On the ramp-to-ramp "turn" restriction-- does that really still happen? I find those particular artificial restrictions to be jarring -- when I'm making scans across areas and see them I have to zoom in and check each segment to make sure that they're correct. The faux restrictions have been absent from central Ohio Interstate (and other) ramps for at least a year (if not longer) and I've never seen a misroute (or any URs regarding same).

Perhaps it only happens in places where there are perennial/predictable traffic jams (with average speeds slower than the ramps) on the adjacent freeways? If that's the case, I'd rather see the restrictions added as-needed rather than across the board.


Jeff

[GizmoGuy411]

I have been wondering about the false restrictions too. Never experienced an issue or handled a related UR where the restriction did not exist.

Do we need to revisit this, or is it the issue as Jeff described?
Sent from my Galaxy Nexus using Tapatalk 2

[jondrush]

I think you will find it much worse in areas where freeways curve hard. Thus the ramp is actually a shorter route.

[jhfrontz]

I think you will find it much worse in areas where freeways curve hard. Thus the ramp is actually a shorter route.

Are you actually running with "favor shorter distance over shorter time" set? If that's the case, then in the scenario you describe, taking the ramp is arguably the correct behavior.

In the default setting (favor shorter time), I would think that the average speed on the ramp would be dramatically lower and there would be the penalty of an intersection. After considering all that, if it is indeed still shorter time-wise to take the ramp, then -- again -- taking the ramp is arguably the correct behavior.

Do you have any [recent] examples of this happening?