usava (Virginia State Highways)

[mapmikey]

I have gone through Set #2 of Froggie's feedback and done what was suggested with the following comments:

VA 199 I previously addressed by eliminating the point

VA 191 is a mixed bag: traffic log says what froggie says; route log, postings say it ends at Airline; Shapefiles call it US 13 (as US 13 S/460 W must use this for continuity); 2004 VDOT county atlas doesn't label it at all; VHP says it ends at Military Hwy and I can't remember why I specifically have it that way.  I added the waypoint based on the example of VA 32 being done into Newport News despite no postings past its southern US 17 split

VA 190 - note that Jim ran a routine to change all my pky to pkwy throughout the entire route lists

VA 189 - I also changed the SR 666 name to Gates Rd as it is within the City of Suffolk

VA 179 - official sources disagree between Dave's choice and yours but I moved it to yours because that is where the pavement changes.

VA 168 - I left MusRd because it is an interchange but added Norview.  Also added one at the Government Rd location north of US 460 because there is an on and off ramp in that location.  I chose to leave the exit numbers for the toll road.  They are referenced on VA 168 Business waypoints anyway.


I have sent both rounds of Virginia changes to Jim...

Mike

[froggie]

VA 191 is a mixed bag: traffic log says what froggie says; route log, postings say it ends at Airline; Shapefiles call it US 13 (as US 13 S/460 W must use this for continuity); 2004 VDOT county atlas doesn't label it at all; VHP says it ends at Military Hwy and I can't remember why I specifically have it that way.

At one point in the not-too-distant past, postings continued it south of Airline.  That, in conjunction with the traffic log, is likely why we had it at Military Hwy on VHP.

VA 179 - official sources disagree between Dave's choice and yours but I moved it to yours because that is where the pavement changes.

I ran the mileages from the traffic log and what we have on VHP and came up with my suggested point as a result.

[Markkos1992]

Minor changes in Prince George County

VA 156:  The point at SR 630 (Lamore Drive) needs to be slightly relocated.  I remember this intersection was relocated sometime in the 2000s, but I cannot remember offhand exactly when.
VA 106:  The point at SR 634 (Allin Rd) needs to be recentered onto the roundabout completed around 2010.

[froggie]

Continuing backward from where I left off...

VA 138:  Suggest replacing the shaping point south of VA 137 with a point at SR 617.

VA 134:  I'm not sure I like the placement of the point at I-64(265).  On the one hand, there are two direct ramps between westbound 64 and VA 134.  On the other hand, the primary reason for that interchange is LaSalle Ave (former VA 167), and the LaSalle Ave intersection with 134 splits where the 64 ramps connect to 134.  Personally, I'd ditch the 64 point and add a point at LaSalle Ave.

HamRoaPkwy, properly labeled, should be HamRoaCenPkwy.

Suggest a point at SR 600/Big Bethel Rd, which is a north-south arterial.

VA 130:  Suggest replacing the VolHudRd point with a point at SR 650/W Perch Rd in conjunction with replacing the shaping point near the Pedlar River with a point at SR 635/Buffalo Springs Turnpike.

VA 128:  Is a shaping point needed between Odd Fellows Rd and BUSINESS 460/501?

VA 123:  Given the built-up suburban nature of this road, and the arterial nature of the intersecting roads, I could see adding points at three more locations:  SR 641/Old Bridge Rd, SR 643/Lee Chapel Rd, and SR 620/Braddock Rd.

VA 117:  Suggest a point at Cove Rd NW.

VA 116:  Suggest replacing the AerRd point with a point at SR 681 (main access road to the east of Roanoke and south of the river).

VA 114:  What's labeled as SR 659 is *NOT* SR 659 (which is actually at the PriForkRd point).  It should be relabeled ConRd (for Constitution Rd).

VA 106 (besides what was just mentioned):  Suggest replacing the shaping point east of I-295 with a point at SR 616.

Suggest a point at SR 607 near Wayside.

