When people hear that a tech giant is “taking” land for data centers, it’s easy to picture bulldozers rolling across pristine acreage with little oversight and even less accountability. But the reality—at least in one Oregon case that has sparked confusion online—is more complicated, and that complexity is exactly what an interactive map built by local resident Isabelle Reksopuro is trying to make easier to understand.
Reksopuro’s project grew out of a familiar problem: misinformation travels faster than permitting paperwork. She began hearing claims that Google was gobbling up public land in Oregon to fuel its data center expansion. Google, for its part, has denied taking that land. The dispute, as Reksopuro explains, hinges on how different parties describe the same events—and on the difference between reclaiming or seeking ownership of land versus “stealing” it outright.
At the center of the story is a portion of Mount Hood National Forest near The Dalles, a city close to the Washington state border. According to reporting referenced in the discussion around the map, The Dalles sought to reclaim or obtain ownership of a 150-acre area within the national forest. The city’s rationale was tied to municipal needs, including access to Mount Hood’s watershed. In other words, the land question isn’t simply “Google vs. Oregon.” It’s a layered set of requests, approvals, and interpretations involving a city’s infrastructure planning, federal land management, and the energy and computing demands of major power users.
That distinction matters because it changes what “data center expansion” means in practice. Data centers don’t just appear; they require electricity, water planning, and long-term infrastructure commitments. Those commitments often involve multiple stakeholders—utilities, local governments, federal agencies, and private companies—each with their own incentives and narratives. When the public hears only one version of events, the story can flatten into a single villain and a single act of wrongdoing. Reksopuro’s map pushes back against that simplification by connecting construction activity with policy developments and by encouraging readers to look at the underlying claims rather than the headlines.
The map’s premise is straightforward: if you want to understand what’s happening “in your backyard,” you need a tool that shows where projects are being proposed or built and how policy decisions are evolving alongside them. But the deeper value is less about geography and more about context. Data centers are often discussed as if they’re purely technical infrastructure—servers, cooling systems, and racks. Yet they are also political infrastructure. They sit at the intersection of land use, environmental review, energy procurement, and regulatory oversight. That intersection is where misunderstandings thrive.
One reason is that the language around data centers is frequently imprecise. People say “Google took land,” but the legal and administrative reality might involve a city requesting ownership, a process for access to resources, or a negotiation over jurisdiction and use rights. Even when a company is a major customer of the infrastructure ecosystem, it may not be the entity directly holding the land title. In many cases, the company is a “power user”—a phrase Reksopuro uses to describe Google’s role in the broader system—rather than the sole actor driving every land-related decision.
This is where the map becomes more than a locator. It’s a narrative correction mechanism. It invites readers to ask: Who is making the request? What exactly is being requested—ownership, access, permits, easements, or something else? Which agency has authority? What stage is the project in? And what policy changes are occurring simultaneously?
Those questions are especially important because data center development is rarely a single event. It’s a chain reaction. A city’s infrastructure needs can trigger land negotiations. Energy demand can drive utility planning and grid upgrades. Environmental review processes can shape timelines and outcomes. Meanwhile, AI policy—often discussed in national terms—can influence local decisions indirectly by affecting how quickly compute demand grows, what kinds of workloads are prioritized, and what compliance expectations emerge.
Reksopuro’s map is built to reflect that chain reaction. It tracks both construction activity and AI policy developments, which is a crucial pairing. Too often, people treat “AI policy” as something abstract—rules written far away from the places where concrete is poured and transmission lines are upgraded. But AI policy can have real-world consequences for infrastructure. If policy encourages certain deployments, accelerates adoption, or changes reporting requirements, it can affect demand forecasts. Those forecasts then influence whether developers pursue new sites, whether utilities invest in capacity, and whether local governments adjust zoning or permitting approaches.
In the Oregon case, the controversy illustrates how quickly the public can lose the thread when these connections aren’t clearly communicated. A claim surfaces that a company is taking public land. Another claim counters that the company denies doing so. Then the story becomes a tug-of-war between competing statements, with little room for the nuance that would help most readers understand what’s actually happening.
Reksopuro’s approach doesn’t ask readers to pick a side based on who sounds more convincing. Instead, it asks them to examine the structure of the dispute. The Dalles, as described in the discussion around the case, sought ownership or access related to watershed needs. That detail reframes the conflict: it suggests that the city’s municipal planning is part of the story, and that Google’s involvement—while significant in terms of demand—may be better understood as participation in a larger infrastructure ecosystem rather than unilateral land acquisition.
This reframing is not meant to absolve anyone of responsibility. It’s meant to clarify what responsibility actually attaches to. If a city is seeking ownership for watershed access, then the relevant questions include whether the request aligns with environmental protections, how the federal land management process responds, and what safeguards exist to ensure that water and ecosystem impacts are properly evaluated. If a company is a major power user, then the relevant questions include how its demand is reflected in utility planning, whether energy sourcing is transparent, and how the company’s growth affects local communities.
Transparency is the throughline. Without it, the public is left to interpret complex processes through incomplete information. With it, people can evaluate claims more fairly—even when they disagree about the outcome.
That’s why the map’s existence feels timely. Data center controversies are increasingly common, and they often follow a predictable pattern: a project is proposed or expanded; local residents raise concerns about land use, environmental impact, and community benefits; online narratives harden into simplified versions of events; and then official statements arrive, sometimes too late or too technical to counter the momentum of misinformation.
Reksopuro’s map tries to interrupt that pattern early by giving readers a way to see what’s happening and how it connects to policy. It’s not just a “where” tool. It’s a “what’s the status and what’s the context” tool. That distinction matters because data center debates are often about timing. A reader might see a location and assume construction is underway, when in fact the project could be in a planning or permitting phase. Or they might assume a company is the landholder, when the land request could be coming from a municipality or another entity. Or they might assume a policy change is irrelevant locally, when it could be shaping demand and investment decisions.
The map’s focus on both construction and AI policy also highlights a broader truth: infrastructure and governance are moving together. Data centers are physical manifestations of digital priorities. As AI capabilities expand, the compute footprint expands too. That expansion creates pressure on energy systems, water systems, and land systems. Policy decisions—whether about AI safety, transparency, licensing, or deployment—can influence how quickly that pressure builds.
But policy isn’t only about AI models. It’s also about the rules governing the environments where those models run. That includes permitting standards, environmental review requirements, and public records practices. When those systems are opaque, the public experiences the consequences without understanding the process that produced them.
Reksopuro’s work implicitly argues that public understanding should be treated as part of infrastructure planning, not as an afterthought. If residents are expected to live with the impacts of data center development—traffic, noise, visual changes, energy strain, water usage—then they deserve access to clear information about what is being proposed, what is being approved, and what is still uncertain.
There’s also a communication challenge that the map addresses indirectly. Many people don’t know how to read the language of land use disputes. Terms like “reclaim,” “ownership,” “access,” “watershed,” and “public land” can mean different things depending on jurisdiction and legal framing. Without a guide, readers may interpret these terms emotionally rather than legally. A map that connects the dots can reduce that emotional interpretation by grounding the conversation in verifiable details.
Still, it’s worth acknowledging what a map can’t do. A map can’t replace due process. It can’t guarantee that every claim is correct. It can’t resolve disputes between parties with conflicting interests. What it can do is make it harder for misinformation to flourish by providing a structured starting point for inquiry.
In the Oregon story, the map’s value is that it helps readers understand why “Google took land” might be an oversimplification. It also helps explain why “Google is just a power user” might be a partial truth that still leaves open questions about how demand translates into local impacts. Both statements can be true in different ways depending on what exactly is being described. The map’s job is to show readers where the ambiguity lives and how to investigate it.
That investigation is particularly important for communities that feel blindsided. Data centers are often discussed as inevitable progress, but local residents experience them as sudden changes. Even when a project has been in planning for years, the public may only learn about it when it becomes visible—when construction begins, when permits are posted, or when a controversy goes viral. By then, trust may already be damaged.
Reksopuro’s map offers a different model: build a tool that helps people track developments continuously, not just reactively. That model aligns with how modern information ecosystems work. People don’t