My WebLink
|
Help
|
About
|
Sign Out
Home
Search
10-02-2017 Council Packet
LinoLakes
>
City Council
>
City Council Meeting Packets
>
1982-2020
>
2017
>
10-02-2017 Council Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/14/2018 2:23:41 PM
Creation date
3/14/2018 12:14:46 PM
Metadata
Fields
Template:
City Council
Council Document Type
Council Packet
Meeting Date
10/02/2017
Council Meeting Type
Work Session Regular
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
171
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
<br /> <br />Collecting speeds in this manner is typically done with a hand held radar unit, giving the <br />operator the discretion of whether or not to include the vehicle’s speed based on actual observed <br />free flow conditions. Only those vehicles traveling at free flow speeds are recorded and <br />evaluated. <br /> <br />This method of collecting speed data most closely matches that used to set speed limits. This <br />type of analysis was reserved for this stage in the process due to the increased cost of collecting <br />the data. <br /> <br />From the collected data, the 85th Percentile Speed and the Pace will again be determined and <br />evaluated. For a formal speed study, the City’s established threshold for a speeding problem is <br />an 85th percentile speed equal to or greater than 33 miles per hour on a street posted at 30 miles <br />per hour. If the street is deemed to have a speeding problem, the City will begin development of <br />traffic calming alternatives to address the specific situation. <br /> <br />Development / Implementation of Traffic Calming Measure(s): <br />The City’s Traffic Calming Program has defined three standard objectives. These objectives will <br />be included in all traffic calming measure alternatives in addition to any other traffic goals the <br />neighborhood residents may want Staff to consider. These objectives will provide the City staff <br />direction and a standard to measure the success of the calming measure. Staff will include the <br />residents’ suggestions in the conceptual plans wherever feasible. If alternative solutions are <br />presented, discussion of the positives and negatives of each alternative will be presented. <br /> <br />Petition No. 2: <br />Following the selection of a traffic calming measure(s), a second petition describing the <br />proposed improvement will need to be signed by residents living in the affected area. In order <br />for the improvement to proceed, 85 percent of the households in both the affected area and on the <br />affected street need to sign the petition. <br /> <br />Council Approval and Funding of Project: <br />Upon the recommendation of City staff and approval by the City Council, the traffic calming <br />device(s) will be installed. Funding allocated by the City Council will be based on the cost of <br />the traffic calming device(s). Funding sources may consist of: <br />• Inclusion in the City’s Capital Improvement Plan (CIP) <br />• Special request from the City Council <br />• Assessment process <br /> <br />Nine Month Review: <br />Following the installation of the traffic calming device(s), an evaluation will be conducted for up <br />to nine months to measure its effectiveness and to determine if the objectives were met. The <br />evaluation will be based on the following criteria: <br />• Speed data will be collected to determine if overall traffic speeds were reduced. <br />• A review of the accident history will be conducted to identify any adverse impacts the <br />traffic calming devices may have caused. By slowing traffic, eliminating conflicting <br />movements, and sharpening driver attention, installation of traffic calming devices may <br />reduce the number of accidents. <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.