Virginia

[WillWeaverRVA]

I'm sure such a bridge would be a drawbridge. A high level bridge would not be worth the costs for the amount of traffic using it, despite how much Surry is "growing". And either way it would be lengthy.

It's an awful idea.

[Takumi]

One thing I do miss is the cities like Williamsburg that once used small cut out shields.   I used to like them over the rectangular shield guide signs of today.

When I lived in Norfolk 1991-93 we used to go to Williamsburg a lot.  Always enjoyed the piles of cutouts.  Wished I'd taken some pictures.  Paying $ for each photo changes the philosophy on what you photograph.

I will admit the replacement signage they used, along with Newport News and more recently, Covington, are pretty sharp.

It looks like they use the same sign specs as the cutouts and the old white border signage, just...not cut out.

[roadman65]

What's up with VA Route 35 having its northern terminus at a rural intersection in the middle of nowhere instead of at I-95/ US 301 nearby in Templeton?  I would think that Secondary Route 622 could easily be extended to mutual end at I-95 Exit 41.

[74/171FAN]

What's up with VA Route 35 having its northern terminus at a rural intersection in the middle of nowhere instead of at I-95/ US 301 nearby in Templeton?  I would think that Secondary Route 622 could easily be extended to mutual end at I-95 Exit 41.

US 301 is concurrent with VA 35 at the I-95 interchange so SR 622 would have to end where US 301 turns north of the interchange at Sunnyside (the west frontage road to I-95 north of the interchange).

[WillWeaverRVA]

What's up with VA Route 35 having its northern terminus at a rural intersection in the middle of nowhere instead of at I-95/ US 301 nearby in Templeton?  I would think that Secondary Route 622 could easily be extended to mutual end at I-95 Exit 41.

I guess it's a relic of when VA 35 ran to Petersburg?

[74/171FAN]

The VA 35 page on the VA Highways Project states the following:

Around 1961, VA 35 was rerouted over new construction to its current end west of I-95. The old approach to US 301 became SR 668 and also part of a rerouted US 301. VA 35's endpoint was roughly across I-95 from the end of now-SR 696, 0.78 miles south of SR 711.

[Mapmikey]

This is how it was configured up until when 95 was being built:



The current setup is an early example of a state route extending past a natural endpoint at an interchange.  Today there is also VA 76, VA 112, VA 114, VA 130, VA 177, VA 185, VA 210

[roadman65]

https://maps.app.goo.gl/bLBTGQBUmXT3a1m79
This to the right was old VA 35 I take before I-95.


Although interesting to see before I-95 that 301 went through what is now Exit 41. That I figured much as US 301 makes too many turns at that location.  Was going to check historical aerials, but now I do not thanks to Mike.

https://maps.app.goo.gl/9RDot3fV259utvyt7
This opening in the trees must of been where US 301 veered off to the right to continue south while the current US 301 ahead was where VA 35 split off.

https://maps.app.goo.gl/D9bgioEZXWbvYixe7
Also the black on white route number sign next to the street blades is something I noticed VDOT uses at intersections for 600 routes. Never did I see a state primary route have a sign like VA 156 here does.  However the sign shows VA 156 concurrent with US 301 for that short stretch to VA 35 which shield assemblies say otherwise that Route 156 starts at this intersection.
https://maps.app.goo.gl/zD4kxskpzNggSwHk7

[Mapmikey]

https://maps.app.goo.gl/bLBTGQBUmXT3a1m79
This to the right was old VA 35 I take before I-95.


Although interesting to see before I-95 that 301 went through what is now Exit 41. That I figured much as US 301 makes too many turns at that location.  Was going to check historical aerials, but now I do not thanks to Mike.

https://maps.app.goo.gl/9RDot3fV259utvyt7
This opening in the trees must of been where US 301. Veered off to the right to continue south while the US 301 ahead was where VA 35 split off.

The 1958 aerial is interesting, because it shows the original 301 routing (roughly the 95 NB ramp location plus 156-301 overlay) and the then-modern 301 routing (may have been built as early as 1939), which used 95's current footprint through exit 41 and a bit beyond.

[roadman65]

