Skip to content
Local Ordinance Site selection Data Center

Data Center Zoning: What Cities Actually Require

Obedio research
Obedio research

Between June 1 and September 12, 2026, 2,146 local governments in the United States took up a data center item in a public meeting — 5,446 agenda items in all. Taken together they show what a developer will actually be asked for in a new jurisdiction, and how much of it is still unsettled.

At a Glance
5,446 data center agenda items across 2,146 jurisdictions, June 1 – September 12, 2026
1,550 items mention a moratorium, across 788 jurisdictions
46 jurisdictions state a setback or buffer distance in feet
26 state a noise limit as a number
687 jurisdictions raised water, cooling or gallons

Most Cities Pause Before They Write Rules

A temporary pause is the most common local action on data centers by a wide margin. Of the 5,446 items, 1,550 mention a moratorium, spread across 788 jurisdictions — far more than every numeric standard in the record combined.

Twelve months is the usual length, appearing in roughly 255 items. Six months appears in about 83, eighteen months in 28, a 180-day pause in 33, and two years in 23. Nearly all of them attach a study directive: Newton Falls, Ohio introduced an emergency twelve-month moratorium that also directs a review of the city's zoning, utility, infrastructure and public-safety standards, and temporarily suspends discretionary utility-service approvals along with land-use approvals.

A few would narrow the pause by size rather than by use. Chemung, New York referred a proposed moratorium to the town and county planning boards in June and scheduled a public hearing, which it held in July; the draft exempts academic, research and educational computing facilities whose aggregate IT load does not exceed 1 megawatt. In Dover-Foxcroft, Maine, a resident brought a moratorium proposal to the Select Board in July; as described in her testimony it would run 180 days and apply only to data centers larger than 10 megawatts.

Where the Activity Is Concentrated

Five states account for most of the volume. Pennsylvania leads with 890 items across 339 jurisdictions, narrowly ahead of Michigan (809 items, 274 jurisdictions), then New Jersey (603 / 171), Ohio (503 / 158) and New York (299 / 148). Virginia, long the center of the industry, records 174 items across 51 jurisdictions, where the regulations are generally further along.

Pennsylvania's lead is breadth rather than depth. Nearly 340 distinct Pennsylvania jurisdictions took up a data center item in this window, most of them for the first time.

The Setback Is the Most Common Hard Number

Where a jurisdiction writes a number, it is usually a distance. Forty-six jurisdictions state a setback or buffer in feet, and the spread between them is wide.

Kent County, Delaware has proposed 300 feet for the facility and 400 feet for accessory equipment including generators. Stow, Ohio has proposed 75 feet from a property line abutting residential use. Hogansville, Georgia has text amendments at second reading that would increase setbacks to 750 feet next to residential, public or institutional uses.

Granbury, Texas shows how contested the number can be. A resident drafted an amendment calling for a 1,000-foot setback; city staff countered with 500 feet from residential districts and 300 feet from churches, schools, day cares and hospitals, and flagged the risk of a regulatory taking at the larger distance. The council postponed the decision in August.

The measurement point matters as much as the distance. Norton, Ohio's proposed ordinance measures its 1,000-foot separation from the closest outer wall of the nearest building or any noise-producing apparatus on the property, to the outer wall of a place of public assembly or the property line of any residentially zoned parcel — with a separate 200-foot setback to all property lines. Penn Township, Pennsylvania has proposed a 300-foot setback from any body of water, perennial or intermittent stream, or wetland.

There is a point where distance becomes exclusion, and at least one township has done the arithmetic in public. West Whiteland Township, Pennsylvania found that at a 1,000-foot separation from sensitive receptors, about 80 acres of the township remain eligible — and roughly half of that is floodplain requiring a variance. Township staff cautioned that counting an athletic field as a sensitive receptor would create a de facto exclusion.

Noise Limits Are Rarer Than You Would Expect

Noise comes up constantly — more than 200 items mention decibels — but only 26 jurisdictions state an actual number. Where they do, the limits run from about 35 dB to 80 dB, with the largest cluster at 45, 55 and 65.

Perryville, Missouri adopted a 65 dB(A) limit in August. Penn Township, Pennsylvania has proposed 65 dBA during the day and 45 dBA at night, measured at the boundary of the property containing the sensitive receptor rather than at the data center's own line — a choice that removes the advantage a very large parcel would otherwise give an operator.

The gap between a limit and a workable limit is being argued by residents as much as by staff. In Lancaster, Ohio an adjoining property owner filed a written comment arguing the city's draft specifies no acoustic metric at all — no weighting, no averaging period, no measurement method — and proposed replacing it with 45 dB(A) and 55 dB(C) as a one-hour equivalent level at the adjacent residential or agricultural property line overnight. The C-weighting is aimed at the low-frequency hum that A-weighted limits tend to miss.