VA 103:  Suggest replacing the western shaping point with a point at SR 645.

VA 100:  Suggest replacing the shaping point north of DeerRidRd with a point at SR 749/Sylvatus, adding a point at SR 693/Sylvatus, and moving the BrimRd point to SR 607/Patterson.

Suggest moving the WooFarmRd point south to SR 609.

[yakra]

HamRoaPkwy, properly labeled, should be HamRoaCenPkwy.

The guideline is as follows:

If the cross road name has more than 3 words, use one of two options:
1. Pick out the two most important words besides the road type and use only those: Martin Luther King Boulevard becomes MarKingBlvd. Three words in total are included in shortened form.
2. Pick out one important word besides the road type and use it and the initials of the other words: Martin Luther King Boulevard becomes MLKingBlvd. Two words in total are included in shortened form along with initials of the rest.

Thus HamRoaPkwy is correct. HRCenPkwy, HamRCPkwy or HRoaCPkwy would also be compliant, but IMO calling "Center" one of "the two most important words" (as in HamCenPkwy or RoaCen Pkwy) is a stretch. I like HamRoaPkwy best.

[mapmikey]

Have to say I am a little fuzzy on the need for strict guidelines on aspects of TM that don't affect how the computer code interprets it (e.g. proper overlay calculation).  The users who create lists aren't provided with the rules so they have to click on the point to see what it is named anyway (and the rule list is long enough that clicking on the point is faster anyway).

My 2 cents...

I will continue to follow whatever guidelines are asked of me...

Mike

[froggie]

Thus HamRoaPkwy is correct. HRCenPkwy, HamRCPkwy or HRoaCPkwy would also be compliant, but IMO calling "Center" one of "the two most important words" (as in HamCenPkwy or RoaCen Pkwy) is a stretch. I like HamRoaPkwy best.

If this is the case, then HRCenPkwy would be the best fit.  Because for this roadway, Center *IS* the most important word.  It's so named because it's adjacent to the Hampton Roads Center development area of Hampton.

[michih]

Have to say I am a little fuzzy on the need for strict guidelines on aspects of TM that don't affect how the computer code interprets it (e.g. proper overlay calculation).  The users who create lists aren't provided with the rules so they have to click on the point to see what it is named anyway (and the rule list is long enough that clicking on the point is faster anyway).

Agree!

[mapmikey]

all items VA100-156 are addressed and are in my queue...

mike

[yakra]

At the end of the day, the guidelines can produce multiple results, so clicking the point is still necessary. That said though, I do think consistency and brevity are worthy goals.

I agree with froggie's assessment of HRCenPkwy.

[Jim]

At the end of the day, the guidelines can produce multiple results, so clicking the point is still necessary. That said though, I do think consistency and brevity are worthy goals.

Pretty much what I was going to post.

[Markkos1992]

I was considering waiting on Froggie finishing his peer review to mention this but I will go ahead and mention it now.

VA 28:points at Severn Way (SR847) and Dulles Center Blvd (DulCenBlvd) should be marked as closed. The SteDr point should remain but possibly be renamed???

 I just finally clinched VA 28 north of I-66 less than two weeks ago when in the area about 10 days ago.

-Mark AKA 74/171FAN

[dave1693]

Quick note...

VA 203: the waypoint marked as SR601 should be SR604. 601 doesn't come anywhere near this intersection, which is the southwestern end of SR604, locally dubbed the "Sandy Point Speedway". (My wife grew up in the area, and my mother-in-law still lives there, so we have been to this intersection rather a lot.)

Dave

[dave1693]

VA 28:points at Severn Way (SR847) and Dulles Center Blvd (DulCenBlvd) should be marked as closed. The SteDr point should remain but possibly be renamed???

Well, all the signs on 28 now say "Warp Drive" so perhaps it should be renamed...

Dave

[mapmikey]

I have fixed the VA 28 and VA 203 files.

I did not fix the VA 28 freeway file as it is going away so I didn't see the need to do so...