The Attempt to Fix Virginia Signage Featuring WillWeaverRVA

[WillWeaverRVA]

A couple of newbies a caught last night.

Main St WB approaching S. 8th St




8th St SB approaching Canal St (actually just past Cary)

Glad those are there. Those movements had been unsigned for years.

[plain]

There's a few more signs that popped up recently that I couldn't get pics of yet. One of which is a I-95 sign oddly placed on Hermitage Rd NB at Robin Hood Rd. I'm going to try for that one again today

[WillWeaverRVA]

There's a few more signs that popped up recently that I couldn't get pics of yet. One of which is a I-95 sign oddly placed on Hermitage Rd NB at Robin Hood Rd. I'm going to try for that one again today

There is a slip ramp from Robin Hood Rd to southbound I-95, is it referring to that?

[plain]

There's a few more signs that popped up recently that I couldn't get pics of yet. One of which is a I-95 sign oddly placed on Hermitage Rd NB at Robin Hood Rd. I'm going to try for that one again today

There is a slip ramp from Robin Hood Rd to southbound I-95, is it referring to that?

Yes. The arrow on the sign is slanted and it's on Hermitage. It looks a little out of place to me.

[dfnva]

VA-393 is now posted with an advance trailblazer shield and a trailblazer at the intersection on VA-234 northbound. I was impressed to see proper 3-digit shields with Series C numbers on both shields. Years ago there were LRS signs (aka white rectangles) but they have been long gone.

There were no shields on southbound VA-234, as there is no left turn into the NVCC facility.

I did not drive around Battlefield Pkwy to see if there were additional shields there.

Sorry I didn't get a pic!

I'm wondering if that means VA-394 is also posted now?

After another round of GSV updates, VA 393 and VA 394 are still not posted. VA 213 isn't posted either but I wasn't expecting it to be.

[FLAVORTOWN]

A while back I put in a request to have VA-338 re-signed, no dice. There was a VA-338 shield at Seven Corners that disappeared recently and it looks like VDOT doesn't want to bother until that whole area gets rebuilt.

I am not sure if Falls Church even wants VA-338 signed all the way down Hillwood Ave 

[WillWeaverRVA]

VA-393 is now posted with an advance trailblazer shield and a trailblazer at the intersection on VA-234 northbound. I was impressed to see proper 3-digit shields with Series C numbers on both shields. Years ago there were LRS signs (aka white rectangles) but they have been long gone.

There were no shields on southbound VA-234, as there is no left turn into the NVCC facility.

I did not drive around Battlefield Pkwy to see if there were additional shields there.

Sorry I didn't get a pic!

I'm wondering if that means VA-394 is also posted now?

I spoke to the same engineer about both 393 and 394 so I bet 394 is either posted or will be very soon.

[WillWeaverRVA]

other eastern shore:

VA 187 whose eastern end is not signed and the turn at SR 679 is poorly signed WB.
VA 179 is not posted AFAIK west of VA 126.  It should definitely be posted at SR 718 Pine St and at endpoint

GMSV still doesn't have coverage so can't determine if VA 180 is still poorly posted on both ends

Following up on this, GSV finally went a bit further into Wachapreague and it looks like VA 180 is now rather heavily posted in town on white rectangle signs. A lot of the rectangles look new. VA 180Y is posted on a rectangle as plain VA 180, but there is a brand new, 3-digit VA 180Y shield leaving VA 180 (replacing an old 2-digit shield that had been there).

GSV decided to stop about 50 feet short of the end of VA 180 but there appears to be a white rectangle at the eastern end.

Unfortunately there's still no GSV of the other end in Harborton, although the extremely brief VA 178 concurrency is posted with a rather unique arrow that looks new and probably replaced a plain ol' left arrow.

[Mapmikey]

There's been a zigzag arrow there since at least 2007:

http://vahighways.com/multiplex/va178-va180.htm

[Rat Salad]

Imagine my surprise when I came to the intersection of VA route 54 and Medical Drive in Ashland, and discovered I was intersecting US 54.

[WillWeaverRVA]

Imagine my surprise when I came to the intersection of VA route 54 and Medical Drive in Ashland, and discovered I was intersecting US 54.

Yeeeeeeah. That's been there for a while and I don't think VDOT will do anything about it since it's in Ashland.

EDIT: I actually submitted a request to VDOT without it getting rejected for being on a non-VDOT maintained road, so maybe this will get fixed!

[hbelkins]

Imagine my surprise when I came to the intersection of VA route 54 and Medical Drive in Ashland, and discovered I was intersecting US 54.

Yeeeeeeah. That's been there for a while and I don't think VDOT will do anything about it since it's in Ashland.

EDIT: I actually submitted a request to VDOT without it getting rejected for being on a non-VDOT maintained road, so maybe this will get fixed!

Boo, hiss. I hate to see route classification signage errors fixed. Let 'em stay.