Data Center Opposition Returns to Northfield

Griff Wigley

Audio by Paper2Audio.

A proposed zoning-code change drew a packed hearing and a Planning Commission recommendation to ban data centers outright again.

O n Thursday, August 20, the Northfield Planning Commission meeting filled past capacity in the City Council chambers. I counted 28 residents who spoke during the public comment period, plus at least two residents who submitted written comments through the city's online comment system rather than speaking in person. Nearly all spoke in opposition to easing the city's rules around data centers.

The crowd's size caught staff off guard. When I arrived 10 minutes before the meeting, City Administrator Ben Martig had already moved the media table behind the dais to make room for extra chairs. He and Community Development Director Scott Wopata kept at it as people continued arriving, pulling in more chairs, opening two additional rooms for the overflow, and helping residents fill out speaker request slips.

By the end of the night, the Commission had gone considerably further than what was actually on the agenda.

Image summary: A photograph of a crowded room where a group of people are seated and attending a presentation. In the foreground, a man sits at a long desk with a laptop, facing a larger group of people seated in rows of chairs. To the right, a blue banner is partially visible with the words "COW'S COLLECTIVE COMMUNITY".

What was proposed, and what happened

The agenda item began as a request from city staff to change a single number in the Land Development Code: reduce the required setback for data processing facilities from 3,950 feet to 200 feet, measured from any existing or planned park, trail, or recreational feature. Staff described the 3,950-foot figure as a “typo” or an “error.” At that distance, a data center is effectively impossible anywhere in Northfield's industrial zones.

Some residents didn't buy the "typo" framing, and by the end of the discussion, the Commission didn't fully adopt it either. Rather than simply reduce the setback, commissioners amended the proposal into an outright prohibition: data processing facilities would be struck from the list of permitted and conditional uses in the city's industrial district entirely.

A second motion directed staff to return within two months with a separate framework, based on power consumption, that could distinguish small-scale operations from hyperscale ones as part of the broader Land Development Code rewrite already underway.

Both motions passed unanimously. The recommendation now goes to the City Council, which has the final say.

What got answered, and what didn't

Planning Commission policy doesn't allow staff to respond to questions during the public comment period itself. City Councilor Kathleen Holmes, who sits on the Commission as a non-voting liaison, noted that staff would follow up individually with anyone who left contact information. Northfield News reporter Colton Kemp, who covered the meeting, wrote that Wopata kept a running list of questions on his laptop.

I emailed Wopata directly to ask whether he planned to publish written answers to that list. Wopata said, in a brief reply sent by phone from an airport, that he didn't have a plan or a platform to do so. He said he'd likely raise the questions in front of the City Council instead, when the item comes before that body, "to ensure the voices/questions get heard there too."

That means most of what follows won't get a formal public answer unless Council raises it. Some of it already has an answer in the public record, even if no one said it out loud that night.

Are there any secret agreements with a data center developer?

No. Holmes stated directly, on the record, that no council member or staff member has signed a non-disclosure agreement, and no project is currently pending before the city.

Has Northfield been approached by any data center company?

This one remains open. No N.D.A isn't the same as no contact. Kuhlmann's answer in the moment, 'I don't know of anybody who has,' wasn't authoritative, and it's a narrower claim than Holmes's 'no pending project' statement.

What about water use, and the aquifer?

Also unanswered on the record. One resident asked specifically which aquifer would supply an industrial-scale user's water needs. I may look at this in a future post; the University of Minnesota has an ongoing research project on water and energy use by data centers in nearby watersheds that may be a useful resource.

Where does the 200-to-500-foot range actually come from?

The Commission's written findings state that a 500-foot-or-less setback from parks and trails is “typical” nationally, based on staff's review of other cities' ordinances, without naming which jurisdictions or studies. Asked directly why 200 feet specifically, Wopata said it matches the city's existing 200-foot residential setback, and that noise, the original concern behind the setback, is handled through decibel limits enforced at the property line rather than through distance. What's still missing is the specific research behind the 'typical' range claim itself. The record doesn't identify the jurisdictions or studies behind it.

