Sources & evidence

Independent research preview by Kevin Clark · Evidence review: 2026-10-16

What the evidence supports

Visible gaps

• 519 facility records have no operator.
• 1,479 have no positive campus MW value; capacity is distinct from annual electricity use.
• 1,479 have no named utility.
• 409 contain inherited PPA tags. These are withheld from campus contract claims because facility-specific sources are missing.
• Measured campus electricity, emissions, backup fuel, construction materials, and land use are not verified in the current dataset.

Claims removed during review

The public view no longer displays the 50 MW-per-campus demand heuristic, modeled plant emissions, inferred campus electricity mix, unsourced PPA claims, hand-drawn grid-risk regions, illustrative water-stress scores, or unsupported tour statistics. Nearby plant lines show distance context only.

How to cite and check it

Cite the underlying primary source and its reporting year when using a figure. Identify this map as an independent research preview and state its scope. A review date is not the observation date or a guarantee that every record is current.

Download evidence coverage and file checksums (JSON) · Download inventory coverage review (JSON)

To report a correction, email kc@kevinclark.ai with the facility ID, disputed field, and a supporting public source. Reviews are manual; no automatic update cadence is promised.

Grid geography and connection evidence

Grid boundaries are historical snapshots, disabled by default. They do not establish present regional membership, a campus supplier, or available connection capacity. The NERC file retains retired organizations; it must not be treated as a current Regional Entity map. Campus matches use simplified polygon geometry (0.01° tolerance), so boundary-edge locations require source-level review.

Retrieved 2026-10-17. Source dates describe original records; validation dates and hosting updates are separate. Public services mirror HIFLD-derived data; PNNL hosts the ISO/RTO snapshot.

Facility Grid tabs distinguish unverified inventory capacity from IT load, measured peak demand, requested MW, connection approval, and energization. Missing evidence stays unknown. Region exports list geographic inventory matches, never a sum of confirmed connected load. Comparisons do not aggregate MW or water; repeated water reporting locations are flagged.

NERC assessments · EIA operating data · FERC electricity resources. Live grid metrics, current queues, available substation capacity, and confirmed campus connections are not imported.

National facility and development register

The atlas is independent research for utilities, grid operators, developers and infrastructure researchers. National scope is not complete national coverage. The register filters the retained inventory by state, operator and inherited status, with exports preserving verification limits.

The separate project register contains 16 selected operator-reported phases reviewed 2026-10-18. Operating and construction phases are kept distinct. Phase-to-inventory identities and exact coordinates remain unresolved; these records are not new map markers or additions to the national location count. Operator statements are not independent site verification. Completion targets are not approved energization dates.

• Microsoft: Mount Pleasant · first facility — reported operational as of 2026-06-23; phase: First facility; not the full campus.
• Microsoft: Mount Pleasant · second facility — reported under construction as of 2026-06-23; phase: Second facility adjacent to the first.
• Meta: Richland Parish · AI data center — reported under construction as of 2026-08-04; phase: Campus; individual buildings and phases not reconciled.
• Meta: Lebanon · AI data center — reported under construction as of 2026-08-04; phase: Campus; individual buildings and phases not reconciled.
• Meta: El Paso · AI data center — reported under construction as of 2026-08-04; phase: Campus; individual buildings and phases not reconciled.
• Meta: Tulsa · AI data center — reported under construction as of 2026-08-04; phase: Campus; individual buildings and phases not reconciled.
• Meta: Temple · operating milestone — reported operational as of 2026-07-22; phase: Data center serving traffic; later expansion scope not established.
• Meta: DeKalb · serving-traffic milestone — reported operational as of 2023-11-29; phase: Serving-traffic milestone; does not establish completion of every building.
• xAI: Memphis · original Colossus milestone — reported operational as of 2024-12-23; phase: Original Colossus; not Colossus 2 or later expansions.
• Amazon Web Services: Salem Township · campus announcement — reported announced as of 2025-06-09; phase: Announced campus investment; permits, construction and individual phases not established.
• Amazon Web Services: Falls Township · campus announcement — reported announced as of 2025-06-09; phase: Announced campus investment; permits, construction and individual phases not established.
• Microsoft: Cheyenne · proposed land acquisition — reported announced as of 2026-04-14; phase: Proposed 3,200-acre expansion; not the existing operating footprint.
• OpenAI: Abilene · initial operating capacity — reported operational as of 2025-09-23; phase: Initial training and inference workloads; not completion of the entire campus.
• OpenAI: Abilene area · potential expansion — reported announced as of 2025-09-23; phase: Potential additional expansion near the flagship site; separate from initial operating capacity.
• Core Scientific / CoreWeave: Muskogee · HPC groundbreaking — reported under construction as of 2024-11-18; phase: Dated groundbreaking; Core Scientific host and CoreWeave customer roles differ.
• Meta: Huntsville · two-building expansion announcement — reported announced as of 2022-06-09; phase: Two-building expansion; distinct from the earlier campus.

Scope-review notes flag unresolved Wisconsin phases, DeKalb operating/construction entries, Temple's dated operating milestone, original Colossus versus later expansions, the Salem and Cheyenne announcements, and Abilene initial operations versus potential expansion. Download the inherited future-project review queue. No campus status or coordinate was silently overwritten. Announcements, permit applications, approvals, construction, operation, cancellation and withdrawal require separate dated claims; missing approvals, MW and utility evidence stay unknown.

Future-project review findings

Initial desk review completed October 18, 2026 for all 20 inherited future entries. Five entries lack matching primary project evidence: Hamlin Township, Bridgeport, Blue Bell, Clarksburg and Redmond. Other entries retain unresolved campus or phase scope. An unsuccessful search does not establish that a project does not exist. Undated community pages use observation dates, never invented publication or opening dates. Municipal staff recommendations are distinct from final decisions. The downloadable review queue includes findings, reviewed sources, search scope and evidence needed for each record. No inherited phase identity or coordinate has been confirmed by this review.

Facility names and business relationships

Facility names and operators remain inherited inventory fields: 1,224 of 1,499 entries have a name and 980 have an operator. Legal property ownership and building tenants have not been established. Four selected source profiles describe Google campus context in The Dalles, Council Bluffs and Douglas County, plus Core Scientific/CoreWeave roles in a dated Muskogee project announcement. Candidate links are not verified parcel or building identities. A hosting provider, property owner, customer and end user are separate roles. Undisclosed parties remain unknown. Download business relationship sources and candidate links.

Snapshot integrity

SHA-256 checksums identify the reviewed local files; they establish file identity, not factual accuracy.

public/datacenters.json
1fd039a9e6b521a73e74bece59e3127db2ca8142a9ea93ddbaa267a7b8e5aa0b

public/powerplants.json
fea0ef748db8033f76851edd5f3fbeed7260b5fa0b7f52b6bd4a0fac9168ee69

public/watersheds.json
41684c5e96197b43f9bd387d5ba1df1ab30ab4ba6daeb4b9379c59aef8dd0618

src/data/water-disclosures.json
8eee221463da3f1cffad1be324587a15ad1ca4498ec93d9f0701b95ef41088e5

src/data/water-history.json
3b7b8b06d3a01df1a12ea50cc42443b2c6f4e641ace71b69ffbfa6a023ee440d