David Setniker v. Polk County

1 CPM Development Corporation seeks to develop a sand-and-gravel

2 operation on property adjacent to farm land owned by petitioners in Polk County. In

3 pursuing that development, CPM submitted a three-part application to the county, and the

4 county approved it. Petitioners appealed the county's decision to LUBA. LUBA rejected

5 most of petitioners' assignments of error but remanded to the county on others. Rickreall

6 Community Water Assoc., et al v. Polk County, et al, 53 Or LUBA 76 (2006) (Rickreall

7 I). Petitioners sought judicial review, and we affirmed without an opinion. Rickreall

8 Community Water Association et al and Madjic Farms, Inc., et al v. Polk County et al,

9 212 Or App 497, 158 P3d 524 (2007). On remand, the county again approved CPM's

10 application. Petitioners again appealed to LUBA, and LUBA rejected most of the

11 assignments of error, ruled for petitioners on others, and again remanded the application

12 to the county. Petitioners now seek review of that latest LUBA decision, assigning error

13 to LUBA's rejection of some of their arguments; CPM cross-petitions on the ground that

14 LUBA erred in sustaining certain of petitioners' other assignments. For the reasons

explained below, we affirm LUBA's decision in part, reverse in part, and remand. 1 15

16 We take the facts, which are undisputed, from LUBA's opinion. CPM

17 proposed a sand-and-gravel extraction and processing facility, as well as a cement and

18 asphalt processing plant, on part of a parcel zoned exclusively for farm use. The site is

19 located approximately two miles north of the City of Independence, just west of the

1 Rickreall Community Water Association, Madjic Farms, Inc., Michael and Susan

Calef, and E.M. Easterly intervened as petitioners before LUBA. These parties have not

appeared on judicial review.

3

1 Willamette River. Petitioners, the Setnikers, own property adjacent to the parcel.

2 The issues in this case involve the intersection of Oregon State Highway

3 51, which runs north and south, with Oregon State Highway 22, which runs east and

4 west. The 51/22 intersection is controlled by stop signs on the northbound and

5 southbound approaches only; Highway 22 is a through road, five lanes wide. Westbound

6 vehicles on Highway 22 seeking access to the site must use the middle turn lane on

7 Highway 22 (which has no traffic signal) to turn south onto Highway 51, then travel a

8 relatively short distance to the intersection where Highway 51 meets a haul road, and

9 then turn left (east) onto the haul road to the site.

10 In 2001, CPM filed an application with the county for (1) a comprehensive

11 plan amendment to add the site to the county's inventory of significant mineral and

12 aggregate resources; (2) a zoning map amendment to add a mineral and aggregate (MA)

13 overlay zone to the mining site and surrounding area, totaling 336 acres; and (3) a

14 conditional use permit to mine the site. After various delays requested by CPM, the

15 county board of commissioners approved all three elements of the application in 2006.

16 That approval was appealed to LUBA, and in Rickreall I, LUBA remanded the decision

17 to the county after sustaining some assignments of error and rejecting others. As relevant

18 here, the bases for remand included the county's failure to apply the county procedures

19 and code standards applicable to the proposed comprehensive plan amendment and

20 failure to demonstrate compliance with the Transportation Planning Rule (TPR) at OAR

21 660-012-0060, set out below.

4

1 In March 2009, the county planning commission held an evidentiary

2 hearing to address the correct code standards for the comprehensive plan amendment.

3 The remaining bases for remand were reserved for action by the board of commissioners.

4 In June 2009, the planning commission recommended that the board of commissioners

5 approve the requested plan amendment and, after an evidentiary hearing, the

6 commissioners did so, issuing an ordinance that again approved CPM's three-part

7 application. Petitioners once again appealed to LUBA.

8 As relevant to the petition before this court, petitioners argued to LUBA

9 that the county erred in four respects: (1) by misapplying the TPR; (2) by considering

