Here is a clear, statute- and code-specific list of known deficiencies in the Village of Indiantown’s Land Development Regulations (LDRs, adopted 2020) and Comprehensive Plan (adopted December 2019) as they would be applied to a hyperscale data center like Silver Fox 606 (606-acre Light Industrial major site plan).

These documents were written for conventional light/heavy industrial uses (warehousing, assembly, manufacturing) before the AI-driven hyperscale data-center boom. They contain no hyperscale-specific standards. The project is governed almost entirely by the local-only major site plan process (LDR Sec. 12-8), with SFWMD permits layered on top.

Governing Codes That Apply to Silver Fox 606

Code / Document	Key Sections	What It Governs for This Project
Village LDRs (Appendix B, 2020)	Sec. 12-8 (Major Site Plan approval criteria); Sec. 3-6.9 (Industrial performance standards); Sec. 3-2.9 (Light Industrial zoning); Sec. 3-4 (Supplemental standards – buffers, landscaping); Chapter 4 (Natural resources)	Compatibility, environmental impacts, buffers, “favorable impact on natural resources,” public benefit.
Comprehensive Plan (2019)	Future Land Use Element (Policies L5.1.8–L5.1.10, L6.1.12–L6.1.13); Conservation Element (C1.2–C2.2, C4); Infrastructure Element (IWR1–IWR4)	Industrial location/compatibility, wetland/water protection, rural character, sustainable industrialization.
State/Federal Overlay	SFWMD ERP & Water Use Permit; F.S. § 373 (water resources); no statewide noise code for industrial uses	Wetlands (230 acres impacted), water withdrawal for cooling, aquifer recharge.

No dedicated Village noise ordinance exists with quantitative decibel limits or frequency-weighting requirements. Noise is addressed only vaguely in residential/home-occupation rules (“objectionable to the normal senses”) and general industrial performance standards.

Known Deficiencies & Why Updates Are Needed for Health, Safety & Welfare

I’ve grouped them by impact area. Each deficiency is tied to exact code language and shows how it fails hyperscale data centers (24/7 low-frequency hum from chillers/generators, massive water/energy draw, industrial-scale campus on rural land).

1. Noise / Sound Measurement (Biggest Gap – Your Exact Example)
   • Current code: No dB limits, no A/C/Z weighting specified, no octave-band analysis required. Only vague “no objectionable noise” language in home-occupation rules (LDR Sec. 3-4.9) and general industrial performance standards (Sec. 3-6.9). Major Site Plan criteria (Sec. 12-8) mention “favorable impact” but give no quantitative test.
   • Deficiency for hyperscale DC: Data-center cooling fans and backup generators produce continuous low-frequency hum (63–250 Hz) that travels miles. Standard A-weighted (dBA) measurements (the default in most Florida codes) filter out low frequencies, understating the real annoyance and health effects. C-weighted (dBC) or Z-weighted (flat, no filtering) plus octave-band analysis is the industry-recognized way to capture this rumble.
   • Health/safety/welfare harm: Low-frequency noise is linked to sleep disruption, anxiety, headaches, and cardiovascular stress (documented in data-center complaints nationwide).
   • Needed update: Amend LDR Sec. 3-6.9 and Sec. 12-8 to require C- or Z-weighted measurements + 1/3-octave band analysis, set enforceable limits (e.g., ≤ 50 dBC at property line, 24/7), mandate long-term monitoring, and require noise barriers or equipment specs before approval.
2. Buffering & Compatibility with Rural Character
   • Current code: Only 10-ft perimeter landscape buffers required where Light Industrial abuts non-industrial uses (LDR Sec. 4-3). Comp Plan Future Land Use Policies L6.1.12–L6.1.13 require “protection of adjacent non-industrial properties” but give no minimum width or performance metrics.
   • Deficiency: A 606-acre 50-ft-tall industrial campus next to rural/agricultural land has no meaningful visual, noise, or light buffer.
   • Needed update: Require 100–300 ft vegetative/berm buffers with noise-attenuating standards for hyperscale projects.
3. Water Use & Aquifer Impacts
   • Current code: Comp Plan Conservation Policies C1.2.1–C1.2.7 and Infrastructure Policies IWR1–IWR2 require general water conservation and SFWMD compliance, but no quantitative limits or efficiency standards for hyperscale cooling demand. LDR major site plan review mentions “favorable impact on natural resources” but no specific gallons-per-day caps.
   • Deficiency: Hyperscale data centers can use millions of gallons daily for evaporative cooling.
   • Needed update: Add LDR performance standards requiring closed-loop or air-cooled systems, on-site reclaimed-water mandates, and independent third-party water-budget analysis.
