2017 ORS 197.713¹
Industrial development on industrial lands outside urban growth boundaries
  • exceptions

(1) Notwithstanding statewide land use planning goals relating to urbanization or to public facilities and services, a county or its designee may authorize:

(a) Industrial development, including accessory uses subordinate to the industrial development, in buildings of any size and type, subject to the permit approval process described in ORS 215.402 (Definitions for ORS 215.402 to 215.438 and 215.700 to 215.780) to 215.438 (Transmission towers) and to applicable building codes, in an area planned and zoned for industrial use on January 1, 2004, subject to the territorial limits described in subsections (2) and (3) of this section.

(b) On-site sewer facilities to serve the industrial development authorized under this section, including accessory uses subordinate to the industrial development.

(2) Subject to subsection (3) of this section, a county or its designee may consider the following land for industrial development under this section:

(a) Land more than three miles outside the urban growth boundary of every city with a population of 20,000 individuals or more; and

(b) Land outside the urban growth boundary of every city with a population of fewer than 20,000 individuals.

(3) A county or its designee may not authorize industrial development under this section on land within the Willamette Valley as defined in ORS 215.010 (Definitions).

(4) A county or its designee may not authorize under this section retail, commercial or residential development in the area zoned for industrial use. [2003 c.688 §1; 2005 c.666 §1]

Note: 197.713 (Industrial development on industrial lands outside urban growth boundaries) and 197.714 (Cooperation of county and city concerning industrial development) were enacted into law by the Legislative Assembly but were not added to or made a part of ORS chapter 197 or any series therein by legislative action. See Preface to Oregon Revised Statutes for further explanation.

Notes of Decisions

Goal 9, these sec­tions or imple­menting pro­vi­sions which localities must adopt pursuant to statute do not mandate approval of every land use proposal with potentially beneficial economic effects. Benjfran Develop­ment v. Metro. Service Dist., 95 Or App 22, 767 P2d 467 (1989)

Chapter 197

Notes of Decisions

A comprehensive plan, although denominated a “resolu­tion,” is the controlling land use planning instru­ment for a city; upon its passage, the city assumes responsibility to effectuate the plan and conform zoning ordinances, including prior existing zoning ordinances, to it. Baker v. City of Milwaukie, 271 Or 500, 533 P2d 772 (1975)

Procedural require­ments of the state-wide planning goals adopted by the Land Conserva­tion and Develop­ment Commission are not applicable to ordinances adopted before the effective date of the goals. Schmidt v. Land Conserva­tion and Develop­ment Comm., 29 Or App 665, 564 P2d 1090 (1977)

This chapter, 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 (ORS chapter 215) and safeguards ([former] ORS 197.310) exist. Meyer v. Lord, 37 Or App 59, 586 P2d 367 (1978)

Where county’s comprehensive plan and land use regula­tions had not been acknowledged by LCDC, it was proper for county to apply state-wide planning standards directly to individual request for parti­tion. Alexanderson v. Polk County Commissioners, 289 Or 427, 616 P2d 459 (1980)

Issuance of a building permit was a “land conserva­tion and develop­ment ac­tion” where county had no acknowledged comprehensive plan, land was not zoned and no pre­vi­ous land use decision had been made re­gard­ing the land. Columbia Hills v. LCDC, 50 Or App 483, 624 P2d 157 (1981), Sup Ct review denied

Nothing in this chapter grants the Land Conserva­tion and Develop­ment Depart­ment authority to challenge local land use decisions made after comprehensive plan acknowledg­ment. Ochoco Const. v. LCDC, 295 Or 422, 667 P2d 499 (1983)

LCDC has authority in periodic review process to require local govern­ment to add specific language or pro­vi­sions to its land use legisla­tion to assure compliance with statewide goals and LCDC rules. Oregonians in Ac­tion v. LCDC, 121 Or App 497, 854 P2d 1010 (1993), Sup Ct review denied

Atty. Gen. Opinions

Authority of a land conserva­tion and develop­ment com­mis­sion to bind the state in an interstate compact or agree­ment, (1973) Vol 36, p 361; applica­tion of Fasano v. Bd. of County Commrs., (1974) Vol 36, p 960; state-wide planning goal in conjunc­tion with interim Willamette River Greenway boundaries, (1975) Vol 37, p 894; binding effect on govern­mental agencies of the adop­tion of interim Willamette River Greenway boundaries, (1975) Vol 37, p 894; applica­tion to state agencies, (1976) Vol 37, p 1129; preexisting ordinances during the interim imple­menting stage, (1976) Vol 37, p 1329; constitu­tionality of delega­tion to LCDC of authority to prescribe and enforce statewide planning goals, (1977) Vol 38, p 1130; effect of situa­tion where similar peti­tion is filed before both com­mis­sion and a court, (1977) Vol 38, p 1268; considera­tion of availability of public school facilities in determina­tion of whether to approve subdivision, (1978) Vol 38, p 1956

Law Review Cita­tions

10 WLJ 99 (1973); 53 OLR 129 (1974); 5 EL 673 (1975); 54 OLR 203-223 (1975); 56 OLR 444 (1977); 18 WLR 49 (1982); 61 OLR 351 (1982); 20 WLR 764 (1984); 14 EL 661, 693, 713, 779, 843 (1984); 25 WLR 259 (1989); 31 WLR 147, 449, 817 (1995); 36 EL 25 (2006); 49 WLR 411 (2013)

1 Legislative Counsel Committee, CHAPTER 197—Comprehensive Land Use Planning, https://­www.­oregonlegislature.­gov/­bills_laws/­ors/­ors197.­html (2017) (last ac­cessed Mar. 30, 2018).
 
2 Legislative Counsel Committee, Annotations to the Oregon Revised Stat­utes, Cumulative Supplement - 2017, Chapter 197, https://­www.­oregonlegislature.­gov/­bills_laws/­ors/­ano197.­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.