Three NW Iowa Counties Slap One-Year Moratoriums on Data Centers After a 900-Acre Salix Annexation

Geography: Woodbury County, IA (FIPS 19193); Sioux County, IA (19167); Plymouth County, IA (19149) Technology: Data centers

What just happened

The Woodbury County Board of Supervisors voted unanimously to impose a one-year moratorium on data-center development in the unincorporated parts of the county. It is not an isolated act: Plymouth County and Sioux County have passed parallel moratoriums, making this a coordinated three-county response in northwest Iowa — the kind of clustered local action that tends to reset the siting map for a whole sub-region at once.

The common trigger is not a project any of the three counties can actually regulate. It is the City of Salix's annexation of roughly 900 acres tied to a potential MidAmerican Energy data center. Because the site sits inside an incorporated city's jurisdiction, the county moratoriums cannot touch the Salix project itself. As Supervisor Matthew Ung put it on the record: "So even though this isn't about Salix and it can't affect incorporated areas of cities, all three counties are passing moratoriums in response to what one city did."

In other words: a single municipal annexation has spooked three surrounding county boards into freezing data-center development on every acre they do control, while they write rules from scratch.

Why it matters

1. It's a moratorium wave, not a one-off. SitePath's structured tracker (SitePath's data-center dataset) currently logs 22 active data-center moratoriums and exactly one "moratorium wave" nationally. A coordinated three-county freeze in a single Midwest corridor is materially more significant than any one county's pause, and is a candidate to be promoted into SitePath's change feed and the wave count once verified.

2. It marks the Midwest / MidAmerican corridor as a new friction zone. Most of SitePath's data-center moratorium tracking has clustered in places like North Carolina (7 moratorium-active counties) and township-level actions. A hyperscale-scale load sniffing around MidAmerican Energy (Berkshire Hathaway Energy) territory in Iowa — historically a low-friction, cheap-power, wind-rich siting destination — is now generating defensive local zoning. That's a leading indicator worth watching across the rest of MidAmerican's Iowa footprint.

3. The jurisdictional gap is the story. The counties are reacting to a project they can't regulate, by restricting projects that don't yet exist. Expect (a) developers to favor annexation-into-city pathways precisely because they route around county boards, and (b) county-vs-city tension over who captures the tax base versus who absorbs the land-use externalities. This is the same annexation-arbitrage dynamic SitePath should be tracking wherever a city can pull farmland inside its limits.

4. The politics are split on the record. This was not a quiet vote. Resident Steve Corey framed it as protecting rural character: "This is agricultural land. This is a small community, and the people that live down there really do live there for that reason." Against him, Plumbers and Steamfitters union member Dean Bradham argued the economic upside: "This is opportunity, this is the future... we can either be on the train or we can be left behind." Labor-for / ag-residents-against is a recurring fault line in data-center siting fights and is worth tagging as such.

What this changes for SitePath's dataset

• Add/confirm three records, one per county, entity = data-center policy event: Woodbury (19193), Sioux (19167), Plymouth (19149), status moratorium-active, term one year, scope unincorporated areas only, source_url = the kscj.com link above, confidence pending human verification of the official board actions.
• Fix the geo-attribution. The source article is currently tagged in SitePath's news index to FIPS 19061 (Dubuque), 19167, 19193. Dubuque is a misjoin and Plymouth (19149) is missing. Correct set: 19193, 19167, 19149.
• Re-evaluate moratoriumWave in SitePath's data-center dataset (currently 1) — this NW Iowa cluster is a candidate second wave.