Virginia

[roadman65]

It would still be an exception even if it was I-895.  Like I-664, I-785 (officially VA 785 currently), the two cancelled I-795s, and the VDOT-proposed I-864, it is a number >599 that is not a secondary route. 

VDOT explicitly recognizes interstate designations above 599 as exceptions.  See the bottom of page 2 of the 2003 route log

I understand exceptions for interstates as they're not state issued numbers. Just like in New Jersey, 600 series numbers are for intra county route numbers. Yet I-676 exists as it's an interstate not in the NJ numbering convention.

[1995hoo]

If a simple route number causes you such angst, I'd hate to see your reaction if you saw the mile markers on that road.

[roadman65]

If a simple route number causes you such angst, I'd hate to see your reaction if you saw the mile markers on that road.

I'm not angry. Just wondering if VDOT had a numbering scheme and if they broke it for a good reason. I could care less if it was VA 995 or VA 495 or whatever. I'm not like many on here who digress over I-99 being signed into law cause it's between I-79 and I-81 or like your pal who insisted VA 28 should be I-366.

[1995hoo]

I didn't say you were angry. I said the number seems to be causing you angst. I guess your reply #6975 suggested to me that the issue bothers you more than you're saying it actually does.

[roadman65]

I didn't say you were angry. I said the number seems to be causing you angst. I guess your reply #6975 suggested to me that the issue bothers you more than you're saying it actually does.

Sorry misunderstood.

[epzik8]

Exits 133 and 130 on 95 are no longer recognizable. "WELCOME CENTER FOR VIRGINIA" will be stuck in my head for a while.

[WillWeaverRVA]

VA 399 (the Science Museum of Virginia loop road in Richmond) is in the process of being physically destroyed, to be replaced with a green space. There will be a tiny piece saved to use as an access road to the museum's parking deck but no idea if this would still be considered VA 399 or not.

[Hunty2022]

The title for shortest primary route in Virginia would likely go to VA-79, if the VA-399 designation does get decommissioned.

[Mapmikey]

The title for shortest primary route in Virginia would likely go to VA-79, if the VA-399 designation does get decommissioned.

There are several posted routes shorter than VA 79's 0.23 miles.

300Y - 0.04 mi
342 - 0.16 mi
162 - 0.17 mi
391 - 0.17 mi
341 - 0.20 mi

There are several unposted ones shorter as well.

[Rothman]

The title for shortest primary route in Virginia would likely go to VA-79, if the VA-399 designation does get decommissioned.

There are several posted routes shorter than VA 79's 0.23 miles.

300Y - 0.04 mi
342 - 0.16 mi
162 - 0.17 mi
391 - 0.17 mi
341 - 0.20 mi

There are several unposted ones shorter as well.

Add in the state secondary system and it becomes a question of how to determine lengths of those routes posted, due to being discontinuous.

[Mapmikey]

The title for shortest primary route in Virginia would likely go to VA-79, if the VA-399 designation does get decommissioned.

There are several posted routes shorter than VA 79's 0.23 miles.

300Y - 0.04 mi
342 - 0.16 mi
162 - 0.17 mi
391 - 0.17 mi
341 - 0.20 mi

There are several unposted ones shorter as well.

Add in the state secondary system and it becomes a question of how to determine lengths of those routes posted, due to being discontinuous.

none of which matters for the winner of shortest *primary* route in Virginia.  F-routes, however, are technically in the primary system but not what is usually included in questions like these.

I would also not characterize the 50+ SR 600s, for example as a discontinuous route.  Rather they are 50+ separate routes.  SC 51 and PA 97 are examples of primary routes that I would also characterize as separate routes instead of discontinuous like VA 42 and VA 43 are.

[74/171FAN]

VA 399 (the Science Museum of Virginia loop road in Richmond) is in the process of being physically destroyed, to be replaced with a green space. There will be a tiny piece saved to use as an access road to the museum's parking deck but no idea if this would still be considered VA 399 or not.

Well I am definitely glad in regards to the lowest route-numbered game that rickmastfan67 put FL 399 in Travel Mapping.

[Rothman]

The title for shortest primary route in Virginia would likely go to VA-79, if the VA-399 designation does get decommissioned.

There are several posted routes shorter than VA 79's 0.23 miles.

300Y - 0.04 mi
342 - 0.16 mi
162 - 0.17 mi
391 - 0.17 mi
341 - 0.20 mi

There are several unposted ones shorter as well.

Add in the state secondary system and it becomes a question of how to determine lengths of those routes posted, due to being discontinuous.

none of which matters for the winner of shortest *primary* route in Virginia.  F-routes, however, are technically in the primary system but not what is usually included in questions like these.

I would also not characterize the 50+ SR 600s, for example as a discontinuous route.  Rather they are 50+ separate routes.  SC 51 and PA 97 are examples of primary routes that I would also characterize as separate routes instead of discontinuous like VA 42 and VA 43 are.

Wikipedia treats them as discontinuous.

[rover]

1.  Where 664/64/264/460 intersect, I can never figure out where does 664 start/end and likewise 64?
2.  Driving on 295 from 64 to 95, it is so smooth.  I love the 8 lane wide median and the great long merge from 64 WB to 295 NB. 
- Why won't they fix the 295 SB to 64 EB merge to also be high speed?
- Why can't we get 95 from 295 to Fredericksburg the same 4+4 wide median as 295?

[sprjus4]

1.  Where 664/64/264/460 intersect, I can never figure out where does 664 start/end and likewise 64?

Right where the Y-interchange is. I-64, I-664, and I-264 all meet at that point.

Technically, the interchange with US-58 is with I-664, not I-64 nor I-264.