It gets more interesting as after I-95 got built, rather than complete the freeway between Exits 12 and 41 at the time, the Commonwealth chose to four lane US 301 instead while leaving a 29 mile freeway gap between two completed segments.

[Takumi]

I always figured it's because there's a VDOT building in that little stretch.

[Mapmikey]

It gets more interesting as after I-95 got built, rather than complete the freeway between Exits 12 and 41 at the time, the Commonwealth chose to four lane US 301 instead while leaving a 29 mile freeway gap between two completed segments.

Most of US 301 was either already 4-laned or under construction (references begin in 1953 in the CTB) to be 4-laned when I-95 came along.  Page 7 of the Dec 1957 CTB Minutes has an interesting note:

Mr Fugate reported on the proposed development of Route 301 between Route 35 and Emporia Bypass and gave the reasons for the recommendation of our engineers to abandon further improvement of the 4-lane section of road to interstate standards at this time

Here is a photo of US 301 NB at VA 35Y from the mid-late 1950s:


Virginia Hwy Bulletin

[D-Dey65]

It gets more interesting as after I-95 got built, rather than complete the freeway between Exits 12 and 41 at the time, the Commonwealth chose to four lane US 301 instead while leaving a 29 mile freeway gap between two completed segments.

Most of US 301 was either already 4-laned or under construction (references begin in 1953 in the CTB) to be 4-laned when I-95 came along.  Page 7 of the Dec 1957 CTB Minutes has an interesting note:

Mr Fugate reported on the proposed development of Route 301 between Route 35 and Emporia Bypass and gave the reasons for the recommendation of our engineers to abandon further improvement of the 4-lane section of road to interstate standards at this time

Here is a photo of US 301 NB at VA 35Y from the mid-late 1950s:


Virginia Hwy Bulletin

The image is busted, but I think I've seen some of the pre-I-95 configurations of US 301 before within southern Virginia.


On another topic, if I-95 is ever six-laned in southern Virginia, should the Carson Rest Area be reconfigured as a bi-directional one? Maybe add a quarter-cloverleaf ramp to the southbound lanes?

https://maps.app.goo.gl/9RDot3fV259utvyt7
This opening in the trees must of been where US 301 veered off to the right to continue south while the current US 301 ahead was where VA 35 split off.

Move forward and turn that image around, and you'll see a nice brand new sign on I-95. 

https://www.google.com/maps/place/Petersburg,+VA/@37.0908618,-77.3572976,3a,75y,323.93h,91.47t/data=!3m6!1e1!3m4!1sH7Wo9F-778TmGzLKoBLA9w!2e0!7i16384!8i8192!4m7!3m6!1s0x89b1a49a20af6a6f:0xc365091b0b506c76!8m2!3d37.2279279!4d-77.4019267!10e5!16zL20vMG1uOXg?entry=ttu

[Mapmikey]

It gets more interesting as after I-95 got built, rather than complete the freeway between Exits 12 and 41 at the time, the Commonwealth chose to four lane US 301 instead while leaving a 29 mile freeway gap between two completed segments.

Most of US 301 was either already 4-laned or under construction (references begin in 1953 in the CTB) to be 4-laned when I-95 came along.  Page 7 of the Dec 1957 CTB Minutes has an interesting note:

Mr Fugate reported on the proposed development of Route 301 between Route 35 and Emporia Bypass and gave the reasons for the recommendation of our engineers to abandon further improvement of the 4-lane section of road to interstate standards at this time

Here is a photo of US 301 NB at VA 35Y from the mid-late 1950s:


Virginia Hwy Bulletin

The image is busted, but I think I've seen some of the pre-I-95 configurations of US 301 before within southern Virginia.


On another topic, if I-95 is ever six-laned in southern Virginia, should the Carson Rest Area be reconfigured as a bi-directional one? Maybe add a quarter-cloverleaf ramp to the southbound lanes?

https://maps.app.goo.gl/9RDot3fV259utvyt7
This opening in the trees must of been where US 301 veered off to the right to continue south while the current US 301 ahead was where VA 35 split off.

Move forward and turn that image around, and you'll see a nice brand new sign on I-95. 

