Author Topic: VA NMPs  (Read 1853 times)

0 Members and 1 Guest are viewing this topic.

Offline Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 3075
  • Last Login:Today at 06:35:18 am
VA NMPs
« on: January 09, 2020, 08:11:14 pm »
Quote
dc.us029@VA/DC 38.901153 -77.070508
va.gwmempkwy@US29 38.900736 -77.070583
va.gwmempkwy@US29 38.900736 -77.070583
va.us029@VA/DC 38.901153 -77.070508

Sync US 29 and the GW Pkwy here and mark resulting NMPs as FP.  In the meantime, we should determine a consistent label to use for the GW Pkwy.  (I see at least three different variations just by looking at Spout Run Pkwy, US 29, and US 50.)

Quote
va.i095@170 38.791205 -77.174824
va.i395@1 38.791206 -77.174828
va.i395@1 38.791206 -77.174828
va.i495@170(95) 38.791205 -77.174824

I-395 needs to be synced with I-95 and I-495 here. 
Note: You could argue that I-95 (177C) and I-495 (I-95(177C)) could be synced with VA 400 (removing ChuSt).

Quote
va.i095@166 38.740327 -77.189856
va.va286@I-95 38.740394 -77.189877

VA 286 needs to be synced with I-95 here. 
Note 1:  Should a point be added for the on-ramp from Heller Rd (to I-95 NB via the HOT Lanes NB Exit, wow this is odd)?
Note 2:  I was not planning to bring back the 168 issue, but based on how we have moved forward, it should probably be changed to VA289.

Quote
va.va007@FaiLn 39.186032 -78.160166
va.va007@PicSt 39.185632 -78.160654

FPs.  Though in reality, FaiLn, PicSt, or both points could just be removed without any harm (neither are in use).  If kept, PicSt should be EastLn.

Quote
va.va003@VA205_E 38.181968 -76.997573
va.va205@VA3_E 38.182103 -76.997788

VA 205 needs to be synced with VA 3 here.

Quote
va.us017busfre@US17_N 38.340443 -77.492065 LI
va.us017@I-95(133) 38.340444 -77.492065 LI
va.us017busfre@US17_N 38.340443 -77.492065 LI

US 17 BUS needs to be synced with US 17 and I-95 here. (even though they look intentional)

Quote
va.us001busfre@US17Bus_S 38.297961 -77.458549
va.va002@US1Bus_S 38.297945 -77.458527
va.us017busfre@US1Bus_S 38.297961 -77.458549
va.va002@US1Bus_S 38.297945 -77.458527

VA 2 needs to be synced with US 1 BUS and US 17 BUS. 
Note 1: The points just to the east for LafBlvd should be LafBlvd_E on VA 2, US 1 BUS, and US 17 BUS.
Note 2:  VA 2 needs to have the point DixSt added from US 17 BUS to fix the broken concurrency.

Quote
va.va178@VA180_N 37.630454 -75.814108
va.va178@VA180_S 37.630658 -75.81378
va.va178@VA180_N 37.630454 -75.814108
va.va180@VA178_N 37.630658 -75.81378
va.va178@VA180_S 37.630658 -75.81378
va.va180@VA178_S 37.630454 -75.814108
va.va180@VA178_N 37.630658 -75.81378
va.va180@VA178_S 37.630454 -75.814108

FPs, though the VA 180 points on VA 178 should be W and E instead of N and S.

Quote
va.us013@VA182 37.58567 -75.785086
va.va182@MainSt 37.585436 -75.784754
va.va182@MainSt 37.585436 -75.784754
va.va182@US13 37.58567 -75.785086

FPs

Quote
va.i064@200 37.521061 -77.27088
va.i295@28A 37.520959 -77.270923

I-295 needs to be synced to I-64 here.

Quote
va.us060@VA5_W 37.271184 -76.688937
va.va005@+x21 37.271248 -76.689194
va.va005@+x21 37.271248 -76.689194
va.va005@US60Wil_E 37.271184 -76.688937

FPs, but +X21 is unnecessary IMO.

Quote
va.i295@41 37.644956 -77.413702
va.us301@I-295 37.644955 -77.413704
va.i295@41 37.644956 -77.413702
va.va002@I-295 37.644955 -77.413704

