Laserfiche WebLink
5 <br /> <br /> Lane' Code 16.264(3). Application shall indude evidence of compliance with this <br /> requirement. <br /> <br /> EC 9.5750(6)(c) 2. Alternate Sites. <br /> The current code allows applicant to consider alternate sites only in more intensively <br /> used commerdal ahd industrial zones. In many areas, this results in a dearth of <br /> potential alternative sites. AppliCants should be required to submit'documentation <br /> of having considered any feasible sites within the required radius, both in more <br /> intensively zoned properties, and in the same zone as the subject property. This <br /> provides a larger pool of potential alternative sites, and could make it possible to <br /> meet both commUnity and telecommunication provider needs more easily. The <br /> required radius should be increased from 2000 to 2600 feet. This is because the <br /> coverage footprint for PCS antennas has a diameter of approximately 4 miles, and <br /> the antennas can be placed anywhere within a 25% radius of the center and still <br /> provide adequate service (radius of a 4mile drde -- 2 miles, 25% of 2 miles = one <br /> half mile, or 2640 feet). Again, Planning staff lacks the technical expertise to <br /> · determine verity of an applicant's statements regarding RF coverage areas. This <br /> points to the need for independent review of ALL applications by a qualified RF <br /> engineer, whose fee shall be Paid by the applicant. <br /> <br /> EC 9.5750(6)(c) 3. Collocation on existing structures. Current code language <br /> (regarding the applicant's attempt to collocate on existing structures rather than <br />· ! build a new tower) is so broadly written as to allow the applicant to forego <br /> collocation at the wave of a hand. Under current code, an applicant can get out of <br /> collocation merely by stating that it is "impractical". In general, there are two types <br /> of telecommunications applicants: wireless service providers, and tower contractors. <br /> Wireless service providers generally are amenable to collocation, because it saves <br /> the expense of putting up new towers, and gets them on the air faster. ToWer <br /> contractors are more likely to avoid collocation if pOssible, since they make their <br /> money by building new towers and leasing space on them to wireless service <br /> providers. In order to preserve property values for homeowners, Collocation on <br /> existing structures should be required unless the applicant can document with an <br /> independenl~RF engineering report that it is impossible. Wherever possible, mini- <br /> cell technologY on light and power poles should be required. This is another <br /> provision that cannot be administered .effectively without independent review of <br /> ALL applications by an RF engineer. <br /> <br /> EC 9.5750(6)(c) 5. Current code requires the applicant to submit "A statement <br /> Providing the reasons for the location, design, and height of the proposed tower or <br /> antennas." To ensure that the appliCant's claims are .accurate, a provision needs to <br /> be added, either in the telecommunications code 'itself, or better, in site review and <br /> conditional use permit criteria, which sPecifies that applications found to contain <br /> false or misleading statements or information will be suspended, and if already <br /> approved, will be denied. We have found numerous examples from both Lane <br /> County and the City of Eugene in which telecommunications providers have stated <br /> <br /> IV-78 <br /> <br /> <br />