Mike Hammett

How things actually work.

How I Checked Erin Brockovich’s Community-Report Map

Written by

in

I’m CTO of DNA Communications and co-founder of FD-IX, an internet exchange. I have no financial interest in any data center project. This piece documents the map analysis in “What Erin Brockovich Gets Right, and Wrong, About AI Data Centers.”

TL;DR

  • The analysis uses only Brockovich’s own published files: her community reports, her list of facilities, and her zip-code coordinates, as archived on October 10, 2026 [1][2][3].
  • 482 of her 9,683 reports through October 4, 2026, 5.0%, carry a zip code within 10 miles of at least one operating facility on her list and no listed project that isn’t operating. If cancelled projects don’t count, the figure is 510, 5.3%. A wider count, 1,084 reports or 11.2%, sits within 10 miles of an operating facility regardless of what else is nearby.
  • Across every radius from 1 to 30 miles, that share stays between 1.2% and 5.4%; below about 3 miles, the zip-code points are too coarse to mean much.
  • Averaged by status, operating campuses have 14.2 reports within 10 miles, proposed projects 14.3, and campuses under construction 17.9. Medians are 11, 8, and 13.
  • The code below reruns every figure against the archived files.

The inputs

Her map page loads three files from her site: community-reports.json, data-centers-map.json, and zip-geocodes.json. I confirmed that from the page’s own network requests on October 29, 2026.

The community reports file holds one record per report, with six fields: date, city and state, zip code, type, owner, and notes [1]. The archived copy holds 9,683 records, dated June 23, 2024 through October 4, 2026, and every date is in year-month-day form. The type field names the kind of facility, not the complaint: 9,661 records say data center, 18 say battery storage, and 4 are blank. Her stats page for that date shows the same total, 9,683, with data through October 4, 2026 [5].

The facility file lists 545 projects, each with a status and coordinates [2]. Its header says it was updated September 27, 2026, gives the counts by status (139 operational, 166 under construction, 39 permitted, 175 proposed, 26 cancelled), and names Compute Atlas and Epoch AI as its sources [2]. Her home page describes the list’s scope: the pins cover “publicly announced, major AI-focused and hyperscale facilities,” and “many smaller or unannounced facilities are not listed” [4].

The zip-code file gives one latitude and longitude for each zip code it covers, 2,465 of them in the archived copy [3]. The file doesn’t document how its maker chose each point, so I call it the zip code’s coordinate rather than its center.

The live reports file keeps growing. On October 29, 2026, it held 9,733 records, and requests with the version tag in the address, with a different tag, and with none all returned the same file. Filtering the live file to records dated on or before October 4 still returned 9,683, and rerunning the analysis on the live files that day gave the same 1,084 and 482. That match isn’t guaranteed later: a record can be deleted or edited, and the facility file’s statuses will change as projects open. The archived copies are the versions I analyzed, and the code below reads them.

FileArchived copyBytes
community-reports.json[1]1,403,943
data-centers-map.json[2]760,276
zip-geocodes.json[3]142,877

Their SHA-256 hashes, in sha256sum format:

51859eb219c6fa7c28db5421cd7129dac934650570e154968e793344dea75163  community-reports.json
c039d8f64fede66d9788ba3b7ccc00db832f7e8cbcecc15d1d3653a8d6047b40  data-centers-map.json
584fc354c560544e50d9194952b0d8aa1e573d31e52a3e5e4012f03bee5a3f5c  zip-geocodes.json

The method

The method sorts reports by how close their zip code sits to each facility on her list. For each report, I took its zip code’s coordinate and measured the straight-line distance to every facility, using the haversine formula with an Earth radius of 3,958.8 miles. A report counts as near a facility when that distance is 10 miles or less.

Each report goes into one bucket, the most advanced project nearby: operating first, then under construction, then permitted, proposed, or cancelled. Reports with nothing within 10 miles go into a “none” bucket. Five reports have no usable zip code: four are blank, and one, 76000, isn’t in the zip-code file.

The operating-only test then takes the reports near an operating facility and keeps those with no listed project of another status within 10 miles, cancelled projects included. A report near two operating facilities and nothing else stays in. It doesn’t depend on the bucket order: a report near an operating facility lands in the operating bucket whatever else is nearby, and the test then looks at every non-operating project on the list.

