Residents Rally Against 130-Acre Data Center

A crowd gathered outside a Metropolitan Development Commission hearing in Decatur Township with a clear message: not here, not like this. The proposed project—a 130-acre data center—triggered the kind of organized community opposition that developers and investors rarely see coming until it's already a problem.

Data center protests aren't new, but they're getting louder, more organized, and increasingly effective at slowing or reshaping projects that once would have sailed through local approval processes. What's happening in Decatur Township is worth paying close attention to—not just for those with skin in this particular game, but for anyone tracking where infrastructure development is heading.

What's Being Proposed

The project is substantial by any measure. At 130 acres, this isn't a modest colocation facility tucked into an industrial park. It's the kind of large-scale data center campus that hyperscalers and their development partners have been aggressively siting across the Midwest, drawn by available land, access to power infrastructure, and—historically—relatively low community resistance.

A 130-acre footprint puts this project in the same weight class as the mega-campuses that companies like Microsoft, Amazon Web Services, and Meta have been building across states like Ohio, Indiana, and Iowa over the past several years. Projects at this scale typically require significant utility upgrades, consume tens of millions of gallons of water annually for cooling, and can draw anywhere from 100 to 500+ megawatts of power at full build-out.

The backers of the Decatur Township project would frame it in familiar terms: jobs, tax base, economic development, and positioning the region for the digital economy. Those arguments aren't wrong. A facility of this size can generate meaningful property tax revenue and construction employment. The question communities are increasingly asking, though, is whether those benefits are distributed broadly enough to justify the costs that fall on immediate neighbors.

Why Residents Showed Up

When residents organize enough to physically appear at a Metropolitan Development Commission hearing, something has genuinely mobilized them. This isn't passive opposition—it takes time, coordination, and conviction to show up in numbers.

The grievances driving data center protests tend to cluster around a recognizable set of concerns: traffic during construction, noise from industrial-scale cooling systems and backup generators, strain on local power and water resources, and the fundamental question of land use—whether turning 130 acres into server infrastructure is the best possible future for that particular piece of ground.

There's also a deeper tension that rarely makes it into official hearing transcripts: the sense that large infrastructure projects are decided by economic development offices and planning commissions in ways that leave the people who actually live nearby with little real agency. By the time a project reaches a public hearing, the developer has typically spent months or years in preliminary conversations with local officials, site selectors, and utility providers. Residents find out late and feel like the decision has already been made.

In areas where data center development has already taken root, that concern isn't paranoia—it's pattern recognition. Communities that approved one facility often find themselves fielding proposals for adjacent projects before the first one is even fully operational. The cumulative impact of multiple campuses on local roads, water tables, and power grids compounds in ways that no single environmental review fully captures.

The Economic Calculus Is More Complicated Than It Looks

Supporters of projects like this one routinely cite economic impact figures, and those figures aren't fabricated. Data centers do create construction jobs, though the permanent employment numbers are often surprisingly modest for facilities of this size—a fully automated 100MW campus might run with a few dozen full-time employees. The real economic argument is usually about property taxes and the broader ecosystem effects of attracting tech-adjacent industries to a region.

Investors and developers watching community opposition materialize need to understand that protests at this stage aren't just a public relations problem—they're a project risk that can trigger delays, permit denials, legal challenges, and ultimately, cost overruns that reshape a deal's economics entirely.

From an infrastructure investment standpoint, the Decatur Township situation illustrates why community engagement strategy has moved from a nice-to-have to a critical path item. Projects that skip genuine stakeholder engagement in favor of minimum compliance with public notice requirements are increasingly running into organized resistance at exactly the worst possible moment—when permits are pending and capital is committed.

The economic argument also cuts both ways. Residents who oppose a data center aren't simply rejecting economic development. Many are making a competing economic argument: that 130 acres of land developed for industrial-scale computing might displace higher-employment uses, suppress nearby residential property values, or lock in infrastructure choices that limit future flexibility. Those arguments deserve engagement, not dismissal.

The Environmental Reality of Industrial-Scale Computing

Data centers are infrastructure, and like all infrastructure, they have environmental footprints. At the scale being proposed in Decatur Township, the relevant concerns aren't hypothetical.

Water consumption is the environmental issue that surprises people most. Evaporative cooling systems—still common in large data center campuses—can consume millions of gallons per day. In regions where water supply is constrained or contested, that's a significant community concern that goes well beyond aesthetics. Even in areas with adequate water supply, the local draw on municipal systems or aquifers can become a legitimate point of contention.

Power demand is the other major factor. A campus of this size coming online represents a step-change load addition to the local grid. Utilities can handle it, but not always immediately and not always without infrastructure investment that gets socialized across the broader ratepayer base. Communities that have watched their electricity bills rise while a data center negotiates favorable commercial rates next door have a legitimate grievance—and that grievance becomes a recruitment tool for opposition movements.

Regulatory and compliance factors add another layer of complexity. Environmental impact reviews, stormwater management requirements, and—increasingly—state-level data center siting legislation are creating a more demanding approval environment than existed even five years ago. Developers who built their underwriting assumptions on legacy approval timelines are getting caught short.

Where This Goes From Here

The Metropolitan Development Commission hearing is a decision point, not an endpoint. Whatever comes out of it, the underlying dynamics that brought residents to the parking lot outside that hearing room aren't going away.

The most durable path forward for projects facing this level of community opposition typically involves genuine concessions—not the cosmetic kind, but structural commitments on things like water recycling targets, noise mitigation, local hiring preferences, community benefit agreements, and phased development approaches that give residents some visibility into cumulative impact before the full buildout is approved.

Some developers are getting ahead of this. The ones who engage communities before the site plan is finalized—who bring residents into the conversation when there's still flexibility to respond—tend to face shorter approval timelines and fewer expensive mid-process surprises. It costs more upfront in community engagement resources. It costs far less than a six-month delay while legal challenges work through the system.

The broader trajectory of data center development in the Midwest is toward more scrutiny, not less. The AI infrastructure buildout driving demand for new capacity isn't slowing down, but neither is the sophistication of community opposition. The regions that figure out how to align those forces—that develop genuine frameworks for community benefit rather than minimum compliance—will attract capital more reliably than those that don't.

Decatur Township is one hearing in one county. But it's also a signal about where the friction points in infrastructure development are moving. For developers, investors, and local officials, the most useful question isn't how to overcome community opposition—it's how to build projects that don't generate it in the first place.

[INTERNAL LINK: community engagement strategies]

[INTERNAL LINK: data center environmental impacts]

[INTERNAL LINK: economic benefits of data centers]

EDITOR NOTES

• Consider cutting the paragraph discussing the "deeper tension" in the "Why Residents Showed Up" section, as it may feel slightly verbose.
• Ensure that the internal links are relevant and lead to appropriate content on the site.