VA: Various Point Concerns Starting 4/21/2022

[Markkos1992]

Note that there will be plenty of edits to this post.

I-64:  Recommend adding a shaping point between 10 and 14 to keep the line south of US 60.

US 19:  EarBraRd should be slightly relocated.  (also affects US 460)

US 21:  US58/221_N>-US58/221

US 29:  The OakRidRd label here and the SR653 label on VA 56 should be the same if possible for consistency.

US 29 BUS (Danville):
1.  The VA293 labels should be switched if possible.  (I will be using VA293_N for now, but I will update my list file if this is changed.)
2.  ParkAve should be PieDr.
3.  Is there a concurrency with VA 86?  I did not think so officially, but your VAHighways Page indicates one.

US 29 BUS (Altavista):  SR668>-PitAve (I did not see any SR 668 shields.)

US 29 BUS (Lynchburg):  LibUnivDr>-LibUniDr

US 33:  I would personally like a point at Erickson Ave (west of VA 42) as I want to drive Erickson Ave between US 33 and VA 42 in the event that it somehow becomes part of VA 280.  (I do not need this point anymore because I actually clinched it west to SR 613.)

US 58: 
1.  US21/221_S>-US21/221
2.  VA89Trk should be VA89Trk_S.  (also affects US 221)
3.  SR707 could have a point due to signage for VA 392 being here. (also affects US 221)
4.  OakRidFRd needs to be shortened (if correct).

US 58 BUS (Danville):
1.  If possible, the VA51_E and VA51_W labels should be switched.
2.  ParkAve should be PieDr.

US 221: 
1.  US21/58_N>-US21/58
2.  Note that the Lynchburg Meet today indicated that the realignment west of Old Forest Rd at the College Lake Dam will be open next month.  The new alignment is already shown on OSM.
3.  LakDr>-MonAve

US 360: 
1.  OilHillWay should be OliHillWay_N.
2.  CooLanRd>-IndValRd

US 460 BUS (Lynchburg):  SR682>-LeeRd

VA 3 BUS (Fredericksburg):  Consider replacing the shaping point south of VA 212 with a visible point.

VA 7:  VA420>-JanLa (presuming VA 420 is still completely unposted)

VA 20: 
1.  Should a point be added at the entrance to James Madison's Montpelier?
2.  The VA20Bus labels should really be S and N instead of W and E.  (also affects the VA20 labels on VA 20 BUS (Orange))
3.  The shaping point east of VA20Bus_E should be replaced with a visible point at SR 629.

VA 39:  The VA42 points should be S and N instead of W and E.

VA 42 (Harrisonburg):
1. VA269>-VA269_E or SR632
2.  Replacing the shaping point east of VA39_W with a visible point at SR640. (also affects VA 39)

VA 61:
1.  A graph connection is missing at the US 19/US 460 interchange.
2.  I did not see a road around where we have SR613 at.
3.  I-77(64)>-I-77

VA 67:  Should there be a graph connection at the US460 point with US 460?

VA 71:  Consider replacing the shaping point between US58Alt_E and GrayFarmRd with a visible point at SR614.

VA 80:  The VA83 labels should be W and E instead of S and N.

VA 82:  This route should be flipped.

VA 163:  RivBlvd>-RivAve

VA 165: VA192>-AzaGarRd

VA 166:  VA168>-VA168_S.

VA 168 BUS (Chesapeake): 
1.  HarRd>-HanRd.
2.  VA165_E>-VA165_N.  VA165_W>-VA165_S.

VA 170: VA192>-AzaGarRd   (I do anticipate to clinch clinched unsigned VA 192 on 4/28/2022.)

VA 200: 
1.  A point should be added at SR 688 due to the VA 3 Truck prohibition in Kilmarnock.
2.  Consider replacing the shaping point north of SR607 with a visible point.

VA 228:  The LRS Route Overlap map and the 2020 Traffic Data conflict on whether VA 228 still goes through Downtown Herndon or uses the west side of the truck route (which is also signed as SR 606 TRUCK).  Presuming that VA 228 stays as-is for now:

1. SR606>-SteRd (I did not see any SR signage inside the Herndon Pkwy.)
2. MonSt>-MonSt_S

