AARoads Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

New rules to ensure post quality. See this thread for details.

Author Topic: Making US-258/W. Mercury Blvd. a Freeway  (Read 10235 times)

deathtopumpkins

  • *
  • Offline Offline

  • Posts: 2394
  • Location: Southern NH
  • Last Login: December 03, 2021, 05:22:16 PM
Making US-258/W. Mercury Blvd. a Freeway
« on: February 04, 2009, 10:38:53 PM »

Quote
I've mentioned this before, but VA/NC-168, and US-158 between Chesapeake, VA, and Nags Head, NC.

A better case could be made for Northampton between 64 and Diamond Springs (if not all the way to Shore Dr)...


Yeah, that would be good too. It's rather annoying getting off the interstate, sitting through a couple of traffic lights, and then back on the highway without a stoplight for the next 40 miles. This is actually one of the reasons I've stopped taking US-13 when heading north.



I came up with another good one:
US-258/W. Mercury Blvd. between VA-278/King St. and I-64. (http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=Hampton,+VA&sll=38.88306,-94.785589&sspn=147.765094,316.40625&ie=UTF8&ll=37.041819,-76.368628&spn=0.049053,0.077248&t=h&z=14) This, despite being 10 lanes wide for most of it, not counting turn lanes, is a traffic nightmare, as about 100,000 people have to use it as their most direct access to I-64 West. So I propose sacrificing the inner lane going each way from just west of King St., and in that space combined with the existing 3-lane-wide median, build an elevated 4-lane freeway with ramps at LaSalle Ave. (Google Earth says VA-167, but I've never seen it signed as a state route - An existing cloverleaf), Armistead Ave./VA-134 (The mega-intersection with the 3 left turn lanes), and a westbound offramp and eastbound onramp at Coliseum Mall (future site of Hampton Towne Center Mall), before the elevated lanes merge with I-64 WB at its existing interchange with US-258. One of these days I'm actually going to draw up a plan for all of this and maybe get something done about it.
Logged
Disclaimer: All posts represent my personal opinions and not those of my employer.

Clinched Highways | Counties Visited

deathtopumpkins

  • *
  • Offline Offline

  • Posts: 2394
  • Location: Southern NH
  • Last Login: December 03, 2021, 05:22:16 PM
Making US-258/W. Mercury Blvd. a Freeway
« Reply #1 on: February 08, 2009, 04:43:25 PM »

Quote from: froggie
1) First, you could make a better case for US 258/Mercury between 64 and the James River Bridge.  Similar traffic, but west to the JRB has better connectivity.
Meh... I've never noticed traffic as bad on it, and I drive it up to 4 times a week heading out into Smithfield. My main reasoning for east of I-64 is that it backs up a lot as it is the only convenient access to I-64 WB for most of the city of Hampton.

Quote
2) Second, you'd have an easier time upgrading HRC Pkwy to freeway and extending it east to King St.  The latter has been suggested off-and-on for about 40 years.
I didn't think the Parkway existed 40 years ago...  :-/ I've proposed that too, but everyone I know who I canvassed about it when I was actually seriously considering trying to get something done about it said that they would rather deal with the traffic on Mercury than destroy all those wetlands an extension of the parkway would travel through. Thus my proposal for Mercury, as it would not require the acquisition of a new ROW, but rather use Mercury's existing wide median. And the parkway was completely a freeway until sometime around 2000 when they added an at-grade intersection with Coliseum Dr. and extended it westward past Big Bethel Rd. (SR-600) at-grade, and then in late 2008 when they added another signalized at-grade intersection between Magruder and I-64, which really screwed the whole road up. No one uses the new interchange, and to accommodate it they moved the WB onramp from Magruder down by about half a mile, creating a very short weave zone before the exit to I-64 NB.

Quote
LaSalle used to be VA 167, but the route was decommissioned in 1995.  Mapmakers have been very slow to remove it though, hence why it still shows up on some maps.
Thanks, I was wondering about that.

Quote
There's been on-and-off proposals for an interchange here anyway.  Would be expensive since you'd have to take out at least 2 quadrants worth of commercial property.
Ahh, BUT the commercial property on all corners is mostly set back from the intersection. If some sort of a volleyball or something was built, it might not end up necessary to demolish the surrounding businesses, just move their parking lots around a bit.
Logged
Disclaimer: All posts represent my personal opinions and not those of my employer.

Clinched Highways | Counties Visited

deathtopumpkins

  • *
  • Offline Offline

  • Posts: 2394
  • Location: Southern NH
  • Last Login: December 03, 2021, 05:22:16 PM
Making US-258/W. Mercury Blvd. a Freeway
« Reply #2 on: February 08, 2009, 06:19:28 PM »

Yes, well, this is just an idea... no one said VDOT was actually going to build it.  :-P

