OH: OH 13 in Mount Vernon

[Markkos1992]

Since OH 13 NB does not actually seem to be concurrent with US 36/OH 229, I think a point should be added at the Chestnut St/Sandusky St intersection to replace the existing US36_W.  I think the rest of the area seems to be mapped fine.

[mapcat]

The choice seems to be between northbound 13 drivers gaining a false concurrency with 36/229, or southbound 13 drivers losing a true concurrency with 36/229. Neither solution is great, but I don't see one being obviously better than the other, which tips the scale to no-build in my opinion. Am I missing something?

[Markkos1992]

Basically yes, in this scenario, I would prefer no concurrency with US 36/OH 229 for OH 13 though YMMV.

[mapcat]

I'm genuinely curious, not trying to be difficult: how is this adversely affecting your stats/maps?

[Markkos1992]

Right now, none.

However, I am planning to pass through the area on US 36 next month when heading to the Springfield Meet.  Based on me looping to clinch OH 768 and OH 308, I would be getting OH 13 NB between OH 229 and US 36, but I had not anticipated following OH 13 NB from there to Sandusky St (though I easily could and thought about doing that as I typed this).

It is probably best to gain more feedback on this particular item. (though who knows when yakra will return).

[mapcat]

True, the easiest solution would just be a quick round-the-block. But I can see how it's annoying that the system doesn't handle irregular one-way pairs particularly well.

[osu-lsu]

Another reason to go with no-build.
ODOT is going to reroute Oh 13 around downtown Mt. Vernon next year.
https://mountvernonnews.com/stories/671007435-odot-approves-5-6-million-grant-for-sr-13-relocation

[mapcat]

Perfect. Thanks. I'll keep an eye on it.