Laserfiche WebLink
language in the adapted plans described above, <br />The secondary access requirement, which is essentially a modification to the current <br />requirement in the PUD ordi:na.nce and also applying it to subdivisions, has relevance to Land <br />Use Policy 5 in TransPlan: <br />Muaimize the adverse impact of the automobile on local residential streets through the <br />selective use of alternative street designs and application of traffic management <br />techniques. Page 4.} <br />This policy includes several implementation strategies, such as traffic diverters and providing <br />far adequate arterial and collector streets. The proposal here to require secondary access <br />addresses this policy at the initial street planning stage. It is intended to disperse traffic onto <br />more than just one local street when larger developments are proposed. Additionally, it <br />looks at the overall use of a local street in the aggregate, so if a development proposal <br />increases the use of a local street beyond 191ots, and that local street is the only means of <br />ingress and egress ~i. e. , it is the only way in and the only way out}, then access to another <br />street is required when feasible. If access to a development is from a collector or arterial <br />street, then this requirement is nat applicable. <br />Conclusion <br />The City Council finds that, based on the above findings, the residential code amendments <br />are consistent with adopted plans, policies, and standards. _ <br />