Interactive Map Reveals Data Centers in Your City

When Isabelle Reksopuro, a resident of Oregon, learned that Google was acquiring public land in her state to build data centers, she initially struggled to find reliable sources. "There's a lot of misinformation about data centers," she said. "Google has denied appropriating that land." The case of The Dalles, a city near the Washington border where the company has operated facilities for over a decade, shows how such infrastructure can expand in a community's immediate surroundings without residents having clear information about who controls it or what consequences it carries.

That's precisely what an interactive map described by The Verge aims to change: a public lookup tool that lets you locate data centers in US cities and counties, identify their operators, Amazon, Google, Microsoft, Meta and numerous colocation providers among them, and access information about permits, energy consumption and water impact when data is available.

What the tool offers and who built it

The map aggregates information from public records, building permit applications, environmental statements and land ownership databases. It's not a corporate product: behind it are technology policy monitoring organizations and community advocacy groups that have spent years manually tracking infrastructure expansion.

The interface lets you filter by operating company, facility size or proximity to water sources, a criterion that has gained weight as debate over data center water consumption has grown in regions with recurring droughts. Each marker includes, when available, the history of tax incentives received by the facility: in some counties across the southern United States, those figures exceed hundreds of millions of dollars in exemptions.

Why it matters beyond the US

Although the map covers US territory, the debate it opens is relevant in any context where generative AI continues growing as it has in recent years. Each time a model like Claude Opus 4.7 or any large-scale inference system processes a query, it does so in a physical facility that consumes electricity, water and land. That chain, invisible to the end user, has a concrete geography and very tangible local consequences: pressure on electrical grids, competition for water in arid zones, impact on industrial land prices and confidentiality agreements that hinder public scrutiny.

The Oregon case is paradigmatic: The Dalles has watched Google build facilities over more than a decade under agreements that restricted disclosure of energy consumption data. Reksopuro and other residents needed years to obtain information that should theoretically be public.

Who finds this resource useful

The most obvious user profile includes journalists and local activists who need to contextualize urban planning or environmental decisions. But it's also a valuable tool for municipal administrations negotiating terms with large tech operators without comparable references from other municipalities, and for researchers studying the geographic distribution of digital infrastructure and its correlation with energy inequality.

For teams like ours, working with Claude integrations and MCP servers, this kind of transparency is relevant in a more operational sense: knowing where data is processed, what latencies different regions involve and what regulatory frameworks apply to each facility is no small detail when designing production systems with sensitive data.

A data gap the map doesn't entirely close

The tool has clear limitations: it depends on the quality of public records in each jurisdiction, which varies enormously. Some facilities appear without an identified operator; others lack consumption data. The map is only as good as the transparency of the local governments that feed it, and that transparency remains uneven.

That said, the exercise of aggregating and visualizing what is already public, without inventing or speculating, has its own value. When an Oregon resident can search "The Dalles" and see on a map what's there, who operates it and under what terms, that's a concrete step toward a more informed conversation about how the infrastructure supporting much of today's computing is built.

Here at ClaudeWave, we view this kind of scrutiny initiative positively. They don't resolve underlying conflicts, but they do make them harder to ignore.