My WebLink
|
Help
|
About
|
Sign Out
Home
2017-02-01_PC_Agenda_Packet
Roseville
>
Commissions, Watershed District and HRA
>
Planning Commission
>
Agendas and Packets
>
2017 Agendas
>
2017-02-01_PC_Agenda_Packet
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
2/7/2017 8:39:12 AM
Creation date
2/7/2017 8:39:08 AM
Metadata
Fields
Template:
Commission/Committee
Commission/Authority Name
Planning Commission
Commission/Committee - Document Type
Agenda/Packet
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
25
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
wĻŭǒƌğƩtƌğƓƓźƓŭ/ƚƒƒźƭƭźƚƓaĻĻƷźƓŭ <br />aźƓǒƷĻƭΑĻķƓĻƭķğǤͲWğƓǒğƩǤЍͲЋЉЊА <br />tğŭĻЌ <br />While that process would be largely outside the context of the Planning Commission initially, Mr. <br />100 <br />Lloyd advised that direct communication and coordination with the city’s engineers would occur <br />101 <br />for their planning process that would ultimately come to the Planning Commission for information <br />102 <br />and seeking input from the planning perspective. Mr. Lloyd noted that much of that chapter may <br />103 <br />be more technical in nature, with input also given by the Public Works, Environment and <br />104 <br />Transportation Commission and the city’s professional staff. <br />105 <br />Member Daire stated his rationale in asking was the emphasis on community participation, and <br />106 <br />given the technical nature of that portion, wondered how public reaction to proposed changes or <br />107 <br />system arrangements (e.g. designation of collector and arterial streets) would be accomplished. <br />108 <br />While the Request for Proposals (RFP) has yet to be finalized for a consultant for that aspect of <br />109 <br />the comprehensive plan, Mr. Lloyd stated that staff anticipated a similar public engagement <br />110 <br />process somewhat more concentrated within that context. Mr. Lloyd advised that the city engineer <br />111 <br />or Public Works staff would probably be visiting with the Planning Commission to talk about any <br />112 <br />proposed changes, but later in the overall process. <br />113 <br />Based on his planning experience, Member Daire advised that he was thinking about the <br />114 <br />relationship between land use and transportation, thus his concern that communication between <br />115 <br />establishing land uses and anticipated traffic generation in that area needed to be involved in the <br />116 <br />process. <br />117 <br />Chair Boguszewski noted the intent for past identification and appointment of Planning <br />118 <br />Commissioners Bull, Kimble and Gitzen as liaisons to attend meaningful meetings and <br />119 <br />discussions outside this setting, but when involving anything to do with the comprehensive plan <br />120 <br />update. Chair Boguszewski noted that, even though discussions may not be land use specific, <br />121 <br />this should provide a way to raise any flags or identify whether or not additional public <br />122 <br />engagement is needed. As commission representatives participate in those other meetings, <br />123 <br />sessions or phone calls, if something was identified that needed more representation from the <br />124 <br />Planning Commission as community representatives, Chair Boguszewski advised that those <br />125 <br />members could then provide their feedback to note areas that warranted some broader <br />126 <br />engagement, at which time that feedback could be provided. As the RFP comes in, Chair <br />127 <br />Boguszewski emphasized the intent that the Planning Commission serve as the conduit for <br />128 <br />whatever involves the comprehensive plan update. <br />129 <br />Ms. Collins stated, as part of the transportation plan and when a consultant is hired, public <br />130 <br />engagement will be part of the process as well as invitations for the Planning Commission to <br />131 <br />attend and participate in those sections. Ms. Collins also noted that staff intended to have those <br />132 <br />chapters brought to the Planning Commission for review to determine if something is missing or <br />133 <br />awkwardly written before it proceeds; but overall to ensure that synergy throughout all chapters <br />134 <br />and the process itself. <br />135 <br />Chair Boguszewski emphasized that staff involves one or more of the available representatives to <br />136 <br />attend any and all meetings; whether or not staff thinks it may involve a significant revision. <br />137 <br />Given the intent for separate engagement processes for those chapters outside the land use <br />138 <br />realm, Member Bull expressed concern that there may be too many meetings for residents’ <br />139 <br />participation; suggesting that it may be better to merge those meetings instead of having two <br />140 <br />different engagement processes and public meetings. <br />141 <br />Regardless of the Community Development Department having control over those specific <br />142 <br />chapters or not, Ms. Collins assured the Commission that no matter how they were integrated into <br />143 <br />the plan, consideration of avoiding engagement fatigue would be part of the process going <br />144 <br />forward. <br />145 <br />Returning to Member Daire’s previous comment on integration of land use and infrastructure <br />146 <br />contents of the plan, Ms. Purdu noted the advantage of having the Planning Commission involved <br />147 <br />in the overall vision of the comprehensive plan and setting those priorities and goals; with all the <br />148 <br />other elements meant to be consistent with that overview. Ms. Purdu assured the commission <br />149 <br />that what it decided in the first 2-3 months of the process would serve to inform the infrastructure <br />150 <br />and all other chapters as well. <br />151 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.