The density check counts, for each facility, every report within 10 miles of it, then gives the mean and median by status. Density counts aren’t exclusive, so one report can count toward several facilities.

Statuses come from the September 27 file, not from the date of each report. A report filed while a nearby project was still proposed counts as near an operating facility if that project had opened by September 27, so some reports in the operating group were filed before the facility ran.

The results

Bucket (10 miles)ReportsShare
Near an operating facility1,08411.2%
Near a campus under construction, no operating one2,00020.7%
Near only proposed, permitted, or cancelled projects2,37424.5%
Near nothing on her list4,22043.6%
No usable zip code50.05%

482 reports, 5.0% of 9,683, sit near an operating facility and no listed project of another status. They come from 128 zip codes. 333 are near exactly one operating facility; 149 are near two or more. The other 602 of the 1,084 reports near an operating facility are also within 10 miles of a project that isn’t operating; 28 of those are near only a cancelled one. If cancelled projects don’t count, the operating-only count is 510, 5.3%. Measured against the 5,458 reports within 10 miles of anything on her list, rather than all 9,683, 482 is 8.8%.

StatusFacilitiesReports within 10 miles (non-exclusive)MeanMedianFacilities with none
Operational1391,97414.2117
Under construction1662,96717.9139
Proposed1752,49914.3821
Permitted3978320.1162
Cancelled2637814.593

72 of the 139 operating campuses have no listed project of another status within 10 miles of the campus itself; 510 distinct reports sit within 10 miles of at least one of them. That isn’t the same group as the 482. The operating-only test looks at what is within 10 miles of each report; this count looks at what is within 10 miles of each campus. 441 reports are in both. The other 69 of the 510 are near one of those campuses and also near a non-operating project that is more than 10 miles from the campus. The other 41 of the 482 are near only operating campuses that each have a non-operating project within 10 miles of the campus but not of the report. That the 510 equals the operating-only count without cancelled projects is a coincidence. Only 40 operating campuses have no other listed facility of any status within 10 miles, and 330 distinct reports sit near those.

At 25 miles, the buckets shift to 2,312 near an operating facility, 4,800 near only other listed projects, and 2,566 near nothing on the list.

What the numbers do and don’t show

The numbers rest on two things the files don’t document: how each zip code’s point was chosen, and whether a report’s zip code is the reporter’s or the reported site’s. Her form asks for both the reporter’s address and the “AI Data Center Location You Are Reporting” [4]. If the zip is the reported site’s, distance roughly says which project a report is about; if it’s the reporter’s, it says how far the reporter lives from the nearest listed project. The file can’t settle which. Proximity says nothing about which facility a report concerns or what prompted it, and the 5% is a share of submitted reports. A rate of filing would need the population inside each circle, which her files don’t carry and I didn’t compute.

Counted by bucket, more reports sit near projects that aren’t operating, 4,374 or 45.2%, than near operating facilities, 1,084 or 11.2%. Another 4,220, 43.6%, sit near nothing on her list. Counted per facility, operating campuses average 14.2 reports within 10 miles, the same as proposed projects at 14.3, with a higher median, 11 against 8. The operating-only test removes 602 of the 1,084 reports near operating facilities because a non-operating project is also within 10 miles; 67 of the 139 operating campuses have one.

The bucket labels can also mislead in the other direction. Ahwatukee, in Phoenix, zip code 85044, has 18 reports in the operating-only group because Digital Realty’s operating PHX15 is within 10 miles. One of them, dated April 6, 2026, names Menlo Equities as the owner and describes “a million square foot AI center” less than half a mile from the writer’s house. Five others carry only the note “pics,” and 12 have no owner or note. Menlo Digital’s 38-acre Ahwatukee data center has been under construction since April 2026 [6], and it isn’t on her list within 10 miles of that zip code. The April 6 report is about that construction site, and the test files it as operating-only. The other 17 say nothing about which facility they concern, so neither the test nor I can place them.

