Laserfiche WebLink
2.0 Policies <br />1 <br />2 <br />The Neighborhood Traffic Management Program will be governed by the following policies: <br />3 <br />Identified projects will be evaluated for compatibility with transportation goals in the <br />4 <br />RosevilleComprehensive Plan, Chapter 5, Transportation. <br />5 <br />Implementationislimited to local streets. A local street is a street under the jurisdiction <br />6 <br />of the City of Roseville. <br />7 <br />Strategies will be funded by a combination of city funds andneighborhood participation. <br />8 <br />Asystem-wide approachfor neighborhoodtraffic problemswill be used.For each <br />9 <br />project, city staff will determine a logical project boundary. This isnecessary for the <br />10 <br />approval process and will help ensure that the issue ofdisplacement/diversion to other <br />11 <br />local streetsis addressed. <br />12 <br />Projectswill be limited to those local streets where the 85%speed exceeds5 mph <br />13 <br />above the posted speed limitor where there are other existing factors affecting the <br />14 <br />livability of the neighborhood.Table 1 describes otherfactorsthat can betaken into <br />15 <br />consideration. <br />16 <br />Implementation of traffic management strategies will be in accordance with the <br />17 <br />proceduresset forth in this document, and in keeping with sound engineering practices, <br />18 <br />as well as bewithin the city's available financial and staff resources. <br />19 <br />A project on a Municipal State Aid (MSA) road will meet MSA design standards. <br />20 <br />Trucks are allowed on all localstreets unless otherwise posted (by State law trucks must <br />21 <br />be allowed on all Municipal State Aid Roads.) <br />22 <br />Implementation of any device will be consistent with the guidelines in the Minnesota <br />23 <br />Manual on UniformTraffic Control Devices. <br />24 <br />Implementation of strategies shall be consistent with recommended strategies included <br />25 <br />in the Mn/DOT Safety Handbook. <br />26 <br />Initial deployments are considered temporary for study purposesand subject to an <br />27 <br />interim review by Citystaff prior to permanent installation. <br />3.0 Traffic Management Background <br />28 <br />29 <br />The United States has used street closures and traffic diverters dating back to the late 1940s <br />30 <br />andearly 1950s, but it was not until the 1970s that Seattle, Washington completed area-wide <br />31 <br />demonstrations of traffic management strategies. Since then, traffic management has been <br />32 <br />continually studied and implemented throughout the United States. Strategies include street <br />33 <br />closures, traffic diverters, speed humps/bumps, signing, increased enforcement and many <br />34 <br />others, but they all are implemented to accomplish one of the following: <br />35 <br />Modify driver behavior (reduce speed) <br />36 <br />Modify traffic characteristics (reduce volume) <br />37 <br />Improve safety for pedestrian and bicyclists <br />38 <br />Traffic management can be simplified as athree step process: (1) identify the nature and extent <br />39 <br />ofexisting traffic-related problems on a given street or area (2) select and implement the proper <br />40 <br />strategy for reducing the identified problemand (3) evaluate effectiveness, accept, modify or <br />3 City Council Review Draft- 4/06/12 <br /> <br />