Is this actually a typo, or something else?

This is the most tangled of the open questions, because the record contains multiple explanations that don't fully square with each other.

At the meeting, Interim City Planner Mathias Hughey explained where the 3,950-foot number came from: “That is essentially three-quarters of a mile. That is where that number is." A few minutes later, describing the same figure, he called it "a typo at one point," and said it was "more accurately probably just described as an error."

City records confirm the three-quarters-mile origin directly. A December 3, 2024 memo from City Administrator Ben Martig to the City Council describes the setback as “reduced... from 4,000 feet to 3,950 feet for accuracy,” noting that “3,950 feet is 3 over 4 of a mile.” That adjustment was one of several small technical corrections listed in the memo, alongside things like fixing a building-height conflict elsewhere in the code. Whatever the origin of the original 4,000-foot figure, the December 2024 record describes the change to 3,950 as a deliberate correction for accuracy, not as a typo.

Those two things sit oddly together with this year's framing. A distance calculated and refined to approximate three-quarters of a mile isn't usually what people mean by a typo.

The Commission's written resolution offers a third framing, different from either: it states that staff identified the 3,950-foot setback as “a barrier to industrial business creation and economic development,” tied to a 2025 Comprehensive Plan directive to remove such barriers from the Land Development Code. Nothing in that language describes an unintentional mistake.

One resident raised this exact discrepancy in a written comment submitted before the meeting: “Are we correcting a typo, or are we deliberately removing a barrier to data-center development? Those are not the same thing.”

What actually triggered this review now?

Wopata's answer, offered in response to a similar question about a different item on the same night's agenda, was that identifying obstacles to the city's development goals is simply part of his job as the recently hired Community Development Director. Nothing in the public record confirms or rules out any contact with a developer, site selector, or utility beforehand.

The relevant history

This isn't the industrial park's first pass through this debate, and public opposition isn't new either, though this year's turnout dwarfs what came before. At the Planning Commission's November 21, 2024 hearing, seven residents spoke against including data processing facilities in the industrial code, citing water and electricity strain and, in several cases, concern for a neighboring horse farm. Three spoke in favor: Chris Kennelly, who said he had no economic interest in the area; Jane Bartho, president of the Northfield Chamber of Commerce; and Tom Sorem, who owns some of the land that would be rezoned. The Commission voted 5 to 1 to strike data processing facilities from the code entirely, removing both the permitted-use listing and the full set of performance standards staff had drafted. Bill Kuhlmann, now the Commission's chair, cast the lone vote against striking them.

Five days later, the City Council took up the same amendment. Then-Community Development Director Jake Reilly told the Council that the Planning Commission recommended removing data processing facilities, while staff recommended keeping them. Bartho and Sorem both spoke again in favor of keeping the language.

The Council sided with staff, voting 7 to 0 to retain data processing facilities in the code, including the 3,950-foot setback at the center of this year's dispute. A second reading passed 6 to 0 a week later, with one council member absent.

Councilor Holmes, defending that 2024 decision, pointed to the scarcity of industrial land in Northfield and the city's long-standing goal of diversifying its tax base beyond residential property. Whether the Council reaches the same conclusion this time, faced with this Commission's unanimous recommendation, the reversal of its own chair's 2024 position, and a turnout far larger than 2024's, is now the open question.

What's Next?

Staff has two months to return with a power-consumption-based framework intended to distinguish hyperscale facilities from smaller, already-existing data processing uses in town. The City Council will then decide whether to adopt the Commission's prohibition, adopt some modified version of it, or take a different path entirely, as it did in 2024.

I plan to keep following this as it moves to Council.

Links

- August 20 Planning Commission

- Northfield News, August 21: Northfield moves to ban hyperscale data centers following packed public hearing

- Northfield Land Development Code

Image summary: An aerial map photograph of a rural landscape featuring a large, irregular area highlighted in blue, situated among green fields, wooded patches, and a network of roads.

Will the new hyperscale data centers shock your electric bill?

Read full story to

Table summary: A simple subscription form consisting of an input field labeled Type your email... followed by a button labeled Subscribe.