My WebLink
|
Help
|
About
|
Sign Out
Home
2019_01-22_PWETCpacket
Roseville
>
Commissions, Watershed District and HRA
>
Public Works Environment and Transportation Commission
>
Agendas and Packets
>
201x
>
2019
>
2019_01-22_PWETCpacket
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
2/1/2019 2:04:30 PM
Creation date
2/1/2019 1:56:27 PM
Metadata
Fields
Template:
Commission/Committee
Commission/Authority Name
Public Works Commission
Commission/Committee - Document Type
Agenda/Packet
Commission/Committee - Meeting Date
1/22/2019
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.
/
136
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
173 that this came out of Hennepin County this might be one of those opportunities to <br />174 leave bottom up. She did not see that kind of thing reflected in the checklist. Unless <br />175 she was missing it, it looks like there is a section about streetscape/landscape but <br />176 there is nothing really specified in there within the checklist. She thought this <br />177 would be the opportunity to put the green component into this. It seems like if the <br />178 Commission is looking for some specific reference to vegetation or green corridors <br />179 or that sort of thing this is the place to add it. <br />180 <br />181 Mr. Freihammer stated it is referenced under the proposed corridor checklist. There <br />182 is a list of components not including bike and bus features which are noted later. <br />183 Under the existing checklist there is not any documentation of what is existing. <br />184 <br />185 Member Misra stated she is looking at the proposed checklist and even under the <br />186 list of components, intersection components where boxes can be checked to specify <br />187 if the items were looked at, is what she was looking at and wondered if staff could <br />188 add some boxes with some specifi mmendations. She\areat <br />ms like the <br />189 checklist kind of encourages. <br />190 <br />191 Mr. Culver suggested ex nding the greenscape/landscapee boxes in <br />192the checklist for items s as native landscaping, pollinators, etc. <br />193 <br />194 Member Misra indicated that is what she was looking for. <br />195 <br />196 Chair Cihacek asked if this has been read against the Pathway Master Plan or other <br />197 documents to make sure there is no conflict or that these are self-reinforcing. <br />198 <br />199 Mr. Culver thought it reinforces the Pathway Master Plan which has a much more <br />200 specific goal as far as completing specific segments in certain areas and providing <br />201ttreet, <br />reference list. He stated this document says anytime the City is working on a <br />202 whether it is on the Pathway Master Plan or not, anytime a street project is <br />203d at, these are the elements that should be considered. He thought this was <br />204imentary and the Pathway Master Plan was more focused and specific. <br />205 <br />206 Member Kruse asked if Mr. Culver expected this to change things much going <br />207 forward or is this more a formalization of things staff is already doing. <br />208 <br />209 Mr. Freihammer ed it does help to document what is out there and does <br />210 formalize the pr ess, so nothing is missed when being reviewed. <br />211 <br />212 Member Wozniak arrived at the meeting at 7:10 p.m. <br />213 <br />214 Mr. Culver stated the City has always designed the streets for all users, in his <br />215 opinion, but he thought this formalizes staff s thought process to ensure nothing is <br />216 being missed. <br />217 <br />Page 5 of 10 <br />
The URL can be used to link to this page
Your browser does not support the video tag.