10 new evidence without reopening the record to petitioners; (3) by allowing respondent to

11 process aggregate to be extracted from another site, contrary to ORS 517.750(11) and

12 Polk County Zoning Ordinance (PCZO) 174.050; and (4) by not weighing the benefits

and impacts of a new mining site as required by PCZO 115.060(C). 13 LUBA rejected all of

14 petitioners' assignments of error except the error addressing the TPR, which LUBA

15 sustained in part. Petitioners and CPM both seek judicial review. CPM argues that

16 LUBA erred in evaluating its application based on laws and rules that were in effect at

17 the time that the county ruled on its application, instead of laws and rules in effect when

18 CPM originally submitted the application. Petitioners, for their part, argue that LUBA

19 misapplied the TPR by not requiring the county to put in place more measures to mitigate

20 the effects of CPM's proposed operation; that LUBA did not address all of their

21 arguments; and that LUBA erred by upholding a plan amendment and zone change that

5

1 allow CPM to process aggregate extracted off site. We hold that (1) LUBA correctly

2 ruled that the appropriate legal standards were the ones in effect when the county ruled

3 on CPM's application, and not those in effect when CPM originally submitted the

4 application; (2) LUBA misinterpreted the TPR's mitigation requirements; and (3) LUBA

5 correctly ruled in favor of CPM's proposal to process aggregate extracted off site.

6 Therefore, on petitioners' petition for review, we affirm in part, reverse in part, and

remand. On CPM's cross-assignments of error, we affirm.2 7

8 We address each assignment of error in turn, beginning with CPM's cross9

assignment regarding the TPR because our resolution of that issue determines how we

address petitioners' argument regarding application of the same rule. 10

11 CPM's argument deals with the interaction between the TPR and the so12

called "goal-post rule," ORS 215.427(3)(a). Under OAR 660-012-0060(1)(c) of the TPR,

13 if a local government's amendment to a comprehensive plan or land use regulation

14 "significantly affects" a transportation facility--and the 51/22 intersection is a

15 transportation facility--the local government may approve the amendment only if it also

16 adopts one or more of the mitigating measures described in OAR 660-012-0060(2) or

17 OAR 660-012-0060(3). An amendment "significantly affects" a transportation facility if

18 it degrades the facility "[a]s measured at the end of the planning period identified in the

2 Petitioners also assign error to LUBA's failure to require the county to disregard

evidence that petitioners allege they did not have the opportunity to rebut, and to LUBA's

alleged failure to engage in a proper balancing test in order to reach the conclusion that

the project would confer a general public benefit. We reject all of those assignments of

error without discussion.

6

1 adopted transportation system plan." OAR 660-012-0060(1)(c).

2 The "goal-post rule," ORS 215.427(3)(a), provides, in essence, that the

3 rules in existence when an application is complete are the rules that govern the approval

4 or rejection of the application--government, in other words, cannot "move the goal-posts"

5 after the applicant has (to complete the sport metaphor) kicked the ball:

6 "If the application [for a permit, limited land use decision or zone change]

7 was complete when first submitted or the applicant submits additional

8 information * * * within 180 days of the date the application was first

9 submitted and the county has a comprehensive plan and land use

10 regulations acknowledged under ORS 197.251, approval or denial of the

11 application shall be based upon the standards and criteria that were

12 applicable at the time the application was first submitted."

13 Thus, in this case, if the goal-post rule applies, then the degradation is measured as of the

14 end of the planning period that was in effect when CPM first submitted the application in

15 2001. That date was 2020. If the goal-post rule does not apply, then, because the county

16 has adopted a new transportation system plan with a 2030 horizon, projected impacts are

17 measured as of that later date. CPM apparently believes that, if the appropriate date for

18 measuring impacts is 2020--that is, if the goal-post rule does apply--then the TPR does

19 not come into play at all and no mitigation measures are necessary, because as of 2020

