Laserfiche WebLink
<br />#6 - 9.5000; Lot width definition. Testimony expressed concern that the revised detinition will allow <br />additional lots to be developed. <br /> <br />Response: The revised lot width definition attempts to address a more logical place on the lot to measure <br />the true width of a lot (midway backfrom the front property line, rather than only 10 feet back). Staff <br />does not see any correlation between this change and the potential for additional/ots. <br /> <br />#8 - 9.2160; RV sales. Testimony noted concern in allowing RV sales as a pennitted use in the C-2 <br />zone. <br /> <br />Response: Issue covered in attached e~mai/ response to Councilor Bettman. <br /> <br />#12 - 9.2171(11)(d); Outdoor display. Concern expressed that creation of adjustment review provision <br />win lead to rampant sign pollution. <br /> <br />Response: The proposed amendment addresses outdoor display rather than signs. The code currently <br />limits outdoor display to plant and garden supplies. The atnendment would allow consideration of <br />additional outdoor displays through an adjustment revievv process. Future reque..<;ts (beyond plant and <br />garden supplies) would need to submit aformalland use application, andju.stifY that their proposal is <br />consistent ~ith the intent of the commercial development standards. <br /> <br />#14 - 9.2171(15)(e), Ground floor windows/Loading Docks. Concern with proposed exemption. <br /> <br />Response: Issue covered under Council que..<;tions above. <br /> <br />#17 - 9.2450 (table), Trucking Terminals. Concern expressed about whether the current table needs to <br />be changed or whether it reflects true intent. <br /> <br />Response: This issue is partially covered in attached e-mail response to Councilor Bettman. With regard <br />to the que..\'tion of intent, it should be noted that any attempt to intentionally eliminate tnicking terminals <br />from I- 2 and I- 3 during LUCU would have involved significant discussion as such an amendment would <br />have banned thi.... use citywide. <br /> <br />#19 - 9.2741; Height limit. Testimony notes that the impact of this change should be explained for <br />public process. <br /> <br />Response: T7lis amendment clar(fies an existing provision in the Public Land (PL) zone, limiting the <br />height of buildings within 50}t. of a residential zone. The language would clarify that a building <br />straddling the 50foot line, would have to meet the reduced height limit for any portion of the building <br />within 50' ofa residential zone, but not for that portion outside of this 50/oot line. <br /> <br />#24 - 9.2761, Maximum lot size exception for natural resource protection. Concern was expressed <br />that this provision would reduce available tools for natural resource protection. <br /> <br />Response: T71e intent of this amendment is to enable greater opp011unityfor natural resource <br />preservation. Staff sees this being more applicable to smaller scale projects (such as partitions). Larger <br />projects, especially PUD 's, already have the ability to consider different options regarding lot <br />cOl!figurations. <br /> <br />#26 - 9. 775(1)~ Screening of flag lotfi. Testimony requests that the provision for screening along the <br />driveway of flag lots be added back into the code. <br /> <br />Re.~ponse: When LUCU was adopted, the Council modified the flag lot provisions, which included the <br />elimination of the screening requirement alongflag lot driveway. However, the "Purpose section" of the <br /> <br />Page 5 of7 <br />