This article is exclusively
for Heatmap Plus subscribers.
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:
A conversation with Renee Grabe of Nature Forward

This week’s conversation is with Renee Grabe, a conservation advocate for the environmental group Nature Forward who is focused intently on data center development in Northern Virginia. I reached out to her for a fresh perspective on where data centers and renewable energy development fits in the Commonwealth amidst heightened frustration over land use and agricultural impacts, especially after this past election cycle. I thought her views on policy-making here were refreshingly nuanced.
This transcript was lightly edited for clarity.
Tell me more about how you started focusing on data centers.
So, in Fairfax County, in 2020 or 2021, people were pursuing the construction of an indoor ski facility on a landfill. From a climate perspective, to build something that would need to be cooled 24/7 for indoor skiing seemed like a very bad proposal in terms of energy usage. And for what kind of gain?
Then our friends at the Sierra Club were saying, indoor ski slopes? Bad, yes. But data centers? Way, way worse. Those aren’t cooling to support snow but are cooling much larger areas on a much larger scale, dwarfing the area of that one ski slope. This was around the time the Prince William Digital Gateway was showing up – they were saying all these acres of agricultural lands and single-family housing zones were about to be rezoned. This was a big deal, and Sierra Club led the way in opening our eyes to this. The rezoning ultimately passed. The data centers were sued and the people who filed the lawsuit won, but pre-planning for the centers is still allowed to take place.
The way we think about the impacts of data centers, besides the loss of natural lands and the amount of energy that’s going to be needed to power these things, has been diesel generators. These are the things that are backup generation and the camel’s nose under the tent is trying to get them to be primary power.
Now I want to ask you a provocative question: is there any middle ground between letting these projects be built unfettered and outright bans on their development?
We have no regulation today. From our standpoint, these things are coming, they’re here. We know a lot more now than we did in 2022. As we make decisions about how and where to build these facilities we all need – I mean we’re using one right now. I use a data center all day at work. Teams conferencing. ChatGPT to answer a question. We need these. So if we’re going to build them, let’s not give a pass to some of the world’s largest and richest companies. Let’s ask them to put the guardrails on to protect our residences and our infrastructure to make sure they’re as sustainable as possible.
Okay, so what are the guardrails then?
The costs of what was going to go into a data center need to be more transparent. We need to bring accountability to the forefront right away as they’re being built.
In Ohio, they passed a law requiring data center companies to pay for a high percentage of the power they’re using. That cut a significant number of the projects in Ohio. This industry is so speculative and a land grab and a rush to be first to get the most.
You have this dichotomy of land values for residences being inundated, while land values for developers are skyrocketing. We have an affordability crisis going on and we are all on the hook for paying for the infrastructure to power these things.
So when you think about what regulation might make data center development more reasonable, it’s asking for the costs happening to be borne by the industry making them. Let’s get rid of some of the incentives for power users. We don’t need to be encouraging the loss of state revenue, either – we’re leaving money on the table to bring these facilities here.
Lastly, our readers love to get hyperlocal. I know you’re intently focused on Fairfax County right now which has been a big part of the data center boom in Virginia – what’s happening there?
There are a couple things that have happened over the course of this past year. Fairfax County passed a data center zoning ordinance amendment – minimum requirements a data center will have to adhere to. The big thing with that one is, you have to have a special exception if you build within a mile of a Metro station. When you think about good land use and building a data center within a walkable distance of a Metro, that’s eye-openingly poor land use policy and a missed opportunity for transit-oriented development. It doesn’t mean they can’t be built near one but you have to get a special exception.
Some things can’t be regulated at the local level. Like generators. That’s in the hands of the state.
Last night, we had a public hearing at the Fairfax County board level for our policy plan – our comprehensive plan providing guidance for developers who want to get a special exception or rezoning. It is not law. It is not required. It is a visionary document that helps us get to better. They’ve added a section for data centers in that. In May, staff put forward something pretty good, making sure data centers met a minimum level of efficiency. But our chairman of the county board said it went above and beyond our zoning ordinance and said he didn’t think it was appropriate, so staff rewrote that section and stripped out a lot of the specificity and higher standards that were in that document.
At the hearing, they deferred a decision, listening to the public but not having a discussion at the board level. They’ve left the record open through December 9th.
Log in
To continue reading, log in to your account.
Create a Free Account
To unlock more free articles, please create a free account.
It’s aware of the problem. That doesn’t make it easier to solve.
The data center backlash has metastasized into a full-blown PR crisis, one the tech sector is trying to get out in front of. But it is unclear whether companies are responding effectively enough to avoid a cascading series of local bans and restrictions nationwide.
Our numbers don’t lie: At least 25 data center projects were canceled last year, and nearly 100 projects faced at least some form of opposition, according to Heatmap Pro data. We’ve also recorded more than 60 towns, cities and counties that have enacted some form of moratorium or restrictive ordinance against data center development. We expect these numbers to rise throughout the year, and it won’t be long before the data on data center opposition is rivaling the figures on total wind or solar projects fought in the United States.
I spent this week reviewing the primary motivations for conflict in these numerous data center fights and speaking with representatives of the data center sector and relevant connected enterprises, like electrical manufacturing. I am now convinced that the industry knows it has a profound challenge on its hands. Folks are doing a lot to address it, from good-neighbor promises to lobbying efforts at the state and federal level. But much more work will need to be done to avoid repeating mistakes that have bedeviled other industries that face similar land use backlash cycles, such as fossil fuel extraction, mining, and renewable energy infrastructure development.
Two primary issues undergird the data center mega-backlash we’re seeing today: energy use fears and water consumption confusion.
Starting with energy, it’s important to say that data center development currently correlates with higher electricity rates in areas where projects are being built, but the industry challenges the presumption that it is solely responsible for that phenomenon. In the eyes of opponents, utilities are scrambling to construct new power supplies to meet projected increases in energy demand, and this in turn is sending bills higher.
That’s because, as I’ve previously explained, data centers are getting power in two ways: off the existing regional electric grid or from on-site generation, either from larger new facilities (like new gas plants or solar farms) or diesel generators for baseload, backup purposes. But building new power infrastructure on site takes time, and speed is the name of the game right now in the AI race, so many simply attach to the existing grid.
Areas with rising electricity bills are more likely to ban or restrict data center development. Let’s just take one example: Aurora, Illinois, a suburb of Chicago and the second most-populous city in the state. Aurora instituted a 180-day moratorium on data center development last fall after receiving numerous complaints about data centers from residents, including a litany related to electricity bills. More than 1.5 gigawatts of data center capacity already operate in the surrounding Kane County, where residential electricity rates are at a three-year high and expected to increase over the near term – contributing to a high risk of opposition against new projects.
The second trouble spot is water, which data centers need to cool down their servers. Project developers have face a huge hurdle in the form of viral stories of households near data centers who suddenly lack a drop to drink. Prominent examples activists bring up include this tale of a family living next to a Meta facility in Newton County, Georgia, and this narrative of people living around an Amazon Web Services center in St. Joseph County, Indiana. Unsurprisingly, the St. Joseph County Council rejected a new data center in response to, among other things, very vocal water concerns. (It’s worth noting that the actual harm caused to water systems by data centers is at times both over- and under-stated, depending on the facility and location.)
“I think it’s very important for the industry as a whole to be honest that living next to [a data center] is not an ideal situation,” said Caleb Max, CEO of the National Artificial Intelligence Association, a new D.C.-based trade group launched last year that represents Oracle and myriad AI companies.
Polling shows that data centers are less popular than the use of artificial intelligence overall, Max told me, so more needs to be done to communicate the benefits that come from their development – including empowering AI. “The best thing the industry could start to do is, for the people in these zip codes with the data centers, those people need to more tangibly feel the benefits of it.”
Many in the data center development space are responding quickly to these concerns. Companies are clearly trying to get out ahead on energy, with the biggest example arriving this week from Microsoft, which pledged to pay more for the electricity it uses to power its data centers. “It’s about balancing that demand and market with these concerns. That’s why you're seeing the industry lean in on these issues and more proactively communicating with communities,” said Dan Diorio, state policy director for the Data Center Coalition.
There’s also an effort underway to develop national guidance for data centers led by the National Electrical Manufacturers Association, the American Society of Heating, Refrigerating, and Air-Conditioning Engineers, and the Pacific Northwest National Laboratory, expected to surface publicly by this summer. Some of the guidance has already been published, such as this document on energy storage best practices, which is intended to help data centers know how to properly use solutions that can avoid diesel generators, an environmental concern in communities. But the guidance will ultimately include discussions of cooling, too, which can be a water-intensive practice.
“It’s a great example of an instance where industry is coming together and realizing there’s a need for guidance. There’s a very rapidly developing sector here that uses electricity in a fundamentally different way, that’s almost unprecedented,” Patrick Hughes, senior vice president of strategy, technical, and industry affairs for NEMA, told me in an interview Monday.
Personally, I’m unsure whether these voluntary efforts will be enough to assuage the concerns of local officials. It certainly isn’t convincing folks like Jon Green, a member of the Board of Supervisors in Johnson County, Iowa. Johnson County is a populous area, home to the University of Iowa campus, and Green told me that to date it hasn’t really gotten any interest from data center developers. But that didn’t stop the county from instituting a one-year moratorium in 2025 to block projects and give time for them to develop regulations.
I asked Green if there’s a form of responsible data center development. “I don’t know if there is, at least where they’re going to be economically feasible,” he told me. “If we say they’ve got to erect 40 wind turbines and 160 acres of solar in order to power a data center, I don’t know if when they do their cost analysis that it’ll pencil out.”
Plus a storage success near Springfield, Massachusetts, and more of the week’s biggest renewables fights.
1. Sacramento County, California – A large solar farm might go belly-up thanks to a fickle utility and fears of damage to old growth trees.
2. Hampden County, Massachusetts – The small Commonwealth city of Agawam, just outside of Springfield, is the latest site of a Massachusetts uproar over battery storage…
3. Washtenaw County, Michigan – The city of Saline southwest of Detroit is now banning data centers for at least a year – and also drafting regulations around renewable energy.
4. Dane County, Wisconsin – Another city with a fresh data center moratorium this week: Madison, home of the Wisconsin Badgers.
5. Hood County, Texas – Last but not least, I bring you one final stop on the apparent data center damnation tour: Hood County, south of the Texas city of Fort Worth.
A conversation with San Jose State University researcher Ivano Aiello, who’s been studying the aftermath of the catastrophe at Moss Landing.
This week’s conversation is with Ivano Aiello, a geoscientist at San Jose State University in California. I interviewed Aiello a year ago, when I began investigating the potential harm caused by the battery fire at Vistra’s Moss Landing facility, perhaps the largest battery storage fire of all time. The now-closed battery plant is located near the university, and Aiello happened to be studying a nearby estuary and wildlife habitat when the fire took place. He was therefore able to closely track metals contamination from the site. When we last spoke, he told me that he was working on a comprehensive, peer-reviewed study of the impacts of the fire.
That research was recently published and has a crucial lesson: We might not be tracking the environmental impacts of battery storage fires properly.
The following conversation was lightly edited for clarity.
Alright let’s start from the top – please tell my readers what your study ultimately found.
The bottom line is that we detected deposition of fine airborne particles, cathode material – nickel, manganese, and cobalt – in the area surrounding the battery storage facility. We found those particles right after the fire, immediately detected them in the field, sampled the soils, and found visible presence of those particles using different techniques. We kept measuring the location in the field over several months after the fire.
The critical thing is, we had baseline data. We had been surveying those areas for much longer before the fire. Those metals were in much higher concentration than they were before, and they were clearly related to the batteries. You can see that. And we were able to see changes in surface concentrations in the soils over time, including from weather – once the rains started, there was a significant decrease in concentrations of the metals, potentially related to runoff. Some of them migrated to the soil.
What we also noticed is that the protocols that have been used to look at soil contamination call for a surface sample of 3 inches. If your sample thickness is that and the layer of metal deposit is 1 millimeter or 5 millimeter, you’re not going to see anything. If you use standard protocols, you’re not going to find anything.
What does that mean for testing areas around big battery storage fires?
That’s exactly what I hope this work helps with. Procedures designed in the past are for different types of disasters and incidents which are more like landslides than ash fallout from a fire. These metal particles are a few microns thick, so they slide easily away.
It means we have to rethink how we go about measuring contamination after industrial fires and, yes, battery fires. Because otherwise it’s just completely useless – you’re diluting everything.
The other thing we learned is that ashfall deposits are very patchy. You can get different samples between a few feet and find huge differences. You can’t just go out there and take three samples in three places, you have to sample at a much higher resolution because otherwise you’ll miss the whole story.
When it comes to the takeaways from this study, what exactly do you think the lessons should be for the battery companies and regulators involved?
There are a lot of lessons we learned from this fire. The first is that having baseline data around a potential fire site is important because then you can better understand the after.
Then, the main way to assess the potential hazards during the fire and after the fire are air quality measurements. That doesn’t tell you what’s in the air. You could have a high concentration of pollen, and then you know the quality of the air, but if you replace that with metal it is different. It’s not just how much you’re breathing, but what you are breathing.
Also, fast response. [Vistra] just released a report on soil saying there was nothing … but the sampling was done eight months after the fire. Our study shows after the fire you have this pulse of dust, and then it moves. Stuff moves to soil, across habitat. So if you don’t go out there right away, you might miss the whole thing.
Finally, what we found was that the fallout from the fire was not a bullseye pattern centered at the facility but rather offset kilometers away because of the wind.
We didn’t know much about this before because we didn’t have a real case study. This is the first real live event in which we can actually see the effects of a large battery burning.