Author Topic: VA/WV US 50 not lined up + VA/DC: I-66 Not Lined Up with US 50  (Read 1348 times)

0 Members and 1 Guest are viewing this topic.

Offline mapmikey

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 512
  • Last Login:Yesterday at 10:47:34 pm
    • Co-curator Virginia Highways Project
Re: VA/WV US 50 not lined up + VA/DC: I-66 Not Lined Up with US 50
« Reply #15 on: May 20, 2019, 09:17:02 pm »
fixed and submitted

Offline Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 789
  • Last Login:Yesterday at 07:53:52 pm
Re: VA/WV US 50 not lined up + VA/DC: I-66 Not Lined Up with US 50
« Reply #16 on: January 06, 2020, 06:43:40 pm »
Resurrecting this thread because I actually now agree with mapmikey on the I-66 "76" point.

In my opinion, the "76" point should just be put under VA/DC.  VA/DC on both I-66 and US 50 should be moved to the southeast slightly.  We can debate on whether there should be a GWPkwy point synced with I-66, but the I-66(76) point on US 50 should be put under VA/DC as well. 

In DC, I would still change US50 on I-66 to US50_E and I-66 on US 50 to I-66_E.


In the meantime for US 50:
1.  NBraSt should be BraSt_N.  SBraSt should be BraSt_S.  (in Winchester)
2.  FairOak should be changed to FairOaks.  FairOaksMall IMO would go against the three-word rule since Mall is not a road abbreviation.
3.  FairPkDr should be FaiParkDr.
4.  CHRd should be CouHouRd since Court House Rd is two words here.
5.  QueenSt should be QueSt.

Also for VA 110, is PenAccRd correct?
« Last Edit: January 06, 2020, 08:27:16 pm by Markkos1992 »

Offline froggie

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 512
  • Last Login:Yesterday at 05:47:59 pm
Re: VA/WV US 50 not lined up + VA/DC: I-66 Not Lined Up with US 50
« Reply #17 on: January 10, 2020, 11:40:55 pm »
Quote from: Markkos1992
Also for VA 110, is PenAccRd correct?

Much to my surprise, it's actually not.  I'm guessing Mike got that from OSM because that's what OSM calls it.  But both Arlington County GIS and the Pentagon's Transportation Management Plan call it "Connector Road".

Street blades on each end call it "South Parking Conn.".  From my own time at the Pentagon, neither name is really in general use.  Given the official sources mentioned above, I'd use ConRd.

Offline mapmikey

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 512
  • Last Login:Yesterday at 10:47:34 pm
    • Co-curator Virginia Highways Project
Re: VA/WV US 50 not lined up + VA/DC: I-66 Not Lined Up with US 50
« Reply #18 on: January 11, 2020, 11:30:00 am »
This predates my involvement in TM.  Oddly there is no sign on VA 110 itself telling you what the offramp is for.

I will change this to ConRd when I do the VA NMP changes...

Offline mapmikey

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 512
  • Last Login:Yesterday at 10:47:34 pm
    • Co-curator Virginia Highways Project
Re: VA/WV US 50 not lined up + VA/DC: I-66 Not Lined Up with US 50
« Reply #19 on: January 12, 2020, 11:52:13 am »
Resurrecting this thread because I actually now agree with mapmikey on the I-66 "76" point.

In my opinion, the "76" point should just be put under VA/DC.  VA/DC on both I-66 and US 50 should be moved to the southeast slightly.  We can debate on whether there should be a GWPkwy point synced with I-66, but the I-66(76) point on US 50 should be put under VA/DC as well. 

In DC, I would still change US50 on I-66 to US50_E and I-66 on US 50 to I-66_E.


In the meantime for US 50:
1.  NBraSt should be BraSt_N.  SBraSt should be BraSt_S.  (in Winchester)
2.  FairOak should be changed to FairOaks.  FairOaksMall IMO would go against the three-word rule since Mall is not a road abbreviation.
3.  FairPkDr should be FaiParkDr.
4.  CHRd should be CouHouRd since Court House Rd is two words here.
5.  QueenSt should be QueSt.

Also for VA 110, is PenAccRd correct?

I made all the changes.  Here is what I did with US 50/I-66 at the Potomac River:

US 50: Made 76 an alt name for the VA/DC point
US 50: Deleted the I-66(76) point
I-66: Moved the 76 point to sync with the GW Pkwy point, made 76 an alt name for it

In DC, I added a point on both I-66 and US 50 where they diverge before reaching Virginia

While making the DC/VA line point more accurate per the post above, I also made the US 50 and I-66 coordinates slightly different so that there would be no concurrency at the boundary line.  This will almost certainly create a FP NMP

Offline Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 789
  • Last Login:Yesterday at 07:53:52 pm
Re: VA/WV US 50 not lined up + VA/DC: I-66 Not Lined Up with US 50
« Reply #20 on: January 12, 2020, 02:56:17 pm »
Quote
While making the DC/VA line point more accurate per the post above, I also made the US 50 and I-66 coordinates slightly different so that there would be no concurrency at the boundary line.  This will almost certainly create a FP NMP

Looking at the updated list, you are correct on that.