Loading map…

Castanea Township

Anti-Data Center Policies

Castanea Township has enacted two data-center procedural resolutions, but the available descriptions don’t explain their requirements or practical effects, so their impact is unclear.

Incentives

Financial Incentive
3

Financial incentives not assessed from full ordinance text in this tracker import; an empty list is not a confirmed finding that no incentive exists.

Financial incentives not assessed from full ordinance text in this tracker import; an empty list is not a confirmed finding that no incentive exists.

Financial incentives not assessed from full ordinance text in this tracker import; an empty list is not a confirmed finding that no incentive exists.

current law · Castanea Township
The supervisors adopted Resolution 2026-02, and Data Center Resolutions 2026-01 and 2026-02 were forwarded to the solicitor.Castanea Township, Clinton County — data-center procedural resolution 2026-02

What this means

A score of -3 is assigned as the requested fallback because the available sources do not provide enough detail to assess the impact. It should not be read as a source-confirmed finding of significant barriers.

Sources

current law · Castanea Township
The supervisors approved Data Center Resolution 2026-03.Castanea Township, Clinton County — data-center procedural resolution 2026-03

What this means

A score of -3 is assigned as the requested fallback because the available sources do not provide enough detail to assess the impact. It should not be read as a source-confirmed finding of significant barriers.

Sources

pending · Castanea Township
The township secretary said on October 19, 2026 that this draft, based on a Clinton County model for its municipalities, has not been voted on and that later drafts likely exist, and the supervisors' October 19, 2026 agenda listed the data center ordinance for discussion, so no adoption of Ordinance 2026-05, which was on the October 5, 2026 agenda, is confirmed.Castanea Township, Clinton County — proposed data-center ordinance (None Adopted)

What this means

The proposal would impose setbacks from homes or other protected places and noise limits and sound testing. Data centers still have an approval route, but the siting or operating limits significantly narrow feasible projects.

Restrictions & requirementsHide restrictions & requirements28
  • Approval type left as conditional use or special exception; either option earns 1 point, title and § 536.C.2(a)

  • Agricultural lands are Sensitive Receptors for setbacks but data centers are not barred, § 202

  • Base height of § 307 applies; no data center height limit stated, § 536.A.1

  • Environmental Impact Statement required, § 536.D.5

  • Expansion that affects approval thresholds must reapply before construction, § 202 Aggregation.

  • 60 dBA day and 50 dBA night and weekend at the property line, § 536.C.1

  • Section 536.C.2 requires preliminary, interim, and as-built noise studies using ANSI S1.4 meters, with the as-built study six months after occupancy, but the as-built study is not required at full operating load.

  • Backup generators may not run at night except in emergencies; no hours cap, § 536.F.2(b)

  • Vibration study showing nothing perceptible beyond the property line, § 536.C.3.

  • Water feasibility study for non-public sources with nearby well inventory; no pump test, § 536.D.3

  • Cooling method disclosed and closed-loop encouraged, not required, § 536.D.1 to D.2

  • Projected demand and drought consumption addressed in the study; no cap or reporting, § 536.D.3

  • Study describes water recycled or discharged; no approved cooling discharge plan, § 536.D.3(e)

  • Batteries, fuel, and refrigerants disposed of under state and federal law at decommissioning, § 536.J.3(b)

  • Provider certification of capacity without rate-raising upgrades; no electrical inspection, § 536.F.1.

  • On-site generation is a separate use approved under the zoning regulations; no separate setbacks, § 536.F.2

  • Provider must certify service without upgrades that raise local rates, and rate impacts must be noted, § 536.F.1

  • Landscape buffer at least 50 ft wide, § 536.A.1(c)

  • Equipment within 500 ft enclosed or screened with sound barriers where feasible; no height standard, § 536.B.1

  • Emergency Response Plan accepted by the fire department; updates tied to the County Hazard Mitigation Plan, not annual, § 536.G.1

  • First responders must receive system-specific training, § 536.G.1(d)

  • Hazardous materials addressed at decommissioning and bulk fuel storage under township rules, §§ 536.F.5 and J.3

  • Annual fire safety inspections, § 536.G.1

  • Bond or letter of credit in an amount acceptable to the township; removal within 18 months after a one-year start, § 536.J

  • Section 202 defines a data center to include cryptocurrency mining, blockchain processing, and server farms, with a hyperscale class for artificial intelligence, and excludes equipment secondary and customarily incidental to another use, but the exclusion sets no stated size or power limit.

  • One as-built sound study after opening, with later studies optional, § 536.C.2(c)

  • Noise violation requires a Corrective Action Plan; general enforcement under the zoning ordinance, §§ 536.C.2(c) and N

  • Public informational meeting before any hearing or Planning Commission meeting; no project website, § 536.M

Sources

Thank you to the Pennsylvania Data Center Ordinance Tracker for providing proposed local ordinance data for PA. Citation: padatacenterordinances.org, accessed November 3, 2026.Cookie preferences · Report missing data