Richmond has a new mayoral administration, and the new mayor seems to be extra committed to public works and public utility projects after Richmond's water crisis earlier this month. A bunch of 311 requests people have submitted as long ago as 2 years are now being completed, including a bunch of my requests related to signage. It's possible that a bunch of signage errors (or locations where signage is missing) may soon be fixed, including ones related to US 250 - in previous requests, the city kept referring to cryptic emails about signing US 250 in the city and closing requests related to installing signage.
I haven't had a chance to go into the city recently to check on any of them, though.
Requests I put in that are now showing as completed:
- VA 353 posting on Duval St at 8th St (to match the one leaving the VCU Health System staff parking area)
- Missing signage on Sheppard St directing traffic onto Cary St to reach VA 161 (since the exit from VA 146 is signed for VA 161)
- Missing signage for VA 195/I-64/I-95 on Belvidere St at Cumberland St (signage used to exist but was removed)
- Missing VA 147 signage at Main St/Belvidere St intersection (even though Cary St is signed as VA 147)
- "END VA 6" sign missing at Kensington Ave and Arthur Ashe Blvd (was removed a long time ago for a signal upgrade and never replaced)
- Missing US/VA 33 and US 250 signage at Harrison St and Broad St intersection
- Missing VA 33 signage on Leigh St at Harrison St (though there is a reassurance marker on Harrison St)
Requests I put in that have notes saying signage will be installed:
- Missing US 250 and US 360 signage at 17th and Broad (I-95 exit is signed for US 250)
- Missing US 1/US 301/VA 2 signage at Azalea Ave and Chamberlayne Ave
Quote from: WillWeaverRVA on January 31, 2025, 10:11:22 AMRichmond has a new mayoral administration, and the new mayor seems to be extra committed to public works and public utility projects after Richmond's water crisis earlier this month. A bunch of 311 requests people have submitted as long ago as 2 years are now being completed, including a bunch of my requests related to signage. It's possible that a bunch of signage errors (or locations where signage is missing) may soon be fixed, including ones related to US 250 - in previous requests, the city kept referring to cryptic emails about signing US 250 in the city and closing requests related to installing signage.
I haven't had a chance to go into the city recently to check on any of them, though.
Requests I put in that are now showing as completed:
- VA 353 posting on Duval St at 8th St (to match the one leaving the VCU Health System staff parking area)
- Missing signage on Sheppard St directing traffic onto Cary St to reach VA 161 (since the exit from VA 146 is signed for VA 161)
- Missing signage for VA 195/I-64/I-95 on Belvidere St at Cumberland St (signage used to exist but was removed)
- Missing VA 147 signage at Main St/Belvidere St intersection (even though Cary St is signed as VA 147)
- "END VA 6" sign missing at Kensington Ave and Arthur Ashe Blvd (was removed a long time ago for a signal upgrade and never replaced)
- Missing US/VA 33 and US 250 signage at Harrison St and Broad St intersection
- Missing VA 33 signage on Leigh St at Harrison St (though there is a reassurance marker on Harrison St)
Requests I put in that have notes saying signage will be installed:
- Missing US 250 and US 360 signage at 17th and Broad (I-95 exit is signed for US 250)
- Missing US 1/US 301/VA 2 signage at Azalea Ave and Chamberlayne Ave
That's awesome if they followed through...
Quote from: Mapmikey on January 31, 2025, 10:38:44 AMQuote from: WillWeaverRVA on January 31, 2025, 10:11:22 AMRichmond has a new mayoral administration, and the new mayor seems to be extra committed to public works and public utility projects after Richmond's water crisis earlier this month. A bunch of 311 requests people have submitted as long ago as 2 years are now being completed, including a bunch of my requests related to signage. It's possible that a bunch of signage errors (or locations where signage is missing) may soon be fixed, including ones related to US 250 - in previous requests, the city kept referring to cryptic emails about signing US 250 in the city and closing requests related to installing signage.
I haven't had a chance to go into the city recently to check on any of them, though.
Requests I put in that are now showing as completed:
- VA 353 posting on Duval St at 8th St (to match the one leaving the VCU Health System staff parking area)
- Missing signage on Sheppard St directing traffic onto Cary St to reach VA 161 (since the exit from VA 146 is signed for VA 161)
- Missing signage for VA 195/I-64/I-95 on Belvidere St at Cumberland St (signage used to exist but was removed)
- Missing VA 147 signage at Main St/Belvidere St intersection (even though Cary St is signed as VA 147)
- "END VA 6" sign missing at Kensington Ave and Arthur Ashe Blvd (was removed a long time ago for a signal upgrade and never replaced)
- Missing US/VA 33 and US 250 signage at Harrison St and Broad St intersection
- Missing VA 33 signage on Leigh St at Harrison St (though there is a reassurance marker on Harrison St)
Requests I put in that have notes saying signage will be installed:
- Missing US 250 and US 360 signage at 17th and Broad (I-95 exit is signed for US 250)
- Missing US 1/US 301/VA 2 signage at Azalea Ave and Chamberlayne Ave
That's awesome if they followed through...
Yeah, for real. I may go look into this today if I have a chance.
I was in the city a couple weeks ago and vaguely remember seeing some new-looking signage at Azalea and Chamberlayne, but that may not be it.
The 353 posting is there now. The EAST 147 is also there but they fumbled the ball on the 33 signage.
So, of the things I listed that were marked complete, here's what I was able to verify was actually done:
- VA 353 posting on Duval St at 8th St (to match the one leaving the VCU Health System staff parking area) VA 353 is correctly posted. Years ago before a roundabout was built at 8th and Duval, there was a white rectangle sign that had been removed. I was SHOCKED Richmond put this one up. Maybe I can get them to post VA 315 and VA 399. 😂
- Missing signage for VA 195/I-64/I-95 on Belvidere St at Cumberland St (signage used to exist but was removed) Signs were reinstalled.
- Missing VA 147 signage at Main St/Belvidere St intersection (even though Cary St is signed as VA 147) VA 147 is posted here now.
- "END VA 6" sign missing at Kensington Ave and Arthur Ashe Blvd (was removed a long time ago for a signal upgrade and never replaced) There's a new END VA 6 sign up.
- Missing VA 33 signage on Leigh St at Harrison St (though there is a reassurance marker on Harrison St) So there's a VA 33 shield here now, but it's bannerless and not in the correct location (it's facing southbound Harrison), and there still isn't any indication that VA 33 turns from Leigh onto Harrison.
Quote from: WillWeaverRVA- Missing VA 147 signage at Main St/Belvidere St intersection (even though Cary St is signed as VA 147)
I went by this one about an hour ago, and it's *not* my favorite Richmond unisign lmmfaooo
(https://uploads.tapatalk-cdn.com/20250211/2610d142e69a798152237fa485cd1f95.jpg)
J24
Quote from: plain on February 10, 2025, 07:29:20 PMQuote from: WillWeaverRVA- Missing VA 147 signage at Main St/Belvidere St intersection (even though Cary St is signed as VA 147)
I went by this one about an hour ago, and it's *not* my favorite Richmond unisign lmmfaooo
(https://uploads.tapatalk-cdn.com/20250211/2610d142e69a798152237fa485cd1f95.jpg)
J24
Yeeeeah, it's not pretty but it's *there*, and that's good enough for me.
Google Street View has done some long-overdue updates in the Hampton Roads area. I put in a few 311 requests, so here's what I've noticed:
- The erroneous END US 60 (https://www.google.com/maps/@36.8302742,-75.9725688,3a,15y,222.05h,87.1t/data=!3m7!1e1!3m5!1svHyV1KxDNcaMVYstw1du0Q!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D2.9029416746289485%26panoid%3DvHyV1KxDNcaMVYstw1du0Q%26yaw%3D222.04804120401363!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDIxMi4wIKXMDSoASAFQAw%3D%3D) sign on General Booth Blvd in Virginia Beach has been removed.
- Problem is, there is now a bannerless US 60 shield (https://www.google.com/maps/@36.8339373,-75.9723982,3a,18.4y,20.63h,86.76t/data=!3m7!1e1!3m5!1sMqvEWZfqrfkDPNGEI1ZHSw!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D3.2379881953973637%26panoid%3DMqvEWZfqrfkDPNGEI1ZHSw%26yaw%3D20.62856596198783!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDIxMi4wIKXMDSoASAFQAw%3D%3D) northbound on Pacific Ave just north of 5th St, and this isn't US 60. US 60 isn't posted on Atlantic Ave, which is where it actually is.
- None of the other 311 requests I made regarding signage near the oceanfront were fulfilled and all of them are listed as "closed" and "void" in the 311 system. So much for that.
- The erroneous VA 408 sign at First Colonial Rd (which hasn't been VA 408 in years) and US 58 Business has been removed.
Quote from: WillWeaverRVA on February 18, 2025, 03:52:28 PMGoogle Street View has done some long-overdue updates in the Hampton Roads area. I put in a few 311 requests, so here's what I've noticed:
- The erroneous END US 60 (https://www.google.com/maps/@36.8302742,-75.9725688,3a,15y,222.05h,87.1t/data=!3m7!1e1!3m5!1svHyV1KxDNcaMVYstw1du0Q!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D2.9029416746289485%26panoid%3DvHyV1KxDNcaMVYstw1du0Q%26yaw%3D222.04804120401363!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDIxMi4wIKXMDSoASAFQAw%3D%3D) sign on General Booth Blvd in Virginia Beach has been removed.
Is that not where US-60 ends?
Quote from: sprjus4 on February 18, 2025, 04:05:45 PMQuote from: WillWeaverRVA on February 18, 2025, 03:52:28 PMGoogle Street View has done some long-overdue updates in the Hampton Roads area. I put in a few 311 requests, so here's what I've noticed:
- The erroneous END US 60 (https://www.google.com/maps/@36.8302742,-75.9725688,3a,15y,222.05h,87.1t/data=!3m7!1e1!3m5!1svHyV1KxDNcaMVYstw1du0Q!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D2.9029416746289485%26panoid%3DvHyV1KxDNcaMVYstw1du0Q%26yaw%3D222.04804120401363!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDIxMi4wIKXMDSoASAFQAw%3D%3D) sign on General Booth Blvd in Virginia Beach has been removed.
Is that not where US-60 ends?
Officially it ends at the Atlantic Ave turnaround on the north side of Rudee Inlet, and follows Atlantic Ave south of 17th St. (http://www.vahighways.com/route-log/us060.htm)
QuoteIn May 1958 (CTB), US 60 was rerouted onto Pacific Ave from 44th Ave southward to 17th Av then east back to Atlantic. Pacific Ave was a lot of new construction and it had originally been envisioned to make this one-way splits with Atlantic and Pacific. Atlantic Ave from 44th to 17th became US 60 Business (not numbered today).
In Feb 1961 (CTB), US 60 was formally removed from the long-demolished Rudee Inlet Bridge, leaving a discontinuous piece south of the inlet.
In Sept 1961 (CTB), the piece of US 60 below Rudee Inlet was decommissioned to SR 601 (see scan under US 60 Business) and US 60 ended at the Atlantic Ave turnaround at 2nd Ave, where it officially still ends today.
Quote from: 74/171FAN on February 18, 2025, 04:12:41 PMQuote from: sprjus4 on February 18, 2025, 04:05:45 PMQuote from: WillWeaverRVA on February 18, 2025, 03:52:28 PMGoogle Street View has done some long-overdue updates in the Hampton Roads area. I put in a few 311 requests, so here's what I've noticed:
- The erroneous END US 60 (https://www.google.com/maps/@36.8302742,-75.9725688,3a,15y,222.05h,87.1t/data=!3m7!1e1!3m5!1svHyV1KxDNcaMVYstw1du0Q!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D2.9029416746289485%26panoid%3DvHyV1KxDNcaMVYstw1du0Q%26yaw%3D222.04804120401363!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDIxMi4wIKXMDSoASAFQAw%3D%3D) sign on General Booth Blvd in Virginia Beach has been removed.
Is that not where US-60 ends?
Officially it ends at the Atlantic Ave turnaround on the north side of Rudee Inlet, and follows Atlantic Ave south of 17th St. (http://www.vahighways.com/route-log/us060.htm)
QuoteIn May 1958 (CTB), US 60 was rerouted onto Pacific Ave from 44th Ave southward to 17th Av then east back to Atlantic. Pacific Ave was a lot of new construction and it had originally been envisioned to make this one-way splits with Atlantic and Pacific. Atlantic Ave from 44th to 17th became US 60 Business (not numbered today).
In Feb 1961 (CTB), US 60 was formally removed from the long-demolished Rudee Inlet Bridge, leaving a discontinuous piece south of the inlet.
In Sept 1961 (CTB), the piece of US 60 below Rudee Inlet was decommissioned to SR 601 (see scan under US 60 Business) and US 60 ended at the Atlantic Ave turnaround at 2nd Ave, where it officially still ends today.
Yup. It's never ended where that END sign was.
Perhaps the AARoads pages should be updated then...
https://wiki.aaroads.com/wiki/U.S._Route_60
https://wiki.aaroads.com/wiki/U.S._Route_60_in_Virginia
https://www.aaroads.com/guides/us-060-va/
All three indicate the terminus being where Virginia Beach ha(d) it signed.
Quote from: WillWeaverRVA on February 18, 2025, 03:52:28 PMGoogle Street View has done some long-overdue updates in the Hampton Roads area. I put in a few 311 requests, so here's what I've noticed:
- The erroneous END US 60 (https://www.google.com/maps/@36.8302742,-75.9725688,3a,15y,222.05h,87.1t/data=!3m7!1e1!3m5!1svHyV1KxDNcaMVYstw1du0Q!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D2.9029416746289485%26panoid%3DvHyV1KxDNcaMVYstw1du0Q%26yaw%3D222.04804120401363!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDIxMi4wIKXMDSoASAFQAw%3D%3D) sign on General Booth Blvd in Virginia Beach has been removed.
- Problem is, there is now a bannerless US 60 shield (https://www.google.com/maps/@36.8339373,-75.9723982,3a,18.4y,20.63h,86.76t/data=!3m7!1e1!3m5!1sMqvEWZfqrfkDPNGEI1ZHSw!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D3.2379881953973637%26panoid%3DMqvEWZfqrfkDPNGEI1ZHSw%26yaw%3D20.62856596198783!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDIxMi4wIKXMDSoASAFQAw%3D%3D) northbound on Pacific Ave just north of 5th St, and this isn't US 60. US 60 isn't posted on Atlantic Ave, which is where it actually is.
- None of the other 311 requests I made regarding signage near the oceanfront were fulfilled and all of them are listed as "closed" and "void" in the 311 system. So much for that.
- The erroneous VA 408 sign at First Colonial Rd (which hasn't been VA 408 in years) and US 58 Business has been removed.
I am glad some of these things are getting corrected! I attempted to get some signage corrected in Newport News at the US 60/US 258-17 & VA 32 interchange but to no avail. Independent cities and their signage is abysmal in many cases..... it drives me up a wall!
Quote from: sprjus4 on February 18, 2025, 05:28:05 PMPerhaps the AARoads pages should be updated then...
https://wiki.aaroads.com/wiki/U.S._Route_60
https://wiki.aaroads.com/wiki/U.S._Route_60_in_Virginia
https://www.aaroads.com/guides/us-060-va/
All three indicate the terminus being where Virginia Beach ha(d) it signed.
If I have time, I might fix the wiki articles, but they're lifted from the Wikipedia articles that also listed the endpoint in the wrong place.
Quote from: WillWeaverRVA on February 19, 2025, 12:31:46 PMQuote from: sprjus4 on February 18, 2025, 05:28:05 PMPerhaps the AARoads pages should be updated then...
https://wiki.aaroads.com/wiki/U.S._Route_60
https://wiki.aaroads.com/wiki/U.S._Route_60_in_Virginia
https://www.aaroads.com/guides/us-060-va/
All three indicate the terminus being where Virginia Beach ha(d) it signed.
If I have time, I might fix the wiki articles, but they're lifted from the Wikipedia articles that also listed the endpoint in the wrong place.
Yeah, the history section of the VA article could use a ton of expansion as well.
Quote from: WillWeaverRVA on February 18, 2025, 03:52:28 PMGoogle Street View has done some long-overdue updates in the Hampton Roads area. I put in a few 311 requests, so here's what I've noticed:
- The erroneous END US 60 (https://www.google.com/maps/@36.8302742,-75.9725688,3a,15y,222.05h,87.1t/data=!3m7!1e1!3m5!1svHyV1KxDNcaMVYstw1du0Q!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D2.9029416746289485%26panoid%3DvHyV1KxDNcaMVYstw1du0Q%26yaw%3D222.04804120401363!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDIxMi4wIKXMDSoASAFQAw%3D%3D) sign on General Booth Blvd in Virginia Beach has been removed.
- Problem is, there is now a bannerless US 60 shield (https://www.google.com/maps/@36.8339373,-75.9723982,3a,18.4y,20.63h,86.76t/data=!3m7!1e1!3m5!1sMqvEWZfqrfkDPNGEI1ZHSw!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D3.2379881953973637%26panoid%3DMqvEWZfqrfkDPNGEI1ZHSw%26yaw%3D20.62856596198783!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDIxMi4wIKXMDSoASAFQAw%3D%3D) northbound on Pacific Ave just north of 5th St, and this isn't US 60. US 60 isn't posted on Atlantic Ave, which is where it actually is.
- None of the other 311 requests I made regarding signage near the oceanfront were fulfilled and all of them are listed as "closed" and "void" in the 311 system. So much for that.
- The erroneous VA 408 sign at First Colonial Rd (which hasn't been VA 408 in years) and US 58 Business has been removed.
I remember as a child when the former wye split at the intersection of Atlantic and Pacific there was small cut out shields showing both US 60 ( for Pacific SB) and US 60 Business ( for Atlantic SB).
Also on Laskin Road at Pacific the route both US 58 and 60 were signed EB with a white post and small cut out shields on the SE Corner of the intersection with US 58 EB signed straight for its last block and an erroneous US 60 shield with a double headed arrow instead of a business banner shield.
Further South at Pacific and VA Beach Blvd / 17th Street nothing was signed there as today.
So at least something was signed in the resort area unlike nothing signed other than the US 60 shield at Pacific and 5th. Even VA 44 was never signed from US 60 at 22nd as the one way couplet of 21st and 22nd were VA 44. Although the defunct VA Beach - Norfolk Expressway did have an official shield and some were posted on Atlantic and Pacific at 22nd.
Plus Route 44 and I-64 were written in text on a small LGS at 17th to direct motorists WB on VA Beach two blocks to the west and up the parallel street to 22nd I'm guessing to bypass Atlantic and Pacific traffic.
So yes, there was a Business route on Atlantic signed sporadically, but at Atlantic and 17th nothing to show it ended ,( as well as Business 58) there to reveal the official AASHTO routing of US 60 going over one block either way.
Quote from: roadman65 on February 24, 2025, 08:46:54 AMQuote from: WillWeaverRVA on February 18, 2025, 03:52:28 PMGoogle Street View has done some long-overdue updates in the Hampton Roads area. I put in a few 311 requests, so here's what I've noticed:
- The erroneous END US 60 (https://www.google.com/maps/@36.8302742,-75.9725688,3a,15y,222.05h,87.1t/data=!3m7!1e1!3m5!1svHyV1KxDNcaMVYstw1du0Q!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D2.9029416746289485%26panoid%3DvHyV1KxDNcaMVYstw1du0Q%26yaw%3D222.04804120401363!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDIxMi4wIKXMDSoASAFQAw%3D%3D) sign on General Booth Blvd in Virginia Beach has been removed.
- Problem is, there is now a bannerless US 60 shield (https://www.google.com/maps/@36.8339373,-75.9723982,3a,18.4y,20.63h,86.76t/data=!3m7!1e1!3m5!1sMqvEWZfqrfkDPNGEI1ZHSw!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D3.2379881953973637%26panoid%3DMqvEWZfqrfkDPNGEI1ZHSw%26yaw%3D20.62856596198783!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDIxMi4wIKXMDSoASAFQAw%3D%3D) northbound on Pacific Ave just north of 5th St, and this isn't US 60. US 60 isn't posted on Atlantic Ave, which is where it actually is.
- None of the other 311 requests I made regarding signage near the oceanfront were fulfilled and all of them are listed as "closed" and "void" in the 311 system. So much for that.
- The erroneous VA 408 sign at First Colonial Rd (which hasn't been VA 408 in years) and US 58 Business has been removed.
I remember as a child when the former wye split at the intersection of Atlantic and Pacific there was small cut out shields showing both US 60 ( for Pacific SB) and US 60 Business ( for Atlantic SB).
Also on Laskin Road at Pacific the route both US 58 and 60 were signed EB with a white post and small cut out shields on the SE Corner of the intersection with US 58 EB signed straight for its last block and an erroneous US 60 shield with a double headed arrow instead of a business banner shield.
Further South at Pacific and VA Beach Blvd / 17th Street nothing was signed there as today.
So at least something was signed in the resort area unlike nothing signed other than the US 60 shield at Pacific and 5th. Even VA 44 was never signed from US 60 at 22nd as the one way couplet of 21st and 22nd were VA 44. Although the defunct VA Beach - Norfolk Expressway did have an official shield and some were posted on Atlantic and Pacific at 22nd.
Plus Route 44 and I-64 were written in text on a small LGS at 17th to direct motorists WB on VA Beach two blocks to the west and up the parallel street to 22nd I'm guessing to bypass Atlantic and Pacific traffic.
So yes, there was a Business route on Atlantic signed sporadically, but at Atlantic and 17th nothing to show it ended ,( as well as Business 58) there to reveal the official AASHTO routing of US 60 going over one block either way.
Yeah, signage in Virginia Beach was way better in the first couple of decades after it merged with Princess Anne County because there was a lot of leftover VDOT signage. These days Virginia Beach seems uninterested in signing anything other than I-264 on the Oceanfront, although it's finally starting to improve...kinda.
Quote from: WillWeaverRVA on February 24, 2025, 09:35:59 AMQuote from: roadman65 on February 24, 2025, 08:46:54 AMQuote from: WillWeaverRVA on February 18, 2025, 03:52:28 PMGoogle Street View has done some long-overdue updates in the Hampton Roads area. I put in a few 311 requests, so here's what I've noticed:
- The erroneous END US 60 (https://www.google.com/maps/@36.8302742,-75.9725688,3a,15y,222.05h,87.1t/data=!3m7!1e1!3m5!1svHyV1KxDNcaMVYstw1du0Q!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D2.9029416746289485%26panoid%3DvHyV1KxDNcaMVYstw1du0Q%26yaw%3D222.04804120401363!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDIxMi4wIKXMDSoASAFQAw%3D%3D) sign on General Booth Blvd in Virginia Beach has been removed.
- Problem is, there is now a bannerless US 60 shield (https://www.google.com/maps/@36.8339373,-75.9723982,3a,18.4y,20.63h,86.76t/data=!3m7!1e1!3m5!1sMqvEWZfqrfkDPNGEI1ZHSw!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D3.2379881953973637%26panoid%3DMqvEWZfqrfkDPNGEI1ZHSw%26yaw%3D20.62856596198783!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDIxMi4wIKXMDSoASAFQAw%3D%3D) northbound on Pacific Ave just north of 5th St, and this isn't US 60. US 60 isn't posted on Atlantic Ave, which is where it actually is.
- None of the other 311 requests I made regarding signage near the oceanfront were fulfilled and all of them are listed as "closed" and "void" in the 311 system. So much for that.
- The erroneous VA 408 sign at First Colonial Rd (which hasn't been VA 408 in years) and US 58 Business has been removed.
I remember as a child when the former wye split at the intersection of Atlantic and Pacific there was small cut out shields showing both US 60 ( for Pacific SB) and US 60 Business ( for Atlantic SB).
Also on Laskin Road at Pacific the route both US 58 and 60 were signed EB with a white post and small cut out shields on the SE Corner of the intersection with US 58 EB signed straight for its last block and an erroneous US 60 shield with a double headed arrow instead of a business banner shield.
Further South at Pacific and VA Beach Blvd / 17th Street nothing was signed there as today.
So at least something was signed in the resort area unlike nothing signed other than the US 60 shield at Pacific and 5th. Even VA 44 was never signed from US 60 at 22nd as the one way couplet of 21st and 22nd were VA 44. Although the defunct VA Beach - Norfolk Expressway did have an official shield and some were posted on Atlantic and Pacific at 22nd.
Plus Route 44 and I-64 were written in text on a small LGS at 17th to direct motorists WB on VA Beach two blocks to the west and up the parallel street to 22nd I'm guessing to bypass Atlantic and Pacific traffic.
So yes, there was a Business route on Atlantic signed sporadically, but at Atlantic and 17th nothing to show it ended ,( as well as Business 58) there to reveal the official AASHTO routing of US 60 going over one block either way.
Yeah, signage in Virginia Beach was way better in the first couple of decades after it merged with Princess Anne County because there was a lot of leftover VDOT signage. These days Virginia Beach seems uninterested in signing anything other than I-264 on the Oceanfront, although it's finally starting to improve...kinda.
Yes I wondered about that former assembly on Laskin at Pacific as it had cutouts on a white wooden posts. Now if memory serves me correctly, those white posts were the old way VDOT used to moore shields. Independent cities used small cut outs on v shaped slotted posts, before the uni- shields that many use nowadays.
Quote from: WillWeaverRVA on February 24, 2025, 09:35:59 AMQuote from: roadman65 on February 24, 2025, 08:46:54 AMQuote from: WillWeaverRVA on February 18, 2025, 03:52:28 PMGoogle Street View has done some long-overdue updates in the Hampton Roads area. I put in a few 311 requests, so here's what I've noticed:
- The erroneous END US 60 (https://www.google.com/maps/@36.8302742,-75.9725688,3a,15y,222.05h,87.1t/data=!3m7!1e1!3m5!1svHyV1KxDNcaMVYstw1du0Q!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D2.9029416746289485%26panoid%3DvHyV1KxDNcaMVYstw1du0Q%26yaw%3D222.04804120401363!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDIxMi4wIKXMDSoASAFQAw%3D%3D) sign on General Booth Blvd in Virginia Beach has been removed.
- Problem is, there is now a bannerless US 60 shield (https://www.google.com/maps/@36.8339373,-75.9723982,3a,18.4y,20.63h,86.76t/data=!3m7!1e1!3m5!1sMqvEWZfqrfkDPNGEI1ZHSw!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D3.2379881953973637%26panoid%3DMqvEWZfqrfkDPNGEI1ZHSw%26yaw%3D20.62856596198783!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDIxMi4wIKXMDSoASAFQAw%3D%3D) northbound on Pacific Ave just north of 5th St, and this isn't US 60. US 60 isn't posted on Atlantic Ave, which is where it actually is.
- None of the other 311 requests I made regarding signage near the oceanfront were fulfilled and all of them are listed as "closed" and "void" in the 311 system. So much for that.
- The erroneous VA 408 sign at First Colonial Rd (which hasn't been VA 408 in years) and US 58 Business has been removed.
I remember as a child when the former wye split at the intersection of Atlantic and Pacific there was small cut out shields showing both US 60 ( for Pacific SB) and US 60 Business ( for Atlantic SB).
Also on Laskin Road at Pacific the route both US 58 and 60 were signed EB with a white post and small cut out shields on the SE Corner of the intersection with US 58 EB signed straight for its last block and an erroneous US 60 shield with a double headed arrow instead of a business banner shield.
Further South at Pacific and VA Beach Blvd / 17th Street nothing was signed there as today.
So at least something was signed in the resort area unlike nothing signed other than the US 60 shield at Pacific and 5th. Even VA 44 was never signed from US 60 at 22nd as the one way couplet of 21st and 22nd were VA 44. Although the defunct VA Beach - Norfolk Expressway did have an official shield and some were posted on Atlantic and Pacific at 22nd.
Plus Route 44 and I-64 were written in text on a small LGS at 17th to direct motorists WB on VA Beach two blocks to the west and up the parallel street to 22nd I'm guessing to bypass Atlantic and Pacific traffic.
So yes, there was a Business route on Atlantic signed sporadically, but at Atlantic and 17th nothing to show it ended ,( as well as Business 58) there to reveal the official AASHTO routing of US 60 going over one block either way.
Yeah, signage in Virginia Beach was way better in the first couple of decades after it merged with Princess Anne County because there was a lot of leftover VDOT signage. These days Virginia Beach seems uninterested in signing anything other than I-264 on the Oceanfront, although it's finally starting to improve...kinda.
Agreed! Chesapeake does a much better job regarding signage. I drove around both cities last weekend and noticed the stark difference between the two.
Quote from: jb_va23 on February 25, 2025, 07:59:31 PMQuote from: WillWeaverRVA on February 24, 2025, 09:35:59 AMQuote from: roadman65 on February 24, 2025, 08:46:54 AMQuote from: WillWeaverRVA on February 18, 2025, 03:52:28 PMGoogle Street View has done some long-overdue updates in the Hampton Roads area. I put in a few 311 requests, so here's what I've noticed:
- The erroneous END US 60 (https://www.google.com/maps/@36.8302742,-75.9725688,3a,15y,222.05h,87.1t/data=!3m7!1e1!3m5!1svHyV1KxDNcaMVYstw1du0Q!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D2.9029416746289485%26panoid%3DvHyV1KxDNcaMVYstw1du0Q%26yaw%3D222.04804120401363!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDIxMi4wIKXMDSoASAFQAw%3D%3D) sign on General Booth Blvd in Virginia Beach has been removed.
- Problem is, there is now a bannerless US 60 shield (https://www.google.com/maps/@36.8339373,-75.9723982,3a,18.4y,20.63h,86.76t/data=!3m7!1e1!3m5!1sMqvEWZfqrfkDPNGEI1ZHSw!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D3.2379881953973637%26panoid%3DMqvEWZfqrfkDPNGEI1ZHSw%26yaw%3D20.62856596198783!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDIxMi4wIKXMDSoASAFQAw%3D%3D) northbound on Pacific Ave just north of 5th St, and this isn't US 60. US 60 isn't posted on Atlantic Ave, which is where it actually is.
- None of the other 311 requests I made regarding signage near the oceanfront were fulfilled and all of them are listed as "closed" and "void" in the 311 system. So much for that.
- The erroneous VA 408 sign at First Colonial Rd (which hasn't been VA 408 in years) and US 58 Business has been removed.
I remember as a child when the former wye split at the intersection of Atlantic and Pacific there was small cut out shields showing both US 60 ( for Pacific SB) and US 60 Business ( for Atlantic SB).
Also on Laskin Road at Pacific the route both US 58 and 60 were signed EB with a white post and small cut out shields on the SE Corner of the intersection with US 58 EB signed straight for its last block and an erroneous US 60 shield with a double headed arrow instead of a business banner shield.
Further South at Pacific and VA Beach Blvd / 17th Street nothing was signed there as today.
So at least something was signed in the resort area unlike nothing signed other than the US 60 shield at Pacific and 5th. Even VA 44 was never signed from US 60 at 22nd as the one way couplet of 21st and 22nd were VA 44. Although the defunct VA Beach - Norfolk Expressway did have an official shield and some were posted on Atlantic and Pacific at 22nd.
Plus Route 44 and I-64 were written in text on a small LGS at 17th to direct motorists WB on VA Beach two blocks to the west and up the parallel street to 22nd I'm guessing to bypass Atlantic and Pacific traffic.
So yes, there was a Business route on Atlantic signed sporadically, but at Atlantic and 17th nothing to show it ended ,( as well as Business 58) there to reveal the official AASHTO routing of US 60 going over one block either way.
Yeah, signage in Virginia Beach was way better in the first couple of decades after it merged with Princess Anne County because there was a lot of leftover VDOT signage. These days Virginia Beach seems uninterested in signing anything other than I-264 on the Oceanfront, although it's finally starting to improve...kinda.
Agreed! Chesapeake does a much better job regarding signage. I drove around both cities last weekend and noticed the stark difference between the two.
I feel like it unfortunately has gotten worse over the last decade. They certainly used to be better, and a lot of those signs still remain.
Well, I submitted a bunch of 311 requests to have primary routes signed in Alexandria and was basically told "people know routes by their names and not their numbers so we're not signing them". Ah well.
Quote from: WillWeaverRVA on February 26, 2025, 03:51:43 PMWell, I submitted a bunch of 311 requests to have primary routes signed in Alexandria and was basically told "people know routes by their names and not their numbers so we're not signing them". Ah well.
Im guessing thats why DC no longer signs it's US routes like US 1 or 50 for that reason.
Yet US 29, since being realigned, has been signed on its new alignment. Probably to get drivers adjusted to the New routing.
Quote from: WillWeaverRVA on February 26, 2025, 03:51:43 PMWell, I submitted a bunch of 311 requests to have primary routes signed in Alexandria and was basically told "people know routes by their names and not their numbers so we're not signing them". Ah well.
It's sort of circular: To some extent, people refer to the routes by their names precisely because the numbers aren't posted and they don't know what the numbers are. There are some exceptions—I sometimes hear Duke Street referred to as Route 236, especially when it's being used in the context of that road combined with the part in Fairfax County called Little River Turnpike (e.g., "From Old Town, take 236 west and when you hit the light at Braddock Road, the golf course parking is the next driveway on your right."), and I sometimes hear the portions of Route 1 referred to as such, especially because it changes names multiple times within the City of Alexandria.
Van Dorn Street has route numbers posted in several places within the city limits, but I've never heard anyone call it by its number and I suspect part of the reason there is that it changes numbers (to a secondary route) when it crosses into Fairfax County. I think that's probably also the case for Telegraph Road, which becomes Secondary Route 611 a short distance over the county line. Interestingly, there is at least one sign for Telegraph Road within the city limits that refers to it
solely by number, though it's in a somewhat obscure location for most drivers (https://maps.app.goo.gl/BC9fgXpc5fodNrcn6) (I pass it fairly regularly to connect from eastbound Eisenhower Avenue to southbound Telegraph).
https://maps.app.goo.gl/uiNgL8B5SMyT3gns7?g_st=ac
A US 60 shield I found along Atlantic Ave at Pacific Ave erroneously showing it as N-S.
The latest maps shows that Atlantic Avenue no longer intersects Pacific as a child de sac was created and Atlantic Avenue is in two segments with motorists now using 40th and Pacific to continue the through movements.
I assume that erroneous shield is now gone.
https://maps.app.goo.gl/Cw1m8vRGsUQqbNUY8?g_st=ac
Edit : yes it is gone as I found the latest caption showing the signal gone there which had that shield attached.
Quote from: WillWeaverRVA on February 26, 2025, 03:51:43 PMWell, I submitted a bunch of 311 requests to have primary routes signed in Alexandria and was basically told "people know routes by their names and not their numbers so we're not signing them". Ah well.
...and now I got notified that signs will indeed go up in the next 30 days. I'm gonna have to compile a list of locations I submitted requests for...
Quote from: WillWeaverRVA on February 28, 2025, 11:50:23 PMQuote from: WillWeaverRVA on February 26, 2025, 03:51:43 PMWell, I submitted a bunch of 311 requests to have primary routes signed in Alexandria and was basically told "people know routes by their names and not their numbers so we're not signing them". Ah well.
...and now I got notified that signs will indeed go up in the next 30 days. I'm gonna have to compile a list of locations I submitted requests for...
2 questions...
How many cities did you do this with?
Where would you like your statue placed?
Quote from: Mapmikey on March 01, 2025, 10:22:24 AMQuote from: WillWeaverRVA on February 28, 2025, 11:50:23 PMQuote from: WillWeaverRVA on February 26, 2025, 03:51:43 PMWell, I submitted a bunch of 311 requests to have primary routes signed in Alexandria and was basically told "people know routes by their names and not their numbers so we're not signing them". Ah well.
...and now I got notified that signs will indeed go up in the next 30 days. I'm gonna have to compile a list of locations I submitted requests for...
2 questions...
How many cities did you do this with?
Where would you like your statue placed?
:-D
Just Richmond, Virginia Beach, and Alexandria for now.
Hey, I figured if it worked (to an extent) in Richmond, maybe it'd work elsewhere.
So here are all the 311 requests I put in for signage in Alexandria:
- VA 401 and VA 420 signage at Seminary Rd and Kenmore Ave: Alexandria said no, people use names and not numbers
- VA 402 signage at I-395 and Shirlington Circle: "we will investigate if this is where a route ends or begins, if so we'll put up signage in the next 30 days" (well, I attached the VDOT arcGIS map...)
- VA 236 and VA 400 at Duke St & Washington St: same as VA 402 and I-395
- VA 7 and VA 400 signage at King St & Washington St: same as VA 402 and I-395
- VA 7 and VA 420 signage (plus I-395 and I-495 trailblazers) at King St & Janney's Ln
- VA 402 and VA 420 signage at Quaker Ln, Janney's Ln, & Seminary Rd
- VA 7 and VA 402 signage at King St and Quaker Ln: "The City's Transportation Engineering Division has reviewed your request Route sign designated at various locations. We will work with our Traffic Management team to install such signs at appropriate locations. These signs should be placed in the next 30 business days. Thank you for bringing this to our attention.", i.e. "stop bugging us, we'll put up signs in the next 30 days" :-D
I may need to see what other cities have 311 pages that I can put in requests for.
Quote from: WillWeaverRVA on February 26, 2025, 03:51:43 PMWell, I submitted a bunch of 311 requests to have primary routes signed in Alexandria and was basically told "people know routes by their names and not their numbers so we're not signing them". Ah well.
Funny enough, I had a conversation with a member of the Manassas Park City Council about the lack of posting for VA-213 and this was the answer I received.
Quote from: WillWeaverRVA on March 01, 2025, 12:37:53 PMSo here are all the 311 requests I put in for signage in Alexandria:
- VA 401 and VA 420 signage at Seminary Rd and Kenmore Ave: Alexandria said no, people use names and not numbers
- VA 402 signage at I-395 and Shirlington Circle: "we will investigate if this is where a route ends or begins, if so we'll put up signage in the next 30 days" (well, I attached the VDOT arcGIS map...)
- VA 236 and VA 400 at Duke St & Washington St: same as VA 402 and I-395
- VA 7 and VA 400 signage at King St & Washington St: same as VA 402 and I-395
- VA 7 and VA 420 signage (plus I-395 and I-495 trailblazers) at King St & Janney's Ln
- VA 402 and VA 420 signage at Quaker Ln, Janney's Ln, & Seminary Rd
- VA 7 and VA 402 signage at King St and Quaker Ln: "The City's Transportation Engineering Division has reviewed your request Route sign designated at various locations. We will work with our Traffic Management team to install such signs at appropriate locations. These signs should be placed in the next 30 business days. Thank you for bringing this to our attention.", i.e. "stop bugging us, we'll put up signs in the next 30 days" :-D
I may need to see what other cities have 311 pages that I can put in requests for.
It would be amazing to see VA-420 posted after all these years!
I've been tempted to do this with VDOT to install secondary route shields at intersections with significant secondary routes around Northern VA. These are some that come to mind:
- Route 620 shields on VA-123 for its intersection with Braddock Rd (as well as VA-123 shields approaching Ox Rd heading east on Braddock Rd).
- Route 644 shields on VA-286 for its intersection with Old Keene Mill Road.
- Route 650 shields on VA-236 for its intersection with Annandale Rd.
- Route 659 shields on VA-234 for its intersection with Gum Spring Road.
I'm sure there are many others that would make sense. But maybe these are not necessary due to how drivers refer to these mostly by their street names, anyhow.
Quote from: dfnva on March 01, 2025, 01:21:30 PMIt would be amazing to see VA-420 posted after all these years!
Something tells me that those signs are going to get stolen.
My reading of his summary of their reply is that VA-420 is not one of the ones they're considering posting, though I guess we'll see. I note VDOT itself has never posted that route number on the LGSs on I-395, either.
I'd like to see the VDOT portion of VA-237 signed, considering that there are signs all over for it on I-66 yet nothing on the actual road itself. Anyone interested in filing a request for it :-D
Barely any signs on VA-120 and VA-124 as well :-/
Quote from: WillWeaverRVA on March 01, 2025, 12:37:53 PMSo here are all the 311 requests I put in for signage in Alexandria:
- VA 401 and VA 420 signage at Seminary Rd and Kenmore Ave: Alexandria said no, people use names and not numbers
- VA 402 signage at I-395 and Shirlington Circle: "we will investigate if this is where a route ends or begins, if so we'll put up signage in the next 30 days" (well, I attached the VDOT arcGIS map...)
- VA 236 and VA 400 at Duke St & Washington St: same as VA 402 and I-395
- VA 7 and VA 400 signage at King St & Washington St: same as VA 402 and I-395
- VA 7 and VA 420 signage (plus I-395 and I-495 trailblazers) at King St & Janney's Ln
- VA 402 and VA 420 signage at Quaker Ln, Janney's Ln, & Seminary Rd
- VA 7 and VA 402 signage at King St and Quaker Ln: "The City's Transportation Engineering Division has reviewed your request Route sign designated at various locations. We will work with our Traffic Management team to install such signs at appropriate locations. These signs should be placed in the next 30 business days. Thank you for bringing this to our attention.", i.e. "stop bugging us, we'll put up signs in the next 30 days" :-D
I may need to see what other cities have 311 pages that I can put in requests for.
Maybe Norfolk for VA 404 and 405. Also, do counties have 311 pages, or just cities? I wouldn't mind seeing VA 366, 410, or 327 get signed.
Unrelated, do we think there could be a new VA 408 out there somewhere since 409 and 410 have come back into use in the past 15 years?
VA 327 is signed the way Chesterfield County likes to sign routes.
(https://live.staticflickr.com/65535/53638995400_858084441d_c.jpg) (https://flic.kr/p/2pHTSzw)VA 327 AT SR 1111 (https://flic.kr/p/2pHTSzw) by Mark Moore (https://www.flickr.com/photos/199744333@N06/), on Flickr
Quote from: Takumi on March 02, 2025, 10:24:55 PMUnrelated, do we think there could be a new VA 408 out there somewhere since 409 and 410 have come back into use in the past 15 years?
After VA 410 was discovered I went through the dataset behind the online VDOT map and there were not any other new state routes in there.
Quote from: Takumi on March 02, 2025, 10:24:55 PMQuote from: WillWeaverRVA on March 01, 2025, 12:37:53 PMSo here are all the 311 requests I put in for signage in Alexandria:
- VA 401 and VA 420 signage at Seminary Rd and Kenmore Ave: Alexandria said no, people use names and not numbers
- VA 402 signage at I-395 and Shirlington Circle: "we will investigate if this is where a route ends or begins, if so we'll put up signage in the next 30 days" (well, I attached the VDOT arcGIS map...)
- VA 236 and VA 400 at Duke St & Washington St: same as VA 402 and I-395
- VA 7 and VA 400 signage at King St & Washington St: same as VA 402 and I-395
- VA 7 and VA 420 signage (plus I-395 and I-495 trailblazers) at King St & Janney's Ln
- VA 402 and VA 420 signage at Quaker Ln, Janney's Ln, & Seminary Rd
- VA 7 and VA 402 signage at King St and Quaker Ln: "The City's Transportation Engineering Division has reviewed your request Route sign designated at various locations. We will work with our Traffic Management team to install such signs at appropriate locations. These signs should be placed in the next 30 business days. Thank you for bringing this to our attention.", i.e. "stop bugging us, we'll put up signs in the next 30 days" :-D
I may need to see what other cities have 311 pages that I can put in requests for.
Maybe Norfolk for VA 404 and 405. Also, do counties have 311 pages, or just cities? I wouldn't mind seeing VA 366, 410, or 327 get signed.
Unrelated, do we think there could be a new VA 408 out there somewhere since 409 and 410 have come back into use in the past 15 years?
Online 311 portals seem to be a relatively recent development. Richmond debuted theirs in 2023, and Virginia Beach opened theirs last year. I imagine only cities and most towns would have them since everything else is under VDOT's purview.
Looks like Norfolk (https://www.mynorfolk.org/#/homepage) does have one, as does Chesapeake. Hampton seems to only have a mobile app for requesting city services.
Quote from: 74/171FAN on March 02, 2025, 10:42:17 PMVA 327 is signed the way Chesterfield County likes to sign routes.
(https://live.staticflickr.com/65535/53638995400_858084441d_c.jpg) (https://flic.kr/p/2pHTSzw)VA 327 AT SR 1111 (https://flic.kr/p/2pHTSzw) by Mark Moore (https://www.flickr.com/photos/199744333@N06/), on Flickr
If VDOT isn't going to post shields, this is fine. At least Chesterfield got the route number right, elsewhere they have VA 324 signed as SR 1755 (https://www.google.com/maps/@37.5229443,-77.5634944,3a,75y,64.49h,89.28t/data=!3m7!1e1!3m5!1sZ9gwvGf5M80JDuRkK2DT-Q!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D0.717745491756574%26panoid%3DZ9gwvGf5M80JDuRkK2DT-Q%26yaw%3D64.48782566977775!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDIyNi4xIKXMDSoASAFQAw%3D%3D) for some reason.
Quote from: WillWeaverRVA on March 03, 2025, 10:46:05 AMQuote from: 74/171FAN on March 02, 2025, 10:42:17 PMVA 327 is signed the way Chesterfield County likes to sign routes.
(https://live.staticflickr.com/65535/53638995400_858084441d_c.jpg) (https://flic.kr/p/2pHTSzw)VA 327 AT SR 1111 (https://flic.kr/p/2pHTSzw) by Mark Moore (https://www.flickr.com/photos/199744333@N06/), on Flickr
If VDOT isn't going to post shields, this is fine. At least Chesterfield got the route number right, elsewhere they have VA 324 signed as SR 1755 (https://www.google.com/maps/@37.5229443,-77.5634944,3a,75y,64.49h,89.28t/data=!3m7!1e1!3m5!1sZ9gwvGf5M80JDuRkK2DT-Q!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D0.717745491756574%26panoid%3DZ9gwvGf5M80JDuRkK2DT-Q%26yaw%3D64.48782566977775!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDIyNi4xIKXMDSoASAFQAw%3D%3D) for some reason.
Yeah I have noticed a few of these while working on the Chesterfield County 800+ secondary route list for the AARoads Wiki (https://wiki.aaroads.com/wiki/List_of_secondary_state_highways_in_Chesterfield_County,_Virginia_(800%2B)).
The most obvious goof being SR 1686 (https://www.google.com/maps/@37.4771728,-77.5185105,3a,75y,287.44h,82.88t/data=!3m7!1e1!3m5!1soaAc560m49O5qYJdSrcqpw!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D7.1235427342830775%26panoid%3DoaAc560m49O5qYJdSrcqpw%26yaw%3D287.4356641782833!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDIyNi4xIKXMDSoASAFQAw%3D%3D) when it should be SR 2230.
Quote from: 74/171FAN on March 03, 2025, 01:50:38 PMQuote from: WillWeaverRVA on March 03, 2025, 10:46:05 AMQuote from: 74/171FAN on March 02, 2025, 10:42:17 PMVA 327 is signed the way Chesterfield County likes to sign routes.
(https://live.staticflickr.com/65535/53638995400_858084441d_c.jpg) (https://flic.kr/p/2pHTSzw)VA 327 AT SR 1111 (https://flic.kr/p/2pHTSzw) by Mark Moore (https://www.flickr.com/photos/199744333@N06/), on Flickr
If VDOT isn't going to post shields, this is fine. At least Chesterfield got the route number right, elsewhere they have VA 324 signed as SR 1755 (https://www.google.com/maps/@37.5229443,-77.5634944,3a,75y,64.49h,89.28t/data=!3m7!1e1!3m5!1sZ9gwvGf5M80JDuRkK2DT-Q!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D0.717745491756574%26panoid%3DZ9gwvGf5M80JDuRkK2DT-Q%26yaw%3D64.48782566977775!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDIyNi4xIKXMDSoASAFQAw%3D%3D) for some reason.
Yeah I have noticed a few of these while working on the Chesterfield County 800+ secondary route list for the AARoads Wiki (https://wiki.aaroads.com/wiki/List_of_secondary_state_highways_in_Chesterfield_County,_Virginia_(800%2B)).
The most obvious goof being SR 1686 (https://www.google.com/maps/@37.4771728,-77.5185105,3a,75y,287.44h,82.88t/data=!3m7!1e1!3m5!1soaAc560m49O5qYJdSrcqpw!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D7.1235427342830775%26panoid%3DoaAc560m49O5qYJdSrcqpw%26yaw%3D287.4356641782833!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDIyNi4xIKXMDSoASAFQAw%3D%3D) when it should be SR 2230.
Even some 6xx secondaries have the wrong number on occasion, such as Woodpecker Road as SR 676 instead of 626. (https://maps.app.goo.gl/4QJkRamZieL5Z7Md8) They even had "SR36" on River Road street blades as far west as Riverway Road in the past, but now it looks like newer installations are replacing those with correct 602s. As of now there's still one with a 36 at Second Branch Road.
The Chatsworth Avenue thing for VA 324 has always been odd to me, because Chatsworth Avenue is a nearby neighborhood street in Bon Air, though based on other street blades it does appear to actually be SR 1755.
Quote from: Takumi on March 03, 2025, 02:30:00 PMThe Chatsworth Avenue thing for VA 324 has always been odd to me, because Chatsworth Avenue is a nearby neighborhood street in Bon Air, though based on other street blades it does appear to actually be SR 1755.
Chatsworth Avenue is similar to a city street in that it exists in segments. However, the segment that serves the Bon Air Juvenile Correctional Center is significantly longer than the neighborhood street is, and they're both explicitly part of Chatsworth Avenue (as Bon Air JCC has a Chatsworth Avenue address). That segment predates the neighborhood street, and I guess Chesterfield County decided to name it as part of Chatsworth Avenue.
I submitted some 311 requests to Hampton regarding signing US 258 and VA 143 on or near Fort Monroe since the area is under city jurisdiction now (despite there being some VA 9xxxx routes there), and the VDOT ArcGIS map shows US 258 and VA 143 running on McNair Drive on Fort Monroe as a useless concurrency before ending near the Chamberlin Hotel.
I also submitted one to Norfolk regarding the infamous VA 564 sign leaving the naval base, but I doubt they'll do anything with that one since it's on Navy property (even though VDOT installed it).
Re: Chesterfield putting route numbers on its street blades, VA 366 does not have a number on its blade at all. Just "Brightpoint Dr".
Quote from: Takumi on March 07, 2025, 12:15:49 AMRe: Chesterfield putting route numbers on its street blades, VA 366 does not have a number on its blade at all. Just "Brightpoint Dr".
Since I seem to have made this my new mission, I emailed Chesterfield County about the Chatsworth and Brightpoint sign madness.
Quote from: WillWeaverRVA on March 07, 2025, 09:35:21 AMQuote from: Takumi on March 07, 2025, 12:15:49 AMRe: Chesterfield putting route numbers on its street blades, VA 366 does not have a number on its blade at all. Just "Brightpoint Dr".
Since I seem to have made this my new mission, I emailed Chesterfield County about the Chatsworth and Brightpoint sign madness.
Some of the newer subdivision routes do not have them either, but I think that is more of either an oversight or waiting for VDOT to choose numbers than anything else.
Quote from: 74/171FAN on March 07, 2025, 10:08:47 AMQuote from: WillWeaverRVA on March 07, 2025, 09:35:21 AMQuote from: Takumi on March 07, 2025, 12:15:49 AMRe: Chesterfield putting route numbers on its street blades, VA 366 does not have a number on its blade at all. Just "Brightpoint Dr".
Since I seem to have made this my new mission, I emailed Chesterfield County about the Chatsworth and Brightpoint sign madness.
Some of the newer subdivision routes do not have them either, but I think that is more of either an oversight or waiting for VDOT to choose numbers than anything else.
Some of those subdivisions haven't actually submitted their streets (https://www.vdot.virginia.gov/doing-business/technical-guidance-and-support/land-use-and-development/secondary-street-acceptance-requirements/) to VDOT for addition to the secondary system. They'll probably get route numbers eventually.
Quote from: WillWeaverRVA on March 06, 2025, 10:49:09 PMI submitted some 311 requests to Hampton regarding signing US 258 and VA 143 on or near Fort Monroe since the area is under city jurisdiction now (despite there being some VA 9xxxx routes there), and the VDOT ArcGIS map shows US 258 and VA 143 running on McNair Drive on Fort Monroe as a useless concurrency before ending near the Chamberlin Hotel.
And that didn't take long, all the requests are shown as cancelled.
Quote from: WillWeaverRVA on March 07, 2025, 09:35:21 AMQuote from: Takumi on March 07, 2025, 12:15:49 AMRe: Chesterfield putting route numbers on its street blades, VA 366 does not have a number on its blade at all. Just "Brightpoint Dr".
Since I seem to have made this my new mission, I emailed Chesterfield County about the Chatsworth and Brightpoint sign madness.
I think the Chatsworth one for VA 324 is like the aforementioned VA 36 blades on the west-of-anywhere-VA-36-ever-was parts of River Road, where they likely just made a batch of signs and assumed they all had the same number.
Also worth noting, MPC Way was fairly recent new construction and most if not all of the rest of VA 327 is now behind gates. What few blades are visible on campus on GMSV appear to be university installations.
VA 375 is now posted with erroneous circle shields in both directions from VA 3. The rectangle 375 that had been there 30+ years was removed. This change occurred very recently.
Quote from: Mapmikey on March 08, 2025, 03:52:18 PMVA 375 is now posted with erroneous circle shields in both directions from VA 3. The rectangle 375 that had been there 30+ years was removed. This change occurred very recently.
Since I guess this route is going into Travel Mapping now, I am glad I clinched it in 2022.
Hampton is weird. The city reopened all my Fort Monroe-related 311 requests.
And this is now up at 17th and Broad in Richmond. I need to get them to sign the rest of the movements now.
(https://i.ibb.co/gZH01b3G/IMG-5160.jpg)
What's with that "lifespace communities" link at the bottom?
Quote from: Takumi on March 14, 2025, 01:02:52 PMWhat's with that "lifespace communities" link at the bottom?
I don't know, it sure wasn't there when I made the post. I just removed it. Might be the stupid image host being stupid.
Quote from: Takumi on March 02, 2025, 10:24:55 PMMaybe Norfolk for VA 404 and 405. Also, do counties have 311 pages, or just cities? I wouldn't mind seeing VA 366, 410, or 327 get signed.
As a follow-up on this, I requested them and Norfolk told me no and claimed they're not required to post state routes in their city limits (even though they post others). I raised the point of the signage at VA 403, but that was apparently installed by Virginia Beach.
The zombie 386 shields have been corrected, looks like for a couple years now.
Quote from: Takumi on March 22, 2025, 01:24:27 AMThe zombie 386 shields have been corrected, looks like for a couple years now.
Yeah, old VA 386 is signed as SR 883 now. (https://live.staticflickr.com/65535/53963383863_6730928d94_c.jpg) (https://flic.kr/p/2qdyrY4)US 58 WEST AT SR 883 (https://flic.kr/p/2qdyrY4) by Mark Moore (https://www.flickr.com/photos/199744333@N06/), on Flickr
Quote from: 74/171FAN on March 22, 2025, 08:34:52 AMQuote from: Takumi on March 22, 2025, 01:24:27 AMThe zombie 386 shields have been corrected, looks like for a couple years now.
Yeah, old VA 386 is signed as SR 883 now.
For some reason they took down the directional arrows on both sides here. When they corrected the zombie 386 circles that were briefly posted in 2022, there were arrows pointing in both directions under the 883 shields.
The seriously misguided US 40 shield (https://www.google.com/maps/@36.8550333,-75.994748,3a,19.5y,83.28h,87.41t/data=!3m7!1e1!3m5!1sBd9FiVxM-d_r5cr3iaxvHw!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D2.5914578377291804%26panoid%3DBd9FiVxM-d_r5cr3iaxvHw%26yaw%3D83.28091907917451!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDMxOS4yIKXMDSoASAFQAw%3D%3D) on Laskin Road in Virginia Beach has finally been fixed. (https://www.google.com/maps/@36.8549798,-75.9949903,3a,15.1y,77.75h,88.55t/data=!3m7!1e1!3m5!1srVpZ0bELD9XUKym3j1vURg!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D1.4457076781266096%26panoid%3DrVpZ0bELD9XUKym3j1vURg%26yaw%3D77.75227486421217!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDMxOS4yIKXMDSoASAFQAw%3D%3D)
Sadly, a 311 request that I put in to have the order of these signs (https://www.google.com/maps/@36.8581465,-75.9852681,3a,45.1y,281.42h,87.22t/data=!3m7!1e1!3m5!1sxrfJf5Q3hbM7pyvNSzbLIA!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D2.7758692338375397%26panoid%3DxrfJf5Q3hbM7pyvNSzbLIA%26yaw%3D281.4245392674873!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDMxOS4yIKXMDSoASAFQAw%3D%3D) fixed didn't end up getting done.
Quote from: WillWeaverRVA on March 24, 2025, 03:48:52 PMThe seriously misguided US 40 shield (https://www.google.com/maps/@36.8550333,-75.994748,3a,19.5y,83.28h,87.41t/data=!3m7!1e1!3m5!1sBd9FiVxM-d_r5cr3iaxvHw!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D2.5914578377291804%26panoid%3DBd9FiVxM-d_r5cr3iaxvHw%26yaw%3D83.28091907917451!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDMxOS4yIKXMDSoASAFQAw%3D%3D) on Laskin Road in Virginia Beach has finally been fixed. (https://www.google.com/maps/@36.8549798,-75.9949903,3a,15.1y,77.75h,88.55t/data=!3m7!1e1!3m5!1srVpZ0bELD9XUKym3j1vURg!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D1.4457076781266096%26panoid%3DrVpZ0bELD9XUKym3j1vURg%26yaw%3D77.75227486421217!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDMxOS4yIKXMDSoASAFQAw%3D%3D)
Sadly, a 311 request that I put in to have the order of these signs (https://www.google.com/maps/@36.8581465,-75.9852681,3a,45.1y,281.42h,87.22t/data=!3m7!1e1!3m5!1sxrfJf5Q3hbM7pyvNSzbLIA!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D2.7758692338375397%26panoid%3DxrfJf5Q3hbM7pyvNSzbLIA%26yaw%3D281.4245392674873!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDMxOS4yIKXMDSoASAFQAw%3D%3D) fixed didn't end up getting done.
The only issue with the bottom sign is the color of the "West" shield, I don't think the order itself is an issue.
Quote from: WillWeaverRVA on March 24, 2025, 03:48:52 PMThe seriously misguided US 40 shield (https://www.google.com/maps/@36.8550333,-75.994748,3a,19.5y,83.28h,87.41t/data=!3m7!1e1!3m5!1sBd9FiVxM-d_r5cr3iaxvHw!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D2.5914578377291804%26panoid%3DBd9FiVxM-d_r5cr3iaxvHw%26yaw%3D83.28091907917451!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDMxOS4yIKXMDSoASAFQAw%3D%3D) on Laskin Road in Virginia Beach has finally been fixed. (https://www.google.com/maps/@36.8549798,-75.9949903,3a,15.1y,77.75h,88.55t/data=!3m7!1e1!3m5!1srVpZ0bELD9XUKym3j1vURg!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D1.4457076781266096%26panoid%3DrVpZ0bELD9XUKym3j1vURg%26yaw%3D77.75227486421217!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDMxOS4yIKXMDSoASAFQAw%3D%3D)
Sadly, a 311 request that I put in to have the order of these signs (https://www.google.com/maps/@36.8581465,-75.9852681,3a,45.1y,281.42h,87.22t/data=!3m7!1e1!3m5!1sxrfJf5Q3hbM7pyvNSzbLIA!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D2.7758692338375397%26panoid%3DxrfJf5Q3hbM7pyvNSzbLIA%26yaw%3D281.4245392674873!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDMxOS4yIKXMDSoASAFQAw%3D%3D) fixed didn't end up getting done.
I never knew that Virginia Beach had more misguided error than the VA 225 shield that I found on VA 279 in 2009 (http://vahighways.com/errors/va225on279.jpg), but I guess I shouldn't be surprised.
US 250 is now posted westbound in downtown Richmond coming off I-95.
Unfortunately Richmond replaced an erroneous US 33 shield at Belvidere and Leigh with a brand new erroneous US 33 shield.
I took a side trip out to VSU today. VA 327 is indeed only mentioned on the three MPC Way street blades outside the gates, but there are some new-looking blades at the end of MPC Way that may also say 327 on them. There are still no shields or white rectangles with it.
This popped up recently with all of the new signs Richmond has installed. I'm loving the fact that the city is doing something, though this one is particularly small even by Richmond's standards.
US 1/301 NB at US 60
Image from today
(https://uploads.tapatalk-cdn.com/20250331/c572bf5ac114f8612e71832f4a97d23b.jpg)
J24
Quote from: plain on March 31, 2025, 12:06:46 AMThis popped up recently with all of the new signs Richmond has installed. I'm loving the fact that the city is doing something, though this one is particularly small even by Richmond's standards.
US 1/301 NB at US 60
Image from today
(https://uploads.tapatalk-cdn.com/20250331/c572bf5ac114f8612e71832f4a97d23b.jpg)
J24
Hey, I requested that one too! They didn't do a great job mounting it, though.
Quote from: WillWeaverRVA on March 31, 2025, 09:58:35 AMQuote from: plain on March 31, 2025, 12:06:46 AMThis popped up recently with all of the new signs Richmond has installed. I'm loving the fact that the city is doing something, though this one is particularly small even by Richmond's standards.
US 1/301 NB at US 60
Image from today
(https://uploads.tapatalk-cdn.com/20250331/c572bf5ac114f8612e71832f4a97d23b.jpg)
J24
Hey, I requested that one too! They didn't do a great job mounting it, though.
One very bad wind gust and I feel like that thing is gone.
Quote from: Hunty2022 on March 31, 2025, 12:48:39 PMOne very bad wind gust and I feel like that thing is gone.
Heh. This afternoon's weather forecast suggests you could find out yea or nay very quickly.
A few poor quality cell phone pictures of signage changes in Richmond:
VA 33 trailblazer on northbound Harrison at Leigh (I put in a request for US 33/US 250/END VA 33 signage in front of the Siegel Center at Broad but this hasn't appeared yet):
(https://i.postimg.cc/pVZQRYPN/487197718-10111142893863426-5092056595142892427-n.jpg)
VA 147 "TO VA 161" trailblazer in Carytown. I requested this because signage directing traffic to VA 161 from the VA 161 exit on VA 146 disappears after you turn onto Sheppard Street:
(https://i.postimg.cc/KznWZ9NS/487238812-10111142893888376-4606403136200530088-n.jpg)
US 360 and US 250 trailblazers on 17th Street and Broad:
(https://i.postimg.cc/K8jqwc3M/487031885-10111142894112926-1481115887424818128-n.jpg)
US 250 now posted near VCU Health System coming off I-95 - this is the first US 250 posting in downtown Richmond in decades:
(https://i.postimg.cc/VkhG8yXH/486953884-10111141206000916-1852938478616438739-n.jpg)
If you haven't done so already, could you put in a request for the missing I-95/64 signs on VA 161 AA Blvd at the NB/WB entrance? When VDOT redid the overpass, the city installed some on 161 NB in front of it (originally on the overpass itself before the rehab), but now they're gone too.
These are the only signs left.
https://maps.app.goo.gl/DWqza96uytNHMmP2A
https://maps.app.goo.gl/P3Gac8Lu5E9iJLD36
Former posting in front of overpass
https://maps.app.goo.gl/WisarXbzRD9dmTQu9
Former posting on overpass
https://maps.app.goo.gl/yh8XiDSTVB8YJxwQ9
Quote from: plain on April 01, 2025, 11:45:58 AMIf you haven't done so already, could you put in a request for the missing I-95/64 signs on VA 161 AA Blvd at the NB/WB entrance? When VDOT redid the overpass, the city installed some on 161 NB in front of it (originally on the overpass itself before the rehab), but now they're gone too.
These are the only signs left.
https://maps.app.goo.gl/DWqza96uytNHMmP2A
https://maps.app.goo.gl/P3Gac8Lu5E9iJLD36
Former posting in front of overpass
https://maps.app.goo.gl/WisarXbzRD9dmTQu9
Former posting on overpass
https://maps.app.goo.gl/yh8XiDSTVB8YJxwQ9
I'll put one in.
Quote from: WillWeaverRVA on April 01, 2025, 11:57:19 AMQuote from: plain on April 01, 2025, 11:45:58 AMIf you haven't done so already, could you put in a request for the missing I-95/64 signs on VA 161 AA Blvd at the NB/WB entrance? When VDOT redid the overpass, the city installed some on 161 NB in front of it (originally on the overpass itself before the rehab), but now they're gone too.
These are the only signs left.
https://maps.app.goo.gl/DWqza96uytNHMmP2A
https://maps.app.goo.gl/P3Gac8Lu5E9iJLD36
Former posting in front of overpass
https://maps.app.goo.gl/WisarXbzRD9dmTQu9
Former posting on overpass
https://maps.app.goo.gl/yh8XiDSTVB8YJxwQ9
I'll put one in.
While you're at it, you could ask about the posting at the east end of VA 197, and maybe even the publicly accessible sections of VA 318.
Quote from: Takumi on April 01, 2025, 02:48:27 PMQuote from: WillWeaverRVA on April 01, 2025, 11:57:19 AMQuote from: plain on April 01, 2025, 11:45:58 AMIf you haven't done so already, could you put in a request for the missing I-95/64 signs on VA 161 AA Blvd at the NB/WB entrance? When VDOT redid the overpass, the city installed some on 161 NB in front of it (originally on the overpass itself before the rehab), but now they're gone too.
These are the only signs left.
https://maps.app.goo.gl/DWqza96uytNHMmP2A
https://maps.app.goo.gl/P3Gac8Lu5E9iJLD36
Former posting in front of overpass
https://maps.app.goo.gl/WisarXbzRD9dmTQu9
Former posting on overpass
https://maps.app.goo.gl/yh8XiDSTVB8YJxwQ9
I'll put one in.
While you're at it, you could ask about the posting at the east end of VA 197, and maybe even the publicly accessible sections of VA 318.
I requested that I-95/I-64 signage. I already have a request out for the VA 197 posting, and I assume it's not fixed if you're asking.
I'm thinking about VA 318 and VA 399, but with Bank Street not being continuous anymore (there is a segment near the State Capitol that is no longer open to traffic) and much of what is assigned as VA 318 behind gates now, I don't think Richmond would sign it.
EDIT: I requested VA 315 and VA 399. I'm not going to bother with VA 318 because I know VDOT won't post it in Capitol Square and I don't think Richmond would put a 318 shield at the Capitol Square entrance.
Quote from: WillWeaverRVA on April 01, 2025, 03:21:53 PMQuote from: Takumi on April 01, 2025, 02:48:27 PMQuote from: WillWeaverRVA on April 01, 2025, 11:57:19 AMQuote from: plain on April 01, 2025, 11:45:58 AMIf you haven't done so already, could you put in a request for the missing I-95/64 signs on VA 161 AA Blvd at the NB/WB entrance? When VDOT redid the overpass, the city installed some on 161 NB in front of it (originally on the overpass itself before the rehab), but now they're gone too.
These are the only signs left.
https://maps.app.goo.gl/DWqza96uytNHMmP2A
https://maps.app.goo.gl/P3Gac8Lu5E9iJLD36
Former posting in front of overpass
https://maps.app.goo.gl/WisarXbzRD9dmTQu9
Former posting on overpass
https://maps.app.goo.gl/yh8XiDSTVB8YJxwQ9
I'll put one in.
While you're at it, you could ask about the posting at the east end of VA 197, and maybe even the publicly accessible sections of VA 318.
I requested that I-95/I-64 signage. I already have a request out for the VA 197 posting, and I assume it's not fixed if you're asking.
I'm thinking about VA 318 and VA 399, but with Bank Street not being continuous anymore (there is a segment near the State Capitol that is no longer open to traffic) and much of what is assigned as VA 318 behind gates now, I don't think Richmond would sign it.
EDIT: I requested VA 315 and VA 399. I'm not going to bother with VA 318 because I know VDOT won't post it in Capitol Square and I don't think Richmond would put a 318 shield at the Capitol Square entrance.
I haven't been that way to see the end of 197 and I didn't remember if you'd asked about it already. But 315 is probably a better idea than 318.
Quote from: Takumi on April 01, 2025, 04:19:46 PMQuote from: WillWeaverRVA on April 01, 2025, 03:21:53 PMQuote from: Takumi on April 01, 2025, 02:48:27 PMQuote from: WillWeaverRVA on April 01, 2025, 11:57:19 AMQuote from: plain on April 01, 2025, 11:45:58 AMIf you haven't done so already, could you put in a request for the missing I-95/64 signs on VA 161 AA Blvd at the NB/WB entrance? When VDOT redid the overpass, the city installed some on 161 NB in front of it (originally on the overpass itself before the rehab), but now they're gone too.
These are the only signs left.
https://maps.app.goo.gl/DWqza96uytNHMmP2A
https://maps.app.goo.gl/P3Gac8Lu5E9iJLD36
Former posting in front of overpass
https://maps.app.goo.gl/WisarXbzRD9dmTQu9
Former posting on overpass
https://maps.app.goo.gl/yh8XiDSTVB8YJxwQ9
I'll put one in.
While you're at it, you could ask about the posting at the east end of VA 197, and maybe even the publicly accessible sections of VA 318.
I requested that I-95/I-64 signage. I already have a request out for the VA 197 posting, and I assume it's not fixed if you're asking.
I'm thinking about VA 318 and VA 399, but with Bank Street not being continuous anymore (there is a segment near the State Capitol that is no longer open to traffic) and much of what is assigned as VA 318 behind gates now, I don't think Richmond would sign it.
EDIT: I requested VA 315 and VA 399. I'm not going to bother with VA 318 because I know VDOT won't post it in Capitol Square and I don't think Richmond would put a 318 shield at the Capitol Square entrance.
I haven't been that way to see the end of 197 and I didn't remember if you'd asked about it already. But 315 is probably a better idea than 318.
The 197 trailblazer has been corrected.
A few pictures. First, the fixed VA 197 trailblazer at its eastern end at US 1/301. I asked for an end sign but sadly it wasn't installed. Oh well.
(https://i.postimg.cc/1zb1MvHL/IMG-5367.jpg)
A rather wonky trailblazer sign for US 301/VA 2 and US 1 at Azalea Avenue and Chamberlayne Avenue. There are VDOT-installed signs northbound on Chamberlayne approaching this intersection, but they are primarily for NASCAR race traffic headed for I-95 and I-295. There was no indication US 1 turned left here. Now there is, even if it's not in the right order.
(https://i.postimg.cc/zvFmz8rr/IMG-5368.jpg)
Trailblazers for VA 161 leaving I-95 near the northern city limits of Richmond. There is a "TO VA 161" trailblazer on the offramp from I-95, but there weren't trailblazers at VA 161 itself. There still aren't, as this is a little ways away from the actual intersection. Also, I find it odd there's a VDOT "adopt a highway" sign here when Westbrook Avenue isn't even maintained by VDOT.
(https://i.postimg.cc/PJhcF98F/IMG-5369.jpg)
I've seen quite a few adopt-a-highway signs on non-VDOT streets over the years.
There's a US 1/301 SOUTH posting now at the entrance ramp to the Lee Bridge from S. 2nd St. I couldn't get a pic but here's the location, it's above this bicycle route shield.
https://maps.app.goo.gl/knrXNfPyedbLE64k9
Quote from: plain on April 03, 2025, 11:17:26 AMThere's a US 1/301 SOUTH posting now at the entrance ramp to the Lee Bridge from S. 2nd St. I couldn't get a pic but here's the location, it's above this bicycle route shield.
https://maps.app.goo.gl/knrXNfPyedbLE64k9
Interesting. I had requested it but Richmond told me no. Then I found out someone else requested it too, I guess they told me no because they'd already done it. :D
This is kind of random but I submitted several requests to VDOT using their contact form. They will be installing signs for VA 393 in Prince William County (the NOVA Manassas Campus) in the next 30 days. VA 393 hasn't been posted since the mid-1990s.
Unfortunately I'm out of luck on VA 213 in Manassas Park - VDOT won't even post signs near VA 213, even in locations that are not within Manassas Park, although there are now multiple "begin" and "end state maintenance" signs up. Manassas Park and then-Delegate Danica Roem already told me there's no interest in signing VA 213...which means it should probably be decommissioned, but what do I know?
N. 9th St at VA 33 in Richmond
Image from today
(https://uploads.tapatalk-cdn.com/20250408/2b501bba94ccc20d2b36dcaf3305d697.jpg)
SM-A156U
Quote from: plain on April 08, 2025, 04:04:05 PMN. 9th St at VA 33 in Richmond
Image from today
(https://uploads.tapatalk-cdn.com/20250408/2b501bba94ccc20d2b36dcaf3305d697.jpg)
SM-A156U
I didn't request a sign there so I can't take credit for that! :-D
I'm pretty sure you set off the chain of events :-D
The VDOT engineer who contacted me the other day about VA 393 contacted me today about VA 394 (NOVA Woodbridge campus). All 394 shields were removed when the entrance to Freedom High School was built and he's going to reinstall them along SR 638 in the next 30 days.
Quote from: WillWeaverRVA on April 09, 2025, 05:57:49 PMThe VDOT engineer who contacted me the other day about VA 393 contacted me today about VA 394 (NOVA Woodbridge campus). All 394 shields were removed when the entrance to Freedom High School was built and he's going to reinstall them along SR 638 in the next 30 days.
Any word from any other jurisdictions?
Quote from: Takumi on April 10, 2025, 12:26:10 AMQuote from: WillWeaverRVA on April 09, 2025, 05:57:49 PMThe VDOT engineer who contacted me the other day about VA 393 contacted me today about VA 394 (NOVA Woodbridge campus). All 394 shields were removed when the entrance to Freedom High School was built and he's going to reinstall them along SR 638 in the next 30 days.
Any word from any other jurisdictions?
So here are all the requests I put in during the past couple of days:
- Sign VA 393 at Northern Virginia Community College (Manassas): Yes, they'll sign it (advance signage with shields on VA 234) in the next 30 days
- Sign VA 394 at Northern Virginia Community College (Woodbridge): Yes, they'll sign it (advance signage with shields on SR 638) in the next 30 days
- Sign VA 213 in some part of Prince William County just outside Manassas Park: No, Manassas Drive is a Manassas Park city street despite its primary designation and it's up to the city to sign it. It's been a while since I contacted Manassas Park so maybe I'll reach out again and see if they'll post signs at the VA 213/VA 28 intersection since there were once signs there.
- Sign VA 324 at Bon Air Juvenile Correctional Center (namely Chatsworth Avenue): No, we don't want people to think the road is open to the public (even though most other correctional facilities in the state are signed somehow). I contacted Chesterfield County about the street name sign and never got a reply.
- Sign VA 327 at Virginia State University: haven't heard back
- Sign VA 366 at Brightpoint Community College: haven't heard back
- Sign VA 120 & VA 123 at their intersection just before the Chain Bridge: This intersection is going to be rebuilt soon in a joint VDOT/Arlington County project and signage will be posted once it's done. I thought about contacting DCDOT to post VA 120 and VA 123 on the other side of the Chain Bridge but realized that has a snowball's chance in hell of happening.
I will say, the engineer who called me back about the signage in Northern Virginia was a really nice guy and wasn't weirded out at all by my requests. He seemed pretty enthusiastic about it, actually, and he was very helpful.
Okay, I laughed at the thread title. :-D
Did you ever ask about VA 410 in Powhatan? I think that would be worthy of being posted, especially since the nearby VA 313 (which is for a much different, less public, facility) at least gets a white rectangle. (My ultimate fantasy would be for it to get a "To" posting from US 522, but one thing at a time.)
Quote from: Takumi on April 10, 2025, 07:53:11 PMDid you ever ask about VA 410 in Powhatan? I think that would be worthy of being posted, especially since the nearby VA 313 (which is for a much different, less public, facility) at least gets a white rectangle. (My ultimate fantasy would be for it to get a "To" posting from US 522, but one thing at a time.)
It was done for the former VA 392 (https://www.google.com/maps/@36.737486,-80.7924755,3a,28y,99.04h,93.57t/data=!3m8!1e1!3m6!1s5ITof_Gl8A38crIjoUVTHA!2e0!5s20180501T000000!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D-3.5676225737435914%26panoid%3D5ITof_Gl8A38crIjoUVTHA%26yaw%3D99.0375379691818!7i13312!8i6656!5m1!1e1?entry=ttu&g_ep=EgoyMDI1MDQwOC4wIKXMDSoASAFQAw%3D%3D) on US 58/US 221 so there is a case for it. Of course, the "TO VA 410" would have to be on US 522 at SR 617.
Quote from: WillWeaverRVA on March 07, 2025, 11:01:45 AMQuote from: WillWeaverRVA on March 06, 2025, 10:49:09 PMI submitted some 311 requests to Hampton regarding signing US 258 and VA 143 on or near Fort Monroe since the area is under city jurisdiction now (despite there being some VA 9xxxx routes there), and the VDOT ArcGIS map shows US 258 and VA 143 running on McNair Drive on Fort Monroe as a useless concurrency before ending near the Chamberlin Hotel.
And that didn't take long, all the requests are shown as cancelled.
Maybe because Fort Monroe is now under National Park Service jurisdiction rather than city or DOD jurisdiction, and perhaps NPS doesn't feel route signage within their park is a priority (even to the point of letting local sign crews place route markers there)?
I went down there toward the end of March, saw no US 258 or VA 143 signs on fort property.
Quote from: Takumi on April 10, 2025, 07:53:11 PMDid you ever ask about VA 410 in Powhatan? I think that would be worthy of being posted, especially since the nearby VA 313 (which is for a much different, less public, facility) at least gets a white rectangle. (My ultimate fantasy would be for it to get a "To" posting from US 522, but one thing at a time.)
I'll ask about it tomorrow.
Quote from: oscar on April 10, 2025, 08:57:07 PMQuote from: WillWeaverRVA on March 07, 2025, 11:01:45 AMQuote from: WillWeaverRVA on March 06, 2025, 10:49:09 PMI submitted some 311 requests to Hampton regarding signing US 258 and VA 143 on or near Fort Monroe since the area is under city jurisdiction now (despite there being some VA 9xxxx routes there), and the VDOT ArcGIS map shows US 258 and VA 143 running on McNair Drive on Fort Monroe as a useless concurrency before ending near the Chamberlin Hotel.
And that didn't take long, all the requests are shown as cancelled.
Maybe because Fort Monroe is now under National Park Service jurisdiction rather than city or DOD jurisdiction, and perhaps NPS doesn't feel route signage within their park is a priority (even to the point of letting local sign crews place route markers there)?
I went down there toward the end of March, saw no US 258 or VA 143 signs on fort property.
That's odd because there are lots of I-64 signs around. I was under the impression that the fort itself was NPS property, but the rest of the island is under the control of the Fort Monroe Authority, which is a joint city/state entity.
Quote from: Takumi on April 10, 2025, 07:53:11 PMDid you ever ask about VA 410 in Powhatan? I think that would be worthy of being posted, especially since the nearby VA 313 (which is for a much different, less public, facility) at least gets a white rectangle. (My ultimate fantasy would be for it to get a "To" posting from US 522, but one thing at a time.)
Somehow I forgot to request signs for VA 410 and I just did it this morning.
There is now a VA 366 posting on a Chesterfield County street sign at Brightpoint Community College's Chester campus. No VDOT signs yet.
Quote from: WillWeaverRVA on April 10, 2025, 08:36:12 AMI will say, the engineer who called me back about the signage in Northern Virginia was a really nice guy and wasn't weirded out at all by my requests. He seemed pretty enthusiastic about it, actually, and he was very helpful.
I very recently had the same experience with an engineer from MDOT (Michigan) when I wrote asking some "why?" questions about the freeway sign plans for an upcoming replacement project. I think that quite a lot of them appreciate that there actually are some people who take a real interest in their others-perceive-it-as-geeky work.
Quote from: WillWeaverRVA on April 16, 2025, 05:16:11 PMThere is now a VA 366 posting on a Chesterfield County street sign at Brightpoint Community College's Chester campus. No VDOT signs yet.
Just saw it. It appears they put a pair of small decals with the route number onto the existing sign. Whatever, I'll take it.
Did you ever hear back from Richmond about VA 315 and 399? As of tonight they remain unposted.
Eastbound Broad at Belvedere has a "TO EAST VA 33" trailblazer turning onto northbound Belvedere.
Quote from: Takumi on April 20, 2025, 10:45:26 PMDid you ever hear back from Richmond about VA 315 and 399? As of tonight they remain unposted.
Eastbound Broad at Belvedere has a "TO EAST VA 33" trailblazer turning onto northbound Belvedere.
Haven't heard about 315 or 399 yet, not exactly getting my hopes up with it. The VA 33 trailblazer is brand new, there had been a US 33 shield there for quite a while.
I put in a few more requests last week - VA 197's turn from Saunders to Laburnum is no longer posted after some signs got knocked over a while ago, and there is also no signage for I-195 or I-64 at that intersection. I also requested signage for the VA 6 transition from Patterson to Kensington, as well as missing signage at the southern end of the VA 10/VA 161 concurrency.
Speaking of VA 161, southbound VA 161 approaching US 360 was erroneously signed as northbound VA 161 for several years and that has now been corrected (https://www.google.com/maps/@37.5033989,-77.4750275,3a,75y,150.93h,83.99t/data=!3m8!1e1!3m6!1sZJoppL73YheVu9hwFJTwsg!2e0!5s20250301T000000!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D6.008252019957169%26panoid%3DZJoppL73YheVu9hwFJTwsg%26yaw%3D150.92619950169814!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDQxNi4xIKXMDSoASAFQAw%3D%3D).
GSV has been updating in parts of Richmond recently (there's a bunch of new content in South Richmond from March and April 2025), which is saving me a lot of trouble and seemingly aimless driving. :-D
EDIT: The onramp from 2nd Street at Oregon Hill to the southbound Lee Bridge is now posted (https://www.google.com/maps/@37.5355348,-77.4493758,3a,18.4y,244.41h,77.67t/data=!3m7!1e1!3m5!1s6eKktS5pY2cH-3_eAFC69w!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D12.330906958910745%26panoid%3D6eKktS5pY2cH-3_eAFC69w%26yaw%3D244.41189334442765!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDQxNi4xIKXMDSoASAFQAw%3D%3D) - previously it had only ever been posted for USBR 1.
QuoteHaven't heard about 315 or 399 yet, not exactly getting my hopes up with it.
That sucks. I think if I had to pick one or the other, at least VA 315 has use as a through route and could justify being posted.
QuoteThe VA 33 trailblazer is brand new, there had been a US 33 shield there for quite a while.
This makes me think that the reason the US/VA 33 transition point isn't posted correctly is because Richmond doesn't want the general public to use that route for whatever reason.
Quote from: Takumi on April 21, 2025, 01:11:50 PMQuoteThe VA 33 trailblazer is brand new, there had been a US 33 shield there for quite a while.
This makes me think that the reason the US/VA 33 transition point isn't posted correctly is because Richmond doesn't want the general public to use that route for whatever reason.
You're probably right, considering you can't even turn left from eastbound Broad onto Harrison (to begin down VA 33) or Hancock (to continue on US 33 until it ends at Leigh).
If it were up to me I'd truncate US 33 to US 250 since there is effectively now a gap in the designation (there's a GRTC Pulse station separating what is officially two segments of US 33), and even with the new mayoral administration, Richmond still seems averse to posting US 33 anywhere...except for roads that aren't US 33.
QuoteIf it were up to me I'd truncate US 33 to US 250 since there is effectively now a gap in the designation (there's a GRTC Pulse station separating what is officially two segments of US 33), and even with the new mayoral administration, Richmond still seems averse to posting US 33 anywhere...except for roads that aren't US 33.
I would still have US 33 end along US 250 along US 1/US 301 and VA 33's west end be on Leigh St at US 1/US 301. Even signage along US 250 EB supports that idea even with the US 33 error. (https://www.google.com/maps/@37.5491899,-77.4480234,3a,39.3y,118.6h,89.57t/data=!3m7!1e1!3m5!1s8WG2wWD2mAkqKbV6mLHxMw!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D0.42902443195514195%26panoid%3D8WG2wWD2mAkqKbV6mLHxMw%26yaw%3D118.604330392777!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDQxNi4xIKXMDSoASAFQAw%3D%3D)
Quote from: 74/171FAN on April 21, 2025, 01:21:54 PMQuoteIf it were up to me I'd truncate US 33 to US 250 since there is effectively now a gap in the designation (there's a GRTC Pulse station separating what is officially two segments of US 33), and even with the new mayoral administration, Richmond still seems averse to posting US 33 anywhere...except for roads that aren't US 33.
I would still have US 33 end along US 250 along US 1/US 301 and VA 33's west end be on Leigh St at US 1/US 301. Even signage along US 250 EB supports that idea even with the US 33 error. (https://www.google.com/maps/@37.5491899,-77.4480234,3a,39.3y,118.6h,89.57t/data=!3m7!1e1!3m5!1s8WG2wWD2mAkqKbV6mLHxMw!2e0!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D0.42902443195514195%26panoid%3D8WG2wWD2mAkqKbV6mLHxMw%26yaw%3D118.604330392777!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDQxNi4xIKXMDSoASAFQAw%3D%3D)
As Takumi posted, that US 33 shield is now a VA 33 shield. ;)
@Mapmikey: The now-erroneous signage for VA 414 at Salem Road and Lynnhaven Parkway in Virginia Beach appears to be gone (https://www.google.com/maps/@36.7909182,-76.1253679,3a,75y,214.1h,83.12t/data=!3m8!1e1!3m6!1sijXS4GvfTLNHkXQj5mVodA!2e0!5s20250301T000000!6shttps:%2F%2Fstreetviewpixels-pa.googleapis.com%2Fv1%2Fthumbnail%3Fcb_client%3Dmaps_sv.tactile%26w%3D900%26h%3D600%26pitch%3D6.875331251460494%26panoid%3DijXS4GvfTLNHkXQj5mVodA%26yaw%3D214.10368092232196!7i16384!8i8192?entry=ttu&g_ep=EgoyMDI1MDQxNi4xIKXMDSoASAFQAw%3D%3D) now, based on March 2025 GSV.
Not looking like 315 or 399 will be signed. Unlike 353, Richmond DPW does not maintain those roads and so they're deferring to VMFA and the Science Museum (neither one of whom I think would be interested in signing those routes).
Seems like we've gotten about as far as we'll get then. Although I wonder if I could commission Jake to make a VA 315 cutout shield, pass it off as an art piece, and donate it to the VMFA on the condition that they post it on the road somewhere.
(https://media.tenor.com/H5Tf_9O04Q8AAAAM/its-its-always-sunny.gif)
something something Richard Ankrom
VDOT sent me notifications that my requests regarding VA 393 (NOVA Manassas campus off VA 234) and VA 394 (NOVA Woodbridge campus off SR 638) in Prince William County have been completed/resolved.
Interestingly, two requests I put in regarding posting VA 213 are also showing as completed, even though the engineer I spoke to told me it was up to Manassas Park to decide whether to post VA 213 or not (and Manassas Park had previously told me no).
Unfortunately I'm not really in a position to go check and see if signs have been posted.
Quote from: WillWeaverRVA on April 29, 2025, 01:37:09 PMUnfortunately I'm not really in a position to go check and see if signs have been posted.
I am sure I will get to it eventually if no one beats me to it.
I created a Google Doc to keep track of all my requests, and damn. I haven't added the Richmond ones yet and this is a lot. Clearly I have waaaaaaay too much time on my hands. :-D
https://docs.google.com/spreadsheets/d/121YA6uNruVHSTiGu0cqceUpV23pncZoH3LfZbHxir64/edit?gid=0#gid=0
VDOT claims to have completed my VA 327 request. I'll have to try to check it out if I have time.
Quote from: WillWeaverRVA on April 30, 2025, 08:28:16 AMVDOT claims to have completed my VA 327 request. I'll have to try to check it out if I have time.
If they did, it happened today, because I drove by VSU yesterday and there were no signs for it other than the blades on MPC way. I'll check it out again later.
I just drove the perimeter of the campus and looked down every road that goes past a gate, and saw no new 327 signs anywhere. I'll check again another day.
Quote from: Takumi on April 30, 2025, 06:09:36 PMI just drove the perimeter of the campus and looked down every road that goes past a gate, and saw no new 327 signs anywhere. I'll check again another day.
Argh. Well, thanks for checking.
Richmond put up a few missing VA 33 movements and replaced a couple of faded trailblazers. I was also told they put up trailblazers for US 1 and US 301 at the Idlewood Ave roundabout just off VA 195 (the exit is signed for US 1 and US 301, but the exit deposits you in the middle of Oregon Hill with no indication on how to get there).
VDOT has marked a few of my Chesterfield requests as completed, but they're not completed. Not sure what the deal is with that.
Quote from: WillWeaverRVAVDOT has marked a few of my Chesterfield requests as completed, but they're not completed. Not sure what the deal is with that.
What did they say was completed? I can go check 327 and 366 again later today.
Quote from: Takumi on May 02, 2025, 02:31:22 PMQuote from: WillWeaverRVAVDOT has marked a few of my Chesterfield requests as completed, but they're not completed. Not sure what the deal is with that.
What did they say was completed? I can go check 327 and 366 again later today.
That's the weird thing, unlike Richmond's 311 service, there's no notes or anything, just a note saying "your request has been resolved" for both the VA 327 request (https://my.vdot.virginia.gov/ServiceRequest/Get/2109141) and the VA 366 request (https://my.vdot.virginia.gov/ServiceRequest/Get/2109137). The same is true for some SR rectangles along VA 147 that are pointing the wrong way (into the City of Richmond) and a SR 2480 sign on SR 604 that's missing an arrow panel - they're listed as resolved but haven't been fixed.
I also don't like how you can report something as a sign needing to be installed or replaced and their system changes it to "traffic study request". I may need to resubmit the requests.
Quote from: WillWeaverRVA on May 02, 2025, 02:58:47 PMQuote from: Takumi on May 02, 2025, 02:31:22 PMQuote from: WillWeaverRVAVDOT has marked a few of my Chesterfield requests as completed, but they're not completed. Not sure what the deal is with that.
What did they say was completed? I can go check 327 and 366 again later today.
That's the weird thing, unlike Richmond's 311 service, there's no notes or anything, just a note saying "your request has been resolved" for both the VA 327 request (https://my.vdot.virginia.gov/ServiceRequest/Get/2109141) and the VA 366 request (https://my.vdot.virginia.gov/ServiceRequest/Get/2109137). The same is true for some SR rectangles along VA 147 that are pointing the wrong way (into the City of Richmond) and a SR 2480 sign on SR 604 that's missing an arrow panel - they're listed as resolved but haven't been fixed.
I also don't like how you can report something as a sign needing to be installed or replaced and their system changes it to "traffic study request". I may need to resubmit the requests.
Yeah, nothing has changed. I wonder if that means they declined the request without reason.
Given Chesterfield added the 366 number to its street blade, do you know if they corrected the one for VA 324?
Quote from: Takumi on May 02, 2025, 04:20:18 PMQuote from: WillWeaverRVA on May 02, 2025, 02:58:47 PMQuote from: Takumi on May 02, 2025, 02:31:22 PMQuote from: WillWeaverRVAVDOT has marked a few of my Chesterfield requests as completed, but they're not completed. Not sure what the deal is with that.
What did they say was completed? I can go check 327 and 366 again later today.
That's the weird thing, unlike Richmond's 311 service, there's no notes or anything, just a note saying "your request has been resolved" for both the VA 327 request (https://my.vdot.virginia.gov/ServiceRequest/Get/2109141) and the VA 366 request (https://my.vdot.virginia.gov/ServiceRequest/Get/2109137). The same is true for some SR rectangles along VA 147 that are pointing the wrong way (into the City of Richmond) and a SR 2480 sign on SR 604 that's missing an arrow panel - they're listed as resolved but haven't been fixed.
I also don't like how you can report something as a sign needing to be installed or replaced and their system changes it to "traffic study request". I may need to resubmit the requests.
Yeah, nothing has changed. I wonder if that means they declined the request without reason.
Given Chesterfield added the 366 number to its street blade, do you know if they corrected the one for VA 324?
The 324 one hasn't been corrected, though they did correct some 711/675 mixups on Robious Rd. They may not want to sign 324 either.
Quote from: WillWeaverRVA on May 02, 2025, 06:32:00 PMThe 324 one hasn't been corrected, though they did correct some 711/675 mixups on Robious Rd.
It would be better if it all became SR 711 or even re-entered the primary system, but that is fictional territory.
Quote from: 74/171FAN on May 02, 2025, 06:45:27 PMQuote from: WillWeaverRVA on May 02, 2025, 06:32:00 PMThe 324 one hasn't been corrected, though they did correct some 711/675 mixups on Robious Rd.
It would be better if it all became SR 711 or even re-entered the primary system, but that is fictional territory.
I think you mean that's our next challenge after getting signage corrected. I believe the corridor between 60 and 288 meets most if not all of the CTB's requirements for upgrading secondary routing to primary.
Quote from: 74/171FAN on May 02, 2025, 06:45:27 PMQuote from: WillWeaverRVA on May 02, 2025, 06:32:00 PMThe 324 one hasn't been corrected, though they did correct some 711/675 mixups on Robious Rd.
It would be better if it all became SR 711 or even re-entered the primary system, but that is fictional territory.
I have actually asked about having 711 and 675 just be one continuous route since the staggered intersection between then-VA 44, VA 147, and SR 675 hasn't been around for like 70 years but never got a response.
Quote from: WillWeaverRVA on May 02, 2025, 11:50:09 PMQuote from: 74/171FAN on May 02, 2025, 06:45:27 PMQuote from: WillWeaverRVA on May 02, 2025, 06:32:00 PMThe 324 one hasn't been corrected, though they did correct some 711/675 mixups on Robious Rd.
It would be better if it all became SR 711 or even re-entered the primary system, but that is fictional territory.
I have actually asked about having 711 and 675 just be one continuous route since the staggered intersection between then-VA 44, VA 147, and SR 675 hasn't been around for like 70 years but never got a response.
I think it's just like that because Powhatan already had a 675 when VA 44 was downgraded and they never had a reason to change the number.
I got in touch with VDOT about some of the requests being marked as resolved and was told that VDOT has no plans to sign VA 327 or 366, but they will reach out to me later.
Apparently even though the VDOT engineer I spoke to about VA 324 said they weren't interested in posting that route, VDOT has contacted Chesterfield County about signage, so it's possible 324 may be posted in some way soon.
Oddly, the two SR rectangles that were installed by VDOT on the wrong side of VA 147 can't be fixed by VDOT because they are technically in the City of Richmond.
Anything on 410?
Also I'm not terribly surprised if VDOT doesn't pursue more signing on 327 and 366. 327 is now mostly behind gates (the MPC Way segment is by far the longest section that isn't, and it's only a few blocks long) and 366 is a minor enough route that the lone street blade posting covers acknowledgement of it being a state route.
Given how Richmond has handled the requests for 315 and 399, it wouldn't surprise me if they wouldn't do anything with the white rectangles if you asked them to.
Quote from: Takumi on May 05, 2025, 01:50:53 PMAnything on 410?
Also I'm not terribly surprised if VDOT doesn't pursue more signing on 327 and 366. 327 is now mostly behind gates (the MPC Way segment is by far the longest section that isn't, and it's only a few blocks long) and 366 is a minor enough route that the lone street blade posting covers acknowledgement of it being a state route.
Given how Richmond has handled the requests for 315 and 399, it wouldn't surprise me if they wouldn't do anything with the white rectangles if you asked them to.
Nothing on 410 yet.
I'm gonna see if the city will at least just rotate the rectangles so they point the right way. I'm sure I can word the request in a way where they'd be fine with doing that.
315 may yet be signed, that request seems to still be open and I misread the response to the 399 one. And I'm tempted to contact the science museum and see if they can get 399 posted somehow anyway.
Posting 315 trailblazers on 161 seems plausible, if nothing else. It's not like it's a gated route like 327 and even 410 are. My thought is that the museums may just not want to encourage through traffic on it by having the route posted, and may have told the city such.
US 522 is posted from the south end of VA 410, so there likely was a conscious decision not to post it when it was opened.
Quote from: Takumi on May 05, 2025, 02:53:23 PMPosting 315 trailblazers on 161 seems plausible, if nothing else. It's not like it's a gated route like 327 and even 410 are. My thought is that the museums may just not want to encourage through traffic on it by having the route posted, and may have told the city such.
US 522 is posted from the south end of VA 410, so there likely was a conscious decision not to post it when it was opened.
VA 410 was actually secondary for a brief period before it was upgraded, IIRC. I might have to find an old version of the ArcGIS map to find out what it was before it became VA 410.
Quote from: WillWeaverRVA on May 05, 2025, 03:29:26 PMQuote from: Takumi on May 05, 2025, 02:53:23 PMPosting 315 trailblazers on 161 seems plausible, if nothing else. It's not like it's a gated route like 327 and even 410 are. My thought is that the museums may just not want to encourage through traffic on it by having the route posted, and may have told the city such.
US 522 is posted from the south end of VA 410, so there likely was a conscious decision not to post it when it was opened.
VA 410 was actually secondary for a brief period before it was upgraded, IIRC. I might have to find an old version of the ArcGIS map to find out what it was before it became VA 410.
While you're there, could you check to see if the road leading to Wallis Ridge Prison in Big Stone Gap has a number? I can't get the map to load right to save my life.
Quote from: Takumi on May 05, 2025, 04:11:02 PMWhile you're there, could you check to see if the road leading to Wallis Ridge Prison in Big Stone Gap has a number? I can't get the map to load right to save my life.
The map says it's an unnumbered town road.
GSV has updated in much of Alexandria and none of the signage I requested has been installed (someone who messaged me on Bluesky also confirmed this a bit earlier). Go figure.
(By the way, MapGenerator is extremely useful for finding GSV updates. I think it was created for GeoGuessr. https://map-generator-nsj.vercel.app/)
Quote from: WillWeaverRVA on April 29, 2025, 01:37:09 PMVDOT sent me notifications that my requests regarding VA 393 (NOVA Manassas campus off VA 234) and VA 394 (NOVA Woodbridge campus off SR 638) in Prince William County have been completed/resolved.
Since I work relatively close to the Manassas NOVA campus, I decided to drive by there after work today. The VA-393 signs have not been posted yet. I'm thinking it would only be posted on VA-234 northbound as the southbound approach does not allow left turns.
Quote from: dfnva on May 09, 2025, 04:57:02 PMQuote from: WillWeaverRVA on April 29, 2025, 01:37:09 PMVDOT sent me notifications that my requests regarding VA 393 (NOVA Manassas campus off VA 234) and VA 394 (NOVA Woodbridge campus off SR 638) in Prince William County have been completed/resolved.
Since I work relatively close to the Manassas NOVA campus, I decided to drive by there after work today. The VA-393 signs have not been posted yet. I'm thinking it would only be posted on VA-234 northbound as the southbound approach does not allow left turns.
I also drove by there today and through campus. There are at least 3 VA 234 shields on campus.
I can also confirm that VA 213 is not posted anywhere either
Quote from: Mapmikey on May 09, 2025, 05:47:46 PMQuote from: dfnva on May 09, 2025, 04:57:02 PMQuote from: WillWeaverRVA on April 29, 2025, 01:37:09 PMVDOT sent me notifications that my requests regarding VA 393 (NOVA Manassas campus off VA 234) and VA 394 (NOVA Woodbridge campus off SR 638) in Prince William County have been completed/resolved.
Since I work relatively close to the Manassas NOVA campus, I decided to drive by there after work today. The VA-393 signs have not been posted yet. I'm thinking it would only be posted on VA-234 northbound as the southbound approach does not allow left turns.
I also drove by there today and through campus. There are at least 3 VA 234 shields on campus.
I can also confirm that VA 213 is not posted anywhere either
Sigh. Thanks for checking.
I commend your efforts Will!
When I drove to Delaware for Christmas, I worked in U.S. 1/301 from Petersburg north to the split in Richmond. Beyond SR 145, the next reassurance markers for U.S. 1/301 I saw were a set in the median after SR 161 (Bells Road) and another in the median by Webber Avenue.
There was no junction shield for U.S. 360 but at least there were west/east shields at Hull Street. No signage whatsoever at Semmes Avenue for U.S. 60.
Also no signage Idlewild Avenue and Cumberland Street for SR 195. You have no idea that the Downtown Expressway exists...
Granted there was construction at the southeast corner of Broad Street, but no shields posted for any route. On Broad Street westbound there was at least a shield assembly for U.S. 1/301 south and trailblazers for I-95/64 referencing U.S. 1/301 north.
You get an "I-95/64 THIS LANE" overhead mounted to the signal mast arm at Clay Street as your lone indication of the forthcoming interchange. North from there no shields were posted until an assembly for SR 197 east and trailblazers for I-64/95 at Laburnum Avenue, followed by the first reassurance markers for U.S. 1/301 posted since Webber Avenue.
And of course which you have already addressed, at the north split of U.S. 1/301, there was only a set of North U.S. 301/TO SR 2/TO I-95/TO I-295 shield assembly preceding Azalea Avenue. No indication of U.S. 1 turning west.
Quote from: Alex on May 10, 2025, 08:34:48 AMI commend your efforts Will!
When I drove to Delaware for Christmas, I worked in U.S. 1/301 from Petersburg north to the split in Richmond. Beyond SR 145, the next reassurance markers for U.S. 1/301 I saw were a set in the median after SR 161 (Bells Road) and another in the median by Webber Avenue.
There was no junction shield for U.S. 360 but at least there were west/east shields at Hull Street. No signage whatsoever at Semmes Avenue for U.S. 60.
Also no signage Idlewild Avenue and Cumberland Street for SR 195. You have no idea that the Downtown Expressway exists...
Granted there was construction at the southeast corner of Broad Street, but no shields posted for any route. On Broad Street westbound there was at least a shield assembly for U.S. 1/301 south and trailblazers for I-95/64 referencing U.S. 1/301 north.
You get an "I-95/64 THIS LANE" overhead mounted to the signal mast arm at Clay Street as your lone indication of the forthcoming interchange. North from there no shields were posted until an assembly for SR 197 east and trailblazers for I-64/95 at Laburnum Avenue, followed by the first reassurance markers for U.S. 1/301 posted since Webber Avenue.
And of course which you have already addressed, at the north split of U.S. 1/301, there was only a set of North U.S. 301/TO SR 2/TO I-95/TO I-295 shield assembly preceding Azalea Avenue. No indication of U.S. 1 turning west.
Thanks! :)
Quote from: WillWeaverRVA on May 05, 2025, 02:24:53 PMI'm gonna see if the city will at least just rotate the rectangles so they point the right way. I'm sure I can word the request in a way where they'd be fine with doing that.
And the city just told me VDOT needs to fix those rectangles, but they're going to contact VDOT themselves to let them know so we're not going back and forth on the issue.
VDOT has indeed fixed the rectangles after Richmond contacted them.
Also, US 1/US 301 is now posted on Idlewood Avenue in Richmond leaving VA 195 - previously it hadn't been, and the exit from VA 195 is signed as being for US 1/US 301 Belvidere St.
I've been out of town the past few weeks but now that I'm home I've noticed a lot of new signs around Richmond. I'm going to try and get some pics today.
Quote from: plain on May 24, 2025, 11:59:43 AMI've been out of town the past few weeks but now that I'm home I've noticed a lot of new signs around Richmond. I'm going to try and get some pics today.
Thanks! My car is out of commission again so I haven't been able to do as much field checking.
VA 327 and 366 have no changes.
Quote from: WillWeaverRVA on January 31, 2025, 10:11:22 AMRichmond has a new mayoral administration, and the new mayor seems to be extra committed to public works and public utility projects after Richmond's water crisis earlier this month. A bunch of 311 requests people have submitted as long ago as 2 years are now being completed, including a bunch of my requests related to signage. It's possible that a bunch of signage errors (or locations where signage is missing) may soon be fixed, including ones related to US 250 - in previous requests, the city kept referring to cryptic emails about signing US 250 in the city and closing requests related to installing signage.
I haven't had a chance to go into the city recently to check on any of them, though.
Requests I put in that are now showing as completed:
- VA 353 posting on Duval St at 8th St (to match the one leaving the VCU Health System staff parking area)
- Missing signage on Sheppard St directing traffic onto Cary St to reach VA 161 (since the exit from VA 146 is signed for VA 161)
- Missing signage for VA 195/I-64/I-95 on Belvidere St at Cumberland St (signage used to exist but was removed)
- Missing VA 147 signage at Main St/Belvidere St intersection (even though Cary St is signed as VA 147)
- "END VA 6" sign missing at Kensington Ave and Arthur Ashe Blvd (was removed a long time ago for a signal upgrade and never replaced)
- Missing US/VA 33 and US 250 signage at Harrison St and Broad St intersection
- Missing VA 33 signage on Leigh St at Harrison St (though there is a reassurance marker on Harrison St)
Requests I put in that have notes saying signage will be installed:
- Missing US 250 and US 360 signage at 17th and Broad (I-95 exit is signed for US 250)
- Missing US 1/US 301/VA 2 signage at Azalea Ave and Chamberlayne Ave
My response to this is. The city may have larger fish to fry.
Quote from: Takumi on May 24, 2025, 12:56:45 PMVA 327 and 366 have no changes.
Yeah, at this rate I'm not expecting them to based on what VDOT told me.
Quote from: bwana39 on May 24, 2025, 02:18:42 PMMy response to this is. The city may have larger fish to fry.
Like what?
Quote from: Mapmikey on May 24, 2025, 05:15:12 PMQuote from: bwana39 on May 24, 2025, 02:18:42 PMMy response to this is. The city may have larger fish to fry.
Like what?
Signage is pretty low priority for cities. The state DOT might have a higher one.
As an independent city, Richmond gets money from VDOT to use on its non-interstate roads. The state doesn't do anything within the city boundaries. Rectifying missing/erroneous/illegible signage is definitely worth the effort and in Richmond's case had been accumulating over 3 decades.
Quote from: Mapmikey on May 24, 2025, 05:15:12 PMQuote from: bwana39 on May 24, 2025, 02:18:42 PMMy response to this is. The city may have larger fish to fry.
Like what?
I have lived in this city since 1985. I have at least 8 different major issues that I have complained to the city government about.
Here is the latest, that I sent to my city councilperson two weeks ago.
Tiny roundabouts that are proliferating around the city --
poor traffic engineering and unsafe road features. VDOT would never design something like this. DOTs properly design them as at Maury Street interchange with I-95, and Dock Street near the Great Shiplock Park.
Tiny roundabouts can create several challenges, despite their intended benefits for traffic flow and safety. Some common problems include:
=> Confusion for drivers – Smaller roundabouts can be unclear, leading to hesitation or incorrect navigation.
=> Limited space for larger vehicles – Trucks, buses, and emergency vehicles may struggle to maneuver through tight roundabouts.
=> Pedestrian safety concerns – Crosswalks near small roundabouts can be difficult to navigate, especially if visibility is poor.
=> Inefficiency in high-traffic areas – When placed in busy intersections, tiny roundabouts may not handle congestion effectively.
=> Cyclist navigation issues – Cyclists may find it harder to merge safely with vehicle traffic in compact roundabouts.
Tiny roundabouts create more problems than they solve! When they're too small, they can lead to confusion, inefficient traffic flow, and difficulties for larger vehicles. Good roundabout design needs to balance safety, space, and usability—if those factors aren't considered properly, drivers end up frustrated instead of benefiting from the intended traffic improvements.
All these tiny roundabouts need to be removed.
Road Diets -- are proliferating all over the city.
Road Diets are where lanes are removed from arterial roads to make space for bike paths -- are controversial, especially when the new bike lanes remain underused. Some common concerns include:
=> Increased congestion – Reducing lanes can lead to longer travel times for drivers, especially in high-traffic areas.
=> Low bike usage – If few cyclists use the new lanes, it raises questions about whether the change was worth the disruption.
=> Business impact – Some businesses worry that fewer lanes mean less accessibility for customers, affecting revenue.
=> Emergency vehicle delays – Narrower roads can make it harder for ambulances and fire trucks to navigate quickly.
However, supporters argue that road diets can improve safety, encourage alternative transportation, and create more walkable communities. Some cities have even reversed road diets after public backlash.
These Road Diets may be useful in a few places, but the vast majority carry no visible bicycle traffic.
It is especially egregious to see them on arterials like Warwick Road. This road used to be a narrow 2-lane secondary road, and it was rebuilt, relocated and extended about 2000, to the 4-lane divided arterial it is now. VDOT and FHWA spent a lot of money to build it with roadways designed for cars, trucks and buses.
Now in the last year 2 lanes each way have been striped off so that only bicycles can use them. Normally you can drive the entire length and not see one bicycle using them.
The city needs to reopen this road to the 4-lane arterial that it was built to be. ASAP.
Quote from: WillWeaverRVA on May 24, 2025, 04:16:06 PMQuote from: Takumi on May 24, 2025, 12:56:45 PMVA 327 and 366 have no changes.
Yeah, at this rate I'm not expecting them to based on what VDOT told me.
VA 399 as well. I didn't go by VA 315 today but I'd be surprised if they signed it.