Virginia

[Bitmapped]

Has there been any consideration of building a bypass of Front Royal for US 340 and/or US 522?

[Rothman]

Has there been any consideration of building a bypass of Front Royal for US 340 and/or US 522?

*looks at I-66*

[Bitmapped]

Has there been any consideration of building a bypass of Front Royal for US 340 and/or US 522?

*looks at I-66*

That helps VA 55, not the north-south routes.

[Mapmikey]

Has there been any consideration of building a bypass of Front Royal for US 340 and/or US 522?

*looks at I-66*

That helps VA 55, not the north-south routes.

Actually, if you ask Google to show you how to get from just north of I-66 on US 522 to Culpeper, it is the same time to use I-66 to US 17 to Warrenton as it is to use US 522...

US 522 is not really a through route south of Front Royal and there are numerous obstacles both east and west for a 522 Bypass.

A US 340 bypass around the west of Front Royal at least looks doable, but I would be surprised if there is enough through traffic going south of Skyline Drive to warrant it.

[Thing 342]

Traffic from 340 or 522 headed to I-66 can skip most of downtown by taking 55 east to exit 13...

[Beltway]

Has there been any consideration of building a bypass of Front Royal for US 340 and/or US 522?

There's never been a formal VDOT proposal for a US-340 or US-522 bypass of Front Royal. The only planning work in that corridor is the current Route 340/522 STARS study, which looks at safety and congestion on the 1.1‑mile segment near I‑66 Exit 6, not a new‑location route.

Geography also works against a bypass. Shenandoah National Park and the Blue Ridge limit options to the east, and the Shenandoah River and its floodplain constrain the west. Traffic volumes north of town are handled by the existing four‑lane divided highway that carries both routes toward Double Tollgate.

So far, VDOT's approach has been incremental improvements to the existing corridor, not studying or advancing a bypass.

[WillWeaverRVA]

VDOT is embarking upon the next phase of its project to revamp the US 1/Princess Anne Street/Hanson Avenue intersection in Fredericksburg. Unfortunately, this phase will include the removal of the now-erroneous but vintage overhead signs on southbound US 1 just over the Falmouth Bridge.

https://www.vdot.virginia.gov/news-events/news/fredericksburg-district/overnight-full-stops-on-route-1-near-falmouth-bridge-in-fredericksburg-next-week.php

[Beltway]

Speaking of the Falmouth Bridge ... looks like it is still a few years away, construction starting in 2030.

https://www.vdot.virginia.gov/projects/fredericksburg-district/falmouth-bridge-rehabilitation-project-route-1-over-the-rappahannock-river/

Quote:
The project will replace the existing bridge superstructure to include new girders, new deck, and new rails with pedestrian accommodations. Concrete repairs will also be completed on the existing piers and abutments. Once completed, bicyclists and pedestrians will have improved space to walk, run, and bike. A shared use path will be built on the upstream side of the bridge, along the southbound lanes. This path will have space to support bicyclist and pedestrian traffic and will be separated from vehicle traffic by a barrier. Sidewalk will be built along the downstream side of the bridge, along the northbound lanes. 

Falmouth Bridge will remain open during construction with three travel lanes at most times. Two lanes of Route 1 southbound will remain open, but Route 1 northbound will be reduced to a single lane. Construction crews will use the closed northbound lane to accomplish the needed work and will shift traffic as construction progresses. 

Falmouth Bridge opened in 1943. It has four travel lanes and carries an average of 40,000 vehicles a day.  Total project funding is approximately $160 million.

[Thing 342]

CNHP posted a large new update on the Colonial Parkway restoration project, with completion unsurprisingly pushed back to November 2026: https://www.nps.gov/colo/planyourvisit/colo-parkway-rehab.htm

I drove the York River section today and one-way lights have been installed on the two bridges undergoing improvements. At the current rate things have gone on this project, seems hard to believe that work will be anywhere near completion by the time of the temporary re-opening to Penniman Rd in June.

[Great Lakes Roads]

VDOT to renumber the exits along US 23 in Norton and Big Stone Gap to mileage-based.

Exits 1 & 2 in Big Stone Gap --> exits 33 & 35
Exits 1 & 2 in Norton --> exits 42 & 44

[sprjus4]

VDOT to renumber the exits along US 23 in Norton and Big Stone Gap to mileage-based.

Exits 1 & 2 in Big Stone Gap --> exits 33 & 35
Exits 1 & 2 in Norton --> exits 42 & 44

Good change, IMO. Would like to start seeing this  with other US / state highways around the state. It only exists for a couple of them.