And I mentioned ROW acquisition and moving parking lots in different situations.  ;-)

As for cost... eventually they will need to do something, and who knows, this could prove to be the cheapest option.
Logged
Disclaimer: All posts represent my personal opinions and not those of my employer.

Clinched Highways | Counties Visited

deathtopumpkins

  • *
  • Offline Offline

  • Posts: 2394
  • Location: Southern NH
  • Last Login: December 03, 2021, 05:22:16 PM
Making US-258/W. Mercury Blvd. a Freeway
« Reply #3 on: February 08, 2009, 08:59:35 PM »

VDOT doesn't maintain US routes? Hmm...  :-/

But just to move the parking lots do you really think that they would need to acquire the entire property?
Logged
Disclaimer: All posts represent my personal opinions and not those of my employer.

Clinched Highways | Counties Visited

deathtopumpkins

  • *
  • Offline Offline

  • Posts: 2394
  • Location: Southern NH
  • Last Login: December 03, 2021, 05:22:16 PM
Making US-258/W. Mercury Blvd. a Freeway
« Reply #4 on: February 08, 2009, 10:53:39 PM »

Well I guess that makes sense...

And I'm splitting this off into a thread in the Mid-Atlantic board... I feel we've hijacked a bit.
Logged
Disclaimer: All posts represent my personal opinions and not those of my employer.

Clinched Highways | Counties Visited

74/171FAN

  • *
  • *
  • Offline Offline

  • Posts: 2334
  • Age: 29
  • Location: Harrisburg, PA
  • Last Login: December 04, 2021, 08:45:47 PM
Re: Making US-258/W. Mercury Blvd. a Freeway
« Reply #5 on: March 13, 2009, 04:26:39 PM »

Quote
I've mentioned this before, but VA/NC-168, and US-158 between Chesapeake, VA, and Nags Head, NC.

A better case could be made for Northampton between 64 and Diamond Springs (if not all the way to Shore Dr)...


Yeah, that would be good too. It's rather annoying getting off the interstate, sitting through a couple of traffic lights, and then back on the highway without a stoplight for the next 40 miles. This is actually one of the reasons I've stopped taking US-13 when heading north.



