Author Topic: NC: US-52 exit numbers (between NC-66 & I-74)  (Read 1447 times)

0 Members and 1 Guest are viewing this topic.

Offline rickmastfan67

  • TM Collaborator (A)
  • Hero Member
  • *****
  • Posts: 1829
  • Gender: Male
  • Last Login:Today at 06:11:34 am
NC: US-52 exit numbers (between NC-66 & I-74)
« on: September 14, 2020, 07:34:40 pm »
With no change over to I-74 #'s in sight for quite a few years still, should we finally add the US-52 exit numbers to the file between "*NC66Con" & "I-74"?  Especially since we already have the exit numbers on US-52 between 84 & 116 in the file.

Offline rickmastfan67

  • TM Collaborator (A)
  • Hero Member
  • *****
  • Posts: 1829
  • Gender: Male
  • Last Login:Today at 06:11:34 am
Re: NC: US-52 exit numbers (between NC-66 & I-74)
« Reply #1 on: September 14, 2020, 07:54:29 pm »
Also, on a side note south of the former NC-66 interchange.

SprSt -> 108 or 108A (would need updated in US-311 & NC-8 too)
WauSt -> 108A or 108A_A (would need updated in US-311 & NC-8 too)
NOTE: those are the best solutions I can think of for this interesting quirk due to the split interchange ramps.

As for these two closed interchanges, since they did have #'ing posted before they were closed, I think it's safe to convert them as well instead of using the name of the road for the closed interchange.
*StaDr -> *108C (would need updated in US-311 & NC-8 too)
*4thSt -> *110A (would need updated in US-311 & NC-8 too)

Offline mapmikey

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1171
  • Last Login:Today at 02:58:32 pm
    • Co-curator Virginia Highways Project
Re: NC: US-52 exit numbers (between NC-66 & I-74)
« Reply #2 on: November 13, 2020, 10:54:59 pm »
Made changes except:

Did not change US 311 since it is going away
Did not change anything with the 108A situation.  A different solution would be to consolidate to one point labeled 108A and placed at the Waughtown St overpass

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4234
  • Last Login:February 13, 2024, 07:19:36 pm
  • I like C++
Re: NC: US-52 exit numbers (between NC-66 & I-74)
« Reply #3 on: November 17, 2020, 10:35:15 pm »
Did not change anything with the 108A situation.  A different solution would be to consolidate to one point labeled 108A and placed at the Waughtown St overpass
This looks appropriate.
Sri Syadasti Syadavaktavya Syadasti Syannasti Syadasti Cavaktavyasca Syadasti Syannasti Syadavatavyasca Syadasti Syannasti Syadavaktavyasca

Offline mapmikey

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1171
  • Last Login:Today at 02:58:32 pm
    • Co-curator Virginia Highways Project
Re: NC: US-52 exit numbers (between NC-66 & I-74)
« Reply #4 on: December 19, 2020, 10:20:05 am »
I enacted this solution and is in the queue

Offline Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 3075
  • Last Login:Today at 03:58:40 pm
Re: NC: US-52 exit numbers (between NC-66 & I-74)
« Reply #5 on: December 20, 2020, 12:43:15 pm »
One further question:  Did we want the US 52 exit numbers on I-74FutPil?

When it comes to US 311, I did not see any signage when I drove in the area on November 14th, but I can only account for I-40 and US 421 so I am not 100% confident on deleting it yet.
« Last Edit: December 20, 2020, 12:46:14 pm by Markkos1992 »

Offline rickmastfan67

  • TM Collaborator (A)
  • Hero Member
  • *****
  • Posts: 1829
  • Gender: Male
  • Last Login:Today at 06:11:34 am
Re: NC: US-52 exit numbers (between NC-66 & I-74)
« Reply #6 on: December 20, 2020, 01:29:16 pm »
One further question:  Did we want the US 52 exit numbers on I-74FutPil?

I would say no, since they are US-52 mileage ones, and we've only added numbers to 'Future Interstate' files when the exit numbers were based on the Future Interstate mileage.

Offline Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 3075
  • Last Login:Today at 03:58:40 pm
Re: NC: US-52 exit numbers (between NC-66 & I-74)
« Reply #7 on: March 21, 2021, 08:00:05 pm »
I do not believe that we have anything else to address here at this point.