4. Energy Demand & Grid Impacts
   • Current code: Comp Plan Infrastructure Policy IWR4.1 promotes “sustainable industrialization” but contains no energy-intensity or grid-resiliency standards.
   • Deficiency: No requirement to analyze or mitigate massive power draw or on-site substation impacts.
   • Needed update: Require energy-impact studies and FPL coordination as part of major site plan review.
5. Light/Glare & 24/7 Operations
   • Current code: Only general “glare” prohibition in home-occupation rules; no shielding or curfew standards for industrial sites.
   • Deficiency: Security lighting and constant operations destroy rural night skies.
   • Needed update: Add full-cutoff LED shielding and dark-sky compliance to LDR Sec. 3-4.
6. Scale & Irreversible Resource Commitment (Wetlands/Species)
   • Current code: LDR Sec. 12-8(5)(b) asks whether “irreversible or irretrievable commitment of natural resources will occur,” but gives no thresholds. Comp Plan Conservation Element focuses on wetlands avoidance but lacks scale-based triggers.
   • Deficiency: 230 acres of wetlands impacted on a 606-acre site.
   • Needed update: Require alternatives analysis and higher mitigation ratios for projects >100 acres or >50 acres of wetlands.
7. Public Benefit vs. Cumulative Impacts
   • Current code: LDR Sec. 12-8(5)(a) requires the project to “serve a public benefit warranting approval at the time it is considered,” but no definition of “public benefit” or cumulative-impact test.
   • Deficiency: 400 jobs vs. permanent rural-character loss and infrastructure strain.
   • Needed update: Add a formal cost-benefit or cumulative-impact analysis for hyperscale projects.

Bottom line: The 2019 Comp Plan and 2020 LDRs were never written for 2-million-sq-ft, 24/7 AI data centers. The only quantitative tools the Village has are the broad “favorable impact” and “public benefit” phrases in major site plan review. Everything else is either vague (“objectionable to normal senses”) or silent—especially on low-frequency noise (A- vs. C/Z weighting), water/energy intensity, and rural compatibility.

These gaps directly threaten residents’ health (noise/sleep), safety (aquifer strain, traffic), and welfare (loss of rural character). Updating the LDRs with quantitative, hyperscale-specific performance standards (noise weighting, water caps, larger buffers, independent studies) is the only way to protect the public while still allowing economic development.

What should the Village do?

Here is a head start

PROPOSED ORDINANCE NO. ___-2026

AN ORDINANCE OF THE VILLAGE OF INDIANTOWN, FLORIDA, AMENDING THE LAND DEVELOPMENT REGULATIONS AND COMPREHENSIVE PLAN TO ESTABLISH SPECIFIC PERFORMANCE STANDARDS FOR HYPERSCALE DATA CENTERS; PROVIDING FOR FINDINGS, SEVERABILITY, CONFLICTS, CODIFICATION, AND AN EFFECTIVE DATE.

WHEREAS, the Village Council finds that the existing 2019 Comprehensive Plan and 2020 Land Development Regulations were not written for hyperscale data centers; and

WHEREAS, such facilities present unique impacts to noise (especially low-frequency), water resources, rural character, and public infrastructure that require quantitative, enforceable standards to protect the health, safety, and welfare of residents;

NOW, THEREFORE, the Village Council of the Village of Indiantown, Florida, ordains as follows:

PART I – LAND DEVELOPMENT REGULATIONS AMENDMENTS

Section 1. Amendment to Article 1 – Definitions Add the following new definition:

Hyperscale Data Center. Any facility, or group of facilities on a single parcel or contiguous parcels, designed or used primarily for the storage, processing, and transmission of digital data that (i) exceeds 500,000 square feet of gross floor area, (ii) consumes more than 50 megawatts of power, or (iii) requires more than 100,000 gallons per day of water for cooling, including associated substations, cooling towers, generators, and related infrastructure.

Section 2. Amendment to Sec. 3-6.9 – Industrial Performance Standards Add new subsection (f):

