Author Topic: TN 137 is signed  (Read 914 times)

0 Members and 5 Guests are viewing this topic.

Offline mapcat

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1794
  • Last Login:Yesterday at 11:03:13 pm
Re: TN 137 is signed
« Reply #15 on: January 01, 2025, 01:02:14 pm »
But US-23 isn't ramps officially.
And 36 is north of 346?
What you're calling 36 is what I'm calling the ramps connecting 36/346 to 23 (and concurrent 137). Users who want to map their travel from the 36/346 junction north to Virginia would add the segment of 23 and/or 137 to their files.
Clinched:

Offline neroute2

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1166
  • Last Login:Yesterday at 09:42:38 pm
Re: TN 137 is signed
« Reply #16 on: January 01, 2025, 01:47:25 pm »
But US-23 isn't ramps officially.
And 36 is north of 346?
What you're calling 36 is what I'm calling the ramps connecting 36/346 to 23 (and concurrent 137). Users who want to map their travel from the 36/346 junction north to Virginia would add the segment of 23 and/or 137 to their files.
I'm asking if that part of 36 is officially ramps. If not, the official status of 137 doesn't matter because we're not following official ramp status.


Offline neroute2

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1166
  • Last Login:Yesterday at 09:42:38 pm
Re: TN 137 is signed
« Reply #17 on: January 01, 2025, 01:56:37 pm »
Time to clear it up. According to TDOT, 36 and 137 are both non-ramps to the state line. In addition, the northernmost 0.04 mi of 36 is US 23.

Offline mapcat

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1794
  • Last Login:Yesterday at 11:03:13 pm
Re: TN 137 is signed
« Reply #18 on: January 01, 2025, 03:57:55 pm »
TDOT is not calling that segment ramps. I am.
Clinched: