Research Note: Data Center Siting

Research Note: Data Center Siting

Question

The siting guide needs to find fatal constraints before a project team reduces a location to land price, power promises, and incentives.

What the sources establish

The DOE data-center resource hub connects large-load development with generation, transmission, efficiency, permitting, and public infrastructure. The Office of Indian Energy FAQ adds land area, water, fiber, interconnection, power generation, leases, permitting, Tribal law, sovereignty, revenue, and workforce.

Fairfax County's adopted zoning amendment shows how local fit can create measurable building, equipment, noise, screening, and distance requirements. Its terms are jurisdiction-specific and should be treated as an example of questions a site record must answer.

The USGS National Groundwater Conditions application provides current and historical context for monitored groundwater locations. It is a screening input, not a substitute for a water-right, utility-capacity, hydrogeologic, or watershed study.

The FEMA National Risk Index and local hazard records can identify flood, wildfire, heat, storm, seismic, and other exposures. A national screening score should not replace parcel-level engineering, climate projections, insurance analysis, or emergency planning.

EPA's Clean Air Act resources for data centers make backup and on-site generation part of site due diligence. A reliable electrical design can still create a local permitting and air-quality constraint.

Disagreement and uncertainty

Public maps vary in resolution, freshness, and purpose. Utility capacity is not established by a nearby substation. Water availability is not established by a pipe or an average annual rainfall figure. Fiber proximity is not the same as diverse usable routes. Tax incentives do not cure a missing interconnection, inadequate emergency response, incompatible land use, or an unwilling host.

A site can be technically feasible and still fail governance, sovereignty, ratepayer, community, or closure tests.

Editorial use

The public guide should use a constraint-first sequence. Define the workload and phases. Test power, water, fiber, hazards, land, permits, air, noise, construction, workforce, emergency response, public infrastructure, community authority, expansion, and closure. Record every disqualifier, evidence owner, source date, uncertainty, and next decision.

Do not publish a composite score. A site advances only when each fatal constraint is resolved or explicitly accepted by the party with authority to accept it.