Laserfiche WebLink
Planning Commission Meeting <br />Minutes -Wednesday, October 03, 2007 <br />Page 3 <br />an applicant needed to meet a set of twelve (12) criteria for consideration, including <br />whether or not the applicant created the hardship; and staff's ability to discern setback <br />variance requests and their appropriateness, with applicants usually following the <br />advice of staff and revising their requests prior to proceeding through an informal or <br />formal process (i.e., Development Review Committee recommendations). <br />Commissioner Gottfried opined that a good portion of the current rules and regulations <br />would self-regulate the lots, with variances considered on a case by case basis, and <br />were relatively few in perspective to the total number of lots. Commissioner Gottfried <br />further opined that creating an entire set of rules specific to the SFROD was <br />cumbersome; and expressed confidence in staff's ability to monitor applications; and <br />the market place to dictate the rules. <br />Ms. Radel clarified that non-conforming lots within the district were approximately 100; <br />however, that there were a much greater number of lots that would be impacted. <br />Chair Bakeman recognized that height was a topic of much Study Group discussion, <br />but expressed her willingness to leave the height as currently indicated. <br />Commissioner Doherty complimented staff on the wonderful rendering of the small <br />lots on the map; with Ms. Radel advising that she would pass on Commission <br />comments to GIS Technician Joel Koepp, for his development of the mapping <br />Chair Bakeman thanked staff for pursuing the modifications, upon City Council <br />direction; opining it made the many hours spent by the Study Group worthwhile. <br />Commissioner Boerigter opined that the modifications directed for revision to-date by <br />the City Council were only the fringe issues at the lot split study issue; and the meat of <br />the issue are those items needing substantial policy discussions by the City Council to <br />allow for implementation. <br />Staff was requested to include footnotes as applicable to assist novice readers of the <br />code, including various charts for consistency; to create a separate section for the <br />overlay district; define "overlay district;" incorporate typographical corrections as <br />verbally noted throughout review; to add a column to the Chart of uses in Section <br />1004.015 for SFROD to be consistent with and avoid confusion with headings on the <br />next chart; define "SFROD" in the beginning, including the abbreviation of such; define <br />"Riparian Lot" (adjacent to water) in shoreland districts; define or clarify "lot" or "lot line <br />front" for corner lot dimensions, consistent with the definition of "yard;" further <br />clarification of how staff defines the front lot line as the shortest of the two dimensions; <br />consider whether language related to lot line front and rear was necessary; and to <br />bring a refined document to the Commission for further review prior to finalization and <br />recommendation to the City Council. <br />Commissioner Wozniak asked for a timeline from staff on those elements related to <br />environmental protection and sustainability, and the review of the overall zoning code. <br />Mr. Paschke advised that part of Interim Community Director Mike barrow's charge <br />from the City Manager and part of his contract, was for his review of and <br />recommendation to the City Council flags and earmarks for areas of the code where <br />environmental issues could be incorporated. Mr. Paschke advised that he would <br />consult with Mr. Darrow and provide a more definitive response at the November <br />Planning Commission meeting. <br />Concluding discussion included possible language revisions to the preamble or <br />purpose statement; with Commission consensus that the existing language, as <br />adopted, was crafted after substantial discussion and refinement; and would be better <br />left without additional tweaking at this stage. <br />