My WebLink
|
Help
|
About
|
Sign Out
Home
2011-10-25_PWETC_Minutes
Roseville
>
Commissions, Watershed District and HRA
>
Public Works Environment and Transportation Commission
>
Minutes
>
201x
>
2011
>
2011-10-25_PWETC_Minutes
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
11/28/2011 9:20:59 AM
Creation date
11/28/2011 9:20:41 AM
Metadata
Fields
Template:
Commission/Committee
Commission/Authority Name
Public Works Commission
Commission/Committee - Document Type
Minutes
Commission/Committee - Meeting Date
10/25/2011
Commission/Committee - Meeting Type
Regular
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
12
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
to promote safe neighborhoods with respect to traffic for all users of the roadway, <br /> and to alleviate conflicts between real and/or perceived traffic using the same <br /> corridor; defining the jurisdiction of roadways in the Definition Section to clarify <br /> the type of streets and to be consistent with and reference the Transportation Plan <br /> of the Comprehensive Plan (e.g. local streets, arterials, or collectors). <br /> 4.0 Procedure Summary <br /> Step 1 <br /> Ms. Bloom summarized the various steps proposed, based on staff s review of the <br /> City of Edina's TMP and the relationship to and definition of benefitted areas, <br /> project areas, and benefitted neighborhoods, and the implementation based on <br /> 51% of the neighborhood; effectiveness of an application from an individual <br /> versus a petition of more than one individual; and how to define project areas. <br /> Discussion included project areas defined as a block between cross streets; <br /> recognizing the need to define dead-end streets and/or cul-de-sacs differently as <br /> project areas; assessment area(s)for affected neighborhoods determined by staff <br /> unless there was a disagreement between staff and the neighbors on defining the <br /> project area, at which time the Public Works, Environment, and Transportation <br /> Commission would serve as the third-party appeal group to provide an unbiased <br /> resolution or if staff determines the affected area should be broadened; and <br /> preference to keep the process as simple as possible in determining the project <br /> area; clarifying the definition of the project neighborhood as the stretch of street <br /> between intersections or the entire cul-de-sac; and identifying the notice area for <br /> the entire affected area. <br /> Section 2.0 Policies <br /> Member Stenlund noted the need for consistent language for"strategies" and/or <br /> "devices." <br /> Section 3.0 Definitions <br /> Discussion included consistent identification of collector and arterial streets, with <br /> staff suggesting further internal review following staff s changing the language to <br /> "local streets," and whether the context still remained; with consensus to remove <br /> lines 5 — 16 in their entirety with the exception of the fifth sentence that was to <br /> remain intact; and intent of the processes and strategies for local streets to <br /> "improve neighborhood traffic conditions." <br /> Step 3 —Data Collection and Traffic Study (page 5) <br /> Discussion included steps to determine if a request falls under the guidelines of <br /> the internal Traffic Safety Committee or the Traffic Management Plan for initial <br /> review; the process of an engineering study, as needed, in that process; and <br /> informing the neighborhood before any application has staff time invested; <br /> affected area versus benefitted or impacted area; establishment of project <br /> boundaries; and the role of the Public Works, Environment and Transportation <br /> Commission and how/when requests are considered: annually or as they're <br /> Page 4 of 12 <br />
The URL can be used to link to this page
Your browser does not support the video tag.