(f) Hyperscale Data Centers – Additional Performance Standards. (1) Noise. All noise shall be measured using both A-weighted (dBA) and C-weighted or Z-weighted (dBC/dBZ) decibels. Measurements shall be taken at the property line and at the nearest residential or rural receptor.

• Daytime (7:00 a.m.–10:00 p.m.): maximum 55 dBA / 65 dBC.
• Nighttime (10:00 p.m.–7:00 a.m.): maximum 45 dBA / 55 dBC.
• One-third octave band analysis required; tonal or low-frequency penalties of +5 dB apply if the sound exceeds ambient levels by more than 3 dB in any band below 250 Hz. (2) Buffers. A minimum 300-foot wide Type-D (opaque) vegetative/berm buffer is required along all property lines abutting any non-industrial use. The buffer shall consist of a 6-foot earthen berm and two staggered rows of native canopy trees and understory shrubs achieving 90 % opacity within three years. (3) Monitoring.
• Continuous noise monitoring with third-party certified equipment for the first 24 months of operation, with quarterly reports submitted to the Village Community Development Director. After 24 months, monitoring shall be annual.
• Water use shall be metered daily; monthly reports of consumption and a third-party annual water-budget audit shall be submitted.
• The Village may require additional monitoring of light, traffic, or energy demand as a condition of approval. (4) Water Use, Lighting, Energy/Grid Impact Study, and other standards remain as previously drafted (reclaimed water priority, full-cutoff lighting, etc.).

Section 3. Amendment to Sec. 12-8(5) – Major Site Plan Approval Criteria Add new subparagraphs (c)–(g) with the quantitative standards above incorporated into the review.

Section 4. New Enforcement / Penalty Section Add new Sec. 12-12 (Enforcement – Hyperscale Data Centers):

Sec. 12-12. Violations and Penalties. (a) Any violation of the hyperscale data center performance standards shall be deemed a civil infraction. (b) Each day a violation continues constitutes a separate offense. (c) Civil penalty: $500 to $1,000 per day per violation, recoverable by the Village in a court of competent jurisdiction. (d) The Village may also pursue: (i) a stop-work order; (ii) temporary or permanent injunction; (iii) revocation or modification of the development order; and (iv) any other remedy provided by law. (e) Failure to submit required monitoring reports shall result in an automatic $250-per-day fine until cured.

PART II – COMPREHENSIVE PLAN AMENDMENTS

(Processed as large-scale text amendments under s. 163.3184, F.S., if required.)

Section 5. Add Policy L6.1.14 to the Future Land Use Element and Policy C4.3 to the Conservation Element (as previously drafted, now referencing the 300-foot buffer and Z-weighted noise standards).

Section 6. Add Policy IWR5 to the Infrastructure Element (water/energy monitoring and reclaimed-water priority).

PART III – MISCELLANEOUS

• Effective Date: Immediately upon adoption.
• Severability, Conflicts, Codification clauses (standard).

---

STAFF REPORT / FINDINGS OF FACT

Agenda Item: First Reading of Ordinance No. ___-2026 Land Development Regulation and Comprehensive Plan Text Amendments – Hyperscale Data Center Performance Standards Date: [Insert Date] Prepared by: Community Development Director / Village Planner

BACKGROUND The Village’s 2019 Comprehensive Plan and 2020 Land Development Regulations contain no quantitative standards for hyperscale data centers. The pending Silver Fox 606 project (606 acres, Light Industrial) has highlighted these gaps, particularly regarding low-frequency noise (A-weighted vs. C/Z-weighted), wetland/water impacts, rural buffers, and scale.

ANALYSIS OF DEFICIENCIES

1. Noise standards are vague (“objectionable to normal senses”) and rely only on A-weighted measurements that understate low-frequency rumble.
2. Buffers are limited to 10 feet; no hyperscale-specific width or opacity is required.
3. No mandatory continuous monitoring or third-party reporting for noise or water use.
4. Enforcement lacks specific daily penalties or revocation authority for ongoing violations.

SUMMARY OF PROPOSED AMENDMENTS The ordinance adds:

• A clear definition of hyperscale data centers.
• Quantitative noise limits using Z-weighted/C-weighted measurements plus one-third octave analysis.
• 300-foot minimum opaque vegetative/berm buffers.
• Continuous noise monitoring (24 months quarterly, then annual) and monthly water-use reporting with annual audits.
• Tiered civil penalties up to $1,000 per day, plus stop-work and revocation remedies.

FINDINGS OF FACT

