Clinched Highway Mapping

yakra · Joined: 30 Jul 2008 Posts: 2600 Location: Area Code 207

I-20 BL (Abilene) is actually two separate business loops: one for Tye and one for Abilene.
A little similar to the (West) & (East) San Angelo US 67 business routes in close proximity.

I'll be submitting an update to split this apart into two separate loops:
TX I-20BLAbi I-20_W I-20(278) becomes I-20BLTye.
TX I-20BLAbi I-20(279) I-20_E stays I-20BLAbi.

Of the nine travelers affected by the change:
Six travelers, oscar_voss, dlee, 25or6to4, barefoot_driver, rlee & weathermiz have clinched the current route end to end. They will still show a 100% clinch of I-20BLAbi. However, if they've actually clinched the Tye segment, they'll have to enter that back into their lists separately.

jonfmorse: no 100% clinch; will still need to add in the TX I-20BLTye I-20_W I-20_E line

terescoj and klundgren only have the I-20(278) I-20(279) segment, the short concurrency with the parent stitching the two loops together. With this segment gone, their .lists will throw an error message. No big deal, their mileage here is still accounted for by their clinches of that part of I-20. The TX I-20BLAbi I-20(278) I-20(279) .list file line can be cut out as dead weight.

oscar_voss · Joined: 27 Jul 2008 Posts: 622 Location: Arlington VA

When I was there a few years ago, the Abilene and Tye BL(s) struck me as weird, but decided not to suggest the change being proposed now, because of how the ramps to/from WB I-20 overlap (the off-ramp to the Tye segment is well east of the on-ramp from the Abilene segment). But if TxDOT treats them as separate routes, so should we.

I've already added the new TX I-20BLTye I-20_W I-20_E line to the local copy of my list file.

yakra · Joined: 30 Jul 2008 Posts: 2600 Location: Area Code 207

Changes are in the HB.