20 there will not be any "significant effects" on the 51/22 intersection. Petitioners, for their

21 part, argue that the goal-post rule does not apply; therefore, the appropriate date for

22 measuring impact is 2030, and, by that time, the CPM project will have a "significant

23 effect[ ]," and consequently the county must meet the mitigation requirements.

24 The county, on remand, concluded that the goal-post rule applied to CPM's

7

1 application and applied the 2020 planning horizon. On appeal to LUBA, petitioners

2 argued that the goal-post rule does not apply to a zone change or a permit application that

3 is consolidated with and dependent upon a simultaneous comprehensive plan amendment.

4 In response, CPM argued that, by its plain language, the goal-post rule does apply.

5 LUBA agreed with petitioners, concluding:

6 "[I]n applying OAR 660-012-0060(1)(c), the county was required to

7 determine whether the plan and zoning amendments significantly affect

8 transportation facilities '[a]s measured at the end of the planning period

9 identified in the adopted transportation system plan,' i.e. the 2009 TSP

10 [Transportation System Plan], which has a planning period of 2030."

11 Now, in its cross-petition, CPM assigns error to LUBA's conclusion. CPM argues that

12 LUBA erred in concluding that the goal-post rule does not apply to zone changes or

13 permit applications that are consolidated with a comprehensive plan amendment and, in

doing so, ignored the plain language of the statute.3 14 We agree with LUBA.

15 In Rutigliano v. Jackson County, 42 Or LUBA 565, 572 (2002), LUBA

16 discussed how the goal-post rule applies to a consolidated application where a zone

17 change is dependent upon a plan amendment. LUBA explained,

18 "ORS 215.427 is almost entirely directed at requiring counties to

19 render a final decision on an 'application for a permit, limited land use

20 decision or zone change' within 150 days. The fixed goal post rule is

21 appended to a comprehensive statute that is almost entirely directed at

22 ensuring that three kinds of land use applications receive a final decision

3 In CPM's first assignment of error on cross-petition, it argues that LUBA erred in

suggesting that the TPR applied to the plan text amendment. However, LUBA held that

the TPR, whether or not it applied to the plan text amendment, nevertheless applied to

respondent's request for a zone change. CPM does not challenge that decision, which is

an independent basis for rejecting CPM's argument. Accordingly, we reject this

assignment of error.

8

1 within 150 days. The usual situation that the legislature envisioned in

2 adopting and amending ORS 215.427 over the years is an 'application for a

3 permit, limited land use decision or zone change' that is already anticipated

4 by the acknowledged comprehensive plan and land use regulations and

5 therefore requires no post-acknowledgement comprehensive plan or land

6 use regulation amendment.

7 "However, ORS 215.427 also embodies a second important

8 principle. Where the acknowledged comprehensive plan or land use

9 regulations do not anticipate the 'application for a permit, limited land use

10 decision or zone change' and the acknowledged comprehensive plan or land

11 use regulation must be amended to allow the application to be approved,

12 the 150-day deadline does not apply. ORS 215.427(6) makes it clear that

13 the 150-day deadline does not apply to an 'application for a permit, limited

14 land use decision or zone change,' in that circumstance. Edney v. Columbia

15 County Board of Commissioners, 318 Or [138, 143-44, 863 P2d 1259

16 (1993)]. To the extent that ORS 215.427(6) leaves anything to the

17 imagination concerning whether the 150-day deadline might apply to an

18 'application for a permit, limited land use decision or zone change,' ORS

19 215.427(8) expressly provides that the 150-day deadline does not apply

20 where such applications require a concurrent comprehensive plan

21 amendment.

22 "* * * * *

23 "We conclude that where a county has a unified zoning and

24 comprehensive plan map, such that the zoning map cannot be amended

25 without that amendment being both a 'comprehensive plan change' and a

26 'zone change,' the fixed goal post rule does not apply. Our reason for

