2017 ORS 215.276¹
Required consultation for transmission lines to be located on high-value farmland

(1) As used in this section:

(a) “Consult” means to make an effort to contact for purpose of notifying the record owner of the opportunity to meet.

(b) “High-value farmland” has the meaning given that term in ORS 195.300 (Definitions for ORS 195.300 to 195.336).

(c) “Transmission line” means a linear utility facility by which a utility provider transfers the utility product in bulk from a point of origin or generation, or between transfer stations, to the point at which the utility product is transferred to distribution lines for delivery to end users.

(2) If the criteria described in ORS 215.275 (Utility facilities necessary for public service) for siting a utility facility on land zoned for exclusive farm use are met for a utility facility that is a transmission line, or if the criteria described in ORS 215.274 (Associated transmission lines necessary for public service) for siting an associated transmission line are met, the utility provider shall, after the route is approved by the siting authorities and before construction of the transmission line begins, consult the record owner of high-value farmland in the planned route for the purpose of locating and constructing the transmission line in a manner that minimizes the impact on farming operations on high-value farmland. If the record owner does not respond within two weeks after the first documented effort to consult the record owner, the utility provider shall notify the record owner by certified mail of the opportunity to consult. If the record owner does not respond within two weeks after the certified mail is sent, the utility provider has satisfied the provider’s obligation to consult.

(3) The requirement to consult under this section is in addition to and not in lieu of any other legally required consultation process. [2009 c.854 §1; 2013 c.242 §7]

Note: 215.276 (Required consultation for transmission lines to be located on high-value farmland) was enacted into law by the Legislative Assembly but was not added to or made a part of ORS chapter 215 or any series therein by legislative action. See Preface to Oregon Revised Statutes for further explanation.

Atty. Gen. Opinions

Effect of constitu­tional pro­vi­sion requiring pay­ments based on govern­ment regula­tions restricting use of prop­erty, (2001) Vol 49, p 284

Chapter 215

Notes of Decisions

Published notice is adequate if prop­erty owners can reasonably ascertain that prop­erty in which they hold interest may be affected. Clackamas County v. Emmert, 14 Or App 493, 513 P2d 532 (1973), Sup Ct review denied

Statutory scheme es­tab­lishing LCDC and granting it authority to es­tab­lish state-wide land use planning goals does not unconstitu­tionally delegate legislative power where both standards (under this chapter) and safeguards ([former] ORS 197.310) exist. Meyer v. Lord, 37 Or App 59, 586 P2d 367 (1978)

Where county had not yet adopted comprehensive plan but had zoned certain por­tions “primarily agricultural,” county had not enacted adequate interim measures to protect its agricultural land until exclusive farm use zoning was completed. Columbia County v. LCDC, 44 Or App 749, 606 P2d 1184 (1980)

Atty. Gen. Opinions

Fasano v. Bd. of County Commrs., applica­tion to county governing bodies and planning com­mis­sions, (1974) Vol 36, p 960; binding effect on govern­mental agencies of the adop­tion of interim Willamette River Greenway boundaries, (1975) Vol 37, p 894

Law Review Cita­tions

36 EL 25 (2006)

1 Legislative Counsel Committee, CHAPTER 215—County Planning; Zoning; Housing Codes, https://­www.­oregonlegislature.­gov/­bills_laws/­ors/­ors215.­html (2017) (last ac­cessed Mar. 30, 2018).
2 Legislative Counsel Committee, Annotations to the Oregon Revised Stat­utes, Cumulative Supplement - 2017, Chapter 215, https://­www.­oregonlegislature.­gov/­bills_laws/­ors/­ano215.­html (2017) (last ac­cessed Mar. 30, 2018).
3 OregonLaws.org assembles these lists by analyzing references between Sections. Each listed item refers back to the current Section in its own text. The result reveals relationships in the code that may not have otherwise been apparent.