Laserfiche WebLink
to improve the public way for broader goals of <br />mobility, connectivity, and accessibility. The <br />exception to this is for comprehensive master <br />planned developments where the developer <br />proposes a system of streets internal to the <br />development as part of the site concept as a <br />whole and will ultimately be dedicating those <br />to the community as public streets. These <br />types of developments commonly take the <br />form of a planned unit development (PUD), <br />TND, TOD, or occur within a form -based <br />regulating plan area. In these cases, zoning <br />language regulates street design within the <br />confines of the development area and may <br />require that design facilitate connections to <br />transportation networks off -site. The challenge <br />with such design provisions is to effectively <br />achieve synergies between the internal circu- <br />lation elements within that defined area and a <br />system of complete streets on the connected <br />and surrounding public roadway system. <br />Private development does have an impact, not <br />only on traffic volumes on public streets but <br />on access to the full range of modes by which <br />people travel. If zoning is intended to manage <br />private development in pursuit of implement- <br />ing community -wide goals, including those for <br />complete streets, then those elements should <br />be part of any regulations package. <br />INCORPORATING CS PROVISIONS INTO <br />DEVELOPMENT REGULATIONS <br />Just as a community's comprehensive plan es- <br />tablishes a legal standing for zoning, provisions <br />for completing the streets are most sound when <br />associated with a documented community - <br />wide complete streets policy encompassing all <br />public ways. Any language requiring complete <br />streets elements in zoning or subdivision <br />regulations should be cross - referenced with a <br />broader transportation policy. Where a com- <br />munity adopts not only a CS policy but a well - <br />detailed design- guidance manual, then that <br />can serve as a basis for comparable design <br />language in the regulations. <br />In New Haven, along with the adoption <br />of the city's CS complete streets policy and <br />design manual into the code of ordinances, <br />the zoning regulations were updated to <br />include more comprehensive requirements <br />for bicycle and pedestrian access internal to <br />a development. Similarly, Charlotte, North <br />Carolina, adopted an Urban Street Design <br />Guidelines Policy Summary in zoo7. The <br />city subsequently added a subdivision ordi- <br />nance amendment requiring all new streets <br />in proposed subdivisions to meet those <br />urban street design guidelines and adopted <br />® Visualizing a complete street for downtown Norwalk, Connecticut. <br />zoning language to require connectivity as <br />part of its six distinct TOD overlay zones. The <br />TOD regulations have the following guiding <br />statement of intent: "Transit oriented devel- <br />opment uses shall be integrated with the <br />surrounding community, easily accessible, <br />and have a good internal circulation system <br />for a variety of travel modes." This state- <br />ment of intent is followed by specific stan- <br />dards addressing the location and design <br />of sidewalks, streetscapes, bicycle parking, <br />urban open spaces, access /entrances, and <br />consistency with station -area plans as well <br />as other site features ( §9.12o1- 1213). <br />It is worth noting that communities can <br />take two overall approaches to incorporating <br />CS principles into development regulations: <br />as guidelines and as requirements. Each <br />approach has its place. While requiring <br />features such as sidewalks and bicycle <br />parking guarantees inclusion on a site plan, <br />the drawback is that requirements tend to <br />be rigid and need qualification. Conversely, <br />street elements phrased as guidelines can <br />leave their application open to interpreta- <br />tion, and it may be more challenging for a <br />planning or zoning commission to get what <br />they deem best for a site. In both cases, <br />carefully drawn graphics depicting the <br />desired design are extremely beneficial to <br />making the regulations' intent clear. <br />Complete streets, by their very nature, <br />are context sensitive. For example, it is not <br />uncommon for an urban site within a TOD <br />district to be essentially landlocked, with <br />limited connectivity to existing public streets <br />and where design flexibility for the interface <br />with that street is desirable. Flexibility in <br />design, written as guidelines as opposed to <br />requirements, gives the zoning commission <br />and developer room to negotiate the most <br />effective means to ensure access by many <br />modes in the specific context of the site. <br />CRAFTING REGULATORY AMENDMENTS FOR <br />COMPLETE STREETS: TWO METHODS <br />There are many communities that have <br />adopted zoning and subdivision provisions <br />requiring individual CS elements such as <br />sidewalks and bicycle parking as part of <br />design for new developments. Many have <br />also taken a fresh look at their parking regu- <br />lations as a means to consider better accom- <br />modations for pedestrians and bicyclists. <br />Consequently, communities commonly have <br />incorporated language regarding mobility <br />ZONINGPRACTICE 2.13 <br />AMERICAN PLANNING ASSOCIATION (pages <br />