27 reaching that conclusion is simple. The 'application[s]' that are subject to

28 the fixed goal post rule of ORS 215.427(3) are the same 'applications for a

29 permit, limited land use decision or zone change' that are subject to the 150-

30 day deadline of ORS 215.427(1). If the legislature had intended to make

31 combined applications for both comprehensive plan map amendments and

32 zoning map amendments subject to the fixed goal post rule, it could have

33 said so. No plausible argument has been presented in this appeal for

34 construing the term 'zone change' broadly enough to include a change to a

35 unified map that is both a zoning map and comprehensive plan map. * * *

36 While the application at issue seeks a 'zone change,' that is not all it seeks.

37 Because [the] petitioner's application seeks more than a 'zone change,' it is

38 not limited to one or more of the three kinds of land use applications

39 described in ORS 215.427(1) and is not subject to the fixed goal post rule."

9

Id. 1 at 572-75 (emphases in original; footnotes omitted). We agree with LUBA's analysis

2 and reasoning--in a nutshell, the goal-post rule does not apply when the standards that it

3 requires to remain fixed are themselves bound up with the application. Accordingly, we

4 reject CPM's cross-petition and agree that the goal-post rule does not apply to a zone

5 change or permit application that is consolidated with, and dependent upon, a

6 comprehensive plan amendment. Thus, the relevant date for determining whether the

7 county's proposed amendment would significantly affect the intersection is 2030.

8 We now turn to petitioners' assignments of error on judicial review, the first

9 of which challenges LUBA's application of the TPR. Because the county found that

10 respondent's proposed application would "significantly affect" a transportation facility as

11 of 2030, OAR 660-012-0060(1), the county imposed two conditions of approval intended

12 to ensure that traffic from the proposed development would not render the 51/22

13 intersection "[in]consistent with [its] identified function, capacity, and performance

14 standards." The first condition prohibited CPM's employees and contract haulers that

15 travel west on Highway 22 from turning south onto Highway 51 at the intersection

16 between 4:00 and 6:00 p.m. and, instead, required them to use an eight-mile long

17 alternate route. The second condition, intended to discourage haulers from violating the

18 first condition, required CPM to erect a gate or chain across the entrance to the haul road

19 from Highway 51 between 4:00 and 6:00 p.m. The gate or chain would not physically

20 prevent a determined hauler from entering the site, but it would make entry more

21 difficult.

10

1 To LUBA, petitioners argued, among other things not at issue before us,

2 that the re-routing and chaining conditions did not constitute sufficient or permissible

3 mitigation under the TPR. That rule provides:

4 "(1) Where an amendment to a functional plan, an acknowledged

5 comprehensive plan, or a land use regulation would significantly affect an

6 existing or planned transportation facility, the local government shall put in

7 place measures as provided in section (2) of this rule to assure that allowed

8 land uses are consistent with the identified function, capacity, and

9 performance standards * * * of the facility. * * *

10 "* * * * *

11 "(2) Where a local government determines that there would be a

12 significant effect, compliance with section (1) shall be accomplished

13 through one or a combination of the following:

14 "* * * * *

15 "(e) Providing other measures as a condition of development or

16 through a development agreement or similar funding method, including

17 transportation system management measures, demand management or

18 minor transportation improvements. Local governments shall as part of the

19 amendment specify when measures or improvements provided pursuant to

20 this subsection will be provided.

21 "(3) Notwithstanding sections (1) and (2) of this rule, a local

22 government may approve an amendment that would significantly affect an

23 existing transportation facility without assuring that the allowed land uses

24 are consistent with the function, capacity and performance standards of the

25 facility where:

26 "(a) The facility is already performing below the minimum

27 acceptable performance standard identified in the TSP [Transportation

28 System Plan] or comprehensive plan on the date the amendment application

29 is submitted;

30 "(b) In the absence of the amendment, planned transportation

31 facilities, improvements and services as set forth in section (4) of this rule