VA 228 TRUCK (Herndon): 
1.  SumRd>-SumDr
2.  Maybe replace the shaping point east of VA228_N with a visible point at Worchester St (WorSt).
3.  Maybe change SR675 to SprSt.  I am unsure on this one because I do not want the SR606 labels to be changed (see above on VA 228).
4.  MonSt_N>-MonSt.  MonSt_S>-VanBurSt.

VA 230:  SR613 should be slightly relocated.

VA 244:  Do we still need the ColPike label since it was not truncated?

VA 269:
1.  VA42>-SR632
2.  Add a shaping point between the two existing shaping points to keep the line fully south of I-64/US 60.
3.  I-64(34)>-I-64(35)

VA 286:  KinRd should be JohnKinRd.

VA 290:  The VA42Bus labels can be changed to S and N instead of W and E, but I would argue that it is not enforceable since VA 42 BUS has no direction banners.

VA 293:  VA360>-VA360_E

VA 311:  Craig County GIS indicates that NatForRd and PotMouRd may be incorrect.

VA 311 (Crows):  Consider replacing the shaping point south of VA159 with a visible point.

VA 392: While I wonder how much of this should be here, there was construction going on here when I clinched it so its days may or may not be numbered.  It is posted for now.

[Markkos1992]

US 11: 
1.  Consider changing SR609 to HilHwy.  I am unsure if SR 609 makes it to US 11.
2.  Consider changing SR730 to WasAve.  I am unsure if SR 730 makes it to US 11.
3.  MainSt should be RifDr (Rifton Dr).
4.  BraAveSW>-BraAve_E.
5.  10thStSW should probably be 10thSt or 10thSt_XXX.

Newer point concerns as of 6/21/2022:

I-785 FUT (Danville):  US58/360_E>-US58/360

