The Attempt to Fix Virginia Signage Featuring WillWeaverRVA

[plain]

The city has informed me that the "END US 250" request, some missing movements at US 360 where it turns from Fairfield Way onto Mechanicsville Turnpike, and some missing VA 197 signage at Saunders and Laburnum have been resolved.

I saw a BEGIN US 250 sign yesterday morning on Broad St WB, but it was at 23rd St 

[WillWeaverRVA]

The city has informed me that the "END US 250" request, some missing movements at US 360 where it turns from Fairfield Way onto Mechanicsville Turnpike, and some missing VA 197 signage at Saunders and Laburnum have been resolved.

I saw a BEGIN US 250 sign yesterday morning on Broad St WB, but it was at 23rd St 

That's actually where it's supposed to be according to the VDOT ArcGIS map!

[plain]

The city has informed me that the "END US 250" request, some missing movements at US 360 where it turns from Fairfield Way onto Mechanicsville Turnpike, and some missing VA 197 signage at Saunders and Laburnum have been resolved.

I saw a BEGIN US 250 sign yesterday morning on Broad St WB, but it was at 23rd St 

That's actually where it's supposed to be according to the VDOT ArcGIS map!

I think that map is old schooling it in this regard because I could've sworn US 250's terminus was moved to US 360 years ago.

[WillWeaverRVA]

The city has informed me that the "END US 250" request, some missing movements at US 360 where it turns from Fairfield Way onto Mechanicsville Turnpike, and some missing VA 197 signage at Saunders and Laburnum have been resolved.

I saw a BEGIN US 250 sign yesterday morning on Broad St WB, but it was at 23rd St 

That's actually where it's supposed to be according to the VDOT ArcGIS map!

I think that map is old schooling it in this regard because I could've sworn US 250's terminus was moved to US 360 years ago.

Oh crap, you're right. The 2003 route log says it ends at 18th, not 23rd. I've created a sign error! 

[dfnva]

I was in the Woodbridge area, so I drove by the NOVA campus, and didn't see any postings of VA-394 on southbound Neabsco Mills Rd at either of the entrances. There is still a gigantic VA-1 shield as it approaches US-1.

On a separate note, with an effort to finally get VA-28 signed at the terminus of VA-215, I also asked VDOT about the feasibility of signing more significant secondary routes with shields in the northern Virginia area where primary routes cross them (some examples... Route 620 on VA-123, Route 644 on VA-286, Route 659 on VA-234, Route 650 on VA-236). The response I got was there seems to be no interest in doing so due to the use of GPS, locals' use of road names, and that LRS signs or inclusion of the route number on street name signs is sufficient (though one or both are missing at all of these intersections except one case). I find that odd since I wasn't asking for every secondary route to be posted with a shield like they often are in rural areas of the state. But, I tried.

[1995hoo]

