Laserfiche WebLink
widening in these model runs; the mitigations are at the intersection level only.) Mitigation <br />measures significantly reduce overall delay (about 60 percent in the P.M. and 55 percent in <br />the A.M.) in Year 2010 compared to unmitigated Year 2010 conditions. Even with <br />additional mitigations, with Year 2025 regional traffic growth, delay increases by another <br />five percent in the P.M. over mitigated Year 2010 conditions. During the morning peak <br />hour, however, traffic delay is reduced by 13 percent relative to mitigated 2010 conditions <br />by the proposed Year 2025 mitigations and the regional 2025 roadway network. <br /> <br />With intersection mitigations alone, a small number of intersections continue to function at a <br />level of service worse than level-of-service D, the current General Plan standard, in the <br />Year 2025 model run. Most of these are within the Downtown, currently exempt from this <br />standard. The key unmitigated intersections not in the Downtown are Hopyard Road at the <br />1-580 off-ramp and at Owens Drive, and Sunol Boulevard at Sycamore Road. <br /> <br /> CONSTRAINED GATEWAY CONCEPT <br /> <br /> One important assumption in the Year 2025 model run which is key to future runs is the <br /> effect that congestion at major city gateways has on overall city traffic. Most gateways are <br /> fairly congested in the Year 2025 model run. This congestion impacts local drivers and <br /> limits cut-through traffic to a degree. For future traffic modeling purposes, staff intends to <br /> explore alternatives which continue to limit cut-through traffic by street design, while <br /> minimizing congestion along City streets not heavily used by through traffic. This will <br /> allow reasonable comparisons to be made and to better reflect the City's sensitivity to other <br /> traffic-related effects such as livability, noise, etc. <br /> <br /> As has been previously described, all the model runs to date have been "constrained" model <br /> runs rather than "demand" model runs. A constrained model run takes into account <br /> congestion on all routes if traffic volumes generated by the assumed land uses approach or <br /> exceed the traffic-carrying capacity of the assumed traffic network. A demand model run, <br /> on the other hand, simply places traffic where the land use/traffic assumptions would put it <br /> on a give traffic network as if adequate capacity exists everywhere. A demand model run, <br /> in essence, would show how traffic would move on an overall network if there were no <br /> congestion. However, since congestion appears to be a long-term fact of life on most <br /> regional routes which are key to Pleasanton's planning, constrained model runs have been <br /> used. These replicate actual travel behavior described earlier: peak-hour spreading and <br /> cut-through traffic. <br /> <br /> SR 05:135 <br /> Page 5 <br /> <br /> <br />