US 29: 
1.  Consider replacing the shaping point north of US29BusCha_N with visible point(s).
2.  US250/250Bus_W should be US250/250Bus.
3.  Note point suggestions from I-66 Express Lanes thread (https://forum.travelmapping.net/index.php?topic=4739.msg26409#msg26409).
4.  TreSt>-ThoSt

US 221: 
1.  MulAllRd should really be BarSt or SR615.
2.  I recommend replacing CouHomRd if possible.
3.  The shaping point east of CouHomRd should be relocated.

VA 43: 
1.  SR628_N and SR723 should be slightly relocated.
2.  Consider replacing the shaping point north of OttHillRd with a visible point.

VA 130: 
1.  It looks like SR635 needs to be majorly relocated.
2.  Is there a good replacement for CraDr?

[mapmikey]

Changes made and sent.

I elected to reroute 228 over the west half of 228 Truck which matches gis and what Herndon formally requested

I elected not to do anything with VA 244.  More thought needed.  While the trolley project that prompted relinquishing 244 was cancelled,  I have seen no evidence VA 244 was actually taken back into the system.  GIS shows it ending at the Arlington line, plus a second segment west off of the eastern VA 27 interchange a short distance.  These segments match the 2020 traffic data

[Markkos1992]

VA 244 is still signed from VA 120 SB.  While VA 244 was barely signed in Arlington County beyond that sign and the VA 27 interchanges, I think this is best considered as a no-build (except for moving or replacing the ColPike label).  I feel similar about VA 237 east of VA 120.  In fact, I thought VA 237 was better signed east of VA 120 than west of VA 120 towards US 29. (hence why I wonder if you jumped the gun on truncating VA 237)

VA 228 was not posted through Herndon or south of the truck route so I have no issue with moving forward with the relocation. 

US 360:
1.  OilHillWay should be OliHillWay_N.

Definitely still seeing OilHillWay_N here instead of OilHillRd_N.

VA 61:  I am seeing BenBoltAve instead of BenBoltLn.

VA 67:  Is it me or is the SR806 point "just a bit outside"?  The line should also be south of US460 west of US460_W.

VA 228 TRUCK (Herndon):  SR606_E>-SR606 or changing SR606>-SR606_W on VA 228.  (with SR 606 TRUCK being posted on Herndon Pkwy I am unsure if SR 606 still goes through the center of Herndon)

[dave1693]

VA 228 was not posted through Herndon or south of the truck route so I have no issue with moving forward with the relocation. 

VA 228 TRUCK (Herndon):  SR606_E>-SR606 or changing SR606>-SR606_W on VA 228.  (with SR 606 TRUCK being posted on Herndon Pkwy I am unsure if SR 606 still goes through the center of Herndon)

Well, we don't track Virginia SRs (because that way lies madness, even though they are state maintained and signed and would add LOTS of miles to my list) so for tracking purposes it's a moot point. However, I will be back in Herndon tomorrow and/or Monday and will check all the signage in town. (My stay in PA was extended due to multiple parental medical issues. And if next week my dad isn't improved from this week, we're calling the doctor. Having aging parents sucks, even if it beats the alternative, which it currently does.)

[Markkos1992]

VA 228 was not posted through Herndon or south of the truck route so I have no issue with moving forward with the relocation. 

VA 228 TRUCK (Herndon):  SR606_E>-SR606 or changing SR606>-SR606_W on VA 228.  (with SR 606 TRUCK being posted on Herndon Pkwy I am unsure if SR 606 still goes through the center of Herndon)

Well, we don't track Virginia SRs (because that way lies madness, even though they are state maintained and signed and would add LOTS of miles to my list) so for tracking purposes it's a moot point. However, I will be back in Herndon tomorrow and/or Monday and will check all the signage in town. (My stay in PA was extended due to multiple parental medical issues. And if next week my dad isn't improved from this week, we're calling the doctor. Having aging parents sucks, even if it beats the alternative, which it currently does.)

Yeah, I did not see any SR 606 signs inside Herndon Pkwy when I was there last month.  However, I am unsure that necessarily matters here.

[mapmikey]

There are no SR postings within Herndon as VDOT does not maintain their streets.

I changed the SR 606 references to SteRd and EldSt respectively.

Made the corrections to US 360, VA 61 and VA 67.

The fact that Virginia sometimes leaves postings up is irrelevant to me...if the CTB decommissions the route it should come off of TM.

I would love to be able to do 'select Virginia SRs' which could at a minimum have former state highways. 

[Markkos1992]

The fact that Virginia sometimes leaves postings up is irrelevant to me...if the CTB decommissions the route it should come off of TM.

I thought we had gone into maintainer-preference mode last time we discussed this.  I think it had something to do with how yakra handles TX.

[dave1693]

There are no SR postings within Herndon as VDOT does not maintain their streets.

That's been true the whole 3+ decades I've lived in Northern Virginia, but some SR postings inside Herndon were actually not uncommon up until the past few years. (I'm looking at 606 ,but also 666 on Van Buren and Monroe Streets, and 675? on Spring Street. Signs all gone now.) There were SR 606 signs on Elden St until earlier this year, but the recent road work on Elden St appears to have included taking down the last 3-4 that were left (I double checked that yesterday).

Herndon Parkway is still signed as both SR 606 Truck and VA 228 Truck in all sections north of 606 and as VA 228 Truck in all sections south of 606. No non-truck VA 228 signs to be found anywhere in town; Herndon pulled down the last few VA 228 signs on the routing through town either this year or last when renovating the road. \

The fact that Virginia sometimes leaves postings up is irrelevant to me...if the CTB decommissions the route it should come off of TM.

It has always been my impression that how things are signed is more important. I welcome others who, unlike myself, are actual region maintainers to correct me or offer opinions.

I would love to be able to do 'select Virginia SRs' which could at a minimum have former state highways.

If we decide to open that can of worms I will offer my assistance.

[mapmikey]

It has always been my impression that how things are signed is more important. I welcome others who, unlike myself, are actual region maintainers to correct me or offer opinions.

The problem with Virginia in this regard is that if I did that, the VA 305 in Virginia Beach would've originally been in TM despite being decommissioned in 1961; some of the Virginia 4xx routes would have to be included even though decommissioned in 2001.

Where I *do* use posting is US routings within Independent Cities, as their routes get changed via posting but there is never any AASHTO or CTB documentation, so I don't know if the route has officially moved or not.

I would love to be able to do 'select Virginia SRs' which could at a minimum have former state highways.

If we decide to open that can of worms I will offer my assistance.

Wouldn't be my first priority - would like to be able to do primary routes not posted the "right way" and also the unposted ones, most of which were posted in recent years and many appear on the standard official state maps.

I would also like to do the NC secondary 10xx series routes, which are posted better than normal SR routes.  There are probably 500 of these statewide, since they don't retain the same number when they cross a county line.

[Markkos1992]

VA 244 Update:  https://www.aaroads.com/forum/index.php?topic=294.msg2908993#msg2908993