Author Topic: NC: US 311, NC 700, and Other Nearby Point Concerns  (Read 1480 times)

0 Members and 1 Guest are viewing this topic.

Online Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 3075
  • Last Login:Today at 06:52:43 pm
NC: US 311, NC 700, and Other Nearby Point Concerns
« on: March 21, 2021, 01:00:42 pm »
1.  The US52_N alternate label may be removed as it is not currently in-use.
2.  A point should be added at MLKDr_S (where US 311 turns off MLK Dr to New Walkertown Rd).
3.  Adding a point at 14thSt should then be good to eliminate the shaping point around 8th St.
4.  NC66Wal should be just NC66.
5.  I was debating on whether FaggRd would be a solid point to replace the shaping point between DenRd and NC65_W.  However, FaggRd would be great to add to NC 65 to replace a nearby shaping point.  (What happened to NC 65 in OSM?  Who knows.....)
6.  BentPlaRd should be RidRd (Ridge Rd).
7.  MadDillRd should be MadDilRd.
8.  The shaping point between US220Bus/704 and US220/704 could be replaced by a point at Mineral Springs Rd (MinSprRd) or be removed. (also affects US 220 BUS (Madison) and NC 704, removing it gets rid of a sharp angle error)
9.  (Side Note for US 220 BUS (Madison) and NC 704 only) I would change MarSt to MarSt_N and DecSt to DecSt_W.
10.  The shaping point between US220/135 and SetBriRd should be replaced with a point at StoMouRd (Stone Mountain Rd).  (also affects NC 135)
11.  The shaping point east of SetBriRd should just be removed.  (also affects NC 135)
12. (NC 135 only) I would change NC770 to US311/770.
13.  It is interesting that the NC770 label here is NC87/14.  I am unsure how I am for doing that for US 311.  (Using NC14/87 would create a duplicate label error (maybe multiple)) 
14.  A point should be added at MainSt to replace the nearby shaping point to the east.  (also affects NC 770)

NC 700:
1.  DunnSt should be removed as it is not in-use.
2.  The shaping point near MainSt should instead be a point at MainSt.
3.  I would add a point at Quesenberry Rd (QueRd) as the route is close to going out of tolerance here.
4.  Not a change, but Happy Home School Rd reminds me of SR 619 (Happy Hill Rd) in Chesterfield County, Virginia.  I have been on Happy Hill Rd a few times over the years.

NC 14/NC 87
1.  A point should be added at Aiken Rd (AikRd) to replace the nearby shaping point (unless you get obsessed with the mapview line making river crossings like myself).
2.  SR1700 should be FisHillRd (Fisher Hill Rd).
3.  (NC 14 only) OldUS158Bus can be removed as an alternate label as it is not currently in-use.
4.  (NC 87 only)  NC210_S, SanByp_S, BurDrv, SanByp_N, NC100_N, NC100_S, and NC700/770 can be removed as alternate labels as they are not currently in-use.  I will most likely start a new thread specifically related to the BraBlvd point.

Routes to edit along I-74 due to the US 311 truncation to Winston-Salem:

NC 66: US311_S should be I-74.  US311_N should be just US311.  (Side Note:  It is odd to me that there are no "TO US 311 NORTH" shields on NC 66 at Main St south of Walkertown.)
I-85BL (Lexington, NC)/US 29/US 70: I-74/311 should be just I-74.
US 220 BUS (Asheboro, NC):  Was US311Ext US 311 at some point?  I would like for OldUS311 to be the solution here.  Secondly (but not highly important), I am tempted to recommend replacing the shaping point north of here with a visible one at Providence Church Rd (ProChuRd).

EDIT: Added unused alternate labels for NC 87 that were previously only in-use by me.
« Last Edit: March 22, 2021, 08:24:35 am by Markkos1992 »

Online mapmikey

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1171
  • Last Login:Today at 06:53:11 pm
    • Co-curator Virginia Highways Project
Re: NC: US 311, NC 700, and Other Nearby Point Concerns
« Reply #1 on: March 21, 2021, 01:50:56 pm »
US311Ext is the actual street name.  And it was US 311 until 1972 when the US 220 freeway was opened to the US 311 exit.

Online Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 3075
  • Last Login:Today at 06:52:43 pm
Re: NC: US 311, NC 700, and Other Nearby Point Concerns
« Reply #2 on: March 24, 2021, 01:42:53 pm »
US311Ext is the actual street name.  And it was US 311 until 1972 when the US 220 freeway was opened to the US 311 exit.

I was using the below quote in the manual, but since US311Ext is the road name, you are not forced to go OldUS311.

Quote
   If the old highway has a posted name that mentions the old designation, then applying the above rule will result in a label like OldUS40 for "Old Route 40" if the route was formerly US 40.

Online mapmikey

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1171
  • Last Login:Today at 06:53:11 pm
    • Co-curator Virginia Highways Project
Re: NC: US 311, NC 700, and Other Nearby Point Concerns
« Reply #3 on: August 19, 2021, 07:57:05 pm »
I think I got everything in here...lot of side bars in this one

Online Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 3075
  • Last Login:Today at 06:52:43 pm
Re: NC: US 311, NC 700, and Other Nearby Point Concerns
« Reply #4 on: August 31, 2021, 10:41:40 am »
Speaking of sidebars, NC 66 is fine label-wise, but I just realized that the route should be flipped.

NC 14/NC 87:  It looks like the new AikRd point is at the wrong intersection.

NC 135:  The shaping point east of SetBriRd needs to be removed to fix the now broken concurrency with US 311.

Otherwise everything else was covered.

Online mapmikey

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1171
  • Last Login:Today at 06:53:11 pm
    • Co-curator Virginia Highways Project
Re: NC: US 311, NC 700, and Other Nearby Point Concerns
« Reply #5 on: September 17, 2021, 05:02:58 pm »
corrections made