https://www.google.com/maps/place/Petersburg,+VA/@37.0908618,-77.3572976,3a,75y,323.93h,91.47t/data=!3m6!1e1!3m4!1sH7Wo9F-778TmGzLKoBLA9w!2e0!7i16384!8i8192!4m7!3m6!1s0x89b1a49a20af6a6f:0xc365091b0b506c76!8m2!3d37.2279279!4d-77.4019267!10e5!16zL20vMG1uOXg?entry=ttu

Picture shows on some of my devices but not others.

Here's the actual link to it:  http://www.vahighways.com/va-ends/old/old35y_st.jpg

The point where 301 slid over to use 95's footprint is at the median crossover on 95, per the 1958 aerial - https://maps.app.goo.gl/eywiGtEzyUdKZzz2A

The location cited by Roadman65 was fully treed as late as Dec 2021 - https://maps.app.goo.gl/rFUxmSdhV8aq3k9v5 - and was likely cleared to install the new sign.

[plain]

That sign was installed last year. Actually there are similar signs on I-95 SB just south of VA 802 north of Richmond, as well as I-64 WB approaching VA 249 and EB approaching VA 623, and I'm pretty sure on I-85 also.

[plain]

Richmond seems to be moving forward with the replacement of the Arthur Ashe Boulevard (VA 161) bridge over the railroad tracks near I-95/64. Besides being old, this bridge is the site of a fairly recent train derailment.

https://richmondbizsense.com/2024/02/07/planning-commission-approves-boutique-hotel-in-the-fan-new-bridge-on-arthur-ashe-blvd/

[roadman65]

I just realized that I-495 independent of I-95 doesn't use the conventional clockwise beltway exit numbers.  I know I-95 uses its own based on the zero milepost south of Emporia, and ditto in MD from the Woodrow Wilson Bridge, but you figure they would start from zero at Springfield and head north or clockwise to College Park, MD.

[1995hoo]

I just realized that I-495 independent of I-95 doesn't use the conventional clockwise beltway exit numbers.  I know I-95 uses its own based on the zero milepost south of Emporia, and ditto in MD from the Woodrow Wilson Bridge, but you figure they would start from zero at Springfield and head north or clockwise to College Park, MD.

The Beltway used to have sequential clockwise numbers starting at Exit 1 in Alexandria and running around to Exit 38 at I-295 in Maryland. The latter state renumbered its exits around 1980-ish when it switched to milepost numbering, so the numbers counted up from Exit 2 at I-295. The numbers on I-495 continued the I-95 numbering. Virginia, meanwhile, didn't change its numbers, so they continued to run from Exit 1 to Exit 14. People complained that it was too confusing to have the numbers change from Exit 14 to Exit 41 at the state line (this argument never made any sense to me at all because exit numbers almost always reset at state lines), and apparently there was some confusion over duplicated exit numbers (maybe more logical because Virginia's Exit 2 was about three miles west of Maryland's). So eventually Virginia renumbered some of its Beltway exits to continue Maryland's numbering, with the exception of the part of the Virginia Beltway that carries I-95. (This, in turn, confuses people—if I give someone directions, I always have to explain that Exit 173 comes up three miles after Exit 57.)

Virginia had not renumbered the Beltway exits when it adopted milepost numbering throughout most of the rest of the state.

[tmoore952]

I just realized that I-495 independent of I-95 doesn't use the conventional clockwise beltway exit numbers.  I know I-95 uses its own based on the zero milepost south of Emporia, and ditto in MD from the Woodrow Wilson Bridge, but you figure they would start from zero at Springfield and head north or clockwise to College Park, MD.

The Beltway used to have sequential clockwise numbers starting at Exit 1 in Alexandria and running around to Exit 38 at I-295 in Maryland. The latter state renumbered its exits around 1980-ish when it switched to milepost numbering, so the numbers counted up from Exit 2 at I-295. The numbers on I-495 continued the I-95 numbering. Virginia, meanwhile, didn't change its numbers, so they continued to run from Exit 1 to Exit 14. People complained that it was too confusing to have the numbers change from Exit 14 to Exit 41 at the state line (this argument never made any sense to me at all because exit numbers almost always reset at state lines), and apparently there was some confusion over duplicated exit numbers (maybe more logical because Virginia's Exit 2 was about three miles west of Maryland's). So eventually Virginia renumbered some of its Beltway exits to continue Maryland's numbering, with the exception of the part of the Virginia Beltway that carries I-95. (This, in turn, confuses people—if I give someone directions, I always have to explain that Exit 173 comes up three miles after Exit 57.)