A zip code’s coordinate can sit miles from a rural reporter’s home, and the size and direction of that error vary from place to place. Her list covers major AI and hyperscale facilities and leaves out many smaller ones [4], so “near nothing” means only that no listed facility is within 10 miles. The omitted facilities skew older, smaller, and already running, so their absence pushes the operating-only share down. A share of submitted reports also can’t count neighbors of a running facility who have never heard of her map. Reports also track approval fights: neighbors organize when a project is proposed, so a map built from voluntary submissions will cluster around proposals, whatever happens after a facility opens. The test measures distance only. It doesn’t measure noise, light, wells, water supply, or electricity costs.

Across every whole-mile radius from 1 to 30 miles, the operating-only share runs from 1.2% at 1 mile to a peak of 5.3% at 6 miles, or 5.4% if cancelled projects don’t count, then mostly falls as wider circles catch more new projects. Below about 3 miles, the circles get smaller than many zip codes, so a report’s assigned point may say little about where the reporter or the site is; I’d give those radii little weight. At 5 miles, it’s 442 reports, 4.6%. At 10 miles, it’s 482, 5.0%. At 25 miles, it’s 211, 2.2%.

The code

The code is here so anyone can check the numbers. One block of JavaScript reproduces every figure above from the three archived files [1][2][3]. Read it before you run it: it only downloads those three files and counts. Open any page on web.archive.org, for example, the archived stats page [5], open the browser’s developer console, and paste it. Your browser may ask you to type a confirmation before it accepts pasted code; that warning is there for good reason, so run only code you’ve read. Change RADIUS to rerun at another distance, and set CANCELLED_COUNTS to false to leave cancelled projects out of the operating-only test.

// Settings. RADIUS is in miles. CANCELLED_COUNTS: true counts a cancelled project as a non-operating project nearby.
const RADIUS = 10, CANCELLED_COUNTS = true;
// Archived inputs (October 10, 2026 captures). To use her live files instead, run on brockovichdatacenter.com
// and set FILES to ['/community-reports.json', '/data-centers-map.json', '/zip-geocodes.json'].
const FILES = [
  '/web/20261010001606id_/https://www.brockovichdatacenter.com/community-reports.json?v=20261004',
  '/web/20261010001606id_/https://www.brockovichdatacenter.com/data-centers-map.json?v=20260927',
  '/web/20261010001607id_/https://www.brockovichdatacenter.com/zip-geocodes.json?v=20260927'];
const [all, fj, g] = await Promise.all(FILES.map(u => fetch(u, {cache: 'no-store'}).then(r => r.json())));
const reps = (Array.isArray(all) ? all : Object.values(all).find(Array.isArray))
  .filter(r => (r.date || '') <= '2026-10-04');
const fac = fj.fac;
const R = 3958.8, rad = x => x * Math.PI / 180;
const hv = (a, b, c, d) => { const dl = rad(c - a), dn = rad(d - b);
  const h = Math.sin(dl / 2) ** 2 + Math.cos(rad(a)) * Math.cos(rad(c)) * Math.sin(dn / 2) ** 2;
  return 2 * R * Math.asin(Math.sqrt(h)); };
const near = (p, f) => hv(p.lat, p.lng ?? p.lon, f.lat, f.lon) <= RADIUS;
const order = ['operational', 'under_construction', 'permitted', 'proposed', 'cancelled'];
const nonOp = f => f.s !== 'operational' && (CANCELLED_COUNTS || f.s !== 'cancelled');
const buckets = {}; let noZip = 0, opOnly = 0, opAndNonOp = 0, opOnlyMulti = 0;
for (const r of reps) {
  const z = g[r.zip]; if (!z) { noZip++; continue; }
  const b = order.find(s => fac.some(f => f.s === s && near(z, f))) || 'none';
  buckets[b] = (buckets[b] || 0) + 1;
  if (b !== 'operational') continue;
  if (fac.some(f => nonOp(f) && near(z, f))) { opAndNonOp++; continue; }
  opOnly++; if (fac.filter(f => f.s === 'operational' && near(z, f)).length > 1) opOnlyMulti++;
}
const zc = {}; reps.forEach(r => { if (g[r.zip]) zc[r.zip] = (zc[r.zip] || 0) + 1; });
const within = f => Object.keys(zc).reduce((n, z) => n + (near(g[z], f) ? zc[z] : 0), 0);
const distinct = list => Object.keys(zc).reduce((n, z) => n + (list.some(f => near(g[z], f)) ? zc[z] : 0), 0);
const perStatus = {};
for (const f of fac) { const p = perStatus[f.s] ??= {facilities: 0, reports: 0, counts: []};
  const n = within(f); p.facilities++; p.reports += n; p.counts.push(n); }
