VA: US 1/US 301 ALT/VA 36 in Petersburg

[Markkos1992]

This is posted separately from my other US 1/US 301 thread as I expect there to be discussion on this one.

This is a thread I have wanted to create for a while (arguably since 2003 but Petersburg's posting continues to be unclear).  This is specifically regarding the traffic patterns in Petersburg.  Note that the 2018 VDOT Traffic Logs do not reflect this, which is why I had not posted this previously. 

US 1/US 301 ALT:
1.  These routes are not posted as turning onto Jefferson St anymore, but they are posted as turning at Adams St.  The ALT label is only shown on Adams St southbound at Washington St here.
2.  While the US 1 TRUCK route still looks legitimate based on the shields, the only US 1 SB shield left following the VA 36/Market St route is facing VA 36 EB traffic now.  I am interpreting US 1 TRUCK SB as US 1 SB at this point.

Basically, I believe that these two routes should be relocated to follow Adams St now.  This would result in the following changes:

US 1:
VA36Trk_W http://www.openstreetmap.org/?lat=37.224771&lon=-77.415408 (was just VA36Trk, this should also be changed on US 460 BUS (Petersburg))
VA36_W http://www.openstreetmap.org/?lat=37.226446&lon=-77.406498
US301Alt_S http://www.openstreetmap.org/?lat=37.227091&lon=-77.403038
US460Bus_E +US1Trk_S http://www.openstreetmap.org/?lat=37.227385&lon=-77.401487
US301_S +US1Trk_N http://www.openstreetmap.org/?lat=37.232310&lon=-77.402920
VA36Bol http://www.openstreetmap.org/?lat=37.232682&lon=-77.403064 (also would be added to US 301)


US 301 ALT:  (Part of me also wants to suggest adding a point at Graham Rd due to the I-95 connection, but I do not see that as truly necessary especially with Southside Regional Medical Center moving to the southern end of the city at least 5-10 years ago now.)
US1_S http://www.openstreetmap.org/?lat=37.227091&lon=-77.403038
US460Bus_E +US1Trk http://www.openstreetmap.org/?lat=37.227385&lon=-77.401487
US301_N +US01_N http://www.openstreetmap.org/?lat=37.232310&lon=-77.402920

Other label revisions including demoting the existing US1_N points at Jefferson St (JefSt) would need to be done in the VA 36 and US 460 BUS (Petersburg) files.

As seen below, the current US1_S point on US 301 would need to become 3rdSt.

VA 36:

I am proposing a new route be created for VA 36 WB here.  (was done for PA 61 TRUCK in Sunbury for different directions)  Note that graph connections should still be added at US 301 and US 1 (see this thread on PA 116 in Hanover).

I would call it VA36Bol (for Bollingbrook St) and have the following coordinates:
VA36_W http://www.openstreetmap.org/?lat=37.232754&lon=-77.407168  (MarSt on VA 36 would need to be edited)
SycSt_S http://www.openstreetmap.org/?lat=37.232558&lon=-77.404867
US301_N http://www.openstreetmap.org/?lat=37.232682&lon=-77.403064
3rdSt http://www.openstreetmap.org/?lat=37.232757&lon=-77.401477
BolSt_E http://www.openstreetmap.org/?lat=37.234582&lon=-77.395034
VA36_E http://www.openstreetmap.org/?lat=37.229901&lon=-77.391504 (at Crater Rd and Washington/Wythe St, will affect VA 36, may affect US 301 and US 460 BUS (Petersburg))

Note that some NMPs will most likely be created on the north end of Petersburg as a result.

Let the discussion begin...

EDIT:  One other note on US 460 BUS (Petersburg), I would change I-95 to I-95(52) and I-95Con to I-95(50A).

[mapmikey]

Petersburg signing practices are terrible...

I am not convinced about US 1 SB following the US 1 Truck routing.  There is also this assembly showing them running differently - https://goo.gl/maps/JhsH2wsGbGrvND1ZA

If US 1 SB still runs with VA 36 west, then in addition to creating a VA 36 separate file there should also be a US 1 version.  Plus adding US 1 Truck.  Plus extending VA 36 Truck further east than is in the HB currently.

Incidentally, shouldn't the VA 36Bol file be done with waypoints the opposite direction since that is the direction of travel for VA 36 west?

Weirdly, the 2004 (last issue by VDOT) Chesterfield County map shows 301 ALT moved to Adams but shows US 1 on Jefferson.

[Markkos1992]

Petersburg signing practices are terrible...

Alone why I held off on even moving this to discussion for so long.  I remember seeing US 1 NB still being posted as going north on Jefferson St for quite a few years even though older GSV does not seem to show it.

I am not convinced about US 1 SB following the US 1 Truck routing.  There is also this assembly showing them running differently - https://goo.gl/maps/JhsH2wsGbGrvND1ZA

I remember the Market St signage being shown from VA 36 WB for a while as well citing your case, but I again could not see it on older GSV surprisingly.   

Otherwise, I think that having US 1/US 301 ALT centered on Adams St covers all situations here.  (including the lack of needing a new US 1 TRUCK, no normal traveler heading south into Petersburg is going to head west to Market St to get to Wythe St)

Incidentally, shouldn't the VA 36Bol file be done with waypoints the opposite direction since that is the direction of travel for VA 36 west?

I would support that.  Does anyone else know of another situation in the HB similar to this? 

[mapmikey]

changes made and sent in...hopefully I got it all

[Markkos1992]

It looks good to me.  There are NMPs that will need to be added to nmpfps.log as I predicted.

[Markkos1992]

I put FPs in datacheck.fps for the self-reference errors for VA36Bol(https://github.com/TravelMapping/HighwayData/pull/3458).

This should stay open for now until I look through all of the many other VA NMPs that are still lurking around.

[Markkos1992]

va.us001@US301_S 37.23231 -77.40292
va.us001@VA36Bol 37.232682 -77.403064
va.us001@US301_S 37.23231 -77.40292
va.va036bol@US301_N 37.232682 -77.403064
va.us001@US301_S 37.23231 -77.40292
va.va036trkpet@VA36_E 37.232682 -77.403064
va.us001@VA36Bol 37.232682 -77.403064
va.us301@US1_S 37.23231 -77.40292
va.us001@VA36Bol 37.232682 -77.403064
va.us301altpet@US301_N 37.23231 -77.40292
va.us001@VA36Bol 37.232682 -77.403064
va.va036trkpet@US301_S 37.23231 -77.40292
va.us301@3rdSt 37.232361 -77.401428
va.va036bol@3rdSt 37.232757 -77.401477
va.us301@US1_S 37.23231 -77.40292
va.va036bol@US301_N 37.232682 -77.403064
va.us301@US1_S 37.23231 -77.40292
va.va036trkpet@VA36_E 37.232682 -77.403064
va.us301altpet@US301_N 37.23231 -77.40292
va.va036bol@US301_N 37.232682 -77.403064
va.us301altpet@US301_N 37.23231 -77.40292
va.va036trkpet@VA36_E 37.232682 -77.403064
va.va036bol@US301_N 37.232682 -77.403064
va.va036trkpet@US301_S 37.23231 -77.40292
va.va036trkpet@US301_S 37.23231 -77.40292
va.va036trkpet@VA36_E 37.232682 -77.403064

These NMPs are all FPs and will not be included in my email.

However, US 301 should have a point at VA36Bol to fix the now broken concurrency with US 1 that I did not notice until now.

[mapmikey]

This last fix is done and in the queue

[Markkos1992]

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

The NMPs being added to nmpfps.log should finalize this thread.