My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Staff Report
>
OnTrack
>
CU
>
2014
>
CU 14-3
>
Staff Report
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/20/2015 2:35:57 PM
Creation date
5/20/2015 2:34:07 PM
Metadata
Fields
Template:
PDD_Planning_Development
File Type
CU
File Year
14
File Sequence Number
3
Application Name
AT&T AT CROSSFIRE
Document Type
Staff Report
Document_Date
5/20/2015
External View
Yes
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
312
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
<br />There is no clear, convincing and verifiable evidence submitted in relation to this <br />requirement. Specifically, none of the following has been demonstrated by clear, <br />convincing and verifiable technical evidence: <br />That in this instance, for technical reasons, the asserted gap must be filled from a <br />single facility, to the exclusion of all reasonable alternatives; <br />That the selected location is the only location or combination of locations, to the <br />exclusion of all reasonable alternative locations, that would enable the asserted gap <br />to be filled; <br />That there is no viable alternative to filling the asserted gap and improving overall <br />coverage than by constructing a new tower; <br />That the facility must be 75’ in height. <br />The applicant’s legal counsel responded to the CMS report (see Attachment 18), asserting that <br />CMS mischaracterized the code criteria requirements of EC 9.5750(6)(b)(3) and took exception <br />to CMS stating there was no clear and convincing evidencefrom the applicant showing <br />compliance with this section of the code. They statethat “the balance of the discussion on Page <br />7 [CMS report, Attachment 2] relies on the erroneously referenced standard of “clear and <br />convincing” evidence, which is not followed in Oregon and should be discarded”. <br /> <br />EC 9.5750(6)(b)(3) requires the applicant to provide evidence demonstrating collocation is <br />impractical. Staff agrees with the applicant that CMS mischaracterizes the standard of proof <br />required. Under the Eugene Code and Oregon state law, an applicant is not required to carry its <br />burden to demonstrate compliance with an approval criterion by “clear and convincing” <br />evidence. Specifically, EC 9.7085 requires the decision in this case be based on reliable, <br />probative and substantial evidence. That said, the CMS comments can be read to contend that <br />the technical evidence provided by the applicant is not sufficient, even under that standard. <br /> <br />The CMS report describes several areas of the applicant’s evidence that question the validity <br />and clarity of the evidence provided. As pointed out by CMS, the applicant’s statement that, <br />“There [are] no existing buildings of sufficient height that will meet AT&T’s coverage goals” <br />does not support the technical need for the proposed facility. Also, CMS points out that, “both <br />the size and location of the search ring strongly indicate that a single-facility approach was the <br />only option considered”. Since the applicant did not refute this assertion by CMS, staff is <br />unclear if the applicant actually considered other options aside from a single antenna facility at <br />75 feet in height. CMS’s response to comments from the applicant’s legal counsel (see <br />Attachment 3) state that, “It has not been demonstrated by verifiable technical evidence that <br />the use of one (1) or more existing facilities/structures cannot be attached to, in order to <br />achieve the approximate coverage the proposed facility is intended to provide”. <br /> <br />As noted above under subsection 2, the applicant indicates that collocation on EWEB facilities <br />was noted feasible, primarily because EWEB prohibits collocation on poles with live power lines. <br />Staff has requested EWEB to clarify their policies about collocation, and understands that EWEB <br />does not prohibit all poles with live power lines (see Attachment 20). EWEB does prohibit poles <br />with transmission conductors but will consider collocation on many of their poles provided their <br />HO Agenda - Page 28 <br />
The URL can be used to link to this page
Your browser does not support the video tag.