32 would not be adequate to achieve consistency with the identified function,

11

1 capacity or performance standard for that facility by the end of the planning

2 period identified in the adopted TSP;

3 "(c) Development resulting from the amendment will, at a minimum,

4 mitigate the impacts of the amendment in a manner that avoids further

5 degradation to the performance of the facility by the time of the

6 development through one or a combination of transportation improvements

7 or measures[.]"

8 OAR 660-012-0060. Petitioners' argument, if we understand it correctly, begins with the

9 undisputed (at this stage of the case) premise that the amendments sought by CPM will

10 "significantly affect" the 51/22 intersection, presumably by increasing the number of

11 westbound vehicles that would make left turns off of Highway 22 on to Highway 51, and

12 that, therefore, the county can meet the requirements of the TPR rule only by complying

13 with either subsections (1) and (2)(e), or subsection (3). Subsections (1) and (2)(e),

14 petitioners contend, require the county to undertake "measures" that will "assure that [the

15 land uses proposed in CPM's application] are consistent with the identified function,

16 capacity, and performance standards" of the 51/22 intersection. In other words,

17 petitioners argue--and this is the key to their argument--subsections (1) and (2)(e) require

18 the rerouting and entrance blocking to mitigate not only the intersection's failures caused

19 by CPM's proposed site, but also eliminate any failures that the intersection already has

20 or will encounter without the proposed site, that is, failures caused by existing traffic and

21 so-called "background traffic" growth. Therefore, the argument continues, because the

22 rerouting and blocking will at best offset the impacts of CPM's proposed development but

23 will not bring the presently failing or project-to-fail intersection into full consistency with

24 its function, capacity and performance standards, CPM's only option is subsection (3),

12

which does 1 permit measures that will mitigate only the failures caused by the proposed

2 site. And, the argument goes, it is undisputed that CPM cannot meet one of the

