My WebLink
|
Help
|
About
|
Sign Out
Home
Agenda - Public Works Committee - 04/21/2009
Ramsey
>
Public
>
Agendas
>
Public Works Committee
>
2000 - 2009
>
2009
>
Agenda - Public Works Committee - 04/21/2009
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/14/2025 9:33:06 AM
Creation date
4/17/2009 7:33:05 AM
Metadata
Fields
Template:
Meetings
Meeting Document Type
Agenda
Meeting Type
Public Works Committee
Document Date
04/21/2009
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
90
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 />3.0 REFINING OEFINITIONS FOUND IN SPEED LIMIT STATurES <br />, ' <br /> <br />Detinitions relative to speed Hmits, as well as to other traffic regulations, are found in Minnesota <br />Statute169.01DEFINITIONS, As part of the Task Force work, all applicable definitions were <br />reviewed. Where the need for clarification or improvement was noted, the committee worked to <br />develop revised definitions. Presented below are three definitions which were studied in detail; <br />changes were recommended for all three of them. <br /> <br />,3.1 Urban District <br /> <br />3.1.1 Urban District Discussion <br /> <br />The task force studied the definition that is used for "Urban District.1I In Minnesota <br />statute the Urban District definition is based exactly on the definition as expressed in <br />the UniformVehicle Code (UVC). This definition has been in use in the uve since <br />1934 and is used by many other states besides Minnesota. Those factors provided a <br />baseline level of support for its use. <br /> <br />The task force identified deficiencies in the definition as detailed below, but did not <br />believe that these deficiencies detracted sufficiently from the definition to warrant its <br />being substantially changed. <br /> <br />The identified possible deficiencies included the following: <br /> <br />. Although the general concept of an "Urban District" is understandable, the <br />wording in the definition is vague. <br />. The definition may be considered outdated for current development patterns. <br />. The definition relies on spacing between stnlctures for defining the distance; <br />there are no distinctions madefor other factors which influence the safety) <br />throughput and safe travel speed of a road (e.g., width of road or boulevard, <br />frequency of driveways or cross streets, number of lanes, access control, <br />parking, road curvature and alignment, etc.). <br />. Similarly, the. definition does not address other area conditions that can <br />influence the perception of appropriate speed (e. g., nearby large commercial <br />development, setback of buildings, pedestrian activity and pedestrian paths). <br />. The definition does not make a distinction relative to a roadway function or <br />surrounding land use (e.g., residentiaLor business). <br />. The use oithe word "street" within the definition (rather than "street or <br />highway") causes confusion amOl'1gst agencies over which roadways are <br />covered by this definition (e.g., are "highways" covered?) <br /> <br />Regarding the lack of distinction regarding the surrounding land use, the Task Force <br />explored the possibility of creating two classifications within the urban category (e.g., <br />an IIUrban Business Roadway" and an "Urban Residential Roadway"). However, <br />after considerable discussion within the Task Force, it was determined that a <br />substantial change in the "Urban District" application may be difficult for drivers to <br />understal1d. Drivers can clearly understand when they are operating in an Urban <br />District; howevel', it may be difficult to notice the change from an Urban Business <br /> <br />Page 13 <br /> <br />40 <br />
The URL can be used to link to this page
Your browser does not support the video tag.