Typeost

Tech news in plain type

Latest / Policy

Policy

Bill would bar new data centers on certain US federal lands

An Oregon congresswoman's bill would block new data center construction on federally controlled land, including supporting infrastructure.

Oregon Representative Maxine Dexter has introduced H.R. 11002, the Protecting Our Public Lands from Data Centers Act, according to TechRadar. The bill would restrict construction of new data centers on federally managed land across the United States.

TechRadar reports that the proposal would cover millions of acres of federal property. It would also apply to supporting infrastructure built alongside commercial data center facilities, not only the facilities themselves.

According to the outlet, the bill would also limit the sale or transfer of covered land. The available reporting does not give full details on how that provision would work.

TechRadar notes that both the Biden and Trump administrations advanced federal land access for data center development. Its headline suggests that national parks could be safe for now under the proposal, though the reporting does not describe how far the bill has progressed through Congress.

Background

Data centers are large facilities filled with servers that run cloud services, store information, and train and operate artificial intelligence systems. They consume substantial electricity and require extensive cooling, which pushes operators to look for sites with reliable power, available land, and access to water or transmission lines. Over the past several years, that search has increasingly included property owned by the federal government, which holds large areas across the western United States.

Those holdings are overseen by agencies with different missions, including land management, energy, and defense. Federal land is commonly used for grazing, recreation, mining, timber, conservation, and energy projects. Using it for commercial computing is a newer question, and it brings in agency rules, environmental review, and leasing arrangements that differ from private land deals.

Public land policy in the United States has long involved competing goals: keeping land open for public use, allowing development that supports the economy, and protecting natural and cultural resources. Congress often sets those limits through statutes, while agencies write the detailed rules. When a new category of use appears, lawmakers may respond with specific prohibitions or leave the question to administrative processes. Measures that restrict a land use can be introduced for many reasons, including environmental concerns, community objections, or a desire to preserve land for future generations. Bills like this often face a long path through committees, and many never become law. That context helps readers weigh an introduction against an enacted rule.

Why it matters

The proposal sits at the intersection of two fast-moving trends: the rapid buildout of computing capacity for artificial intelligence and cloud services, and growing attention to how land, power, and water are allocated. If federal land becomes a routine site for large facilities, agency decisions could shape where infrastructure goes for years.

A statutory ban would give those decisions a clearer boundary. Leaving the question to existing rules would keep it in agency hands, where it could shift with each administration. The reporting's note that both recent administrations supported access to federal land for data centers suggests the issue crosses party lines, even as lawmakers may disagree about its direction.

For companies, the outcome affects site planning and the availability of locations with the power access they need. For communities near federal lands, it affects whether protected landscapes stay shielded from large industrial projects. The bill is also a signal about how the government wants to balance digital infrastructure against other uses of the land it holds.

What to watch

Watch for the bill's committee assignment and whether it gains cosponsors, since early support can indicate its prospects. Pay close attention to how the final text defines data centers and supporting infrastructure, because narrow or broad definitions would change its reach considerably. The language on sale or transfer of covered land will matter for long-term protection.

Look for any response from federal agencies and for any existing or pending projects that could be affected. Also watch whether a companion bill appears in the Senate. Finally, observe whether the debate shifts toward energy supply, since demand from computing is a major pressure behind these land decisions.

Viewpoints

Commentary from our columns: three angles on this story.

The Skeptic open questions and weak points

The first question to ask is how much this bill would actually change. Introducing a bill is a signal, not a rule, and the distance between the two can be wide. Key terms will decide almost everything. What counts as a data center? Where does supporting infrastructure end? Would a construction restriction also reach expansions of existing facilities, or upgrades to power lines that cross federal parcels? Each gap could leave room for projects to proceed in a different form.

The national park framing in the headline deserves caution too. Parks are one part of federal land, and the reporting does not say whether the bill would reach them in every case. Readers should not treat a headline as a guarantee. Until the text is examined closely, the reassuring reading and the narrower reading could both be true at once. Good policy starts with questions like these, and the answers are still missing.

The Rulebook privacy, safety and regulation

Public land law is already a patchwork, and this bill would add a clear prohibition to it. Its strongest instinct is the attempt to cover supporting infrastructure, not only buildings. Facilities depend on power connections, cooling systems, roads, and fiber routes. A rule that ignores those pieces can be sidestepped without much effort.

The provision on sale or transfer points toward a longer horizon, aiming to keep land from drifting out of public control over time. Those are sensible goals. Enforcement will still decide the outcome. Agencies will need precise standards, and courts may eventually be asked to interpret vague phrases. Lawmakers should also consider how a ban fits with existing permitting and environmental review, so the rules do not contradict one another. The best version of this bill would be specific, workable, and durable across administrations, which is a high bar for any single measure.

The Ledger the business angle

For operators, a restriction on federal land is a site-selection problem before it is a political one. Developers look for power, land, water, and connectivity, and federal parcels have sometimes offered large tracts that were comparatively available. Removing that option would push projects toward private land, where prices, zoning disputes, and utility queues already create friction.

The likely business response is diversification: more emphasis on existing campuses, on sites near generating capacity, and on partnerships with utilities. Investors will also weigh policy risk. A bill that is introduced but not enacted creates uncertainty rather than a fixed cost, and markets tend to price uncertainty in. The sale-and-transfer language matters here as well, since it shapes how long any government-owned site could remain an option. Most of the real money will still flow through decisions made far from Washington, in state and local planning offices and utility boardrooms.

More in Policy