00-003041GM 1000 Friends Of Florida, Inc. vs. Department Of Community Affairs And The City Of Stuart
 Status: Closed
Recommended Order on Thursday, January 11, 2001.


View Dockets  
Summary: Agency intent to determine City`s plan policies in compliance. Recommended one policy deferred planning in joint planning area to inter-local agreements; other policy incorporated the deferred planning; both not in compliance for that reason.

1STATE OF FLORIDA

4DIVISION OF ADMINISTRATIVE HEARINGS

81000 FRIENDS OF FLORIDA, )

13INC., )

15)

16Petitioner, )

18) Case No. 00-3041GM

22vs. )

24)

25DEPARTMENT OF COMMUNITY )

29AFFAIRS and THE CITY OF )

35STUART, )

37)

38Respondents. )

40_____________________________ )

42RECOMMENDED ORDER

44On October 9, 2000, a formal administrative hearing was

53held in this case in Tallahassee, Florida, before J. Lawrence

63Johnston, Administrative Law Judge, Division of Administrative

70Hearings.

71APPEARANCES

72For Petitioner: Terrell K. Arline, Esquire

78Legal Director

801000 Friends of Florida

84926 East Park Avenue

88Post Office Box 5948

92Tallahassee, Florida 32301

95For Department: Shaw P. Stiller, Esquire

101Department of Community Affairs

1052555 Shumard Oak Boulevard

109Tallahassee, Florida 32399-2100

112For City: Robert C. Apgar, Esquire

118Yeline Goin, Esquire

121320 Johnston Street

124Tallahassee, Florida 32303

127STATEMENT OF THE ISSUES

131The issues in this case are whether certain amendments to

141the Intergovernmental Coordination Element (ICE) of the

148Comprehensive Plan of the City of Stuart (City), adopted by

158Ordinance No. 1702-99, are "in compliance," as defined in and

168required by the "Local Government Comprehensive Planning and

176Land Development Regulation Act," Chapter 163, Part II,

184Florida Statutes.

186PRELIMINARY STATEMENT

188After the City's adoption of the plan amendments, the

197Department of Community Affairs (DCA) gave notice of intent to

207find the amendments "in compliance." Petitioner filed a

215Petition for Formal Administrative Hearing on June 20, 2000.

224DCA referred the matter to the Division of Administrative

233Hearings (DOAH). In accordance with the Joint Response to

242Initial Order, the case was set for hearing in Tallahassee on

253October 9, 2000.

256On October 6, 2000, the parties filed a Prehearing

265Stipulation. By way of opening statement at final the

274hearing, Petitioner further narrowed the issues by focusing

282exclusively on certain reasons why two new policies in the

292amendments to the ICE--Policy A8.19 and Policy A8.20--were not

"301in compliance"; other contentions in the Petition for Formal

310Administrative Hearing were abandoned. Petitioner then called

317Charles Pattison as an expert witness in comprehensive

325planning and had Petitioner's Exhibits 1, 2, and 3 admitted in

336evidence. The City called Robert Pennock as an expert witness

346in comprehensive planning, as well as the City's planner,

355Kimberly Delaney; the City also had its Exhibits 2, 6, and 7

367admitted in evidence. DCA had DCA Exhibit 1 admitted in

377evidence and relied on the parties' stipulation to the

386timeliness and propriety of DCA's procedures for issuance of

395its notice of intent to find the plan amendments "in

405compliance."

406After presentation of evidence, Petitioner and the City

414requested a transcript of the final hearing, and the parties

424were given ten days from the filing of the transcript in which

436to file proposed recommended orders ( PROs). The Transcript

445was filed on November 2, 2000, but the City's Unopposed Motion

456for Extension of Time to File [ PROs] was granted, and the time

469for filing PROs was extended to December 8, 2000. The City

480and DCA filed PROs on the due date; Petitioner filed its PRO

492on December 11, 2000, along with a Motion for Extension of

503Time to File PRO, which neither the City (which filed a

514statement of no objection) nor DCA has opposed. As a result,

525all the parties' PROs have been considered in reaching this

535Recommended Order.

537FINDINGS OF FACT

5401. Ordinance No. 1702-99 adopted by the City of Stuart,

550Florida, on April 10, 2000, amends the City's Comprehensive

559Plan by adding Policies A8.19 and A8.20. The purpose of

569Policies A8.19 and A8.20 was to comply with Section

578163.3177(6)(h)1.a., Florida Statutes (2000). (All statutes

584cited in this Recommended Order are the Florida Statutes

593(2000).

5942. The parenthetical preamble to Policies A8.19 and

602A8.20 states:

604Policies A8.19 and A8.20 are based on

611extensive meetings with Martin County staff

617during the preparation of this revision to

624the ICE Element as well as negotiations

631that occurred over the course of the past

639year and a half in conjunction with

646Stuart's annexation of parcels and related

652plan amendments. It is proposed that these

659policies and steps will help to resolve and

667avoid intergovernmental disputes as well as

673contribute to meeting the new requirements

679of Chapter 163. Additional changes were

685made in response to comments from Martin

692County.

6933. Policy A8.19 provides:

697During the year 2000, the City will

704coordinate with Martin County to establish

710two Joint Planning Areas ( JPAs).

716(1) One JPA will establish an area where

724annexation is likely to occur during the

731planning period. Within this first JPA,

737joint planning shall occur on all relevant

744annexation issues identified by the City

750and county, including intergovernmental

754coordination; land use compatibility;

758natural resource protection; and provision

763of services, infrastructure and

767transportation facilities.

769(2) The second JPA will be for general

777planning purposes. Infrastructure

780planning, recognition of service areas and

786mitigation of cross-jurisdictional impacts

790on infrastructure shall be addressed within

796the second JPA.

799(3) Within two months after the effective

806date of this policy, the City will prepare

814and propose draft policies and areas for

821each of the JPAs. The City will request

829the active participation and input of

835County staff in this initial drafting

841phase. Joint Planning Areas must be

847incorporated into both the City and County

854comprehensive plans or through formal

859adoption of an official agreement between

865the City of Stuart and Martin County.

872Therefore, the City shall propose a special

879purpose, joint meeting(s) of the City and

886County LPAs to develop the specific

892policies and establish the specific areas

898for presentation to the respective

903governing boards for ultimate adoption into

909each comprehensive plan or by official

915agreement between the City of Stuart and

922Martin County after a public hearing.

9284. Policy A8.20 provides:

932During the year 2000, the City shall

939initiate discussions with Martin County to

945establish a joint procedure to facilitate

951future annexations into the City. This

957joint procedure will include:

961a. Provision of early notice to the county

969of the possibility of annexation.

974b. Use of joint plans prepared for the

982JPA's established under Policy A8.19 to the

989extent they apply to the particular

995annexation area.

997c. Provision of county review of the

1004possible impacts of the potential

1009annexation and intergovernmental assessment

1013of mitigation options.

1016d. Consideration of mitigation options by

1022the City.

10245. It is possible that the City and County could

1034establish the "joint procedure to facilitate future

1041annexations" under Policy A8.20 through formal adoption of an

1050official agreement between the City and Martin County, instead

1059of amendment to their comprehensive plans (similar to the

1068explicit procedure referred to in Policy A8.19.) In addition,

1077Policy A8.20 does not explicitly limit the City and County to

1088the items described in the policy for inclusion in the joint

1099procedure; additional items could be added to the joint

1108procedure.

11096. Prior to adoption of Policies A8.19 and A8.20, the

1119City and County entered into interlocal agreements for joint

1128infrastructure service areas. It cannot be ascertained at

1136this time whether those joint infrastructure service areas

1144will be within one of the two JPAs to be established under

1156Policy A8.19.

11587. Another of the policies adopted through Ordinance No.

11671702-99, namely Policy A7.2, provides:

1172The City shall consider for annexation only

1179those parcels of land which may be lawfully

1187annexed pursuant to Chapter 171, Florida

1193Statutes.

11948. Petitioner did not allege in its Petition for Formal

1204Administrative Hearing that the phrase "area where annexations

1212are likely to occur during the planning period" in Policy

1222A8.19(1) was vague. Petitioner mentioned the issue in the

1231Brief General Statement of [Its] Position in the parties'

1240Prehearing Stipulation, but the issue was omitted from that

1249document's joint statement of "the mixed issues of law and

1259fact which remain to be litigated."

1265CONCLUSIONS OF LAW

12689. Section 163.3184(9), Florida Statutes, provides that,

1275in this proceeding, the subject comprehensive plan amendments

"1283shall be determined to be in compliance if the local

1293government's determination of compliance is fairly debatable."

1300In this case, Petitioner bears the burden of proving, beyond

1310fair debate, that Policies A8.19 and A8.20 are not "in

1320compliance."

"1321Fairly Debatable" Standard

132410. In Martin County v. Yusem , 690 So. 2d 1288, 1295

1335(Fla. 1997), the Court equated the "fairly debatable" standard

1344under Section 163.3184(9) with the "fairly debatable" standard

1352applicable to decisions of local governments acting in a

1361legislative capacity, stating:

1364The fairly debatable standard of review is

1371a highly deferential standard requiring

1376approval of a planning action if reasonable

1383persons could differ as to its propriety.

1390The Yusem court also quoted from City of Miami Beach v.

1401Lachman , 71 So. 2d 148, 152 (Fla. 1953):

1409An ordinance may be said to be fairly

1417debatable when for any reason it is open to

1426dispute or controversy on grounds that make

1433sense or point to a logical deduction that

1441in no way involves its constitutional

1447validity.

1448However, in deciding whether planning decisions are fairly

1456debatable, statutory and rule compliance criteria also must be

1465ascertained and applied.

"1468In Compliance" Definition

147111. Under Section 163.3184(1)(b), "in compliance" means

"1478consistent with the requirements of ss. 163.3177, 163.3178,

1486163.3180, 163.3191, and 163.3245, with the state comprehensive

1494plan, with the appropriate strategic regional policy plan, and

1503with chapter 9J -5, Florida Administrative Code, where such

1512rule is not inconsistent with this part and with the

1522principles for guiding development in designated areas of

1530critical state concern."

1533Internal Consistency Argument

153612. Although omitted from Petitioner's PRO, Petitioner

1543argued at final hearing that neither Policy A8.19 nor Policy

1553A8.20 is "in compliance" because both are internally

1561inconsistent with Policy A7.2. See Section 163.3177(2). To

1569the contrary, Policy A8.19 and Policy A8.20 clearly are not

1579inconsistent with Policy A7.2. Instead, this argument

1586actually just begs Petitioner's other arguments as to why

1595annexations permitted under Policy A8.19 and Policy A8.20

1603allegedly are unlawful and why the policies therefore are not

"1613in compliance."

1615Pertinent "Compliance" Requirements

161813. Section 163.3177(6)(h)1. requires, in pertinent

1624part, that the ICE include:

1629An intergovernmental coordination element

1633showing relationships and stating

1637principles and guidelines to be used in the

1645accomplishment of coordination of the

1650adopted comprehensive plan with the plans

1656of school boards and other units of local

1664government providing services but not

1669having regulatory authority over the use of

1676land, with the comprehensive plans of

1682adjacent municipalities, the county,

1686adjacent counties, or the region, and with

1693the state comprehensive plan, as the case

1700may require and as such adopted plans or

1708plans in preparation may exist. This

1714element of the local comprehensive plan

1720shall demonstrate consideration of the

1725particular effects of the local plan, when

1732adopted, upon the development of adjacent

1738municipalities, the county, adjacent

1742counties, or the region, or upon the state

1750comprehensive plan, as the case may

1756require.

1757a. The intergovernmental coordination

1761element shall provide for procedures to

1767identify and implement joint planning

1772areas, especially for the purpose of

1778annexation, municipal incorporation, and

1782joint infrastructure service areas.

1786Section 163.3177(6)(h)4. requires of adoption plan amendments

1793implementing these requirements by December 31, 1999, but no

1802party has raised the failure to meet the deadline as being a

1814reason why the policies in question are not "in compliance."

182414. Section 163.3177(10)(b) states in pertinent part:

"1831Intergovernmental coordination, as set forth in paragraph

1838(6)(h), shall be utilized to the extent required to carry out

1849the provisions of chapter 9J-5, Florida Administrative Code."

185715. Florida Administrative Code Rule 9J-5.015 states in

1865pertinent part: "It is the purpose of the intergovernmental

1874coordination element to . . . determine and respond to the

1885needs for coordination processes and procedures with adjacent

1893local governments . . .." (All rules cited are Florida

1903Administrative Code rules.)

190616. Rule 9J5 -5.015(3)(c)4. requires the

1912intergovernmental coordination element (ICE) of the

1918comprehensive plan to "contain one or more policies for each

1928objective which address programs, activities, or procedures

1935for: [t]he coordination of planning activities mandated by

1943the various elements of the comprehensive plan with other

1952local governments . . . [and] [r] esolving annexation issues

1962. . .." (Emphasis added.)

1967Policy A8.19 Arguments

197017. Petitioner makes essentially four arguments why

1977Policy A8.19 is not "in compliance." Petitioner's first

1985argument is that the policy itself does not identify the Joint

1996Planning Areas ( JPAs), especially the first (annexation) JPA,

2005either by mapping or some other similarly definitive means.

2014Petitioner's second (and related) argument is that paragraph

2022(3) of the policy permits deferral of identification (as well

2032as implementation) of the JPAs to interlocal agreements

2040between the City and County, in lieu of incorporation in the

2051comprehensive plans of the City and County. Petitioner's

2059third argument is that, by requiring establishment of the

2068annexation JPA only in areas "where annexation is likely to

2078occur during the planning period," Policy A8.19 permits

2086annexations to occur outside that JPA. Finally, Petitioner

2094argues that the phrase, "where annexation is likely to occur,"

2104is too vague.

2107Petitioner's First Two Arguments

211118. Petitioner's first two arguments are interwoven and

2119difficult to unravel and understand independent from one

2127another; the same can be said of the counter-arguments of DCA

2138and the City. For that reason, it is concluded that these

2149disputed issues are best considered together as a single

2158argument.

215919. Petitioner initially seemed to argue that Section

2167163.3177(6)(h)1.a. required the JPAs to be identified in

2175Policy A8.19 itself. Ultimately, at the end of its PRO,

2185Petitioner conceded that, even if Policy A8.19 deferred

2193identification and implementation of the JPAs, the policy

2201still would be "in compliance" if not for the option in

2212paragraph (3) of the policy for subsequent identification and

2221implementation through interlocal agreement, in lieu of

2228incorporation in the comprehensive plans of the City and

2237County.

223820. In support of its argument, Petitioner cited other

2247parts of Chapter 163 containing requirements for

2254identification of areas or places. See , e.g. , Section

2262163.3177(6)(a) and (d). Petitioner also cited the Final

2270Order, Dept. of Community Affairs, et al., v. Collier County,

2280et al. , 99 E.R.F.A.L.R. 259 (Admin. Comm'n, June 22, 199 9)(the

2291Collier County Final Order), adopting Recommended Order, DOAH

2299Case No. 98 -0324GM, entered March 19, 1999. In the Collier

2310County Final Order, the EAR (Evaluation and Appraisal Report)-

2319based comprehensive plan amendments in issue failed to map or

2329otherwise definitively identify "land use categories in which

2337public schools are an allowable use" notwithstanding the

2345requirement in Section 163.3177(6)(a) that the Future Land Use

2354Element "clearly identify" those land use categories.

2361Instead, identification of those land use categories was

2369deferred to interlocal agreement between the County and School

2378Board. As stated in Finding 17 of the Recommended Order in

2389that case:

2391In place of regulating school uses like

2398other land uses-- i.e. , in the Plan--the

2405County instead has elected to resolve

2411school-siting issues through another means-

2416- i.e. , an Interlocal Agreement, which is

2423mentioned in Sanitary Sewer Policy 1.2.6.

2429However, the use of the Interlocal

2435Agreement, rather than the Plan, attenuates

2441public participation, precludes plan

2445challenges by the public or DCA under

2452Chapters 163 and 9J-5, and fails to ensure

2460that the two parties will site schools

2467consistent with the minimum criteria of

2473Chapters 163 and 9J-5.

247721. Petitioner also cites Section 163.3194(4)(b), which

2484states: "It is the intent of this act [ i.e. , Part II of

2497Chapter 163] that the comprehensive plan set general

2505guidelines and principles concerning its purposes and contents

2513and that this act shall be construed broadly to accomplish its

2524stated purposes and objectives." Petitioner argues that the

"2532purposes and objectives" of Part II of Chapter 163 cannot be

2543met if the JPAs are not identified and implemented either in

2554Policy A8.19 itself or through incorporation in the

2562comprehensive plans of the City and County.

256922. Petitioner also points to the rule of statutory

2578interpretation that related statutes should be read in pari

2587materia and harmonized so that proper effect is given to all

2598related statutes. See Golf Channel, Inc. v. Martin Jenkins ,

2607752 So. 2d 561 , 564 (Fla. 2000); Dept. of Revenue v. Stafford ,

2619646 So. 2d 803 (Fla. 4th DCA 1994). Petitioner argues that

2630the best way to comply with those rules of statutory

2640construction would be to require the JPAs to be identified and

2651implemented either in Policy A8.19 itself or through

2659incorporation in the comprehensive plans of the City and

2668County.

266923. DCA and the City contend that the language of

2679Section 163.3177(6)(h)1.a. is clear and unambiguous in only

2687requiring " procedures to identify and implement joint planning

2695areas." (Emphasis added.) In arguing that identification and

2703implementation of the JPAs need not be incorporated in either

2713Policy A8.19 itself or in a subsequent amendment to the

2723comprehensive plans of the City and County, they cite to other

2734basic rules of statutory interpretation. "[W]hen the language

2742of a statute is unambiguous and conveys a clear and ordinary

2753meaning, there is no need to resort to other rules of

2764statutory construction." Starr Tyme, Inc. v. Cohen , 659

2772So. 2d 1064, 1067 (Fla. 1995 ). In those instances, the

2783language of a statute should be given its plain and ordinary

2794meaning. See Smith v. Crawford , 645 So. 2d 513 (Fla. 1st DCA

28061994). Statutory language is not assumed to be superfluous;

2815meaning should be given to all words and phrases contained in

2826a statute. See Terrinoni v. Westward Ho! , 418 So. 2d 1143

2837(Fla. 1st DCA 1982). Similarly, courts may not insert words

2847or phrases in a statute that to all appearances were not in

2859the mind of the legislature when the law was enacted. See

2870Rebich v. Burdine's and Liberty Mut. Ins. Co. , 417 So. 2d 284

2882(Fla. 1st DCA 1982).

288624. DCA and the City also argue that Petitioner fails to

2897take into account Section 163.3171, which they assert

2905specifically authorizes the interlocal agreement option in

2912Policy A8.19(3).

291425. Section 163.3171 provides in pertinent part:

2921(1) A municipality shall exercise

2926authority under this act [ i.e. , Part II of

2935Chapter 163, which is entitled the "Local

2942Government Comprehensive Planning and Land

2947Development Regulation Act"] for the total

2954area under its jurisdiction.

2958Unincorporated areas adjacent to

2962incorporated municipalities may be included

2967in the area of municipal jurisdiction for

2974the purposes of this act if the governing

2982bodies of the municipality and the county

2989in which the area is located agree on the

2998boundaries of such additional areas, on

3004procedures for joint action in the

3010preparation and adoption of the

3015comprehensive plan, on procedures for the

3021administration of land development

3025regulations or the land development code

3031applicable thereto, and on the manner of

3038representation on any joint body or

3044instrument that may be created under the

3051joint agreement. Such joint agreement

3056shall be formally stated and approved in

3063appropriate official action by the

3068governing bodies involved.

3071* * *

3074(3) Combinations of municipalities

3078within a county, or counties, or an

3085incorporated municipality or municipalities

3089and a county or counties, or an

3096incorporated municipality or municipalities

3100and portions of a county or counties may

3108jointly exercise the powers granted under

3114the provisions of this act upon formal

3121adoption of an official agreement by the

3128governing bodies involved pursuant to law.

3134No such official agreement shall be adopted

3141by the governing bodies involved until a

3148public hearing on the subject with public

3155notice has been held by each governing body

3163involved. The general administration of

3168any joint agreement shall be governed by

3175the provisions of s.163.01 except that when

3182there is conflict with this act the

3189provisions of this act shall govern.

319526. Harmonizing all of these related statutes, it is

3204concluded that Section 163.3171(1) does authorize the use of

3213interlocal agreements to identify and implement joint planning

3221areas, but only to the extent of designating the portions of

3232the unincorporated county in which joint city/county planning

3240will take place and establishing "procedures for joint action

3249in the preparation and adoption of the comprehensive plan, on

3259procedures for the administration of land development

3266regulations or the land development code applicable thereto,

3274and on the manner of representation on any joint body or

3285instrument that may be created under the joint agreement."

3294Similarly, Section 163.3171(3) only authorizes the City and

3302County to "jointly exercise the powers granted under the

3311provisions of this act [ i.e. , Part II of Chapter 163] upon

3323[ i.e. , after ] formal adoption of an official agreement by the

3335governing bodies involved pursuant to law." (Emphasis and

3343bracketed explanation added.) This provision was not intended

3351to authorize subsequent planning within the jurisdiction of a

3360joint planning area to be conducted through interlocal

3368agreement. To the contrary, the last sentence of Section

3377163.3171(3) would require such joint planning to meet the

3386ordinary requirements of "this act," i.e. , Part II of Chapter

3396163. See Pinellas County v. City of Gulfport , 458 So. 2d 436,

3408438 (Fla. 2d DCA 1984). Cf. also Rules 9J-5.005(7)( i), 9J-

341911.004(2)(a)4.-5., and 9J-11.006(1)(a)9. and (b).

342427. Applying these statutory interpretations to this

3431case, Policy A8.19(3) does not appear to limit the JPA

3441interlocal agreements to mere identification and

3447implementation of the JPAs, with subsequent joint planning

3455policies to be adopted in accordance with the ordinary

3464requirements of Part II of Chapter 163. To the contrary, the

3475policy appears to authorize adoption of joint planning

3483policies through interlocal agreement(s), in lieu of

3490incorporation in the comprehensive plans of the City and

3499County. To that extent, Policy A8.19(3) is not "in

3508compliance."

"3509Where Annexations Are Likely to Occur" Arguments

351628. Petitioner's next argument is that Policy A8.19 is

3525not "in compliance" because, by requiring establishment of the

3534first (annexation) JPA only in the "area where annexation is

3544likely to occur during the planning period," Policy A8.19

3553permits annexations to occur outside the JPA. Petitioner also

3562argues that the language used to describe the annexation JPA

3572is too vague to be "in compliance" with Sections

3581163.3177(6)(h)1.a. and 163.3171.

358429. As for the "vagueness" issue, Petitioner never

3592raised the issue in its Petition for Formal Administrative

3601Hearing. Although mentioned in the Prehearing Stipulation,

3608the issue was omitted from that document's joint statement of

"3618the mixed issues of law and fact which remain to be

3629litigated." For those reasons, the issue was waived. See

3638Final Order, Heartland Environmental Council v. Dept. of

3646Community Affairs , 96 E.R.F.A.L.R. 185 (Dept. Comm. Affairs,

3654Nov. 25, 1996), adopting in part and modifying Recommended

3663Order, DOAH Case No. 94-2095GM, entered October 15, 1996.

367230. If the "vagueness" issue were considered, it would

3681be concluded that Petitioner did not prove beyond fair debate

3691that Policy A8.19 is not "in compliance" because it is too

3702vague. Section 163.3177(6)(h)1. requires the City to adopt an

"3711intergovernmental coordination element showing relationships

3716and stating principles and guidelines to be used in the

3726accomplishment of coordination of the adopted comprehensive

3733plan" with the plan of Martin County. It is concluded that

3744the phrase "area where annexations are likely to occur during

3754the planning period" is clear enough to guide establishment of

3764the annexation JPA.

376731. Petitioner's "vagueness" argument is tied to and

3775dependent on what appears to be Petitioner's main argument

3784regarding the "likely to occur" language--that Policy A8.19 is

3793not "in compliance" because it does not require the annexation

3803JPA to include all areas where annexations could possibly

3812occur, so that annexations outside the annexation JPA would be

3822possible.

382332. Annexation is controlled by Chapter 171 of the

3832Florida Statutes. Chapter 171 authorizes municipalities to

3839annex land under the terms of the statute. See SCA Services

3850of Florida, Inc. v. City of Tallahassee , 418 So. 2d 1148, 1150

3862(Fla. 1st DCA 1982), rev. denied , 427 So. 2d 737 (Fla. 1983).

3874In effect, Petitioner's argument is that Section

3881163.3177(6)(h)1.a. supersedes and controls to the extent of

3889conflict with Chapter 171 and that Section 163.3177(6)(h)1.a.

3897requires joint planning before all annexations.

390333. If Petitioner's argument were accepted, the City

3911would be required to predict with absolute certainty where all

3921annexations, including voluntary annexations, will occur.

3927Such predictive ability would be difficult, if not practically

3936impossible. Without the perfect ability to make such

3944predictions, the only way to be assured that all annexations

3954will occur within the annexation JPA would be for the JPA to

3966cover the entire unincorporated county. That could require

3974unnecessary and wasteful planning. It is concluded that it is

3984unreasonable to interpret Section 163.3177(6)(h)1.a. so as to

3992require possibly illogical and wasteful planning.

399834. It also is noted that Section 163.3177(6)(h)1.a.

4006addresses municipal incorporation and joint infrastructure

4012service areas, as well as annexation. Yet, as Petitioner

4021agrees, municipal incorporation clearly is authorized outside

4028a JPA. Similarly, the City and County already have entered

4038into interlocal agreements for joint infrastructure service

4045areas. Although it cannot be ascertained at this time whether

4055those joint infrastructure service areas will be within either

4064of the two JPAs to be established under Policy A8.19,

4074Petitioner does not contend that they are illegal.

4082Notwithstanding Petitioner's arguments to the contrary, it is

4090logical to conclude that annexations under Chapter 171 also

4099are not illegal because they are outside the annexation JPA in

4110whole or in part.

411435. Petitioner also cites Section 163.3211, which is

4122entitled "Conflict with other statutes," and which states:

4130Where this act may be in conflict with any

4139other provision or provisions of law

4145relating to local governments having

4150authority to regulate the development of

4156land , the provisions of this act shall

4163govern unless the provisions of this act

4170are met or exceeded by such other provision

4178or provisions of law relating to local

4185government, including land development

4189regulations adopted pursuant to chapter 125

4195or chapter 166. Nothing in this act is

4203intended to withdraw or diminish any legal

4210powers or responsibilities of state

4215agencies or change any requirement of

4221existing law that local regulations comply

4227with state standards or rules.

4232(Emphasis added.) But, as emphasized language suggests, this

4240statute does not apply to Chapter 171, which deals with

4250annexations, not regulation of land development.

425636. Finally, it is noted that Policy A8.19 only provides

4266for the establishment of the annexation JPA. It does not

4276annex land or expressly authorize annexation outside the

4284annexation JPA. If land outside the annexation JPA is annexed

4294in the future, a petition for certiorari review could be filed

4305under Section 171.081 to assert a claim that such an

4315annexation "does not meet the requirements established for

4323annexation."

432437. For these reasons, it is concluded that the language

4334in Policy A8.19 providing for the establishment of the

4343annexation JPA in the "area where annexation is likely to

4353occur during the planning period" is "in compliance."

4361Policy A8.20

436338. The first part of Petitioner's argument that Policy

4372A8.20 is not "in compliance" is based on the policy's

4382requirement that the joint procedure to be adopted by the City

4393and County under the policy use the "joint plans prepared for

4404the JPA's established under Policy A8.19 to the extent they

4414apply to the particular annexation area." This part of

4423Petitioner's argument on Policy A8.20 is primarily based on

4432Policy A8.19's failure to require the annexation JPA to

4441include all areas where annexations could possibly occur.

4449This argument already has been rejected in Conclusions of Law

445937, supra . However, to the extent that Policy A8.20 relies on

4471Policy A8.19, Policy A8.20 is not "in compliance" to the

4481extent that Policy A8.19 is not. See Conclusions of Law 27,

4492supra .

449439. Petitioner also argues that, while Policy A8.20

4502requires establishment of "a joint procedure to facilitate

4510annexations," to include four listed items, it does not

4519prohibit the joint procedure from including additional items

4527and does not expressly require incorporation of the joint

4536procedure in a comprehensive plan amendment.

454240. It must be kept in mind that, unlike Policy A8.19,

4553Policy A8.20 was not adopted under Section 163.3171 to meet

4563the requirements of Section 163.3177(6)(h)1.a.-- i.e. , it does

4571not provide for establishment of a joint planning area, and

4581its operation is not limited to the jurisdiction of the JPAs

4592addressed in Policy A8.19 (in particular, the annexation JPA.)

4601As a result, Sections 163.3171 and 163. 3177(6)(h)1.a. do not

4611operate to require incorporation of the joint procedure to be

4621adopted in response to Policy A8.20 in the comprehensive plans

4631of the City and County.

463641. In addition, Section 163.3177(6)(h)1. only requires

4643the ICE to "[show] relationships and [state] principles and

4652guidelines to be used in the accomplishment of coordination of

4662the adopted comprehensive plan" with the plan of Martin

4671County. Rule 9J5 -5.015(3)(c)4. requires the intergovernmental

4678coordination element (ICE) of the comprehensive plan to

"4686contain one or more policies for each objective which address

4696programs, activities, or procedures for: [t]he coordination

4703of planning activities mandated by the various elements of the

4713comprehensive plan with other local governments . . . [and]

4723[r] esolving annexation issues . . .." (Emphasis added.) ICE

4733policies are adequate if they meet these statutory and rule

4743criteria, so as to make it possible to determine whether

4753subsequent coordination efforts are consistent with the

4760policies. Part II of Chapter 163 does not require all

4770intergovernmental coordination to be accomplished through

4776comprehensive plan amendments; nor does it prohibit additional

4784coordination beyond what is required by ICE policies. For

4793these reasons, it is concluded that Policy A8.20 is "in

4803compliance," except to the extent of its reliance on Policy

4813A8.19.

4814RECOMMENDATION

4815Based upon the foregoing Findings of Fact and Conclusions

4824of Law, and it is

4829RECOMMENDED that, after further proceedings in accordance

4836with Section 163.3184(9)(b), the Department of Community

4843Affairs:

48441. Determine Policy A8.19 not "in compliance";

48512. Determine Policy A8.20 not "in compliance" to the

4860extent that it relies on Policy A8.19; and

48683. Submit this Recommended Order to the Administration

4876Commission to take final action and, in accordance with

4885Section 163.3184(11)(a), specify as remedial action that the

4893City of Stuart amend Policy A8.19 to require joint planning

4903policies for the JPAs to be adopted by incorporation in the

4914comprehensive plans of the City and Martin County.

4922DONE AND ENTERED this 11th day of January, 2001, in

4932Tallahassee, Leon County, Florida.

4936_____________________________

4937J. LAWRENCE JOHNSTON

4940Administrative Law Judge

4943Division of Administrative Hearings

4947The DeSoto Building

49501230 Apalachee Parkway

4953Tallahassee, Florida 32399-3060

4956(850) 488-9675 SUNCOM 278-9675

4960Fax Filing (850) 921-6847

4964www.doah.state.fl.us

4965Filed with the Clerk of the

4971Division of Administrative Hearing

4975this 11th day of January, 2001.

4981COPIES FURNISHED:

4983Terrell K. Arline, Esquire

4987Legal Director

49891000 Friends of Florida

4993926 East Park Avenue

4997Post Office Box 5948

5001Tallahassee, Florida 32301

5004Shaw P. Stiller, Esquire

5008Department of Community Affairs

50122555 Shumard Oak Boulevard

5016Tallahassee, Florida 32399-2100

5019Robert C. Apgar, Esquire

5023Yeline Goin, Esquire

5026320 Johnston Street

5029Tallahassee, Florida 32303

5032Steven M. Seibert, Secretary

5036Department of Community Affairs

50402555 Shumard Oak Boulevard, Suite 100

5046Tallahassee, Florida 32399-2100

5049Cari L. Roth, General Counsel

5054Department of Community Affairs

50582555 Shumard Oak Boulevard, Suite 325A

5064Tallahassee, Florida 32399-2100

5067NOTICE OF RIGHT TO SUBMIT EXCEPTIONS

5073All parties have the right to submit written exceptions within 15

5084days from the date of this Recommended Order. Any exceptions to

5095this Recommended Order should be filed with the agency that will

5106issue the final order in this case.

Select the PDF icon to view the document.
PDF
Date
Proceedings
PDF:
Date: 02/08/2002
Proceedings: BY ORDER OF THE COURT: (that appellee Department of Community Affairs` unopposed filed January 31, 2002, for continuance and oral argument is granted). filed.
PDF:
Date: 06/20/2001
Proceedings: Letter to DOAH from the District Court of Appeal filed. DCA Case No.4D01-2320.
PDF:
Date: 06/13/2001
Proceedings: Notice of Appeal (filed by T. Arline).
PDF:
Date: 05/21/2001
Proceedings: Final Order filed.
PDF:
Date: 05/18/2001
Proceedings: Agency Final Order
PDF:
Date: 02/06/2001
Proceedings: Order Extending Time to File Exceptions filed by S. Seibert.
PDF:
Date: 01/11/2001
Proceedings: Recommended Order cover letter identifying hearing record referred to the Agency sent out.
PDF:
Date: 01/11/2001
Proceedings: Recommended Order issued. (hearing held October 9, 2000)
PDF:
Date: 01/09/2001
Proceedings: Recommended Order
PDF:
Date: 12/13/2000
Proceedings: City of Stuart`s Response to Motion for Extension of Time to File Proposed Recommended Order filed.
PDF:
Date: 12/11/2000
Proceedings: Proposed Recommended Order of 1000 Friends of Florida, Inc. filed.
PDF:
Date: 12/11/2000
Proceedings: Motion for Extension of Time to File Proposed Recommended Order filed by Petitioner.
PDF:
Date: 12/08/2000
Proceedings: Department of Community Affairs` Proposed Recommended Order (filed via facsimile).
PDF:
Date: 12/08/2000
Proceedings: City of Stuart`s Proposed Recommended Order filed.
PDF:
Date: 11/21/2000
Proceedings: Order Granting Extension of Time issued.
PDF:
Date: 11/20/2000
Proceedings: Respondent City of Stuart`s Unopposed Motion for Extension of Time to File Proposed Recommended Orders filed.
PDF:
Date: 11/02/2000
Proceedings: Notice of Filing - Transcript filed.
Date: 11/02/2000
Proceedings: Transcript (Volume 1) filed.
Date: 10/09/2000
Proceedings: CASE STATUS: Hearing Held; see case file for applicable time frames.
PDF:
Date: 10/06/2000
Proceedings: (Joint) Prehearing Stipulation (filed via facsimile).
PDF:
Date: 10/03/2000
Proceedings: City of Stuart`s Response to Petitioner`s Request to Produce Documents (filed via facsimile).
PDF:
Date: 09/06/2000
Proceedings: Department of Community Affairs` Notice of Method of Recordation filed.
PDF:
Date: 09/05/2000
Proceedings: Request to Produce Documents (Petitioner) filed.
PDF:
Date: 08/23/2000
Proceedings: Notice of Address Change (R. Apgar) filed.
PDF:
Date: 08/09/2000
Proceedings: Order of Pre-hearing Instructions issued.
PDF:
Date: 08/09/2000
Proceedings: Notice of Hearing issued (hearing set for October 9, 2000; 9:00 a.m.; Tallahassee, FL).
PDF:
Date: 08/07/2000
Proceedings: Joint Response to Initial Order (filed via facsimile).
Date: 07/31/2000
Proceedings: Initial Order issued.
PDF:
Date: 07/26/2000
Proceedings: Notice of Intent to Find the City of Stuart Comprehensive Plan Amendment in Compliance (filed via facsimile).
PDF:
Date: 07/26/2000
Proceedings: Petition for Formal Administrative Hearing (filed via facsimile).
PDF:
Date: 07/26/2000
Proceedings: Agency referral (filed via facsimile)

Case Information

Judge:
J. LAWRENCE JOHNSTON
Date Filed:
07/26/2000
Date Assignment:
09/26/2000
Last Docket Entry:
02/08/2002
Location:
Tallahassee, Florida
District:
Northern
Agency:
ADOPTED IN PART OR MODIFIED
Suffix:
GM
 

Related DOAH Cases(s) (2):

Related Florida Statute(s) (8):

Related Florida Rule(s) (1):