My WebLink
|
Help
|
About
|
Sign Out
Home
2013_10_02_PC_Minutes
Roseville
>
Commissions, Watershed District and HRA
>
Planning Commission
>
Minutes
>
201x
>
2013
>
2013_10_02_PC_Minutes
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/21/2014 11:31:27 AM
Creation date
10/21/2014 11:31:26 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.
/
9
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, October 2, 2013 <br />Page 8 <br />Commission, and applicants to determine what would work best and which type of fence or <br />349 <br />screening would best fit a specific application. <br />350 <br />Based on that continued staff involvement in determining height, Member Daire questioned if that <br />351 <br />should be made a part of the motion. <br />352 <br />Mr. Paschke opined that it wasn’t necessary, as most staff review and implementations were <br />353 <br />enforced by staff and it would remain up to staff to advise applicants on how best to achieve code <br />354 <br />compliance based on their particular situation, without explicitly stating it. <br />355 <br />Member Stellmach spoke in general support of the request, including the upcoming section on <br />356 <br />written support. However, Member Stellmach expressed ongoing concerns with the recourse for <br />357 <br />future owners; even though he was somewhat comforted by the fact that future owners could <br />358 <br />learn about this situation in their review of real estate records. Overall, Member Stellmach <br />359 <br />advised that he would support the request. <br />360 <br />Member Cunningham offered her support as well; and expressed her appreciation of the <br />361 <br />clarification that staff would continue to work with applicants; and opined that she did not need <br />362 <br />that language as part of the motion to lend her support of it. <br />363 <br />Based on staff’s report and tonight’s discussion and explanations, Member Keynan spoke in <br />364 <br />support of the motion. <br />365 <br />Member Murphy, admitting to some reservation about eh 100’ being too narrow and somewhat <br />366 <br />arbitrary, offered a suggested language change of 200’ as an option if a Variance process was <br />367 <br />not the only option open to an applicant. <br />368 <br />Mr. Paschke responded that determining whether or not to expand the distance area may be <br />369 <br />considered, any number may be perceived as arbitrary with existing performance standards and <br />370 <br />nuisance codes. Mr. Paschke further stated that the Variance process option came into play only <br />371 <br />if an applicant couldn’t get appropriate sign-off from those within the distance requirement; <br />372 <br />opining that he was unaware of how much or who else may be impacted from that standpoint. Mr. <br />373 <br />Paschke clarified that he was not aware of whether or not the initial 100’ distance was really tied <br />374 <br />to noise or barking; noting that there were many noises in a neighborhood, and questioned <br />375 <br />whether or not a distance requirement had anything to do with a particular use or not beyond <br />376 <br />providing some separation from a residential property. Based on that intent, Mr. Paschke opined <br />377 <br />that the 100’ seemed appropriate, and questioned if 150’ or 200’ would be any more appropriate; <br />378 <br />and if the number was changed to 200’, then the applicant could simply seek a Variance to that <br />379 <br />section of code as an alternative. <br />380 <br />Member Murphy clarified that he wasn’t so much concerned with this application as it was within <br />381 <br />a CB District and dovetailed into that future use well. However, Member Murphy advised that he <br />382 <br />was concerned with its impact with future applications. <br />383 <br />At the request of Vice Chair Boguszewski, Mr. Lloyd clarified that code language takes specific <br />384 <br />note of property lines versus building locations on a property. <br />385 <br />MOTION <br />386 <br />Member Cunningham moved, seconded by Member Stellmach to recommend to the City <br />387 <br />Council APPROVAL of a proposed ZONING TEXT CHANGE; based on the comments and <br />388 <br />findings of Sections 4, 6 and 7, and the recommendation and conditions of Section 8 of the <br />389 <br />staff report dated October 2, 2013; <br />specifically amending Section 1009.02 Conditional <br />390 <br />Uses; D. Specific Standards and Criteria: 1.a to read: <br />391 <br />“Outdoor dog runs or exercise areas shall be located at least 100’ from a residentially <br />392 <br />zoned property or property in residential use \[or shall have the written support of all <br />393 <br />owners of such properties within 100\].” <br />394 <br />Ayes: 5 <br />395 <br />Nays: 1 (Boguszewski) <br />396 <br />Motion carried. <br />397 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.