I-295 needs to be synced with US 301 and VA 2 here.

Quote
va.i064@177 37.655456 -77.605062
va.i295@53 37.655524 -77.605104

I-64 needs to be synced to I-295 here.

Quote
va.i064@186 37.586622 -77.474599
va.i195@I-64 37.586648 -77.474502

I-195 needs to be synced to I-64 here.

Quote
va.i095@82 37.613586 -77.445159 LI
va.us301@I-95(82) 37.613586 -77.44516 LI
va.i095@82 37.613586 -77.445159 LI
va.va002@I-95(82) 37.613586 -77.44516 LI

US 301 and VA 2 should be synced with I-95 here with the point moved to the north inside of I-95.

Quote
va.us060@VA195 37.536113 -77.438743
va.va195@US60 37.536087 -77.438786

US 60 may as well be synced with VA 195.

Quote
va.va147@VA150 37.545232 -77.553129
va.va150@VA147 37.545241 -77.553155

VA 150 should be synced with VA 147.
(Note 1: ThrChopRd on VA 147 should be ThrChoRd.)
(Note 2: Should I-195 have a graph connection with VA 147?)

Quote
va.us360busame@VA38 37.342987 -77.981354
va.va038@VirSt 37.34262 -77.981338
va.va038@US360Bus 37.342987 -77.981354
va.va038@VirSt 37.34262 -77.981338

FPs, though VirSt on VA 38 should be VirSt_S.

Quote
va.us060@I-64(243) 37.236752 -76.634735
va.va143@I-64(243) 37.23706 -76.634617

FPs, though the VA 143 point should be moved onto the route by the on ramp by VA 143 WB.  This could eliminate the NMP.  (Unrelated, but should the route be flipped?)

Quote
va.i064@264 37.031782 -76.377339
va.i664@1 37.03178 -76.377342

I-664 needs to be synced with I-64 here.

Quote
va.i295@3 37.192664 -77.327871
va.us460@I-295 37.192665 -77.327873

US 460 needs to be synced with I-295 here.

Quote
va.i064@284 36.845113 -76.196408
va.i264@14 36.845113 -76.196365

I-264 needs to be synced with I-64 here.

Quote
va.i264@8 36.836218 -76.287732
va.i464@6B 36.83622 -76.287735
va.i464@6B 36.83622 -76.287735
va.us460altnor@I-264(8) 36.836218 -76.287732
va.i464@6B 36.83622 -76.287735
va.va337@I-264(8) 36.836218 -76.287732

I-464 needs to be synced with VA 337, US 460 ALT (Norfolk), and I-264 here.

Quote
va.i064@291 36.762817 -76.268077
va.i464@1 36.762817 -76.26812
va.i464@1 36.762817 -76.26812
va.us017@I-64(291) 36.762817 -76.268077
va.i464@1 36.762817 -76.26812
va.va168@15A 36.762817 -76.268077

I-464 needs to be synced with I-64, US 17, and VA 168 here.

Quote
va.i064@299 36.788013 -76.398196
va.i264@I-64/664 36.787567 -76.39785
va.i064@299 36.788013 -76.398196
va.i664@15 36.788013 -76.398193
va.i264@I-64/664 36.787567 -76.39785
va.i664@15 36.788013 -76.398193

I-64, I-264, and I-664 all need to be synced with each other here.

Quote
va.va165@VA168Bus_N 36.716368 -76.239034
va.va168busche@VA165_W 36.71638 -76.239023

VA 165 needs to be synced with VA 168 BUS here.  Even though it does not show up on the NMP list, the same thing needs to be done for the following:
Quote
va.va165@VA168Bus_S 36.713362 -76.238283
va.va168busche@VA165_E 36.712662 -76.238121

Quote
va.i095@52 37.22862 -77.395592 LI
va.us460buspet@I-95(52) 37.228619 -77.395592 LI
va.i095@52 37.22862 -77.395592 LI
va.va036@I-95 37.228619 -77.395592 LI

US 460 BUS and VA 36 need to be synced with I-95 here.