for (const s in perStatus) { const c = perStatus[s].counts.sort((a, b) => a - b);
  perStatus[s] = {facilities: c.length, reportsNonExclusive: perStatus[s].reports,
    mean: +(perStatus[s].reports / c.length).toFixed(1), median: c[Math.floor(c.length / 2)],
    withNone: c.filter(x => x === 0).length}; }
const op = fac.filter(f => f.s === 'operational');
const noNonOpNearby = op.filter(f => !fac.some(o => nonOp(o) && near(f, o)));
const nothingNearby = op.filter(f => !fac.some(o => o !== f && near(f, o)));
({reports: reps.length, noZip, buckets, opAndNonOp, opOnly, opOnlyNearTwoOrMoreOperating: opOnlyMulti,
  share: (100 * opOnly / reps.length).toFixed(2) + '%', perStatus,
  operatingWithNoNonOperatingNearby: noNonOpNearby.length, distinctReportsNearThem: distinct(noNonOpNearby),
  ofThoseAlsoOperatingOnly: Object.keys(zc).reduce((n, z) => n + (noNonOpNearby.some(f => near(g[z], f))
    && !fac.some(f => nonOp(f) && near(g[z], f)) ? zc[z] : 0), 0),
  operatingWithNothingElseNearby: nothingNearby.length, distinctReportsNearThose: distinct(nothingNearby)});

On her own site, with the live file paths swapped in, the same code reads her current files. The date filter keeps the reports to the October 4 set, but the facility statuses will be whatever the file says that day.

Closing

Her report form already asks whether the facility is “already up and running” or under construction [4]. The published reports file doesn’t include that answer. Publishing it, or a facility identifier with each report, would let anyone separate reports about operating sites from reports about proposals without estimating from distance.


Sources

[1] brockovichdatacenter.com, community reports data file (community-reports.json, version October 4, 2026; analysis by the author; advocacy source), archived October 10, 2026: https://web.archive.org/web/20261010001606id_/https://www.brockovichdatacenter.com/community-reports.json?v=20261004 (live: https://www.brockovichdatacenter.com/community-reports.json)

[2] brockovichdatacenter.com, facility data file (data-centers-map.json, updated September 27, 2026; header lists counts by status and its sources; advocacy source), archived October 10, 2026: https://web.archive.org/web/20261010001606id_/https://www.brockovichdatacenter.com/data-centers-map.json?v=20260927 (live: https://www.brockovichdatacenter.com/data-centers-map.json)

[3] brockovichdatacenter.com, zip-code coordinate file (zip-geocodes.json; advocacy source), archived October 10, 2026: https://web.archive.org/web/20261010001607id_/https://www.brockovichdatacenter.com/zip-geocodes.json?v=20260927 (live: https://www.brockovichdatacenter.com/zip-geocodes.json)

[4] brockovichdatacenter.com, home page (map scope note, data sources and report form; advocacy source), archived October 20, 2026: https://web.archive.org/web/20261020235816id_/https://brockovichdatacenter.com/index.html (live: https://www.brockovichdatacenter.com/)

[5] brockovichdatacenter.com, Community Reports Statistics (“Generated October 4, 2026 · Data through October 4, 2026”, 9,683 total reports; advocacy source), archived October 10, 2026: https://web.archive.org/web/20261010001648id_/https://www.brockovichdatacenter.com/community-stats.html

[6] Arizona’s Family (azfamily.com), How neighbors say data center construction has affected Ahwatukee community, October 28, 2026 (Menlo Digital’s 38-acre data center in Ahwatukee, under construction since April): https://www.azfamily.com/2026/10/29/how-neighbors-say-data-center-construction-has-affected-ahwatukee-community/