Virginia had not renumbered the Beltway exits when it adopted milepost numbering throughout most of the rest of the state.

If that Maryland renumbering occurred around 1980, was that also during the time when the eastern half of the beltway was "just" I-95?

[Mapmikey]

I just realized that I-495 independent of I-95 doesn't use the conventional clockwise beltway exit numbers.  I know I-95 uses its own based on the zero milepost south of Emporia, and ditto in MD from the Woodrow Wilson Bridge, but you figure they would start from zero at Springfield and head north or clockwise to College Park, MD.

The Beltway used to have sequential clockwise numbers starting at Exit 1 in Alexandria and running around to Exit 38 at I-295 in Maryland. The latter state renumbered its exits around 1980-ish when it switched to milepost numbering, so the numbers counted up from Exit 2 at I-295. The numbers on I-495 continued the I-95 numbering. Virginia, meanwhile, didn't change its numbers, so they continued to run from Exit 1 to Exit 14. People complained that it was too confusing to have the numbers change from Exit 14 to Exit 41 at the state line (this argument never made any sense to me at all because exit numbers almost always reset at state lines), and apparently there was some confusion over duplicated exit numbers (maybe more logical because Virginia's Exit 2 was about three miles west of Maryland's). So eventually Virginia renumbered some of its Beltway exits to continue Maryland's numbering, with the exception of the part of the Virginia Beltway that carries I-95. (This, in turn, confuses people—if I give someone directions, I always have to explain that Exit 173 comes up three miles after Exit 57.)

Virginia had not renumbered the Beltway exits when it adopted milepost numbering throughout most of the rest of the state.

If that Maryland renumbering occurred around 1980, was that also during the time when the eastern half of the beltway was "just" I-95?

I-95 replaced I-495 on the eastern half of the beltway in 1975.

From 1977 until the exit renumbering in 1992, I-95 in Virginia had to be the only route in the country to use the same exit number three times in one state. You had Exit 2 (US 301 south of Emporia), Exit 2 (I-85) on the Richmond-Petersburg Turnpike, and Exit 2 (VA 241) on the Capital Beltway; There was Exit 3 (US 58 Emporia), Exit 3 (Downtown Petersburg) on the Richmond-Petersburg Tpk., and Exit 3 (SR 613 Van Dorn St.) on the Capital Beltway; Finally, there was also Exit 4 (US 301 north of Emporia), Exit 4 (Colonial Heights), and Exit 4 (I-395/495) on the Capital Beltway.

[tmoore952]

I just realized that I-495 independent of I-95 doesn't use the conventional clockwise beltway exit numbers.  I know I-95 uses its own based on the zero milepost south of Emporia, and ditto in MD from the Woodrow Wilson Bridge, but you figure they would start from zero at Springfield and head north or clockwise to College Park, MD.

The Beltway used to have sequential clockwise numbers starting at Exit 1 in Alexandria and running around to Exit 38 at I-295 in Maryland. The latter state renumbered its exits around 1980-ish when it switched to milepost numbering, so the numbers counted up from Exit 2 at I-295. The numbers on I-495 continued the I-95 numbering. Virginia, meanwhile, didn't change its numbers, so they continued to run from Exit 1 to Exit 14. People complained that it was too confusing to have the numbers change from Exit 14 to Exit 41 at the state line (this argument never made any sense to me at all because exit numbers almost always reset at state lines), and apparently there was some confusion over duplicated exit numbers (maybe more logical because Virginia's Exit 2 was about three miles west of Maryland's). So eventually Virginia renumbered some of its Beltway exits to continue Maryland's numbering, with the exception of the part of the Virginia Beltway that carries I-95. (This, in turn, confuses people—if I give someone directions, I always have to explain that Exit 173 comes up three miles after Exit 57.)