I came up with another good one:
US-258/W. Mercury Blvd. between VA-278/King St. and I-64. (http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=Hampton,+VA&sll=38.88306,-94.785589&sspn=147.765094,316.40625&ie=UTF8&ll=37.041819,-76.368628&spn=0.049053,0.077248&t=h&z=14) This, despite being 10 lanes wide for most of it, not counting turn lanes, is a traffic nightmare, as about 100,000 people have to use it as their most direct access to I-64 West. So I propose sacrificing the inner lane going each way from just west of King St., and in that space combined with the existing 3-lane-wide median, build an elevated 4-lane freeway with ramps at LaSalle Ave. (Google Earth says VA-167, but I've never seen it signed as a state route - An existing cloverleaf), Armistead Ave./VA-134 (The mega-intersection with the 3 left turn lanes), and a westbound offramp and eastbound onramp at Coliseum Mall (future site of Hampton Towne Center Mall), before the elevated lanes merge with I-64 WB at its existing interchange with US-258. One of these days I'm actually going to draw up a plan for all of this and maybe get something done about it.
DTP:So how would US 258 SB traffic exit the freeway before I-64 if the freeway defaults onto I-64 WB?
Logged
I am now a PennDOT employee.  My opinions/views do not necessarily reflect the opinions/views of PennDOT.

deathtopumpkins

  • *
  • Offline Offline

  • Posts: 2394
  • Location: Southern NH
  • Last Login: December 03, 2021, 05:22:16 PM
Re: Making US-258/W. Mercury Blvd. a Freeway
« Reply #6 on: March 14, 2009, 01:49:34 AM »

I said in that quote, a WB (SB 258) offramp and EB (NB 258) onramp and Coliseum, which is the last intersection before the 64 interchange.
Logged
Disclaimer: All posts represent my personal opinions and not those of my employer.

Clinched Highways | Counties Visited

74/171FAN

  • *
  • *
  • Offline Offline

  • Posts: 2334
  • Age: 29
  • Location: Harrisburg, PA
  • Last Login: December 04, 2021, 08:45:47 PM
Re: Making US-258/W. Mercury Blvd. a Freeway
« Reply #7 on: March 14, 2009, 08:59:52 AM »

I said in that quote, a WB (SB 258) offramp and EB (NB 258) onramp and Coliseum, which is the last intersection before the 64 interchange.
  So the ramps would go to US 258 and the Coliseum I'm presuming?
Logged
I am now a PennDOT employee.  My opinions/views do not necessarily reflect the opinions/views of PennDOT.

froggie

  • *
  • Offline Offline

  • Posts: 12068
  • Location: Greensboro, VT
  • Last Login: December 04, 2021, 11:42:36 AM
    • Froggie's Place
Re: Making US-258/W. Mercury Blvd. a Freeway
« Reply #8 on: March 14, 2009, 09:32:05 AM »

Sounds to me like he's proposing an elevated, elongated flyover that would serve the following four movements:

- EB 64 to EB Mercury (with the touchdown at King St)
- Coliseum Dr to EB Mercury (as above, with the touchdown at King St)
- WB Mercury to WB 64 (with the ramp beginning at King St)
- WB Mercury to Coliseum Dr (as above, with the ramp beginning at King St)
Logged

deathtopumpkins

  • *
  • Offline Offline

  • Posts: 2394
  • Location: Southern NH
  • Last Login: December 03, 2021, 05:22:16 PM
Re: Making US-258/W. Mercury Blvd. a Freeway
« Reply #9 on: March 14, 2009, 11:37:54 AM »

Yeah, that's it basically it froggie. But think more 'elevated freeway' not 'elongated flyover'. As I believe I previously mentioned, in addition to the ramps to 64 and it touching down at King St., there would also be ramps serving Coliseum Dr., Armistead Ave., and LaSalle Ave.
Logged
Disclaimer: All posts represent my personal opinions and not those of my employer.

Clinched Highways | Counties Visited

74/171FAN

  • *
  • *
  • Offline Offline

  • Posts: 2334
  • Age: 29
  • Location: Harrisburg, PA
  • Last Login: December 04, 2021, 08:45:47 PM
Re: Making US-258/W. Mercury Blvd. a Freeway
« Reply #10 on: March 14, 2009, 01:11:50 PM »

Yeah, that's it basically it froggie. But think more 'elevated freeway' not 'elongated flyover'. As I believe I previously mentioned, in addition to the ramps to 64 and it touching down at King St., there would also be ramps serving Coliseum Dr., Armistead Ave., and LaSalle Ave.
  So US 258 traffic not coming to/from I-64 is supposed to follow a frontage road with ramps at Lasalle Ave and signals at VA 134/Armistead Ave and Coliseum Dr???
Logged
I am now a PennDOT employee.  My opinions/views do not necessarily reflect the opinions/views of PennDOT.

njroadhorse

  • *
  • Offline Offline

  • Posts: 958
  • Going wherever the roads take me

  • Location: North Jersey/Blacksburg, VA
  • Last Login: February 03, 2016, 07:05:44 PM
Re: Making US-258/W. Mercury Blvd. a Freeway
« Reply #11 on: March 14, 2009, 02:15:21 PM »

Yeah, that's it basically it froggie. But think more 'elevated freeway' not 'elongated flyover'. As I believe I previously mentioned, in addition to the ramps to 64 and it touching down at King St., there would also be ramps serving Coliseum Dr., Armistead Ave., and LaSalle Ave.
  So US 258 traffic not coming to/from I-64 is supposed to follow a frontage road with ramps at Lasalle Ave and signals at VA 134/Armistead Ave and Coliseum Dr???
Looks to be that way  :-(
Logged
NJ Roads FTW!
I-99... the Glen Quagmire of interstate routes??

deathtopumpkins

  • *
  • Offline Offline

  • Posts: 2394
  • Location: Southern NH
  • Last Login: December 03, 2021, 05:22:16 PM
Re: Making US-258/W. Mercury Blvd. a Freeway
« Reply #12 on: March 14, 2009, 02:43:45 PM »

Not exactly. The frontage roads would just serve local businesses and US-258 would follow the elevated freeway between King St. and Coliseum Dr., with ramps between the frontage roads/freeway at Armistead and LaSalle. At Coliseum, the elevated freeway would merge back into a surface road, but ramps would continue to connect with I-64 WB. Let me draw a diagram in Google Earth:

That's the western end. Understand now?
« Last Edit: March 14, 2009, 03:10:30 PM by deathtopumpkins »
Logged
Disclaimer: All posts represent my personal opinions and not those of my employer.

Clinched Highways | Counties Visited

74/171FAN

  • *
  • *
  • Offline Offline

  • Posts: 2334
  • Age: 29
  • Location: Harrisburg, PA
  • Last Login: December 04, 2021, 08:45:47 PM
Re: Making US-258/W. Mercury Blvd. a Freeway
« Reply #13 on: March 14, 2009, 04:35:49 PM »

Yep I just needed clarification on traffic that wanted to stay on US 258. :clap:
Logged
I am now a PennDOT employee.  My opinions/views do not necessarily reflect the opinions/views of PennDOT.

 


Opinions expressed here on belong solely to the poster and do not represent or reflect the opinions or beliefs of AARoads, its creators and/or associates.