3 conjunctive requirements in subsection (3), namely, (3)(a) ("The facility is already

4 performing below the minimum acceptable performance standard identified in the TSP or

5 comprehensive plan on the date the amendment application is submitted"), because the

6 51/22 intersection was not failing when CPM's application was first submitted in 2001.

7 Thus, petitioners conclude, the county cannot possibly achieve compliance with the TPR

8 without imposing additional mitigation measures that will not only mitigate the effects of

9 CPM's project, but will also mitigate the existing and projected failures that are

10 independent of that project.

11 LUBA rejected petitioners' argument:

12 "Where petitioners go astray is in their apparent understanding that

13 OAR 660-012-0060(2)(e) requires the applicant to provide 'other measures

14 as a condition of development' sufficient to mitigate even failures caused

15 solely by growth in the background traffic. The basic commandment of

16 OAR 660-012-0060(1) and (2) is to ensure that the proposed amendment is

17 'consistent with' the function, capacity and performance standards of

18 transportation facilities. If conditions of approval are sufficient to

19 completely mitigate or eliminate impacts from the proposed amendment on

20 a facility that is projected to fail, then the amendments will not 'worsen' the

21 projected failure for purposes of OAR 660-012-0060(1)(c) and the TPR is

22 satisfied, notwithstanding that the facility is failing or will still fail by the

23 end of the planning period due to growth in background traffic. In short,

24 OAR 660-012-0060(2)(e) and (3) work together to provide means to ensure

25 that the proposed amendment is 'consistent with' the function, capacity and

26 performance standards of the facility, and the two provisions are neither

27 mutually exclusive nor subject to some kind of gap in their coverage."

28 (Emphasis in original.) LUBA's rejection of the key part of petitioners' argument ("OAR

29 660-012-0060(2)(e) requires the applicant to provide 'other measures as a condition of

13

development' 1 sufficient to mitigate even failures caused solely by growth in background

2 traffic") is not persuasive. LUBA relies on "the basic command" of the TPR and,

3 apparently, a reluctance to interpret the rule so as to create a "gap": under petitioners'

4 interpretation of the rule, if an amendment will have a significant impact on a facility that

5 was performing at an acceptable level when the application was submitted but becomes

6 unacceptable within the transportation system plan's time frame (here, 2030) due to

7 naturally occurring growth in background traffic, the local government must require

8 conditions that not only mitigate the damage caused by the amendment but also remedy

9 the facility's failures for which the amendment is in no way responsible.

10 Although LUBA's reading may make more sense and may, in fact, correct a

11 flaw that the rule's drafters inadvertently overlooked, the reading simply cannot be

12 reconciled with the rule's unambiguous language. Subsections (1) and (2)(e) require

13 measures that ensure a facility's consistency with its function, capacity, and performance

14 standards, that is, that ensure that the facility will not fail. Subsection (3) creates an

15 exception: "Notwithstanding sections (1) and (2)," the local government does not have to

16 require measures ensuring that the facility is in compliance with standards, etc., if the

17 facility was already out of compliance when the application was filed, it would be out of

18 compliance by the end of the planning period in the transportation system plan, and the

19 amendment will itself mitigate its own adverse impact.

20 In sum, LUBA erred in ruling that the county could comply with subsection

21 (2)(e) of the TPR by mitigating only CPM's significant adverse effects. As the rule is

14

1 written, if LUBA decides on remand that (1) the 51/22 intersection was consistent with

2 relevant function, capacity, and performance standards when CPM filed its application,

3 and (2) the intersection will become inconsistent with the relevant function, etc., by 2030,

4 due to the effect of the amendments or due to independent growth or background traffic,

5 then the county must put in place measures that will not only mitigate the inconsistencies

6 caused by the amendments but also the inconsistencies resulting independently.

7 Petitioners argue in their second assignment of error that LUBA's treatment

8 of the rerouting measure failed to address all of the extra trips created by the

9 development, instead addressing only those from CPM's employees and independent

10 contractors, and that, in any event, the rerouting measure was neither feasible nor

11 enforceable. Petitioners cite ORS 197.835(11) for the proposition that LUBA was

12 required to address the argument petitioners made to it, namely, that CPM's rerouting of

13 its trucks does not address the effect of vehicles driven by "suppliers, customers, and

14 visitors." ORS 197.835(11)(a) provides, in part:

15 "Whenever the findings, order and record are sufficient to allow

16 review, and to the extent possible consistent with the time requirements of

17 ORS 197.830(14), the board shall decide all issues presented to it when

18 reversing or remanding a land use decision * * * or limited land use

19 decision * * *."

20 As noted earlier, the county imposed two conditions of approval on CPM to ensure that

21 traffic from the proposed development would not worsen or degrade the functionality of

22 the 51/22 intersection: rerouting CPM's trucks during peak hours and placing a gate to

23 discourage truckers from using the intersection during those hours. To LUBA,

15

1 petitioners argued, among other things, that the proposed rerouting condition did not

2 include all trips arriving at the subject site because it did not include trips made by

3 "suppliers, customers, and visitors." We disagree. The county explicitly found,

4 "Independent trucks that haul from the new facility are also

5 controlled by mandatory routing. To ensure compliance with the routing

6 plan, a data sheet would be used for all drivers and visitors instructing them

7 on appropriate routing, and particularly to not make the southbound turning

8 movement at the 51/22 intersection. The applicant states that independent

9 drivers who are discovered to have violated the mandatory routing would

10 be subject to having access privileges revoked. * * *

11 "The applicant states that the mandatory routing plan would also

12 apply to employees and suppliers of the proposed facility. * * *"

13 (Emphasis added.) The county's order plainly took into consideration the "suppliers,

14 customers, and visitors."

15 Petitioners next argue that the county erred in allowing aggregate that is

16 extracted off site to be processed at the subject property. Specifically, petitioners argue

17 that LUBA erred in upholding the county's interpretation of PCZO 174.050. That

18 ordinance provides:

19 "The following uses may be permitted in the MA Extraction Area

20 subject to Site Plan approval * * *:

21 "(A) Mining or extraction of rock, clay, soil, sand, gravel, or other

22 mineral or aggregate material.

23 "(B) Stockpiling and storage of mineral and aggregate materials.

24 "(C) Processing of:

25 "(1) Materials, including crushing, washing, milling, screening,

26 sizing, batching of portland cement; and

16

1 "(2) Batching or blending of mineral and aggregate into asphaltic

2 concrete, except within 2 miles of a planted commercial vineyard.

3 "* * * * *

4 "(G) Sale of products extracted and processed on-site from a mineral

5 and aggregate operation."

6 Petitioners focus on subsection (G), and argue that the necessary implication of that

7 subsection is that, because the sales permitted on site are limited to products that are

8 extracted and processed on site, no processing of products extracted off site is permitted.

9 The logical flaw in that argument is readily apparent: subsection (G) neither says nor

10 implies anything about products that are extracted off site, hauled to the site, processed

11 on site, then hauled and sold off site. LUBA noted as much: "[W]e agree with

12 respondents that [PCZO 174.050(G)] authorizes a limited commercial use within the MA

13 zone, but is probably not intended to proscribe on-site processing of material that was

14 extracted off-site, where that material is then sold to customers off-site." In light of

15 subsection (C), which expressly authorizes on site processing, petitioners' argument is

hardly plausible.4 16

17 Nor is their argument helped by ORS 517.750(11), which provides:

18 "'Processing' includes, but is not limited to, crushing, washing,

19 milling and screening as well as the batching and blending of mineral

20 aggregate into asphalt and portland cement concrete located within the

21 operating permit area."

4 Perhaps to avoid this conclusion, petitioners insist that it is "reasonable and likely

that a significant percentage of aggregate will be sold [on site] * * * that has been mined

off-site." When and if that occurs, we may be called on to decide whether subsection (G)

prohibits such sales. At present, we are not.

17

1 Petitioners would read the phrase "within the operating permit area" to somehow limit the

2 definition of "processing" so as to require that the term apply only to operations taking

3 place within the site where extraction occurred. In fact, the statute says nothing about

4 extraction or any connection between extraction and processing.

5 Whether a local government's interpretation of its land use regulation is

6 "inconsistent with the express language" of the regulation under ORS 197.829(1)(a)

7 "'depends on whether the interpretation is plausible, given the interpretive principles that

8 ordinarily apply to the construction of ordinances under the rules of PGE [v. Bureau of

9 Labor and Industries, 317 Or 606, 610-12, 859 P2d 1143 (1993),]'" as modified by State

10 v. Gaines, 346 Or 160, 171-72, 206 P3d 1042 (2009). Western Land & Cattle, Inc. v.

11 Umatilla County, 230 Or App 202, 209, 214 P3d 68 (2009) (quoting Foland v. Jackson

12 County, 215 Or App 157, 164, 168 P3d 1238, rev den, 343 Or 690 (2007)). As the

13 Supreme Court recently explained, "when a governing body is responsible for enacting an

14 ordinance, it may be assumed to have a better understanding than LUBA or the courts in

15 its intended meaning." Siporen v. City of Medford, 349 Or 247, 258, 243 P3d 776 (2010).

16 Under these standards, we readily conclude that the county's interpretation of PCZO

17 174.050 cannot be rejected.

18 On petition, reversed and remanded for reconsideration of transportation

19 planning rules mitigation requirements; otherwise affirmed. On cross-petition, affirmed.



* * *



See: http://www.publications.ojd.state.or.us/A148070.pdf

On petition, reversed and remanded for reconsideration of transportation planning rules

mitigation requirements; otherwise affirmed. On cross-petition, affirmed.