~_ <br />C. Update Future Trip Generation and Attraction Data <br />Update design year employment and dwelling unit information for the <br />zones in the Ferry Street Bridge area. (As with task B, a parallel <br />effort for the remainder of the metropolitan area will be accomplished <br />under the work activit~ies included in L-COG's Unified Planning Work <br />Program.) The Metropolitan Plan's population and employment assumptions <br />_. (plus some additional empl.oyment at the Special Light.Industrial sites) <br />are currently used in the'TransPlan model. At leas.t some adjustments <br />should be considered for the Riverfront area and downtown Eugene since <br />development now expected may differ from that assumed for TransPlan. <br />The data prepared for CATS should provide a starting point. The "new <br />Metropolitan Plan" forecasts could be used and a couple alternative <br />development scenarios could also be tested. <br />D. Peak Hour Model <br />Develop a peak hour model as a replacement to or supplement of the <br />existing 24-hour model. In discussions with Eugene staff and the proj- <br />ect's traffic consultant, it was determined a peak hour model would be <br />extreme]y useful for the Ferry Street Bridge analysis. A peak hour <br />model is thougfit to be more useful for pro;ject specific analysis than <br />the existing 24-hour model. The biggest advantage of a peak hour model <br />is that it would directly provide design hour volumes for the Ferry <br />Street Bridge ana_lysis. A peak hour model would give us the option of <br />using some of the UTPS features, such as capac.ity restraint, which are <br />not available or not useful with the 24-hour model. The main tasks <br />required of L-COG staff would be development of new trip production and <br />attraction equations and calibration to existing ground counts through <br />link speed adjustments. A major effort might be required of Eugene, <br />Springfield and Lane County staff to furnish valid peak hour ground <br />counts. Ideally, peak hour counts would be taken on all links. By <br />developing peak hour factors, counts at selected.locations could be used <br />to convert recent 24-hour counts to peak hour counts at other locations. <br />E. Model Runs and Forecasting of Volumes <br />Running of the model can be divided into two categories: "regional" and <br />"site-specific." Although there would be little difference in the <br />actual computer use, the coding and analysis would be different. <br />Regional modeling would provide the traffic volume forecasts to evaluate <br />major alternatives includi'ng: testing of a Valley River Bridge, testing <br />of I-5 ramps and interchanges, testing of some new locations for an <br />additional bridge, and testing of improvements in the existing Ferry <br />Street Bridge corridor. Because a variety of possibilities were evalu- <br />ated during develop,ment of TransPlan, relatively few test networks would <br />be required for the regional modeling phase. <br />Site-specific modeling would focus on tests of differing ramp configura- <br />tions and access alignments for both the south and north ends of the <br />primary alternative developed in the regional modeling phase. Because <br />of the number of alternati.ve configu"rations available, considerably more <br />work would be devoted to this phase than the regional modeling phase. <br />