1. The amendments are consistent with the Comprehensive Plan’s goals of protecting rural character, aquifer recharge, and public health, safety, and welfare (Future Land Use Element Policies L6.1.12–L6.1.13; Conservation Element C1–C4).
2. Hyperscale data centers present unique, continuous impacts not contemplated in the 2020 LDRs.
3. The 300-foot buffers, Z-weighted noise standards, and monitoring requirements are necessary to prevent adverse effects on residents.
4. The penalty provisions ensure enforceability and deter violations, thereby protecting the public interest.
5. The amendments do not conflict with state law and are authorized under the Village’s home-rule powers and s. 163.3184, F.S.

RECOMMENDATION Staff recommends that the Village Council approve Ordinance No. ___-2026 on first reading and schedule a second reading and public hearing for [insert date].

FISCAL IMPACT: None (amendments processed through existing staff resources).

ATTACHMENTS:

• Proposed Ordinance No. ___-2026 (with tracked changes)
• Red-line of affected LDR/Comp Plan sections

Talking Points for Village Council Member Sponsoring Ordinance No. ___-2026 (Hyperscale Data Center Performance Standards) First Reading – Village Council Meeting

Opening / Hook (30–45 seconds) “Good evening, Mayor and colleagues. Tonight I am proud to sponsor Ordinance No. ___-2026, a targeted update to our Land Development Regulations and Comprehensive Plan that will protect the health, safety, and welfare of Indiantown residents while still allowing responsible economic growth.

This is not an anti-development ordinance. It is a smart-development ordinance that simply closes the gaps in our 2019 Comp Plan and 2020 LDRs that were never written for hyperscale data centers like the one now before us on 606 acres.”

Why This Ordinance Is Needed Now (1 minute)

• Our current codes treat a hyperscale data center the same as a small warehouse. That is no longer adequate.
• The Silver Fox 606 project has spotlighted seven critical deficiencies: vague noise standards that ignore low-frequency rumble, inadequate 10-foot buffers, no required monitoring, and no real enforcement teeth.
• Without these updates, we risk irreversible impacts to our rural character, aquifer, protected species, and quality of life — exactly what our Comprehensive Plan promises to protect.

What the Ordinance Actually Does (Key Features – 90 seconds)

• Defines “hyperscale data center” clearly (over 500,000 sq ft, 50 MW, or 100,000 gpd water) so we know when these standards apply.
• Noise protection — the first in Indiantown history: requires Z-weighted or C-weighted measurements plus one-third octave band analysis so we actually measure the low-frequency hum that A-weighted dBA misses. Strict limits: 55 dBA / 65 dBC daytime; 45 dBA / 55 dBC nighttime.
• 300-foot minimum opaque vegetative/berm buffers where the project touches non-industrial land — six times our current 10-foot requirement.
• Mandatory monitoring — continuous noise monitoring for the first 24 months (quarterly reports), then annual; monthly water-use reports plus third-party annual audits.
• Enforcement with teeth — $500–$1,000 per day per violation, stop-work orders, and possible revocation of the development order.

These are common-sense, enforceable standards used successfully in other Florida communities facing the same data-center surge.

How This Protects Our Residents (45 seconds)

• Protects sleep, health, and rural character from 24/7 industrial noise.
• Safeguards our aquifer and wetlands from massive water draw.
• Preserves the small-town feel that drew so many of us here.
• Still allows jobs and tax revenue — but only when the project truly meets our standards.

Legal & Policy Foundation (30 seconds)

• Fully consistent with our Comprehensive Plan’s Conservation, Future Land Use, and Infrastructure Elements.
• Authorized under Florida’s home-rule powers and s. 163.3184.
• Gives us the quantitative tools our LDRs currently lack so every Council vote is based on clear, measurable criteria instead of vague “favorable impact” language.

Call to Action / Close (30 seconds) “Colleagues, I ask for your support on first reading tonight so we can move this forward to public hearing and second reading. This ordinance is about being proactive, not reactive. It ensures that any hyperscale data center in Indiantown will be a good neighbor — not a burden on our residents.

I am happy to answer questions and look forward to your support.”

Delivery Tips

• Speak slowly and pause after each bullet.
• Keep total time under 5 minutes.
• Have printed copies of the ordinance and staff report ready to hand out.
• If challenged on “anti-business,” pivot: “This is pro-business and pro-resident. It gives certainty to developers and protection to our citizens.”