Independent public-records research · Evidence and updates

Safeguards → Operating standards

Operating standards

Some rules exist; new campus-wide limits proposed, not established

Some day-to-day limits already exist, and covered solar facilities have numeric noise limits and separate lighting restrictions. New, campus-wide data-center standards for noise, light, and distance from homes were discussed but are not established in the amendments reviewed.

This is the area most likely to affect neighbors day to day. The key distinction throughout: what is an existing rule, what already applies only to covered solar, and what is a new data-center-specific limit still at the proposal stage.

Noise

General rule triggers SUP · numeric campus standard not established

General industrial noise can trigger special-use-permit treatment, and covered solar facilities already carry numeric limits (50 dBA at the property line of neighboring residentially-zoned lots, 45 dBA at existing neighboring residences 9 p.m.–7 a.m., and 60 dBA at the project boundary unless a higher level is agreed through the specified process). But no new campus-wide numeric data-center noise standard is established in the reviewed amendments — cooling fans and generators are exactly why a defined limit matters.

COUNTY-016

Distance from homes & setbacks

General setbacks exist · residential buffer discussed only

General minimums already apply (30 feet from public-road easements/rights-of-way, 10 feet from adjacent property lines). P&Z recommended discretion for additional data-center setbacks; a fixed, uniform residential buffer was only discussed, not adopted. Note that the one-mile habitable-structure mapping/notice requirement is not the same as a one-mile setback.

COUNTY-017

Lighting

Discussed · covered solar has conditional limits

Lighting restrictions were discussed as potential permit conditions, and solar rules separately allow full-cutoff requirements where needed. A uniform data-center dark-sky standard is not established in the amendments reviewed.

COUNTY-018

Air emissions & generator hours

Consultant preliminary assessment · project air permit unverified

In February correspondence the consultant said preliminary estimates indicated federal PSD air review for most criteria pollutants — an applicant representation, with no project air permit or emission limits established in the reviewed records. Air permitting sits primarily with the state DEQ, so this area's firm answers come through that route rather than the county rules.

consultant correspondence (p.2) · state review →

Spills, stormwater & containment

Existing application framework + proposed detail · project plans unresolved

Existing Chapter 7 industrial application rules already call for engineering and effluent information, and the proposed amendments add secondary-containment detail. But an application requirement is not a built safeguard — detailed, funded stormwater and hazardous-material plans (diesel, transformer oil, battery) for this project are not established in the reviewed records.

COUNTY-011

What you can ask for in county rule comments

The hearing concerns proposed countywide land-use rules, not a Site Layer 4 project permit. Distinguish a requested countywide standard from a future project-specific condition.

These are proposed safeguards, not adopted requirements. The responsible body, legal authority and project applicability must be verified before adoption.

  • Numeric campus-wide limits, adopted before approval — day/night noise in dBA at the property line and nearest residence, dark-sky lighting, and generator run-hour caps.
  • Funded compliance testing at commissioning and in operation, paid by the operator.

Countywide rules hearing — how and when to comment →

One caution: the county's existing solar rules cover qualifying solar only — they don't automatically reach the gas plant, standalone battery, or data center. Go deeper: the full operating entries (COUNTY-016–018, 031). Where the record is silent, this page says so.