Climate & Energy · Data Centers

Corporate Cartography: How Google Used a Map Change to Sidestep Iowa County’s Data Center Rules

When Linn County wrote strict rules for data centers, Google didn’t argue its way through them. It moved the project into a different town. The tactic has a new nickname, and other developers are watching.

Change the rules? Or change the map?

Google chose the map. After a county in eastern Iowa wrote the state’s first serious ordinance for hyperscale data centers, the company stopped negotiating with the county and turned to the small city next door. The land stays where it is. The jurisdiction over it does not. A growing number of observers have started calling the maneuver corporate cartography, a term that gained traction after a Politico investigation into the Iowa dispute.

What Linn County Asked For

Google’s proposal called for a roughly 545-acre data center campus just north of Palo, a town of about 1,600 people some 15 to 20 minutes northwest of Cedar Rapids, near the Duane Arnold Energy Center and an existing solar field. Public records indicate the project could draw as much as 14 million gallons of water per day from the Cedar River. In January, Google offered the county a package that included $1 million per building each year with a 2 percent annual increase, about 100 jobs, a few million dollars for an economic partnership fund and $500,000 for a water balance study.

The county countered. Its officials proposed $70 million up front per building, or $3.25 million a year with a 4 percent escalator, along with full property taxes. In February, the board of supervisors unanimously passed Linn County’s first data center ordinance, which sets rules by facility size and adds requirements on setbacks, noise and traffic. For big projects, it also requires a water study during planning and signed agreements on water use and economic development. Google asked for changes to the water provisions. The county said no.

The land didn’t move. The rulebook did.

The Detour Through Palo

Rather than accept the county’s terms, Google began working with Palo, which sits next to the site, and the company pursued annexation of the property into the city. If that happens, the project answers to Palo’s ordinance, not the county’s. The same site, the same power grid and the same river would be in play, but the water study and agreement requirements Linn County wrote would no longer apply.

Palo’s own rules turned out to be lighter. In July, its city council voted 4 to 1 to approve a data center ordinance, over the objections of a standing-room-only crowd that asked for tougher standards. Residents said the city was acting as a rubber stamp. The ordinance largely mirrors state water quality and consumption rules and, instead of adopting the county’s stricter approach, asks only that the city receive copies of the paperwork the Iowa Department of Natural Resources already requires. A council member said the next step is negotiating a development agreement with Google.

Why a Small Town Might Say Yes

Nothing about this is illegal, and the town’s side of the story deserves a fair hearing. For a city of 1,600, a hyperscale campus is a windfall. By the figures reported, Palo could collect more than $1 million per building in annual property taxes if the land is annexed, and nothing if it isn’t. The county, for its part, would receive about $872,000 per building if the project stayed in its jurisdiction, versus about $610,000 if it were annexed. Palo leaders also point out that Google has agreed to repay roughly $110,000 in legal and engineering costs the city incurred.

That is the bargain at the heart of corporate cartography. The company doesn’t have to defeat a regulation. It only has to find a government that needs the revenue more than it fears the consequences, and those governments are usually the smallest and least equipped to negotiate with a trillion-dollar firm. Critics say the arrangement pushes the costs, a heavier draw on a shared river, strain on the local grid and the question of what happens in a drought, onto residents who live in the county but have no vote in the city.

A Template, Not an Exception

The Iowa fight lands at a moment when the artificial intelligence boom is driving a rush to build hyperscale data centers across North America, and communities are pushing back on noise, electricity demand and water use. Local ordinances are the most direct tool residents have. If a developer can escape one by sliding over a municipal border, that tool loses much of its force, and the incentive to write strong rules weakens, since a strict county only encourages a developer to look at the next town.

There are fixes, and none are exotic. States can require water and energy review regardless of which jurisdiction hosts a project. Counties and neighboring towns can sign agreements to coordinate on regional impacts before a developer arrives. Annexation law can be tightened so that a project of this scale triggers a public process rather than a quiet petition. Those are decisions for legislatures, and so far few have made them.

How the Dispute Unfolded

• JanuaryGoogle offers a term sheet. Linn County counters with higher payments and full property taxes.
• FebruaryThe county unanimously passes its first data center ordinance, including water study requirements.
• SpringGoogle shifts toward annexation into Palo. Questions arise over how much the city negotiated before saying so publicly.
• July 20Palo’s council approves its own data center ordinance on a 4 to 1 vote.
• OctoberNational attention turns to the case as a model for how developers can sidestep local rules.

The deeper question is who decides what a community can say no to. If it’s whoever controls the boundary lines, then the strongest local law in the country is only as strong as the weakest town next to it.