Quote
va.i095@50B 37.216112 -77.383962
va.us301@I-95(50B) 37.21611 -77.383965
va.us301@I-95(50B) 37.21611 -77.383965
va.us460@I-95(50B) 37.216112 -77.383962

I-95 and US 460 need to be synced with US 301 here.

Quote
va.i095@45 37.14188 -77.356153
va.us301@I-95(45) 37.14188 -77.356155

I-95 needs to be synced with US 301 here.

Quote
va.i095@41 37.081476 -77.358298
va.us301@I-95(41) 37.081474 -77.358299
va.i095@41 37.081476 -77.358298
va.va035@I-95 37.081474 -77.358299

I-95 needs to be synced with VA 35 and US 301 here.  (the point here in general should be slightly recentered)

Quote
va.i095@17 36.766701 -77.47344
va.us301@I-95(17) 36.766701 -77.473442

I-95 needs to be synced with US 301 here.

Quote
va.i095@11 36.702593 -77.549443
va.us058@I-95 36.702595 -77.549446

I-95 needs to be synced with US 58 here.

Quote
nc.nc168@VA/NC 36.55053 -76.192798
va.va168@NC/VA 36.550569 -76.192846

VA 168 needs to be synced with NC 168 here.  Also I think NC 168 should be flipped.

Quote
va.va042busday@VA257_N 38.412366 -78.941016
va.va042busday@VA42_W 38.412088 -78.940582
va.va042busday@VA257_N 38.412366 -78.941016
va.va042har@VA257/42Bus 38.412088 -78.940582
va.va042busday@VA257_N 38.412366 -78.941016
va.va257@VA42_N 38.412088 -78.940582
va.va042busday@VA42_W 38.412088 -78.940582
va.va257@VA42Bus_N 38.412366 -78.941016
va.va042har@VA257/42Bus 38.412088 -78.940582
va.va257@VA42Bus_N 38.412366 -78.941016
va.va257@VA42Bus_N 38.412366 -78.941016
va.va257@VA42_N 38.412088 -78.940582

FPs, though VA42_W and VA42_E on VA 42 BUS and VA42Bus_E on VA 42 should be changed to S and N.

Quote
va.va341tow@+X001 37.361085 -78.868371
va.va341tow@+X002 37.361435 -78.868338
va.va341tow@SR613_N 37.361554 -78.869411
va.va341tow@SR613_S 37.36117 -78.869454

FPs.

Quote
va.us221@OraSt 37.338193 -79.496802
va.va122@OraSt 37.338227 -79.496807

US 221 needs to be synced with VA 122.

Quote
va.va311@+x55 37.534798 -80.235718
va.va311@PotMouRd 37.53442 -80.235472
va.va311@+x60 37.537665 -80.270872
va.va311@SR602 37.537959 -80.271102

The shaping points here can probably be removed.  I did not check in the WP Editor if they are within tolerance.

Quote
va.us220busroc@VA40_E 37.001173 -79.890132
va.us220busroc@VA40_W 37.001533 -79.890572
va.us220busroc@VA40_E 37.001173 -79.890132
va.va040@US220Bus_N 37.001533 -79.890572
va.us220busroc@VA40_W 37.001533 -79.890572
va.va040@US220Bus_S 37.001173 -79.890132
va.va040@US220Bus_N 37.001533 -79.890572
va.va040@US220Bus_S 37.001173 -79.890132

FPs

Quote
va.us360@VA304 36.697552 -78.888144
va.us501trksou@VA304 36.697526 -78.888273
va.us501trksou@VA304 36.697526 -78.888273
va.va304@US360 36.697552 -78.888144

US 501 TRUCK needs to be synced with US 360 and VA 304 here.

Quote
va.va293@VA413 36.588039 -79.390377
va.va413@VA293_N 36.587574 -79.390133
va.va293@VA413 36.588039 -79.390377
va.va413@VA293_S 36.588345 -79.390559

VA 413 needs to be synced with VA 293 here with VA293_S and VA293_N as alternate labels if in-use.

Quote
va.us058busstu@VA8Bus_S 36.641281 -80.265684
va.va008busstu@US58Bus_E 36.641295 -80.265625

VA 8 BUS needs to be synced with US 58 BUS here.
Nearby US58BusStu_E on US 58 BUS also needs to be synced with US 58.

