My WebLink
|
Help
|
About
|
Sign Out
Home
2017-01-04_PC_Minutes_Approved (3)
Roseville
>
Commissions, Watershed District and HRA
>
Planning Commission
>
Minutes
>
201x
>
2017
>
2017-01-04_PC_Minutes_Approved (3)
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/13/2017 3:57:58 PM
Creation date
9/13/2017 3:49:13 PM
Metadata
Fields
Template:
Commission/Committee
Commission/Authority Name
Planning Commission
Commission/Committee - Document Type
Minutes
Commission/Committee - Meeting Date
1/4/2017
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.
/
14
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
Regular Planning Commission Meeting <br />Minutes – Wednesday, January 4, 2017 <br />Page 2 <br />and planning staff pertaining to the draft public engagement plan proposed y the consultants. This 47 <br />discussion is intended to yield a recommendation to the City Council regarding how the proposed 48 <br />public engagement plan can be refined, expanded, or contracted to be as successful as possible 49 <br />in drawing robust input from Roseville’s diverse community members as the basis for updates to 50 <br />the comprehensive plan. 51 <br />Mr. Lloyd briefly reviewed last month’s discussion, and noted edits and feedback that had been 52 <br />incorporated into this draft of the spreadsheet for further discussion; and inclusion of a draft Table 53 <br />of Contents as requested by the Commission. Mr. Lloyd stated staff’s anticipation of presenting a 54 <br />revised draft plan to the City Council at their January 23, 2016 meeting based on the 55 <br />Commission’s recommendation after tonight’s expanded discussion. Mr. Lloyd noted that the draft 56 <br />Table of Contents mirrored the structure and content of the existing comprehensive plan, 57 <br />excluding the Economic Development, Public Works, and Parks & Recreation chapters that would 58 <br />not be changed essentially. Mr. Lloyd reminded commissioners that those subheadings and 59 <br />chapters would be handled through a planning process by those departments starting within the 60 <br />next few months working with specific consultants in those areas of expertise. 61 <br />Table of Contents 62 <br />Ms. Perdu briefly summarized work to-date and proposed topics with subheadings under each 63 <br />category, all subject to discussion and change at the leading of the commission. Ms. Perdu 64 <br />advised that this first draft was intended to provide an idea of the intended formatting of the plan 65 <br />per section based on commission feedback at this point, content of the plan and how it relates 66 <br />back to the ideas or vision chapter. Ms. Perdu noted, for instance, in division chapter 2 a 67 <br />decision-making rubric or guiding principles was included to project how the city made decisions 68 <br />that would be consistent with its updated comprehensive plan. In moving through the process, 69 <br />Ms. Perdu advised that she’d provide examples of that process; and over the next few meetings it 70 <br />should become obvious how this update will differ from the current plan; and as infrastructure 71 <br />elements are incorporated by the Public Works Department, with more detail to follow on that and 72 <br />related components. 73 <br />While it may be covered under “economy,” Member Bull noted that even though this is the City of 74 <br />Roseville’s comprehensive plan, how would it coalesce with other communities (e.g. Rice Street 75 <br />corridor) and when bounded by adjacent communities since what they did significantly impacted 76 <br />Roseville as well. Member Bull asked if that was covered or called out elsewhere. 77 <br />Ms. Perdu clarified that the regional context was called out in several spots, as part of 78 <br />Metropolitan Council goals as well, but not specifically addressed in the outline. As the process 79 <br />moves forward, Ms. Perdu noted that “economic development” was certainly one such area 80 <br />where external forces affect what happens in Roseville, including neighborhood character and 81 <br />impacts, housing demand, and population trend aspects in the region as well. Ms. Perdu advised 82 <br />that she would be sure to specifically call out other spots and highlight them in the next iteration. 83 <br />Member Daire asked where data would be included as to how the City of Roseville gained its 84 <br />population, whether from outside the metropolitan area or from other communities within the 85 <br />metropolitan area. 86 <br />Ms. Perdu advised that this demographic, housing and economic data would be included in the 87 <br />“community profile” chapter, with growth trends provided in context of the forecast from the 88 <br />Metropolitan Council. Ms. Perdu offered to call out that data in more detail if desired, but noted 89 <br />there would be different takes on it for several chapters (e.g. housing) including existing and 90 <br />projected needs, migration and commuting patterns and economic development considerations. 91 <br />While it will be touched on in several places, Ms. Perdu agreed it may be good to highlight it as 92 <br />well. 93 <br />At the request of Member Daire, Ms. Perdu confirmed that the Metropolitan Council had several 94 <br />tools to inform the analysis, including GIS metrics for how people live, and travel, that would 95 <br />provide that analysis of internal population circulation, specifically in the “transportation” and 96 <br />“economic development” chapters. At the further request of Member Daire, Ms. Perdu reiterated 97 <br />that the transportation section would be developed under the Public Works realm, using other 98 <br />consultants, later this spring and in conjunction with this commission and city staff. 99
The URL can be used to link to this page
Your browser does not support the video tag.