Laserfiche WebLink
<br />9.6810 <br /> <br />@J <br /> <br />9.6815(2) <br /> <br />@ <br /> <br />9.6820; <br />9.80~)(b) <br /> <br />9.6870 (table) <br /> <br />@ <br /> <br />9.6885(2) <br /> <br />@ <br /> <br />9.7015 <br /> <br />(i) <br /> <br />9.7020 <br /> <br />@ <br /> <br />Requires new local streets to <br />intersect with other streets at <br />intervals of 600' or less <br /> <br />Adjustment Review regarding <br />street connectivity <br /> <br />Cul-de-sac requirements <br /> <br />Cul-de-sac design standards <br /> <br />Tree preservation plans requires <br />report from certified arborist <br /> <br />Completeness Review: <br />Timeline for response to <br />incomplete applications <br /> <br />Waiver oftimelines <br /> <br />Code does not allow flexibility <br />from the 600' standard except <br />for physical constraints. Some <br />larger subdivisions may provide <br />a thorough network of streets, <br />but have an intersection slightly <br />> 600', requiring another <br />unnecessary street. <br />Adjustment review process is <br />redundant. Street connectivity <br />is already evaluated as part of <br />land use application <br />(subdivision, partition, POO, <br />etc). Any requests for <br />exceptions can be handled <br />through the main application. <br /> <br />Language describing when a <br />cul-de-sac vs. alternative <br />designs (i.e. hammerheads) can <br />be used is confusin!!. <br />Right-of-way (ROW) and <br />paving width requirements are <br />not consistent with other <br />adopted public works standards <br />Requirement is limited to <br />certified arborists. In some <br />cases, landscape architects are <br />better equipped to look at <br />broader site design options to <br />improve tree preservation. <br />Especially relevant when tree <br />health/vitality are not key <br />factors. <br />Language is not consistent with <br />more recently adopted State <br />Statutes which puts burden on <br />the applicant to infoM city of <br />their intention to provide <br />missing information, <br />Current language implies any <br />timeline can be waived, <br />however a recently adopted <br />state statute limits time waivers <br />for land use applications. <br /> <br />Create an exception provision <br />allowing requests for <br />exceptions to the 600' standard <br />while maintaining street <br />connectivity and emergency <br />access objectives. <br /> <br />Eliminate requirement for <br />separate adjustment review and <br />instead, fold in same <br />requirements into an exception <br />process as part of the primary <br />land use application review. <br />This will consolidate aU street <br />connectivity discussion without <br />changing any actual <br />requirements. <br />Clarify circumstances in which <br />exceptions to cul-de-sac design <br />can be requested and granted. <br /> <br />Revise the table to specify <br />consistent right-of-way <br />standards for cul-de-sacs <br /> <br />Revise standard to allow <br />landscape architects as well as <br />certified arborists to provide the <br />required report. <br /> <br />Revise language to ensure <br />consistency with State Law. <br /> <br />Clarify limitation on timeline <br />waivers consistent 'with state <br />statutes (maximum of 245 <br />days). <br />