Data center sites
DC-4.1 shows the data center sites in a state with their status and source. It is part of the Data Center Accountability epic.
In short​
- Source: Epoch AI, AI data centers, CC BY 4.0. It's free to reuse with credit, and every record and the page carry that credit.
- Coverage: the largest AI data centers only. Epoch includes planned sites only once they are under construction and likely to finish, so most sites still waiting on a vote aren't here yet.
- Status is worked out from Epoch's dated rows: planned, under construction, or operating.
- A site Epoch stops listing stays visible as "No longer listed by the source", with its last-seen date and last known status. Nothing is labeled "cancelled", because Epoch publishes no such flag.
Where each piece lives
| Step | Where | What it does |
|---|---|---|
| Load | .venv/bin/python -m ingestion.data_centers.epoch_sites [--no-download] [--file-dir DIR] [--dry-run] [--dsn URL] | Writes to the local warehouse unless --dsn says otherwise; Neon URLs in the environment are ignored (#441). Downloads data_centers.csv and data_center_timelines.csv to data/cache/epoch/ and lands each row as JSONB in bronze. Stops with the headers it found if Epoch renames Name, Data center or Date |
| Bronze | bronze.bronze_epoch_data_centers, bronze.bronze_epoch_data_center_timelines | One row per CSV row per downloaded file. PK (file_sha256, row_number), so reloading the same file adds nothing |
| Staging | stg_epoch_data_center, stg_epoch_data_center_timeline | Latest record per site, with first/last seen and is_listed; dated rows typed with guarded casts |
| Mart | data_center_site (public) | One row per site. PK data_center_site_id. Status, last known status, power, source and licence |
| API | GET /api/data-centers/sites?state=&status=&limit= | The state's sites and counts by status. city_applied is always false |
| Page | /data-centers?state=&city=, "Sites" | Status in plain words. Dropped sites are dashed and labeled. With a city filter, the page says the list covers the whole state |
How status is worked out
Epoch's timeline file has one row per site per date, with free-text construction status, buildings operational and IT power. For each site:
- The latest row on or before today has buildings operational → operating. If that count is blank but the row reports IT power above zero, it also counts as operating.
- A row on or before today, but nothing operational → under construction.
- Only future-dated rows → planned.
- No dated rows → no status ("Status not published").
If the newest download doesn't list the site, the status becomes no longer listed, and the result above is kept as
last_known_status.
Decisions and why
- Epoch AI, not the Brockovich map. The map's built and under-construction layers come from open data like Epoch's, but its proposed and community-reported entries are its own, mostly from residents. Its terms require written permission and forbid scraping, so those stay out until the project agrees.
- State from the address. Epoch gives a street address, not a jurisdiction. A US address ending in a state code or
state name gives
state_code; anything else stays null rather than guessed. There is no city field, so a city filter can't narrow sites, and the page says so instead of showing a city label over state data. - Old snapshots are kept in bronze. That's how a site that leaves Epoch's list is noticed and kept.
- Confidence tags become words. Epoch marks names
#likelyor#speculative; the page shows "(likely)" and "(speculative)" so a guess never reads as fact. - Proposed sites before the vote will come from meeting records (agenda items on data center rezonings), which is DC-4.2.