- Why won't they fix the 295 SB to 64 EB merge to also be high speed?

That flyover was only built around 20 years ago or so, so they wouldn't be replacing it anytime soon. Prior to that, all traffic had to take the loop ramp (that still exists as a redundancy)... imagine that with today's volumes! I do agree though, it should have been built with a 55 to 60 mph design speed. Also the merge with the C/D road is abrupt and striped interestingly. That could've been designed better, IMO. But it functions well with the traffic volumes, nonetheless, and probably won't see any modifications in the near future.

[rover]

1.  Where 664/64/264/460 intersect, I can never figure out where does 664 start/end and likewise 64?

Right where the Y-interchange is. I-64, I-664, and I-264 all meet at that point.

Technically, the interchange with US-58 is with I-664, not I-64 nor I-264.

- Why won't they fix the 295 SB to 64 EB merge to also be high speed?

That flyover was only built around 20 years ago or so, so they wouldn't be replacing it anytime soon. Prior to that, all traffic had to take the loop ramp (that still exists as a redundancy)... imagine that with today's volumes! I do agree though, it should have been built with a 55 to 60 mph design speed. Also the merge with the C/D road is abrupt and striped interestingly. That could've been designed better, IMO. But it functions well with the traffic volumes, nonetheless, and probably won't see any modifications in the near future.

So and 264 end where they meet at Bowers Hill
664 starts where it meets the 460/58/264 E-W road
So between 664 and the 264/64 interchange, what is that road signed as?

I totally forgot the 295 SB to 64 EB had a prior cloverleaf until recently, are there any images?
I wonder why if they did redo this so soon they did not make it high speed?

[Mapmikey]

64-264-664 all begin/end at the interchange next to the word Bowers in the diagram above.

'Begin project' is just where construction began as there was already a stub connection between 64-264 and US 13-58-460. This stub is now signed as I-664.

[rover]

64-264-664 all begin/end at the interchange next to the word Bowers in the diagram above.

'Begin project' is just where construction began as there was already a stub connection between 64-264 and US 13-58-460. This stub is now signed as I-664.

Ok, makes sense.  So at the 'Y' interchange:
- The road segment which goes to the SE of it is I-64
- The road segment which goes to the NE is I-264
- The road segment which goes to the SW is I-664 before it cuts N.

So what happens to 12/48/460 at the interchange with I-664?

Also, was there ever any plans originally for I-64 not to cul-de-sac loop but instead maybe be routed onto I-264 to VA Beach?

[froggie]

So what happens to 12/48/460 at the interchange with I-664?

Presuming you mean 13/58/460.  They all continue through the interchange to the first traffic signal to the east, where US 58 continues straight towards Portsmouth and 13/460 turn south, cross under I-664, and then turn onto Military Hwy (Google Maps erroneously labels this as "ALT US 460").  It's the same intersection at which VA 191 begins and heads to the northwest.

Also, was there ever any plans originally for I-64 not to cul-de-sac loop but instead maybe be routed onto I-264 to VA Beach?

Not originally.  The "original" plan did not have an Interstate towards the Virginia Beach Oceanfront....that wasn't added until 1999.

[sprjus4]

Also, was there ever any plans originally for I-64 not to cul-de-sac loop but instead maybe be routed onto I-264 to VA Beach?

Not originally.  The "original" plan did not have an Interstate towards the Virginia Beach Oceanfront....that wasn't added until 1999.

I'll add that I believe VDOT explored options to address I-64's "wrong way" routing in the mid 1990s, and one of those did indeed involve routing I-64 onto I-264, and redesignating I-64 in Chesapeake as I-664.

But in the original 1950s / 1960s interstate plan, I-64 looped around to Bowers Hill where it ended at US-13/58/460, I-464 connected I-64 to I-264, I-264 went between either side of I-64 (except through Downtown Norfolk / the tunnel / Berkley Bridge) and I-564 connected to the Naval Base. That was it for interstates.

What is now I-264 east of I-64 to the Oceanfront was built in the late 1960s as VA-44, a toll road. In the 1990s, the tolls came off and was eventually redesignated as an extension of I-264 since it effectively acted as it.

I-664 was first approved in 1968 and was constructed throughout the 1980s and complete in the early 1990s.

Here is the original 1956 interstate plan for Hampton Roads from the FHWA's Yellow Book.

[Mapmikey]

Here is what the 1956 plan became by 1958



The earliest reference I know of for VA 44 expressway to Virginia Beach is in 1962.

The CTB did consider moving I-64 to replace VA 44 in 1996:
In May 1996 (CTB), VDOT presented 4 options to renumber the interstates in the Hampton Roads area:
1. Extend I-664 around to I-264/VA 44 and replace VA 44 with I-64
2. Extend I-664 around to I-264/VA 44 and replace VA 44 with I-664
3. Replace I-664 with I-64 and replace VA 44 with I-64; Replace I-64 across HRBT to I-264/VA 44 with I-664
4. Replace I-664 with I-64 and replace VA 44 with I-64; Replace I-64 across HRBT to I-264/VA 44 with I-864
The CTB deferred action to June 1996 whereby they elected to defer again. There was no further mention of anything related to this until they renumbered VA 44 as I-264 in Aug 1997.

[Alps]

What was the dashed line west of 264/64 intended to be?

[froggie]

What was the dashed line west of 264/64 intended to be?

Tie-in to what is now 13/58/460 across the swamp.

[Alps]

What was the dashed line west of 264/64 intended to be?

Tie-in to what is now 13/58/460 across the swamp.

I-764??

[froggie]

It wasn't going to be an Interstate.  Just a connection.  You're reading too much into what the map shows.