My WebLink
|
Help
|
About
|
Sign Out
Home
2016-04-06_PC_Minutes
Roseville
>
Commissions, Watershed District and HRA
>
Planning Commission
>
Minutes
>
201x
>
2016
>
2016-04-06_PC_Minutes
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/19/2016 1:55:17 PM
Creation date
5/19/2016 1:55:15 PM
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.
/
19
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, April 6, 2016 <br />Page 16 <br />with enough flexibility and the “approximately perpendicular” language was not needed as <br />751 <br />proposed by staff. Chair Boguszewski suggested the question remained for future decision- <br />752 <br />making if all understood that “radial” differentiated from Roseville’s version of “radial.” Rather than <br />753 <br />relying on city code, Chair Boguszewski suggested that the general definition of “radial” would be <br />754 <br />more dependable for all parties. <br />755 <br />Member Murphy questioned if enough facts or sufficient information was available for the <br />756 <br />commission to act on this recommendation tonight. Member Murphy stated his preference for <br />757 <br />code definitions that were consistent and interpretable by a court or lawyer. <br />758 <br />Using that preference, Chair Boguszewski suggested language excluding “approximately,” <br />759 <br />Member Murphy expressed his interest in seeing the city code referenced by Member Bull before <br />760 <br />making a decision either way. <br />761 <br />Mr. Lloyd displayed a copy of sections of city code, both zoning and subdivision sections, noting <br />762 <br />that he found no definition of “radial” in either section. <br />763 <br />Chair Boguszewski questioned the need for “radial” if revised language includes “approximately” <br />764 <br />for either radial or perpendicular following the concept of approximation. <br />765 <br />Member Gitzen noted that “radial” applied to curves in common usage, while perpendicularity <br />766 <br />didn’t apply to a curve but only a straight line. <br />767 <br />Chair Boguszewski asked for staff’s rationale in requesting this text amendment, whether it was <br />768 <br />seeking to forestall any future confusion or contention in its application, or where it had arisen <br />769 <br />before or been an issue or created an area of disagreement. <br />770 <br />Mr. Lloyd reported that he couldn’t recall any specific issues specific to “radial,” but advised that <br />771 <br />after the Wheaton Woods project, staff was seeking to amend the text to avoid any binds with <br />772 <br />future situations or applications; and used the displayed city map to cite other examples. <br />773 <br />Given the ability to plat as shown, Chair Boguszewski opined that if “radial” was already defined <br />774 <br />in city code as referenced by Member Bull, and if and when that reference could be identified and <br />775 <br />if applicable, there would be no need to revise text to include “approximately.” <br />776 <br />Mr. Lloyd opined that in that case, any old angle would and could apply. <br />777 <br />Chair Boguszewski suggested not taking action on this request tonight, but allow the synopsis of <br />778 <br />this discussion and additional research by staff between now and the next discussion, with <br />779 <br />assistance in finding the city code reference mentioned by Member Bull, for presentation to the <br />780 <br />City Council outlining that the Commission wasn’t able to make a viable recommendation on this <br />781 <br />minor text amendment. Chair Boguszewski noted another option would be to recommend <br />782 <br />approval striking “approximately.” <br />783 <br />Member Daire questioned what was trying to be accomplished. Member Daire opined that <br />784 <br />whether or not there was a prescription for a lot size in either or both zoning or subdivision code, <br />785 <br />the idea was to be able to calculate lot area and find out whether or not complies with the <br />786 <br />minimum spelled out in code. For that reason, Member Daire suggested it may be more desirable <br />787 <br />to say something about the side lot lines being parallel to each other and as rectangular as <br />788 <br />possible. In the example used by Mr. Lloyd, Member Daire noted only one side was irregular; and <br />789 <br />the ability to calculate area was simpler if lots were rectangular in shape and side lines parallel <br />790 <br />versus radial requiring geometrical calculations. <br />791 <br />Mr. Lloyd responded by noting that the goal was not based on calculating lot area or having <br />792 <br />regular shaped lots or simplicity in reviewing particular proposals, but more about the fact that <br />793 <br />irregularly shaped lots were more difficult for people to understand boundaries. Due to the <br />794 <br />relationship of streets and homes on lots, Mr. Lloyd noted that assumptions were often made <br />795 <br />about lot lines, and when those became less predictable, it became more difficult to know <br />796 <br />intuitively where they were. Mr. Lloyd advised that the goal was to have lots regularly shaped for <br />797 <br />simplicity in that regard. <br />798 <br />Member Gitzen spoke in support of staff’s proposal to include the word “approximately,” and if no <br />799 <br />city code definition for “radial” was found, nothing would be lost or gained. <br />800 <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.