Author Topic: NY/CT: Point observations  (Read 1601 times)

0 Members and 1 Guest are viewing this topic.

Offline Duke87

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 939
  • Last Login:Yesterday at 10:48:52 pm
Re: NY/CT: Point observations
« Reply #15 on: August 22, 2022, 07:08:38 pm »
Looking at I-84, based on where ramps go and how exits are numbered now:
- 22 should move east to South Main St
- 23 should be 22A
- 23A can therefore just be 23 (separate ramp to Washington St we can 1PPI out of consideration)
- there simply isn't an exit 24 anymore. The point currently labeled 24 should therefore be 25, since that's what the exit going there is actually numbered
- which means current 25 needs to be 25A
- buuuut there is already a different unrelated exit actually numbered 25A so... gah.

Leaving 24, 25, and 25A as is may be therefore the path of least resistance even if it's nominally "wrong". But I'd still tweak it west of there.

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4234
  • Last Login:February 13, 2024, 07:19:36 pm
  • I like C++
Re: NY/CT: Point observations
« Reply #16 on: October 29, 2022, 11:18:05 am »
Older east-coast urban stuff like this tests the 1PPI bounds of "What exactly is one interchange?", with its unconventional layouts and overlapping or widely spaced partial interchanges.
Sometimes it's good to look closely at the ramps' physical layout, more so than the exit numbers.

- 22 should move east to South Main St
IMO the current placement does a good job of capturing the offramps in both directions, as well as the onramp from Bank St.
The WB Exit 22 onramp OTOH can be 1PPIed in with the Exit 23 complex.

- 23 should be 22A
- 23A can therefore just be 23 (separate ramp to Washington St we can 1PPI out of consideration)
Both 23 & 23A are in use, so I'm hesitant to make changes here.
An argument can be made that 23 is still appropriate here.

Edit: I almost wanna slide the 23 point E to better align with the ramps on the N side of the highway (S side, we essentially have a big-ol' service road; the ramps don't merge back in until after an at-grade intersection @ CT69), but that would start to interfere with the CT69 trace on mapview so I'll just leave it alone.

- there simply isn't an exit 24 anymore. The point currently labeled 24 should therefore be 25, since that's what the exit going there is actually numbered
Vague memory here, maybe I noticed the 25 & 25A mess when making the previous edits for this thread, and decided the historic Exit 24 was a "good enough" fudge for this location? Or maybe not!
Either way, I agree, it's Exit 25, and begs for a change.

- which means current 25 needs to be 25A
- buuuut there is already a different unrelated exit actually numbered 25A so... gah.

Leaving 24, 25, and 25A as is may be therefore the path of least resistance even if it's nominally "wrong". But I'd still tweak it west of there.
Luckily these labels are all unused so changes can be made here with less hassle.
25B would fit the "the next available letter suffix" by my reading, even if it's a little clunky by being out of alphanumeric sequence.
This has almost certainly happened elsewhere, though I can't think of an example off the top of my head.
In any case, we've plenty of cases of exit numbers out-of-sequence due to goofy numbering from a DOT, or weird interchange layouts.
I'm fine with 25, 25B & 25A.
« Last Edit: October 30, 2022, 05:31:49 pm by yakra »
Sri Syadasti Syadavaktavya Syadasti Syannasti Syadasti Cavaktavyasca Syadasti Syannasti Syadavatavyasca Syadasti Syannasti Syadavaktavyasca

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4234
  • Last Login:February 13, 2024, 07:19:36 pm
  • I like C++
Sri Syadasti Syadavaktavya Syadasti Syannasti Syadasti Cavaktavyasca Syadasti Syannasti Syadavatavyasca Syadasti Syannasti Syadavaktavyasca