You’re out of free articles.
Log in
To continue reading, log in to your account.
Create a Free Account
To unlock more free articles, please create a free account.
Sign In or Create an Account.
By continuing, you agree to the Terms of Service and acknowledge our Privacy Policy
Welcome to Heatmap
Thank you for registering with Heatmap. Climate change is one of the greatest challenges of our lives, a force reshaping our economy, our politics, and our culture. We hope to be your trusted, friendly, and insightful guide to that transformation. Please enjoy your free articles. You can check your profile here .
subscribe to get Unlimited access
Offer for a Heatmap News Unlimited Access subscription; please note that your subscription will renew automatically unless you cancel prior to renewal. Cancellation takes effect at the end of your current billing period. We will let you know in advance of any price changes. Taxes may apply. Offer terms are subject to change.
Subscribe to get unlimited Access
Hey, you are out of free articles but you are only a few clicks away from full access. Subscribe below and take advantage of our introductory offer.
subscribe to get Unlimited access
Offer for a Heatmap News Unlimited Access subscription; please note that your subscription will renew automatically unless you cancel prior to renewal. Cancellation takes effect at the end of your current billing period. We will let you know in advance of any price changes. Taxes may apply. Offer terms are subject to change.
Create Your Account
Please Enter Your Password
Forgot your password?
Please enter the email address you use for your account so we can send you a link to reset your password:

Reading the Supreme Court’s decision in Sackett v. EPA might cause you to question your grasp of the English language. Wetlands are wet but are they water? What is water, anyway? Is it distinct from “waters,” plural? How about the word “adjacent” — does it mean “next to” or is it a nonsensical string of syllables signifying nothing?
Even attempting to explain the breakdown of the court’s decision, issued Thursday, requires small abuses of language. The ruling was “nominally unanimous” in that all the justices technically agreed the Environmental Protection Agency overstepped its jurisdiction when it dinged Michael and Chantell Sackett of Idaho in violation of the Clean Waters Act after they backfilled their property with dirt and rocks in preparation for construction. (The EPA claimed the Sackett’s land was protected wetland; in this specific case, the justices didn’t buy it). But the judges were far from unanimous in their reading of the law more broadly, with conservative Justice Brett Kavanaugh notably breaking from his ideological cohorts to issue a scathing clarifying opinion that was joined by the court’s four liberal judges.
Sackett v. EPA was probably always going to come down to semantics. The case marked the latest chapter in a decades-long legal debate over what counts as “waters” when it comes to the “waters of the United States,” which are federally protected by the 1972 Clear Water Act (CWA). In 1975, the Army Corps clarified that wetlands that are “adjacent to other navigable waters” should be considered a part of that protected body of water, and Congress codified this definition in 1977 when it made amendments to the CWA. This conventional interpretation of the words “waters” and “adjacent” had been the standard for 45 years and survived eight presidential administrations.
But hey, what is a word, really? Who decides what it means? Writing for the five other conservative justices, Samuel Alito proposed that wetlands might not be continuously wet enough to count as part of the larger protected whole:
The EPA argues that “waters” is “naturally read to encompass wetlands” because the “presence of water is ‘universally regarded as the most basic feature of wetlands...’”
… which, yeah, of course. Any child can tell you that wetlands are wet and that the “wet” in question is caused by water, not hot lava or buttermilk. But lo! “[T]hat reading proves too much,” Alito said. “Consider puddles, which are also defined by the ordinary presence of water even though few would describe them as ‘waters.’” It’s not even a creative false equivalency; besides, no one is trying to protect puddles.
Alito further fretted that by allowing for a definition of wetlands that includes, uh, wetlands, landowners could face “crushing” fines for “inadvertent violations” of the Clean Water Act “like moving dirt.” As Alito worried, “What are landowners to do if they want to build on their property?” (“Don’t pollute American waterways” seems like a pretty reasonable answer to that question!)
The real battle, though, boiled down to the word “adjacent.” In a 2006 Supreme Court opinion for Rapanos v. United States, the late conservative Antonin Scalia wrote for the plurality that wetlands only count as protected when they are “indistinguishable from waters of the United States.” (The court was divided and the case was ultimately sent back to the Sixth Circuit.)
By this unorthodox interpretation, the Clean Water Act would only protect “wetlands with a continuous surface connection” to protected waters, as Alito endorsed and wrote in the opinion released Thursday. What this means in real life is that when wetlands are separated from a larger body of protected water by something like a man-made levee or a naturally occurring berm or a sand dune — as many wetlands are — then the wetland in question is not indistinguishable from the larger body of water and thus no longer federally protected.
You might notice that “adjacent” and “continuous” are two different words. When Congress adopted the Army Corps’ language for protecting American waters from pollution, it did not protect wetlands that are “indistinguishable from other waters” but rather wetlands that are adjacent to other waters. As Kavanaugh pointed out:
The ordinary meaning of the term “adjacent” has not changed since Congress amended the Clean Water Act in 1977 to expressly cover “wetlands adjacent” to waters of the United States. Then as now, “adjacent” means lying near or close to, neighboring, or not widely separated. Indeed, the definitions of “adjacent” are notably explicit that two things need not touch each other in order to be adjacent.
Alito’s argument that adjacent means the same thing as adjoining goes “against all indications of ordinary meaning,” Kavanaugh added.
This isn’t just semantic nitpicking. The consequences of changing the definition of “adjacent” to something more like “an extension of” have huge ramifications for what the EPA can now protect. Because of that interpretation, millions of acres of wetlands theoretically just lost their federal protections. The Mississippi River, for example, uses levees to control flooding, but under Alito’s definition of “continuous surface connection,” such barriers would “seemingly preclude Clean Water Act coverage of adjacent wetlands on the other side,” Kavanaugh wrote. Federal protection of the Chesapeake Bay might also be up in the air for similar reasons.
Justice Elena Kagan, in her own extra spicy opinion joined by the other court liberals, ripped into the conservative majority for its word games. “[T]he majority shelves the usual rules of interpretation — reading the text, determining what the words used there mean, and applying that ordinary understanding concurring in judgment even if it conflicts with judges’ policy preferences,” she slammed, then added for good measure: “One last time: ‘Adjacent’ means neighboring, whether or not touching ... That congressional judgment is as clear as clear can be — which is to say, as clear as language gets.”
Of course, the decision isn’t about clarity or standard definitions. It’s about muddying the waters. What, after all, do we now make of wetlands that have surface water levels that fluctuate due to tides or dry spells? What of manmade barriers that existed before their builders knew the structures would cut off a wetland from federal protection? What even counts as a “continuous surface connection” — does a ditch? A pipe? How do we make sense of naturally shifting landscapes like dunes that temporarily cut off wetlands, only to eventually melt away again due to erosion or winds?
The conservative justices are more interested in exploitable ambiguities than answers to these questions.
Log in
To continue reading, log in to your account.
Create a Free Account
To unlock more free articles, please create a free account.
The data center boom is everywhere you look in U.S. economic and emissions data.
This is an edition of Heatmap Daily, an evening review of the day’s news written by our executive editor. Sign up for it here.
It isn’t exactly a new thought, but I’ve been struck recently by how many trends in America’s economic and environmental data are fundamentally about the data center boom and the return of electricity demand:
First, the Energy Information Administration reported this week that U.S. emissions grew by more than 2% last year, driven by surging electricity demand and an increase in coal-fired generation. What caused that higher power demand? New factories and data centers — as well as record summertime cooling demand.
Second, many of the new factories driving that higher power demand are themselves producing goods that are … let’s say … data center-adjacent. There are the enormous new semiconductor fabs, of course. But Ford and General Motors have also set up new production lines (or repurposed old ones) to manufacture grid-scale batteries to meet power demand.
Third, take a look at the recent U.S. spending on private non-residential construction — in other words, everything American companies are building that is not houses, condos, or apartments.
The construction industry’s spent almost $60 billion on data centers over the past year, which is more than it spent on all other office buildings combined (and more than it spent building warehouses, too). Just a handful of categories — data centers, power plants, electricity infrastructure, and certain kinds of electronics manufacturing — now make up a third of all U.S. private non-residential construction investment. They’ve never made up such a large share of construction spending since data collection began in 2014.
As The New York Times recently noted, the American economy is unusually dependent on the American stock market right now — and the stock market is unusually dependent on artificial intelligence. This week, investors started to balk at the enormous spending hyperscalers are planning to keep building out the AI boom; Alphabet’s shares dropped 8% this week after it boosted its planned 2026 capital expenditure and signaled 2027 will be even bigger. If the data center boom started to slow down in earnest, then more than just that budget will change.
Speaking of which, my colleague Emily Pontecorvo wrote earlier this week about how many businesses are struggling to even estimate their carbon emissions from artificial intelligence. The carbon accounting startup Watershed recently unveiled a new formula to help companies get a sense of their AI-related emissions.
But even that formula is still limited by the amount of data hyperscalers publish — and they don’t publish that much. Google, for instance, is the only AI company that has (laudably) provided estimates of its emissions on a per-prompt basis. Yet no company has published its per-token emissions, or how emissions sync up with particular models or regions.
So Emily asked Google: Why aren’t you — or any other model provider — disclosing this kind of data yet?
The tech company didn’t get back to us until after we’d published Emily’s story. But its response was interesting enough that I wanted to quote some of it here.
The problem is “industry consensus,” Cooper Elsworth, a Google spokesperson, told us. “There is currently very little consensus on how to comprehensively and fairly measure the serving environmental impact of generative AI (such as text generation),” he wrote. “Without standardized, ‘apples-to-apples’ frameworks, it is difficult to compare different providers accurately.”
That’s partly because energy use — and emissions data — can vary from site to site and depend on “custom-built hardware, software compilers, and advanced inference techniques.” And he claimed Google doesn’t always have the measurement hardware in place to provide such specific estimates: “Providing precise, repeatable data requires highly advanced measurement infrastructure,” he said. “For example, software-based energy monitoring tools often suffer from sampling biases. For our study, we had to step away from top-down averages and directly measure actual energy at the physical power supply unit (PSU) level across our deployed fleet. Not all providers have the telemetry or data sets required to benchmark their operations at this level of granularity.”
Read Emily’s story to understand the other reasons why estimating — or even “guesstimating” — AI-related carbon emissions is so challenging.
A conversation with Emma Uridge of the Kansas Health Institute.
This week’s conversation is with Emma Uridge, analyst with the Kansas Health Institute. Uridge spent copious hours analyzing state and local laws on data center development to best understand how policymakers are responding to the potential environmental public health impacts of large AI infrastructure, including power and water. The report, which came out this week, also goes in depth into those health impacts. I reached out to her to discuss what she sees as must-watch territory for our readers on this emerging policy arena.
Our conversation was lightly edited for clarity.
What is actually being done on policy when it comes to data centers — beyond moratoria of course?
So first I’d like to just talk about the point of moratoria. It’s helpful to talk about how these policies emerge in the first place. One area where moratoria are helpful is when a data center is proposed but the county has no approach for how they’d like to potentially regulate them. That’s temporary, most of the time. It lets local governments conduct research on the various impacts and also negotiate community benefits, ones that can mitigate any potential negative impacts — like Lancaster Pennsylvania, which instituted a community benefit agreement that maximized the potential benefits of development while mitigating what large data centers can do. That agreement looked at capping municipal water use at 20,000 gallons per day and requiring 100% clean energy. It had financial penalties for non-compliance. The company also committed $20 million to their local economic development and clean energy fund. There are ways to negotiate with developers.
We also see amendments to existing zoning. Data center proposals are increasingly popping up in rural areas, many of which are unzoned, so there’s no way a county can negotiate unless there’s a moratorium in place.
Other policy solutions include different performance standards or requiring on-site renewable energy, like what Jefferson County, Missouri, looked at. Also setback requirements, mandatory noise buffers, ending by-right zoning.
Where are local governments getting ideas for regulating data centers?
A lot of the technical information comes from developers. That can in cases be seen as a biased source of information. I wouldn’t say there’s a dedicated group providing assistance to local governments when a project is proposed — which is a similar story to wind industry development, where we have only a handful of consultants who provide technical advice. It can be really helpful to get a multi-disciplinary approach to hearing information. It can be helpful to have the utility commission, public health folks, those in academia, as well as the developer.
As of right now, especially in rural areas, local governments have a hard task of balancing pushback while getting the most accurate, evidence-based, neutral information to make decisions. That balance can be contentious.
What is the federal government doing on data center policy? How is the Trump administration approaching it?
A few things there. In the early days, the drive was for AI expansion and to be competitive with foreign adversaries. Now due to the amount of public pushback in red and blue localities and a more cautious approach.
I’m not seeing a lot of actual policy movement at this time.
I know the EPA is looking at the chemicals used in cooling data centers because when that water is cycled through the system, some of it is discharged into the water system, so they’re looking at the Toxic Substances and Control Act for monitoring that.
How much of an impact does this minimal federal role have on industry behavior?
Y’know, this isn’t specific to data centers. This is true for all kinds of large-scale development: there’s a need to require some sort of federal monitoring and regulation.
That’s where I see an emerging role for public health. At the federal level, there could be policy movement towards requiring some sort of environmental monitoring at data centers to make sure they’re operating responsibility. Looking at specific water use relative to water availability and what happens when there’s a time of severe, persistent drought. With air quality too — we’ve seen areas where the grid isn’t as reliable so their diesel generators are kicking on more and affecting air quality for residents.
We’re just not seeing all of that right now. We need corporate disclosure.
What do you see as the most important public health impacts from data center development?
It varies by localities. The most discussed obviously is water usage. One thing I’d note about my conversations with folks enthusiastic around emerging tech is, there are still questions that need to be asked about the capacity of localities to support a data center. Like a small town in Kansas may only be using 40% of their water for their utility needs. If a data center came online, how much of that water goes to the data center?
One area underexplored within the public health discipline is energy poverty and energy security. The ability of a household to meet the needs of everything energy provides in our lives. It’s known we have an aging electric grid but we’re not talking enough about large-scale blackouts when the grid is not sufficient to support some of these new data centers.
Plus more of the week’s big development fights.
1. Laramie County, Wyoming — Meta is fighting the fine it received in the Cheyenne data center water pollution controversy, and the conflict between the tech giant and the city’s small board of public utilities is continuing to spill out into the public.
2. Niagara County, New York — This county just rejected a solar project’s highway work permits in a show of retaliation against the state’s Office of Renewable Energy Siting.
3. Barron County, Wisconsin — The anti-solar protest is the new campaign stop in deep red Wisconsin.
4. Chesapeake, Virginia — A large battery storage project on the Virginia coastline is on the rocks amidst rampant local opposition.
5. Lewis County, West Virginia — West Virginia is now a key battleground in the fight over transmission, as a line spanning all of West Virginia and Maryland — and cutting through Data Center Alley in Virginia — causes compounding consternation.