Virginia had not renumbered the Beltway exits when it adopted milepost numbering throughout most of the rest of the state.

If that Maryland renumbering occurred around 1980, was that also during the time when the eastern half of the beltway was "just" I-95?

I-95 replaced I-495 on the eastern half of the beltway in 1975.

From 1977 until the exit renumbering in 1992, I-95 in Virginia had to be the only route in the country to use the same exit number three times in one state. You had Exit 2 (US 301 south of Emporia), Exit 2 (I-85) on the Richmond-Petersburg Turnpike, and Exit 2 (VA 241) on the Capital Beltway; There was Exit 3 (US 58 Emporia), Exit 3 (Downtown Petersburg) on the Richmond-Petersburg Tpk., and Exit 3 (SR 613 Van Dorn St.) on the Capital Beltway; Finally, there was also Exit 4 (US 301 north of Emporia), Exit 4 (Colonial Heights), and Exit 4 (I-395/495) on the Capital Beltway.

Wikipedia says that the change to I-95 occurred in 1977 when the highway that would have connected current I-95 MD exit 27 to I-395 in DC was cancelled.

I was never on the beltway until 1979, so I cannot speak to this.

[Mapmikey]

That date is straight out of the VDOT CTB minutes. It is certainly possible the postings didn't change until 1977. And

[1995hoo]

I was four years old in 1977, so I don't recall when the signs actually appeared. I do remember some I-95 shields on I-395 with white-on-blue "OLD" banners where the direction would normally be.

[roadman65]

I just realized that I-495 independent of I-95 doesn't use the conventional clockwise beltway exit numbers.  I know I-95 uses its own based on the zero milepost south of Emporia, and ditto in MD from the Woodrow Wilson Bridge, but you figure they would start from zero at Springfield and head north or clockwise to College Park, MD.

The Beltway used to have sequential clockwise numbers starting at Exit 1 in Alexandria and running around to Exit 38 at I-295 in Maryland. The latter state renumbered its exits around 1980-ish when it switched to milepost numbering, so the numbers counted up from Exit 2 at I-295. The numbers on I-495 continued the I-95 numbering. Virginia, meanwhile, didn't change its numbers, so they continued to run from Exit 1 to Exit 14. People complained that it was too confusing to have the numbers change from Exit 14 to Exit 41 at the state line (this argument never made any sense to me at all because exit numbers almost always reset at state lines), and apparently there was some confusion over duplicated exit numbers (maybe more logical because Virginia's Exit 2 was about three miles west of Maryland's). So eventually Virginia renumbered some of its Beltway exits to continue Maryland's numbering, with the exception of the part of the Virginia Beltway that carries I-95. (This, in turn, confuses people—if I give someone directions, I always have to explain that Exit 173 comes up three miles after Exit 57.)

Virginia had not renumbered the Beltway exits when it adopted milepost numbering throughout most of the rest of the state.

If that Maryland renumbering occurred around 1980, was that also during the time when the eastern half of the beltway was "just" I-95?

I-95 replaced I-495 on the eastern half of the beltway in 1975.

From 1977 until the exit renumbering in 1992, I-95 in Virginia had to be the only route in the country to use the same exit number three times in one state. You had Exit 2 (US 301 south of Emporia), Exit 2 (I-85) on the Richmond-Petersburg Turnpike, and Exit 2 (VA 241) on the Capital Beltway; There was Exit 3 (US 58 Emporia), Exit 3 (Downtown Petersburg) on the Richmond-Petersburg Tpk., and Exit 3 (SR 613 Van Dorn St.) on the Capital Beltway; Finally, there was also Exit 4 (US 301 north of Emporia), Exit 4 (Colonial Heights), and Exit 4 (I-395/495) on the Capital Beltway.

I-87 in New York has three sets of exit numbers.


Exit 2 https://maps.app.goo.gl/LoZmxKNwNKUGFAsu8
Exit 2 https://maps.app.goo.gl/pYkWbgLYrzUPEMrk8
Exit 2 https://maps.app.goo.gl/RX5z8UBwDLKQpTJk8

[elsmere241]

I remember in 1981, the signs on the Maryland part of the Beltway showed old and new numbers.