My WebLink
|
Help
|
About
|
Sign Out
Home
2016-02-03_PC_Minutes
Roseville
>
Commissions, Watershed District and HRA
>
Planning Commission
>
Minutes
>
201x
>
2016
>
2016-02-03_PC_Minutes
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/11/2016 11:15:52 AM
Creation date
4/11/2016 11:15:50 AM
Metadata
Fields
Template:
Commission/Committee
Commission/Authority Name
Planning Commission
Commission/Committee - Document Type
Minutes
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
13
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, February 3, 2016 <br />Page 6 <br />Mr. Gozola suggested this proposed language made more sense to an existing PUD <br />244 <br />owner and provided a better understanding of their process. Mr. Gozola noted that the <br />245 <br />open houses would still be a component of the final plat. <br />246 <br />Specific to the requirements of graphic scale (line 238) as a land surveyor, <br />247 <br />Member Gitzen asked that language be changed to “north arrow” rather than “true <br />248 <br />north arrow;” with that request duly noted by Mr. Gozola. <br />249 <br />Member Daire noted that this language appears to mandate two open houses: one <br />250 <br />related to the sketch plan and one related to the concept plan for a PUD. When calling <br />251 <br />for developer open houses, Member Daire noted that intent was to have the process be <br />252 <br />as open and transparent as possible in describing what was going on, with notifications <br />253 <br />sent out to properties within 500’ of the project two times. <br />254 <br />While this is not currently done, Mr. Paschke clarified that it is being considered; with the <br />255 <br />current process of staff providing an Excel spreadsheet to the developer from the City’s <br />256 <br />database allowing the developer to draft a mailing list of labels to meet their requirement <br />257 <br />to send out a specific notification, currently followed for any open house. <br />258 <br />Since it would require no additional work for city staff, Member Daire contended that due <br />259 <br />to the two separate steps, an open house for the plan review process be included. <br />260 <br />Since the developer would already be receiving a mailing list for those deemed to be <br />261 <br />within 500’ of their property, Member Daire opined that he considered it inconsequential <br />262 <br />that the developer/owner be mandated to send a second notice to those same property <br />263 <br />owners within that 500’ radii using the initial list they received, specifying in bold print <br />264 <br />that this was a sketch plan and describing its intent, as well as the second review for the <br />265 <br />concept plan and describing that intent. While the open houses may seem redundant, <br />266 <br />Member Daire opined that it accomplishes the city’s purpose for transparency, and <br />267 <br />describing all changes up to that point. Member Daire reiterated his preference that the <br />268 <br />developer be mandated to mail both times to those within 500’, even while recognizing <br />269 <br />that the City of Roseville goes beyond the state law requirement of a 350’ notice radius. <br />270 <br />However, Member Daire further opined that he didn’t think this was asking too much of a <br />271 <br />developer to make that effort. <br />272 <br />At the request of Mr. Paschke, Member Daire clarified that his intent was to further <br />273 <br />revise the language, referencing Section 1102.01.B for the open house process, to <br />274 <br />require notification for the sketch plan and again for the concept plan. <br />275 <br />Mr. Paschke noted that this was the intent of the proposed language, with the first open <br />276 <br />house specific to the sketch plan and providing notice to properties within 500’ and to <br />277 <br />repeat that process for the concept plan. Mr. Paschke noted that staff reviews the <br />278 <br />content and information proposed by the developer for both mailings. <br />279 <br />Member Daire sought clarification as to whether the developer/owner was required to <br />280 <br />provide a summary of both meetings to staff. <br />281 <br />Mr. Paschke responded affirmatively, along with providing a summary to those attending <br />282 <br />the meeting as well to ensure that summary is consistent with the recollection of those in <br />283 <br />attendance and assuring them that their issues/concerns had been raised at the sketch <br />284 <br />plan stage. Therefore, Mr. Paschke noted that it was his understanding that as the <br />285 <br />proposal moved toward to the concept stage (e.g. hard documents) those issues were <br />286 <br />documented and had been addressed. <br />287 <br />Mr. Gozola referenced the written summary requirements as a mandatory part of the <br />288 <br />application itself (line 231). <br />289 <br />As confirmed by Mr. Paschke, Chair Boguszewski noted that the aforementioned and <br />290 <br />ongoing work of the joint notification task force, if ultimately approved by the CEC, <br />291 <br />Planning Commission and City Council, would apply to this as well. As an example, if <br />292 <br />the notification area changed, Chair Boguszewski noted it would also apply to this <br />293 <br />ordinance; with Mr. Paschke again confirming that supposition. <br />294 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.