[74/171FAN]

VDOT to renumber the exits along US 23 in Norton and Big Stone Gap to mileage-based.

Exits 1 & 2 in Big Stone Gap --> exits 33 & 35
Exits 1 & 2 in Norton --> exits 42 & 44

Well I did not see US 23 getting mileage exit numbers coming. Maybe this is why VDOT put them in the traffic logs.

[WillWeaverRVA]

VDOT to renumber the exits along US 23 in Norton and Big Stone Gap to mileage-based.

Exits 1 & 2 in Big Stone Gap --> exits 33 & 35
Exits 1 & 2 in Norton --> exits 42 & 44

Well I did not see US 23 getting mileage exit numbers coming. Maybe this is why VDOT put them in the traffic logs.

I'd like it if this became a statewide thing. VA 895 and VA 150 only having a single numbered exit has always bugged me.

[74/171FAN]

VA 895 and VA 150 only having a single numbered exit has always bugged me.

I know VA 895 has exit 3 for VA 281, but I did not think VA 150 had a numbered exit yet.

[WillWeaverRVA]

VA 895 and VA 150 only having a single numbered exit has always bugged me.

I know VA 895 has exit 3 for VA 281, but I did not think VA 150 had a numbered exit yet.

VA 895 and VA 150 officially share mileage, at least in milepost signage.

[plain]

VA 288 not having exit numbers, despite the entire route being up to interstate standards, bugs me.

[Beltway]

VA 288 not having exit numbers, despite the entire route being up to interstate standards, bugs me.

VA-288 not being I-695, bugs me.

VA-895 not being I-895, bugs me.

[WahooBill]

VA-895 not being I-895 or Toll VA-150 is what bugs me

[NE2]

Cockroaches bug me

[WillWeaverRVA]

Cockroaches bug me

Bugs in general bug me

[Beltway]

VA-895 not being I-895 or Toll VA-150 is what bugs me

VA-895 is built to Interstate standards -- VA-150 is not.

[WillWeaverRVA]

VA-895 not being I-895 or Toll VA-150 is what bugs me

VA-895 is built to Interstate standards -- VA-150 is not.

I think @WahooBill was suggesting that VA 895 should be an extension of VA 150 and not the other way around if it isn't going to be I-895. Seeing as internally and on mileposts they share mileage (and VA 895's mileage continues onto VA 150), the whole thing might as well be VA 150 if I-895 isn't going to happen.

[Beltway]

VA-895 not being I-895 or Toll VA-150 is what bugs me

VA-895 is built to Interstate standards -- VA-150 is not.

I think @WahooBill was suggesting that VA 895 should be an extension of VA 150 and not the other way around if it isn't going to be I-895. Seeing as internally and on mileposts they share mileage (and VA 895's mileage continues onto VA 150), the whole thing might as well be VA 150 if I-895 isn't going to happen.

I have have thought about that before, having one number. I am holding out hope that it will become I-895. That is why the got the number in the first place, when it was being planned as a toll-free route.

[WillWeaverRVA]

VA-895 not being I-895 or Toll VA-150 is what bugs me

VA-895 is built to Interstate standards -- VA-150 is not.

I think @WahooBill was suggesting that VA 895 should be an extension of VA 150 and not the other way around if it isn't going to be I-895. Seeing as internally and on mileposts they share mileage (and VA 895's mileage continues onto VA 150), the whole thing might as well be VA 150 if I-895 isn't going to happen.

I have have thought about that before, having one number. I am holding out hope that it will become I-895. That is why the got the number in the first place, when it was being planned as a toll-free route.

Back when RRTPO was taking project suggestions for their 2050 LRTP, I submitted suggestions to complete the missing connection in the I-95/VA 150/VA 895 interchange (southbound I-95 to eastbound VA 895) and get VA 895 signed as I-895 since AASHTO and FHWA seem to approve pretty much anything nowadays (I-343 I'm looking at you).

[hbelkins]

VDOT to renumber the exits along US 23 in Norton and Big Stone Gap to mileage-based.

Exits 1 & 2 in Big Stone Gap --> exits 33 & 35
Exits 1 & 2 in Norton --> exits 42 & 44

Well I did not see US 23 getting mileage exit numbers coming. Maybe this is why VDOT put them in the traffic logs.

US 23 has had border-to-border mileposts (well, nearly border to border, the numbers cut off somewhere between Pound and the Kentucky state line) for about 20 years.

I wonder if they'll be doing something similar to US 19 (Lebanon and Tazewell) and US 460 (Richlands)? Those routes do not have border-to-border mile markers.