Research note

Four of Five Data Center Ban Votes Followed Earlier Local Restrictions

Four of the five US municipalities classified as adopting full data-center bans on November 3, 2026, had already adopted a restriction before Election Day. One had enacted a zoning prohibition; three had imposed moratoria. The votes mattered, but they were not necessarily the first point at which local governments acted against data-center development.

This is an independent five-case cross-check of Ballotpedia’s “five full bans” category, not an estimate of opposition or legal enforceability across the United States.

The five cases

Municipality Documented step before November 3 What voters approved Evidence
Alhambra, California June 22: Ordinance O2M26-4863 prohibited data centers through zoning. Measure DB affirmed the pre-existing ban as voter-approved law. City zoning records; Measure DB analysis
Edgewater, Florida September 14: Ordinance 2026-O-21 halted processing and approval of data-center permits. Amendment 4 placed a prohibition in the city charter, with voter approval required for changes. City council legislative record
Hubbard, Ohio June 1: Ordinance 12-26 imposed a 12-month moratorium. A prohibition on data centers, with modification or repeal by another ballot measure. Municipal ordinance register; independent document-level verification
Urbana, Ohio March 3: Resolution 2727-26 imposed a 12-month moratorium, passed 6–1. A charter prohibition with a limited, conditional exception. Official city council minutes (March 3, attached to March 17 packet)
Granville, Ohio No comparable earlier restriction established in this review. Charter prohibition covering facilities meeting a definition with a greater-than-25-MW power threshold. Published text of proposed Section 10.12

Calculation: Assign 1 when a pre-election municipal data-center prohibition or moratorium has been documented and 0 otherwise. The recorded values are 1, 1, 1, 1, 0. Their sum is 4; the denominator is the five municipalities in Ballotpedia’s full-ban category. Thus 4 ÷ 5 = 80%. Because the last 0 means not established, rather than proof no earlier restriction existed, 80% is a documented minimum for this five-municipality group.

Why the earlier restrictions matter

The timing changes the interpretation of the vote. Alhambra had already banned data centers through its zoning ordinance; Measure DB affirmed that choice through a popular vote. Hubbard and Urbana had already paused development for twelve months; the November measures removed the same built-in deadline from the new prohibitions. Edgewater had already stopped permitting, while the ballot put the restriction into its charter.

These are different legal changes. A voter-approved charter provision can be harder for a council to reverse than its own earlier ordinance. A permanent prohibition is different from a one-year pause. Neither fact makes the vote redundant: it explains what changed.

Edgewater also shows why a label is not enough. The city council agenda called its September ordinance a “permanent moratorium,” yet contemporaneous reporting described a twelve-month sunset in the ordinance. We have confirmed adoption of the pre-election permitting restriction, not independently verified the operative sunset clause in the signed final text. Its duration is therefore not coded as permanent in this analysis.

Another classification caveat: Granville

Ballotpedia includes Granville among the five full bans. But the publicly reproduced proposed amendment defines the covered data center using a power threshold greater than 25 MW. A smaller facility would not be barred by that charter provision solely under this definition, although other rules might prohibit it. This suggests the term “full ban” is not always equivalent to a ban on data centers of every size; it is not a claim about the final legal status of any particular project.

What can be concluded

Election-night counts capture decisions by voters; they do not identify when a community first constrained development. In this narrowly defined five-case group, at least four communities had taken a restrictive municipal step before the vote. For reporting on the November results, the more informative distinction is between first-time restrictions, extensions of temporary pauses, and voter entrenchment of existing policy.

Method and source limitations

Unit: municipality, not project or ballot cast. Selection: all five November 3 measures listed in Ballotpedia’s “full bans” group as checked November 16, 2026. Positive test: an identifiable municipal prohibition or moratorium adopted before November 3. This measure records prior official action, not proof of current enforceability, absence of litigation, or legal redundancy.

Alhambra and Edgewater are supported by municipal records; Urbana’s official minutes record the 6–1 council vote. Hubbard’s ordinance is listed by the city and has been checked against an independent document-level reading of a signed copy, but we could not directly retrieve and inspect that signed copy. Granville’s threshold is supported by published ballot language; the post-election consolidated charter text was not independently inspected. Election results and legal implementation may change after the research cutoff. The calculation is fully reproducible from the five linked records and the stated coding rule.

The Null Institute research note. Source cutoff: November 16, 2026. An independent recalculation of public documents, not a legal opinion or a claim to have discovered the individual ordinances.