Laserfiche WebLink
<br />March 4. 2008 <br /> <br />Memo to Planning & Zoning Commission: <br /> <br />From: Dallas Larson. Administrator <br /> <br />1 believe that P&Z has substantially addressed items 1-6. We should confIrm that you are <br />satisfIed with the proposed resolution. then continue to resolve the items 7-16 <br /> <br />I) Modified 154.023 Site plan review process. I suggest removing the 30 day <br />requirement in (A). Also, the number of copies to submit should change. We do not <br />need sixteen copies. We are bener off with a much smaller number of paper copies <br />in addition to electronic versions. <br />2) Included. 154.110 Fence side setback. A number of people have objected to the <br />requirement to place a fence two feet from the property line where they cannot get <br />the adjoining property owner to agree to a boundary line fence. We hear: ''this is a <br />waste of two feet of my property." <br />3) Modified 10 aI/ow decorative fences only in ell front yards. 154.110 Fences in front <br />yards of commercial and industrial uses. Current rules allow 8 foot fences in front <br />yards of commercial-industrial uses. Do you really intend to allow this? <br />4) Modified language provided. 154.110 Fences in front of residential structures. We <br />may want to refer to front yard rather than front of building. This would clearly <br />indicate that the corner lots may not have a privacy fence in either front side. If this <br />is too restrictive, you may want to limit the long corner side to one-half of the <br />distance from the principal structure to the front property line. <br />5) Left in place. but will restrict snow fences 10 R-I districts. 154.110 (C) Barbed wire <br />and electric fencing. Allowed in R-I zone. You may want to restrict this to animal <br />holding areas and not allow it to be used as a boundary fence. <br />6) Modified to require fencing around permanent pools. 154.110 (E) Swimming pool <br />fencing. Required for any pool with water depth over 24 inches. This may be too <br />broad. <br />