Quote
va.us460taz@VA83_E 37.278936 -82.100605
va.va083@US460_W 37.278953 -82.100605

US 460 needs to be synced with VA 83 here.

Quote
va.i081@3 36.624311 -82.181125
va.i381@1 36.624276 -82.181125
va.i381@1 36.624276 -82.181125
va.us058@I-81(3) 36.624311 -82.181125

I-381 needs to be synced with I-81 and US 58 here.

Also the I-81 point should be ComAve (presuming that VA 381 is not posted anymore and is not in the HB for that reason).

Quote
va.us023busnor@VA78 36.906838 -82.781993
va.va078@MainSt 36.906477 -82.781703

VA 78 should be synced with US 23 BUS (Norton).  I am unsure if the NMP will still exist then or not.

Quote
va.va070@+x1 36.62726 -83.070475
va.va070@+x2 36.627449 -83.070615
va.va070@+x19 36.657269 -83.072455
va.va070@SR617 36.657201 -83.072315
va.va070@+x3 36.63271 -83.061442
va.va070@+x4 36.632934 -83.061388

There probably should be some shaping points removed here.

Quote
va.us058@US58BusEwi_W 36.630579 -83.45718
va.us058busewi@SR687 36.630131 -83.456901
va.us058busewi@SR687 36.630131 -83.456901
va.us058busewi@US58_W 36.630579 -83.45718

FPs




Offline mapmikey

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1171
  • Last Login:Today at 06:18:24 am
    • Co-curator Virginia Highways Project
Re: VA NMPs
« Reply #1 on: February 13, 2020, 09:59:54 pm »
I have gone through all these and made the changes.

Assuming I didn't skip anything or make any mistakes, the remaining NMPs should all be FPs.

Note that in removing shaping points on VA 70 and VA 311 this creates SA errors that are FPs.

in the queue...

Offline Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 3075
  • Last Login:Today at 06:35:18 am
Re: VA NMPs
« Reply #2 on: February 15, 2020, 08:44:41 pm »
I should have everything clarified here within the next couple days.  (First round of FPs can be seen here: https://github.com/TravelMapping/HighwayData/pull/3596)

NMPs missed:
1.  I-395 still needs to be synced with I-95 and I-495 at the Springfield Interchange.
2.  I-95 and VA 289 still need to be synced with each other.
3.  VA 2 still needs to be synced with US 1 BUS and US 17 BUS.
4.  I think that removing +X21 on VA 5 would eliminate the NMP with US 60.
5.  I am not sure if I missed this or not, but VA 165 needs to be synced with VA 337.

Other Thoughts Not Directly Related To NMPs:

Clarifying George Washington Memorial Pkwy current labels:
GeoWasPkwy: VA 123, US 29, I-66, VA 233, VA 400
GWMemPkwy: Spout Run Pkwy
GWPkwy: US 50

It looks like we should go with GeoWasPkwy moving forward for consistency. 

Other GW Pkwy Notes:
1.  I am fine with leaving TurRunPk as-is though I have presumed that Pk is for "Pike" instead of Park.
2.  The line on the GW Pkwy does cross the river between VA 123 and the Spout Run Pkwy.
3.  I do not think I can justify a graph connection with VA 233, but I am surprised that it is even posted.

Other Notes:
1.  VA 147: ThrChopRd should be ThrChoRd.
2.  VA 42 BUS (Dayton):  I missed that VA257_N should be VA257_W and the VA 290 points should be E and W instead of S and N.  (This is not in the NMP FP update for that reason.)
 
« Last Edit: February 16, 2020, 07:18:36 pm by Markkos1992 »

Offline mapmikey

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1171
  • Last Login:Today at 06:18:24 am
    • Co-curator Virginia Highways Project
Re: VA NMPs
« Reply #3 on: April 19, 2020, 07:33:22 pm »
changes made and in the queue

Offline Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 3075
  • Last Login:Today at 06:35:18 am
Re: VA NMPs
« Reply #4 on: April 20, 2020, 04:13:49 pm »
I finished updating the NMP FPs and added a new Datacheck FP for VA 5.  Ultimately this is complete.

https://github.com/TravelMapping/HighwayData/pull/3782