My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Item 6 - PH/Cell Towers
COE
>
City of Eugene
>
Council Agendas 2004
>
CCAgenda-12/06/04Mtg
>
Item 6 - PH/Cell Towers
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
6/9/2010 12:53:55 PM
Creation date
12/1/2004 2:43:15 PM
Metadata
Fields
Template:
City Council
City_Council_Document_Type
Agenda Item Summary
CMO_Meeting_Date
12/6/2004
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
172
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
. Mr. Jerome Udz - 3 - November 8, 2004 <br /> <br /> IV. Variance Provisions <br /> <br /> A~TTVVS continues to be concerned that the proposed variance language is an <br /> inadequate safety valve for the prOposed school and residential sel+~acks. As proposed, a <br /> wireless carrier must demonstrate "to the city's satisfaction" that it "is unable to provide an <br /> aciec~uate level of telecommunications services to the proposer] service area and also comply <br /> with the setback requirements" to obtain a variance. The ambiguous and unsatisfactory nature <br /> of this language is demonstrated bythe conflicting opinions of expressed by Planning 5taft and <br /> others submitting comments regarding the proposed new language. Wireless opponents <br /> express concern that the proposed variance provisions will become the exception that <br /> swallows the rule, while wireless carriers anticipate that the standards will be interpreted <br /> strictly, making them virtually unmeetable. The proposed language should be significantly <br /> modified to provide greater clarity and less opportunity for the arbitral, use of discretion. <br /> <br /> ATTVV$ suggests that the City modify the proposed variance provisions i~ the following <br /> two ways. First, ATTVVS requests that the (;ity consider permitting exceptions from the setback <br /> provisions through an aclministratlve adjustment, rather t~an a variance, process. Second, <br /> A~-I'VV$ reiterates its recluest that the City modify the language of proposed EC 9.570(9)(c)(1) to <br /> read as follows: "That it is not possible for the proposed Wireless facility to satisfy its function <br /> within the applicant's wireless network and also comply with the setback requirements." This <br /> language takes into consideration quality, coverage and capacity demands. It would also <br /> require that the issue be evaluated within the context of the carrier's existing wireless network. <br /> <br /> Aq-FVVS urges the City to consider these revisions. Without such language, the City <br /> exposes itself to litigation not only from wireless carriers asserting that the setbacks constitute a <br /> prohi}3ition of service, but equally to lawsuits from anti-wireless citizens who will assert that the <br /> City has not applied its vague standards strictly enough. Both are likely avoida~D[e through <br /> tighter drafting. <br /> <br /> V. Third Party Technical Review <br /> <br /> As I explained in my August 24, 2004 letter, ATTWS does not object to paying the <br /> actual costs incurred by the City to hire an independent consultant to assist the City in <br /> reviewing its applications. The qualifications and scope of review for these independent <br /> consultants, however, needs to be spelled out more clearly in the wireless code, Specifically, <br /> the wireless code should provide that any independent consultant must be a qualified and <br /> licensed engineer mutually acceptable to both the City and the wireless applicant. Equally <br /> important, the consultant's scope of work should be limited to reviewing and verifying the <br /> wireless carrier's technical assertions - e.g., is there a gap in coverage or insufficient call <br /> capacity, and will the proposed facility resolve that issue, vv~thout such specificity, the <br /> technical consultant's review can morph from the review of a particular facility and how it fits <br /> within the wireless carrier's existing network, to an analysis of the efficacy the carrier's entire <br /> netwo~ design. This is not helpful to either the City ortho wireless carrier. We are in the <br /> process of formulating language addressing this issue and wild provide it to you later this week. <br /> <br /> Vi. Other Issues <br /> <br /> If the Ci~/is committed to amending its wireless code at this time, ATTW$ has several <br /> alternative suggestions to those currently proposed. In particular, A-CIRN5 requests that the <br /> <br /> 11/08/04 ~ON 10:43 [TX/RX NO 8271] <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.