New Search
My WebLink
|
Help
|
About
|
Sign Out
New Search
Highway 126 Conditions Report 2001
COE
>
PW
>
Admin
>
Execs
>
Executive non-confidential
>
Historical
>
Highway 126 Conditions Report 2001
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/21/2009 10:42:18 AM
Creation date
6/1/2009 12:19:10 PM
Metadata
Fields
Template:
PW_Exec
PW_Division_Exec
Administration
PWA_Project_Area
ODOT
PW_Subject
HWY 126
Document_Date
1/1/2001
External_View
No
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
38
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
OR 126WFLQRENCE-EUGENE HIGHWAY CONDITIONS REPORT - 2001 <br />report lies in its pinpointing the geometric, operational, and safety <br />deficiencies that are likely to occur if there is no investment in 126W, <br />or the modes or services that use 126W, beyond those currently planned <br />and programmed. Using the information in this report, ODOT and local <br />partners will be able to define critical problems, analyze alternative <br />improvement concepts, and develop recommended long-term solutions <br />to the problems created by the deficiencies in the 126W corridor. <br />TABLE OF CONTENTS <br />PREFACE <br />ACKNOWLEDGMENTS <br /> <br />126W is important because it is the main transportation facility between <br />the state's second largest city (Eugene) and all points west of Eugene. <br />Figure 2 shows how 126W serves all of western Lane County. <br />126W also connects I-5 and the entire southern end of the <br />Willamette Valley to the coast and coastal communities. <br />When it was constructed, the mostly two-lane rural highway was not <br />envisioned to be carrying the volumes currently forecast for the corridor <br />in the future. Little concern existed about future access needs and <br />various intersection and passing lane configurations were used. <br />December2002 <br />ES-3 <br />EXECUTIVE SUMMARY <br />USER'S GUIDE <br />APPENDICES <br />0 <br />PAGE <br />O <br />VERSION 1.0 <br />
The URL can be used to link to this page
Your browser does not support the video tag.