usava (Virginia State Highways)

[yakra]

I'd suggest fixing it anyway, as all occurrences of "VA28" in a .list file will continue to point to the freeway version, until USAVA is activated & replaces it.

[froggie]

Mike's idea is probably that usava will be activated soon, once reviews and such are completed.

And on that note, I apologize that it's taken me so long...semester got in the way.  But this upcoming week is our last week (finals! yay!) so I should be able to get back to reviewing by next weekend.

[mapmikey]

I'd suggest fixing it anyway, as all occurrences of "VA28" in a .list file will continue to point to the freeway version, until USAVA is activated & replaces it.

All of the fixes are either closing a waypoint or renaming one so existing .list files should still work just fine...?

[johninkingwood]

I am a longtime lurker and road tracker on this site and its predecessor. The new site looks great! I appreciate everyone's hard work.

I keep getting log errors on my line for VA 7. Currently, there is an active line for VA7Fwy (I believe that is how it is presented), and one for VA7. Every time I submit a list, I get errors on both of them. I have attempted multiple submissions on both versions of VA 7. Will the two versions of VA 7 eventually be combined? The freeway bypass around Leesburg and the highway are a continuous road.

On my most recent log, it is not finding the waypoint label between VA28 and VA287. My error reads: "Waypoint label(s) not found in line: VA VA7 VA28 VA287"

I just want to make sure I get the line right on my log.

Thank you so much for your help!

[rickmastfan67]

I think it's because the Virginia routes are in the 'preview' stage.  We've been throwing around just copying over all of the VA-7 file into the 'Fwy' file till we active the system.  Same thing is happening with VA-28.

@mapmikey @froggie @Jim

[Markkos1992]

Froggie, what is the status of your peer review?  I have noticed the points on VA 80 around SR 609 are off (due to the slight relocation as a result of the US 460/Corridor Q Extension- I saw this area as a part of the Pikeville meet a couple years ago, but I cannot remember if VA 80 was relocated yet).

-Mark

[Jim]

Does anyone have comments on the routes that are in usava but which have shorter versions in usansf?  They should be copied over unless usava is really close to full activation.

[froggie]

I've provided comment on everything above VA 100.  I can shift my priority to looking at the rest of the routes this week.

[johninkingwood]

Thanks for the input! I'll leave VA7 off my list until all of VA is active.

Thanks for all your hard work!

[mapmikey]

Froggie, what is the status of your peer review?  I have noticed the points on VA 80 around SR 609 are off (due to the slight relocation as a result of the US 460/Corridor Q Extension- I saw this area as a part of the Pikeville meet a couple years ago, but I cannot remember if VA 80 was relocated yet).

-Mark

Per online maps it appears VA 80 has been temporarily routed on the much older alignment through Breaks.  It will eventually follow the new road with overpass up to Corr Q to go into Kentucky.  VDOT estimates this will occur in late 2017.

What I did to the file was move the BreParRd point to where VA 80 leaves the eventual new VA 80 and renamed it SR 693.  I took the next point up (SR 609) which is right at the overpass and turned it into a "closed" point.  Once VA 80 is moved onto Corr Q the last 3 waypoints on VA 80 will have to be eliminated and a couple new ones installed in their place.

Will be submitted with my next updates...

[Markkos1992]

VA 165:  Given their area importance, suggest points at Centerville Tpk, Indian River Rd, Nimmo Pkwy, and Dam Neck Rd.

For some reason, the Dam Neck Rd point is marked as DamNeckBlvd.

Also since the VA 192 file does not exist due to it being unposted, should that point just be for Azalea Garden Rd?  (applies to VA 170 as well)

VA 36:  The SR 600 point in Matoaca needs to be moved to the intersection at Pickett Ave.

[mapmikey]

VA 165:  Given their area importance, suggest points at Centerville Tpk, Indian River Rd, Nimmo Pkwy, and Dam Neck Rd.

For some reason, the Dam Neck Rd point is marked as DamNeckBlvd.

Also since the VA 192 file does not exist due to it being unposted, should that point just be for Azalea Garden Rd?  (applies to VA 170 as well)

VA 36:  The SR 600 point in Matoaca needs to be moved to the intersection at Pickett Ave.

I have corrected the VA 36 and the Dam Neck Rd points.  In my queue for submittal.

I am inclined to leave VA 192 labels alone.  There are other examples in the Virginia set where an unposted primary route is given a label...

[mapcat]

If you'd consider adding some waypoints, these would be useful to me:

On VA40 at SR681 west of Stony Ctreek
On VA49 at SR625 south of Crewe

Also, I found two concurrency issues. In Bedford, US221 is missing a waypoint for US460Bus that VA122 has. And at SR613 west of Appomattox, VA24 has a waypoint but US460 doesn't.

[mapmikey]

Files edited and submitted...

[dfilpus]

Now US221 has two waypoints labelled US460Bus_W, one in Bedford and one in Lynchburg. There are five places where US221 and a US460Bus intersect:
1. US221/US460Bus, west of Bedford.
2. US460_E, the eastern end of US460Bus Bedford.
3. US460Bus_W, where US 221 turns north from US460Bus Bedford.
4. US460Bus_W, where US 221 turns north from US460Bus Lynchburg.
5. US29Bus. where US221 ends, ending the concurrency with US460Bus Lynchburg.

My suggestion is to relabel points 1 and 3 to use US460BusBed and point 4 to use US460BusLyn.