Laserfiche WebLink
The existing design policies and manuals require updating and reconciliation to <br /> eliminate inconsistencies and integrate all modes of travel regardless of jurisdiction. <br /> The main areas of potential conflict were identified between current design practices <br /> and Complete Streets: lane width, design speed and annual daily traffic threshold, level _ <br /> of service and roadway classification. <br /> Lessons Learned from Interviews <br /> The American Planning Association/National Complete Streets Coalition provided <br /> interview data (which they conducted) for five agencies. Follow-up surveys were <br /> conducted to gather more detailed information on cost/benefit and implementation of <br /> Complete Streets policies. This information was synthesized to determine the following <br /> lessons learned: <br /> • Implementation of Complete Streets is easier if all levels of government are involved <br /> and the policy is developed by stakeholders. <br /> • Complete Streets is inherent to Context Sensitive Solutions (CSS). <br /> • Complete Streets requires a flexible design process. <br /> • No benefit/cost data is available for Complete Streets policy. <br /> Benefit, Feasibility, Cost and Funding <br /> No specific benefit/cost data is available. However, a list of potential benefits and costs <br /> associated with Complete Streets was developed. <br /> Adopting a Complete Streets policy would complement Mn/DOT's existing Context <br /> Sensitive Design policv and would further reinforce its principles. Complete Streets are <br /> considered feasible on state, regional and local levels. <br /> Implementation <br /> Development and implementation of a Complete Streets process should follow a <br /> phased sequential approach: establish need (which has been done by this study); <br /> develop policy; reconcile differences in planning and design policies, guidelines and <br /> manuals; implement; and review/measure/refine. <br /> Recommendations <br /> Being one of the first states to adopt a policy requiring Context Sensitive Design and <br /> Solutions, Minnesota is already positioned to support a "Complete Streets" approach to <br /> transportation investment. In addition, Mn/DOT staff have been actively working on <br /> integrating ADA, CSS and bicycle/pedestrian principles within its agency. Three local <br /> agencies (Hennepin County and the cities of St. Paul and Rochester) in Minnesota have <br /> already adopted their own resolutions for Complete Streets, indicating that Complete <br /> Streets are achievable at a local level. <br /> Mn/DOT needs to be prepared to assist local agencies in developing their local <br /> Complete Streets approach to assist with their specific project development needs. <br /> The study's Advisory Committee identified several key recommendations: <br /> Chapter 1 Complete Streets Legislative Report <br /> Page 2 December 2009 <br />