Laserfiche WebLink
Regular Planning Commission Meeting <br />Minutes – Wednesday, February 3, 2016 <br />Page 12 <br />Member Gitzen noted his concern was whether they were consistent specific to the <br />543 <br />cancellation talked about when approved. <br />544 <br />Mr. Paschke clarified that pre-existing or old PUD’s didn’t necessarily have agreements <br />545 <br />and were approved much differently than today’s PUD’s that were typically subject to <br />546 <br />conditions, most of which would have been met. If there was a need in an existing PUD <br />547 <br />for a condition yet to be met, or still needed, Mr. Paschke stated compared to those <br />548 <br />approved today, then Mr. Paschke stated that yes, it made sense to cancel those PUD’s <br />549 <br />allowing them to function under the general zoning ordinance and no longer needing a <br />550 <br />PUD to amend if already covered in current code. However, Mr. Paschke noted that <br />551 <br />each of those would need to be reviewed independently; and the question answered <br />552 <br />whether if cancelled did it comply with today’s requirements. Mr. Paschke noted that <br />553 <br />there may be some out there better served cancelled and addressed in ways other than <br />554 <br />through a PUD. Mr. Paschke noted that staff may not consider a PUD if they don’t have <br />555 <br />conditions applied to them, or nothing binding, with zoning there forever and a day; and <br />556 <br />opined that it would clear up confusions and misconceptions. <br />557 <br />Mr. Paschke advised that staff, as well as the City Attorney, were in agreement with the <br />558 <br />cancellation language as presented. <br />559 <br />Ayes: 6 <br />560 <br />Nays: 0 <br />561 <br />Motion carried. <br />562 <br />Chair Boguszewski noted this was scheduled to go before the City Council at their <br />563 <br />February 22, 2016 meeting; and tonight’s meeting minutes would be included as part of <br />564 <br />the meeting materials as available. <br />565 <br />Chair Boguszewski again thanked Mr. Gozola for his work; and Mr. Gozola expressed <br />566 <br />his pleasure in working with the Commission as well. <br />567 <br />b. PROJECT FILE 0017, Amendment 28 <br />568 <br />Request by the Community Development Department to consider Zoning Code <br />569 <br />Text Amendments to Roseville City Code related to building materials for <br />570 <br />Chapters 1004 (Residential Districts); 1004 (Commercial and Mixed-Use Districts); <br />571 <br />1006 (Employment Districts); and 1007 (Institutional Districts) <br />572 <br />C <br />hair Boguszewski opened the public hearing for Project File 0017 at 8:14 p.m. <br />573 <br />City Planner Thomas Paschke provided a brief summary of the request as detailed in <br />574 <br />the staff report dated February 3, 2016. Mr. Paschke noted that these amendments <br />575 <br />were based on actual use and supported the use of new technologies available for <br />576 <br />concrete fiber board and its application as a new building material in residential exterior <br />577 <br />uses and the number of variances being requested allowing its use. Mr. Paschke noted <br />578 <br />that without these text amendments related to building materials as noted and detailed <br />579 <br />in the staff report, it left staff in a vulnerable position for approving materials. <br />580 <br />Discussion ensued related to the specifics of this material; material specifications (e.g. <br />581 <br />bare concrete versus stained or pre-colored treatments or raw industrial materials); and <br />582 <br />definition of exterior wall versus an interior wall serving a courtyard and referred to under <br />583 <br />code as a fence or enclosure and not part of the building’s “box.” <br />584 <br />Member Daire referenced line 155 and combination of materials for exterior wall finishes <br />585 <br />and its implications; and language deleted in Section 10502.f (line 159) removing that <br />586 <br />wording, but inconsistent with lines 171 and 183. <br />587 <br />Mr. Paschke noted this was an error in the draft, and language should have been <br />588 <br />stricken in lines 171 and 183 as well. <br />589 <br />At the request of Member Bull, Mr. Paschke clarified that the way code language was <br />590 <br />currently set up, it was not possible to use one material, but design standards required <br />591 <br />different articulations requiring a combination and providing some variety and <br />592 <br />addressing where specific materials are used in a particular design element. <br />593 <br /> <br />