Vibration is being treated as a separate question in a growing number of places. Pleasant Township, Ohio has discussed requiring a vibration study within 2,000 feet of a sensitive use.

Water Rules Now Cover the Source as Well as the Volume

Water, cooling or gallons came up in 1,031 items across 687 jurisdictions. The common form is a daily cap. Perryville, Missouri adopted one in August: no more than 50,000 gallons per day on a thirty-day average.

A cap alone still lets an operator supply itself, and some jurisdictions are closing that route. Norton, Ohio's proposed ordinance states that the applicant is responsible for providing all water for cooling and daily operations, and that the use of existing wells and the digging of new wells are not permitted. Statesboro, Georgia paired a closed-loop requirement with a well-drilling ban to protect the local aquifer. Washington Township, Michigan has proposed an intensity ratio instead of a flat ceiling — 115 gallons per 1,000 square feet above a 60,000-square-foot threshold.

Residents are pushing for thresholds that reach further than the use itself. In Tilden Township, Pennsylvania a resident asked the township to require a water study for any project using more than 5,000 gallons per day, whether or not it is a data center.

Who Pays for the Grid

More than a hundred items address substations, interconnection or ratepayers. The direction is consistent: the developer pays, and says so in writing before approval.

Broken Bow, Nebraska gave first reading in August to a draft ordinance that would require a three-month utility deposit to protect ratepayers from unpaid bills if an operator defaults — after adopting a moratorium in July. The council declined to waive the three readings. Everett, Massachusetts has proposed requiring developers to pay for any electrical infrastructure issues. Franklin County, Virginia's planning commission has drafted a change that would remove the by-right data center use in one district and require, for any facility expected to need at least 100 megawatts, both a sound assessment and specified substation and transmission information from the serving utility.

The Checklist: What a Complete Application Now Looks Like

Across the ordinances that have actually been written, the same items recur. A developer entering a new jurisdiction should expect to answer most of these.

Permitted district and approval route. Almost nowhere is a data center by right. Conditional use, special exception and special land use are the normal paths.

Setback, and the point it is measured from. Fence line, building wall, and noise-producing equipment are all in use, and they are not interchangeable.

Noise limit, weighting and measurement standard. Ask whether the limit is A-weighted, C-weighted, or both, and whose property line it is measured at.

Water source and daily cap. Increasingly two separate requirements.

Evidence of interconnection at application. A will-serve letter, power purchase agreement or written utility agreement, filed with the application rather than promised later.

Decommissioning security. Thirty-six items pair decommissioning with a bond, surety, letter of credit or other financial assurance. Broken Bow, Nebraska's draft would make the bond amount subject to re-evaluation every three years.

Third-party review escrow. Pontiac, Michigan's proposed amendment would require an escrow deposit for third-party review and post-approval compliance monitoring.

Pre-application public process. Upper Frederick Township, Pennsylvania has proposed requiring two public informational meetings before a conditional use application may be filed.

Post-construction audits and metering. Pontiac's proposal would let the city audit and meter the facility at the applicant's expense to confirm continuing compliance.

Host community payment. Still rare — fewer than 20 items mention one. It is among the least developed levers in the record, and the one most likely to change in the next year.

One Thing to Watch

Dexter Township, Michigan replaced the "community benefits" section of its draft with a "risk mitigation" section after legal review of the earlier language. Community benefit clauses are being written quickly right now, and some of them will not survive a challenge.

Where This Is Heading

There is no model ordinance for this use yet. The Michigan Townships Association sample ordinance is circulating widely and appearing verbatim in township packets, but it carries its own warning that adopting it without local changes is strongly discouraged.

Drafts also move quickly once they are on the table. Lancaster, Ohio's staff proposal set setbacks at 500 feet for principal structures and 750 feet for energy-generating accessory structures; the planning commission voted to recommend raising both to 1,000 feet. Perryville, Missouri adopted its ordinance in August and then added a 500-foot residential setback in September.

The pattern is clear enough to plan around. A jurisdiction that has just adopted a pause will usually write standards within a year, and the standards it writes tend to borrow from a neighbor that moved first. That makes the jurisdictions worth reading the ones that have just started a study, rather than the ones with a project already under review.

Obedio tracks data center items in local government meetings nationwide, as they are filed. See what is moving in the jurisdictions you care about.

Schedule a Demo

This article is factual background and is not legal, financial, or investment advice.

Share this post