As a practical matter, I can't say I necessarily disagree with VDOT's point about nobody using the secondary route numbers with one exception. The only secondary route I can think of in Northern Virginia that you routinely hear referred to by number is Route 644, which the radio traffic reporters refer to that way because it changes names when it crosses I-95 and it carries a significant volume of traffic. (Back when the Fairfax County Parkway was a secondary route they referred to it by number as well, but of course it's been renumbered.)

Can you think of any others that people refer to by numbers? To be sure, I can think of secondary routes that change names multiple times (far more than the one time that Route 644 does), but I can't think of anyone using route numbers to refer to them.

[jb_va23]

As a practical matter, I can't say I necessarily disagree with VDOT's point about nobody using the secondary route numbers with one exception. The only secondary route I can think of in Northern Virginia that you routinely hear referred to by number is Route 644, which the radio traffic reporters refer to that way because it changes names when it crosses I-95 and it carries a significant volume of traffic. (Back when the Fairfax County Parkway was a secondary route they referred to it by number as well, but of course it's been renumbered.)

Can you think of any others that people refer to by numbers? To be sure, I can think of secondary routes that change names multiple times (far more than the one time that Route 644 does), but I can't think of anyone using route numbers to refer to them.

I do hear people refer to Braddock Rd as Route 620 every so often.

[Dirt Roads]

Can you think of any others that people refer to by numbers? To be sure, I can think of secondary routes that change names multiple times (far more than the one time that Route 644 does), but I can't think of anyone using route numbers to refer to them.

Don't know if they still talk like this, but SR-606 (Elden Street and Baron Cameron Avenue) in Herndon/Reston was called "six-oh-six" back in the 1980s and 1990s.  Of course, folks pandering to the Reston elite would say "Baron Cameron" on the radio instead.

Heading west, some folks also referred to Sterling Road and Old Ox Road from Herndon around and down to South Riding as "six-oh-six around the airport", even when those street names were preferred by locals. 

[WillWeaverRVA]

Can you think of any others that people refer to by numbers? To be sure, I can think of secondary routes that change names multiple times (far more than the one time that Route 644 does), but I can't think of anyone using route numbers to refer to them.

Don't know if they still talk like this, but SR-606 (Elden Street and Baron Cameron Avenue) in Herndon/Reston was called "six-oh-six" back in the 1980s and 1990s.  Of course, folks pandering to the Reston elite would say "Baron Cameron" on the radio instead.

Heading west, some folks also referred to Sterling Road and Old Ox Road from Herndon around and down to South Riding as "six-oh-six around the airport", even when those street names were preferred by locals. 

Before it became primary, and for a few years after, a lot of folks and most traffic reporters referred to the Fairfax County Parkway as 7100.

[dfnva]

These are interesting points. I have heard people refer to the road I live off of as 619 since it changes names so many times in PWC. It helps that Route 619 is well-posted except where it diverges onto Fuller Heights Rd just outside of Quantico. I've also heard people refer to Route 659 as such. Then, there is the converse where there are primary routes that people rarely, if ever, refer to the route number.

That brings up another thought -- what is the necessity, if any, for posting any route numbers with colloquial use of street names and GPS's except in those cases that most use the route number (e.g. US highways, VA-7, VA-236, VA-234, VA-123, VA-28, and such). However, in my experience the Google maps GPS uses route numbers often for secondary routes and in some cases, in lieu of the street name.

I guess I feel that posting route numbers gives drivers an easier and quicker option for wayfinding and those secondary routes that are the most significant should be posted at all significant intersections. And, then, of course, if a road is a primary route, it should also be posted in most cases.

As a practical matter, I can't say I necessarily disagree with VDOT's point about nobody using the secondary route numbers with one exception. The only secondary route I can think of in Northern Virginia that you routinely hear referred to by number is Route 644, which the radio traffic reporters refer to that way because it changes names when it crosses I-95 and it carries a significant volume of traffic. (Back when the Fairfax County Parkway was a secondary route they referred to it by number as well, but of course it's been renumbered.)

Can you think of any others that people refer to by numbers? To be sure, I can think of secondary routes that change names multiple times (far more than the one time that Route 644 does), but I can't think of anyone using route numbers to refer to them.

[WillWeaverRVA]

Went out and got pictures of the BEGIN and END signs for US 250 and posted them in the appropriate threads.

[WillWeaverRVA]

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.

[dfnva]

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.

It's been less than three weeks since I put in a work order on VDOT's website for VA-28 shields to be installed at the eastern terminus of VA-215 (something that was never done when VA-215 was rerouted to meet VA-28 further south a few years ago). I'm not sure when they were installed (I've been out of town), but two sets of signs for VA-28 were there when I drove by yesterday (advanced trailblazers and more trailblazers at the intersection itself). There was no END VA-215 sign but maybe it's greedy of me to hope that would be installed. At any rate, I was impressed with how quick VDOT did this as it took over a month (maybe two months) for completion of another work order I put in a few years ago (signs for VA-234 on US-29 north).

At any rate, unfortunately I'm doubting those VA-393 or VA-394 signs will be installed, given how quickly the VA-28 signs went up. There were previously LRS signs at both locations years ago but, except in rare circumstances, new LRS signs are not installed around Prince William County.

[WillWeaverRVA]

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.

It's been less than three weeks since I put in a work order on VDOT's website for VA-28 shields to be installed at the eastern terminus of VA-215 (something that was never done when VA-215 was rerouted to meet VA-28 further south a few years ago). I'm not sure when they were installed (I've been out of town), but two sets of signs for VA-28 were there when I drove by yesterday (advanced trailblazers and more trailblazers at the intersection itself). There was no END VA-215 sign but maybe it's greedy of me to hope that would be installed. At any rate, I was impressed with how quick VDOT did this as it took over a month (maybe two months) for completion of another work order I put in a few years ago (signs for VA-234 on US-29 north).

At any rate, unfortunately I'm doubting those VA-393 or VA-394 signs will be installed, given how quickly the VA-28 signs went up. There were previously LRS signs at both locations years ago but, except in rare circumstances, new LRS signs are not installed around Prince William County.

Maybe I'll be annoying and request them again.

[WillWeaverRVA]

Heard back from VDOT regarding the erroneous US 33 signs on northbound I-95 near the Broad St exit. When the signs are replaced as part of normal upkeep, they will be updated to no longer refer to US 33 (just US 250), and the sign for eastbound Broad St will also mention US 360 (since that ramp connects to Oliver Hill Way, which is US 360). US 33 hasn't run out there in over 40 years.

This is why some of the signs on southbound I-95 were changed to refer to only US 250, but there's still a US 33/US 250 sign at the actual exit.

[plain]

Correct sign, but supposed to be facing the opposite direction. How these fools fucked this one up is beyond me. This is US 360 just south of the duplex with US 60.

Images from today

[WillWeaverRVA]

Correct sign, but supposed to be facing the opposite direction. How these fools fucked this one up is beyond me. This is US 360 just south of the duplex with US 60.

Images from today

Yeah, that's wrong. I'll put in a new request...

[WillWeaverRVA]

Correct sign, but supposed to be facing the opposite direction. How these fools fucked this one up is beyond me. This is US 360 just south of the duplex with US 60.

I put in a new 311 request to have the sign rotated. I agree with you, I have no clue how this happens.

I will say, the more 311 requests that get resolved, the better Richmond's signs are starting to look. The first few new signs they installed are really ugly. This one isn't bad at all.

[plain]

Correct sign, but supposed to be facing the opposite direction. How these fools fucked this one up is beyond me. This is US 360 just south of the duplex with US 60.

I put in a new 311 request to have the sign rotated. I agree with you, I have no clue how this happens.

I will say, the more 311 requests that get resolved, the better Richmond's signs are starting to look. The first few new signs they installed are really ugly. This one isn't bad at all.

Yeah the newer signs look a lot better. I'm still in the process of taking pics, will be posting soon.

Also, I've been tipped off to a couple new signs in Hampton. I'm supposed to be heading that way next week, I will try to check.

[WillWeaverRVA]

Correct sign, but supposed to be facing the opposite direction. How these fools fucked this one up is beyond me. This is US 360 just south of the duplex with US 60.

I put in a new 311 request to have the sign rotated. I agree with you, I have no clue how this happens.

I will say, the more 311 requests that get resolved, the better Richmond's signs are starting to look. The first few new signs they installed are really ugly. This one isn't bad at all.

Yeah the newer signs look a lot better. I'm still in the process of taking pics, will be posting soon.

Also, I've been tipped off to a couple new signs in Hampton. I'm supposed to be heading that way next week, I will try to check.

Ooh, please let me know if you find any.

[WillWeaverRVA]

VDOT engineer called and said 393 and 394 signage is still in the works.

[WillWeaverRVA]

One of Virginia Beach's traffic engineers called me today and basically told me they will no longer post signs for primary routes in the city because people don't use them. "Well, GPS devices do but people don't." So I will no longer be submitting any requests there.

They also said they will not touch any existing route signage. I think they removed those VA 414 signs that were on Lynnhaven Pkwy and VDOT was not happy about it.

[74/171FAN]

I guess those that want to have US 58 clinched at its east end will have to traverse 30th St, 31st St, and 32nd St just to be sure.