My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Additional Application Materials (5/4/15)
>
OnTrack
>
CU
>
2014
>
CU 14-3
>
Additional Application Materials (5/4/15)
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/11/2015 9:23:34 AM
Creation date
5/8/2015 2:21:56 PM
Metadata
Fields
Template:
PDD_Planning_Development
File Type
CU
File Year
14
File Sequence Number
3
Application Name
ATT AT CROSSFIRE
Document Type
Application Materials
Document_Date
5/4/2015
External View
Yes
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
36
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
Telecommunication Facilities in the Right-of-Way <br />Policy Guidelines <br /> <br />Background <br />The Eugene Land Use Code (Chapter 9, Ordinance 20078, 1997) provides a comprehensive set of <br />standards regulating telecommunication facilities on private property. One of the cornerstones of <br />Chapter 9 is compliance with the federal Telecommunications Act of 1996 and the retention of locally <br />established land use goals. To that end, the code places a priority on colocation of telecommunication <br />facilities on existing structures as the first option. This includes colocation on existing utility structures. <br />Given that many of these utilities are located in the right-of-way (ROW), the land use code provisions do <br />not apply, as the ROW is unzoned. <br /> <br />Although there are no specific code standards governing the height and appearance of <br />telecommunication features in the pubic ROW, there are City Council adopted Findings in <br />telecommunications-related land use and ROW ordinances, as well as City Council adopted <br />Telecommunication Vision and Policies. As wireless technologies are expanding, it seems prudent to <br />establish general guidelines for future requests for wireless facility colocations on structures located in <br />the public ROW. The following guidelines are therefore provided to aid City of Eugene (city) Public <br />Works and Planning, EWEB and other ROW facility users in their determinations in response to requests <br />for telecommunication facilities in the ROW. <br /> <br />Purpose of the Guidelines <br />The following guidelines are intended to provide general parameters under which requests for telecom <br />facilities may be allowed within the public ROW. The primary objective of these guidelines is to provide <br />telecom providers with a better sense of what the City, EWEB, and other ROW facility users will accept <br />related to telecom facilities in the ROW. <br />It’s important to emphasize that these guidelines do not obligate the city, EWEB or other ROW facility <br />users to accept request even if all these guidelines are met. Likewise, these guidelines are not intended <br />as strict code requirements. In the review of specific requests, if a particular proposal achieves the <br />overarching goal of minimizing impact to surrounding properties by but does not meet every guideline, <br />EWEB, the City and other ROW facility users have the discretion to issue approval. <br />General Guideline <br />1. Colocation of telecom facilities should be limited to ROWs involving public streets. Alleys and <br />public utility easements will be strongly discouraged, unless it can be shown that such locations <br />pose minimal visual impact to surrounding properties. <br />2. The telecom facility must be located on an existing pole or other utility structure. No additional <br />poles or structures may be added in the ROW for the sole purpose of accommodating the <br />telecom facility. <br />3. The existing pole or structure may be replaced by a similar pole or structure provided it complies <br />with the other guidelines listed below. <br />
The URL can be used to link to this page
Your browser does not support the video tag.