My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
1999_Resolutions
Charlottesville
>
City Council
>
Ords Res App
>
Resolutions 1976-2009
>
1999_Resolutions
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
11/22/2024 4:11:13 PM
Creation date
3/30/2015 2:47:14 PM
Metadata
Fields
Template:
City Attorney
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
116
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
• 2. Number of Lanes. Council requests that two (2) primary (north -south) motor vehicle travel lanes, <br />rather than four (4), be constructed (between the 250 By-pass and Rio Road). The footprint for the <br />Parkway acquisition must have a centerline, curves, and size to match approximately the "study <br />alignment" referred to in the Rieley Report as 4 -Lane Divided (4-D), pp. 4-5. If and when a future <br />City Council were to approve an additional two lanes, new primary travel lanes could then be <br />constructed with a minimum of disruption to the Park, its landscape, and greenery and at lower costs <br />for the State and the City. <br />3. Sufficient Rieht-of-Way for Four (4) Lanes. Right of way for four (4) lanes of motor vehicle <br />travel should be acquired at the outset as part of the current project. <br />4. The Intersection at Route 250. Proper design of this intersection is critical if this project is to <br />succeed without considerable damage to the Park. In our opinion, any final design has to include <br />a tightly drawn intersection with a relatively small footprint. The initial VDOT design is far too <br />large. We believe that the total number of lanes created by the intersection should not exceed <br />seventeen (17). <br />Access for pedestrians and bicycle travel to McIntire Park through and around the proposed <br />intersection from the south and east also must be accommodated at grade in an effective manner for <br />the intersection to work as we desire. <br />5. Bicycle and Pedestrian Travel. Council endorses the construction of dedicated "on road" bicycle <br />• lanes on each side of the Parkway's north -south travel lanes to serve high speed cyclists. In addition <br />and in accord with the Metropolitan Planning Organization (the MPO ) recommendation, Council <br />also supports construction of a shared pedestrian/bicycle path much like the one proposed by the <br />VDOT design, but eight rather than five feet in width. <br />6. A New Lake or Pond for the Park. Combination of the storm water management facilities into one <br />pond or "lake", as in the Rieley report, makes sense to all of us. The City will do everything within <br />reason to expand this concept in cooperation with VDOT. Everyone will benefit, park and outdoors <br />enthusiasts, and motorists using the Parkway. <br />7. Additional Park Land. The City respectfully requests that VDOT acquire and donate to the City <br />and County, as part of this project opportunity, the greatest amount of additional land as is possible <br />north and south of Melbourne Road. Our objectives are several. These include replacing any park <br />land losses resulting from this project, enhancing and expanding the northern and eastern sides of <br />McIntire Park, and joining with the County in seeing that park land north of Melbourne, through a <br />linear park or otherwise, becomes a reality before acquisition of additional land in that location <br />becomes occupied or too expensive. These acquisitions should be made easier through VDOT's use <br />of money saved from the City's requested design changes, including those seeking a reduced design <br />speed, two rather than four lanes, and combination of the storm water detention facilities. <br />0 <br />2 <br />
The URL can be used to link to this page
Your browser does not support the video tag.