Meadow Creek Parkway Interchange: Difference between revisions
(updated next meeting) |
Jcglendening (talk | contribs) m (</ref> missing) |
||
Line 39: | Line 39: | ||
==History== | ==History== | ||
On February 18, 2003, City Council heard a report from NDS Director [[Jim Tolbert]] regarding an RFP that was being issued to study possible intersection designs for where the Meadowcreek Parkway would meet the Route 250 Bypass<ref>Charlottesville City Council Minutes. 18 Feb. 2003. City of Charlottesville, Virginia. 24 Mar. 2009 <http://weblink.charlottesville.org/DocView.aspx?id=195906>. | On February 18, 2003, City Council heard a report from NDS Director [[Jim Tolbert]] regarding an RFP that was being issued to study possible intersection designs for where the Meadowcreek Parkway would meet the Route 250 Bypass<ref>Charlottesville City Council Minutes. 18 Feb. 2003. City of Charlottesville, Virginia. 24 Mar. 2009 <http://weblink.charlottesville.org/DocView.aspx?id=195906>.</ref> | ||
== Status == | == Status == |
Revision as of 15:46, 11 August 2009
Meadowcreek Parkway Interchange | ||
---|---|---|
Planned
|
||
Project Overview
|
| |
1. To enhance transportation mobility for local residents
2. To safely accommodate projected future traffic volumes 3. To accommodate and enhance pedestrian and bicycle needs in the project area |
||
Cost | $33-37 million | |
Location | City Council public hearing | |
Sponsor | Charlottesville | |
Next meeting | September 2009 | |
Status Update
|
| |
Funded by Federal appropriation announced in 2005. In design and environmental review stage. This project is being managed by Charlottesville under the First Cities initiative, with technical support provided by VDOT. City Council voted 4-1 in July 2007 to approve project's fit with the city's comprehensive plan.
City Council had been expected to select one recommended alternative in December 2007. Negotiations with the state Department of Natural Resources for impacts to nearby historic sites continues. On February 19, 2008, Neighborhood Development Staff asked City Council to spend $1 million to match a VDOT revenue sharing plan. This would be put aside to pay for pedestrian and improvements, above and beyond the money from the federal government. On March 18, 2008, the steering committee overseeing the interchange designed voted 5-1-1 to select Alternative C1 as its preferred alternative. On June 4, 2008, City Council selected a modified version of Alternative G1. Design revisions are ongoing. |
||
Website | Project website | |
Contact | Angela Tucker, Development Services Manager, Charlottesville |
Map
Project details
The Meadowcreek Parkway Interchange is an element in the development of the city's portion of the Meadowcreek Parkway. Preliminary engineering work is ongoing, with the selection of a final design alternative slated for early 2008. Costs for the project range between $33 to $37 million. The majority of funding comes from an appropriation of federal funds announced in 2005. This came from an earmark from Senator John Warner (R-VA).
The City of Charlottesville is overseeing the project.
The project's stated purpose is:
- To enhance transportation mobility for local residents
- To safely accommodate projected future traffic volumes
- To accommodate and enhance pedestrian and bicycle needs in the project area
History
On February 18, 2003, City Council heard a report from NDS Director Jim Tolbert regarding an RFP that was being issued to study possible intersection designs for where the Meadowcreek Parkway would meet the Route 250 Bypass[1]
Status
In design and environmental review stage. This project is being managed by Charlottesville under the First Cities initiative, with technical support provided by VDOT. City Council voted 4-1 in July 2007 to approve project's fit with the city's comprehensive plan. On February 19, 2008, Neighborhood Development Staff asked City Council to spend $1 million to match a VDOT revenue sharing plan. This would be put aside to pay for pedestrian and improvements, above and beyond the money from the federal government.
On March 18, 2008, the Steering Committee voted to select Alternative C1 as the preferred alternative. [2]. However, City Council decided instead to select Alternative G1, a signalized intersection[3], as its designated alternative.
The project is currently undergoing the Section 106 process with a variety of federal and state agencies including the Department of Historic Resources and the Army Corps of Engineers.
Steering Committee
The project's initial development was overseen by a steering committee, appointed by the Charlottesville Mayor and City Council.
- Richard Berman, Neighborhood Representative
- Stephen Bolton, CHART
- John Conover, Rivanna Trails Foundation
- Michael Farruggio, Charlottesville Parks and Recreation Advisory Board
- Robert Hodous, Charlottesville Regional Chamber of Commerce
- John Hossack, Neighborhood Representative
- Cheri Lewis, Charlottesville Planning Commission
- Kevin Lynch, Charlottesville City Council
- Leigh B. Middleditch, Jr., Citizens Committee for City-County Cooperation
- Calvin Morris, Albemarle County Planning Commission,
- Russell Perry, Planner/Architect
Alternates: (also appointed by Mayor/City Council of Charlottesville)
- Jeffrey Wilbur, Rivanna Trails Foundation
- Robert Winstead, Planner/Architect
Project Team: Technical Support Staff to Steering Committee
- Tony Edwards, Charlottesville City Engineer
- Jeanette Janiczek, Charlottesville VDOT Program Coordinator
- Greg Krystyniak, VDOT Program Manager
- Owen Peery, RK&K Engineers Project Manager
- Leo Rutledge, VDOT Local Assistance Division
- Brent Sprinkel, VDOT Culpeper District
- Mike Svetz, Charlottesville Director of Parks & Recreation
- Angela Tucker, Charlottesville Project Manager
External links
Route 250 Interchange Project by RK&K
Notes
- ↑ Charlottesville City Council Minutes. 18 Feb. 2003. City of Charlottesville, Virginia. 24 Mar. 2009 <http://weblink.charlottesville.org/DocView.aspx?id=195906>.
- ↑ 'Oval roundabout preferred by 250 Interchange Steering Committee', Charlottesville Tomorrow, posted on March 20, 2008
- ↑ 'City Council selects signalized intersection for Meadowcreek Parkway interchange', Charlottesville Tomorrow. 5 Jun. 2008. Charlottesville Tomorrow. 2 Mar. 2009