Downloads

Download all SMRMap data as CSV or JSON under CC BY 4.0. Start with reporting-projects.csv: one row per published project.

Changes to SMRMap’s pages and downloads are listed separately.

Start here

Three kinds of file are on this page. Start with the reporting file. Use the complete structured data when you need every machine column or the full JSON bundle. Leave the application files unless you are rebuilding a page on this site.

  1. reporting-projects.csv — one row for every published project, with readable organization, design and site names and citation links. Read the field guide for columns, joins, blanks and release identity.
  2. Complete structured data — projects.csv keeps its 60 machine columns. The other tables and smrmap-dataset.json are the full public bundle.
  3. Application files — the map and the search index. They are not a report.

Reporting columns: project_id project_name project_url country_code country stage stage_label design_id design_name design_url site_id site_name capacity_summary parties parties_limit party_question party_name party_id party_role party_note party_page party_citation_url party_citation_status listed_source_names listed_source_urls dataset_fingerprint build_date capacity_review summary record_reviewed evidence_dates question_reviews evidence_dates_limit.

The reporting file retains capacity explanations, the project description and its review date. Evidence dates describe the listed documents and recorded events, not proof of current activity. Question-review notes keep known limits and conflicts. The build date only says when the file was generated.

Worked example: HTR-PM

Project: HTR-PM Shidaowan demonstration (prj-htr-pm-shidaowan)

Page: https://smrmap.com/projects/htr-pm-shidaowan/

Design: HTR-PM (dsn-htr-pm)

Site: Shidaowan / Shidao Bay (site-shidaowan)

Capacity: 210 MWe (gross) · plant · 500 MWth (nameplate; basis unspecified)

Parties, in the same order as the joined columns:

The listed_source_urls cell lists sources of the project record. A URL there is not a citation of every party above. Use party_citation_url only where party_citation_status is direct. An inherited operator link can name the operator without a source URL on that link; another role for the same organization can carry its own direct citation. Those are different relationships.

Data fingerprint 434a3ad4fbbaaa6e4b79ee0db9d79c7b9b85f663d24417697f7e09f26d609d55; build date 2026-11-15. The fingerprint identifies the canonical data collections. The build date is when this file was generated. Neither is a source-review date, and neither retrieves an older copy of the file.

Public records for this release (same license as the dataset). The structured bundle includes published project records, designs, organizations, sites, sources, recorded regulatory actions, selected policies, dated project events and the published agreements and programs. Drafts and program aggregates are excluded from the published project set. These records are not a worldwide census; an absent permission record does not establish that no permission exists.

Reporting files

A readable report for a person. It is not the complete machine export.

Complete structured data

Stable machine files and the full public bundle. Existing column names and order stay fixed.

Application files

Files the website uses to draw the map and the search box. They are not the reporting file.

The records under Agreements (fleet and customer agreements, national plans, studies and government programs) are a separate collection and are never counted as projects; their files keep the names programmes.csv and programmes.json. In programmes.csv a cell with several values separates them with a semicolon (;); a semicolon inside a value is written as a comma. participant_names and participant_roles are listed in the same order; design_names gives the names of the linked design profiles in design_ids order, then designs the sources name that have no profile. Scale and capacity are as the sources state them, never computed.

IDs in the files link records to one another. The vendor_ids, operator_ids, participant_roles and sources cells in projects.csv are JSON arrays. Each participant role names an organization, its source-backed relationship and the supporting source ID; source IDs resolve through the structured bundle. Capacity values retain their recorded electrical or thermal basis and module or plant scope.

In designs.csv, read each rating with its qualifier and basis: up_to is a ceiling and approximately is an estimate. A blank qualifier means none is recorded. capacity_scope distinguishes a module from the HTR-PM two-module plant total; the legacy module_* column names alone do not establish scope. Rating notes and class ranges remain separate from a stated numerical rating. Storage-discharge peak output is a separate column, not continuous nameplate power.

Quoted source excerpts are not relicensed. NuclearChain material, including site coordinates derived from GEM's Global Nuclear Power Tracker, remains under CC BY 4.0 with the attribution in LICENSE.txt.

Dates in these files

Data fingerprint for this release: 434a3ad4fbbaaa6e4b79ee0db9d79c7b9b85f663d24417697f7e09f26d609d55, build date 2026-11-15. It identifies the underlying data collections; it is not an archived page or a checksum of any download. Citation blocks on record pages carry the same value.

The appended dataset_fingerprint identifies the ten canonical data collections listed in the build manifest. It is not a checksum of a CSV or rendered page. build_date dates generation, not research. The structured bundle carries both in its metadata. These identifiers do not provide an archive of previous pages; save a PDF for the page you cite.

Full and matching-project CSVs include the project summary and, for each of the five commercial questions, its review_state, derived disposition, qualified note, reviewed_at, supporting sources and reconciliation_needed. Missing reviews say no_review_record. A not-disclosed answer, unavailable source, conflict and non-applicable question remain distinct; a recorded relationship needing reconciliation is flagged without changing its evidence.

latest_dated_listed_source_publications and latest_dated_actual_project_events are separate JSON arrays, preserving names, IDs and date precision. Overlapping periods retain every candidate that could be latest. Source dates cover only publications among the project's listed sources; a shared report is not proof of current project activity. An actual announcement dates the announcement, not its target. Undated sources may be newer. Permission and application dates stay in the regulatory-action records; they are not merged into the event array. Page-update, source-access, review and target dates are excluded from those two arrays.

listed_sources_without_publication_date counts listed sources without a recorded publication date; listed_source_count is the number of distinct listed sources, not independent confirmations.

Appended project CSV column names

summary · dataset_fingerprint · build_date · latest_dated_listed_source_publications · latest_dated_actual_project_events · listed_sources_without_publication_date · listed_source_count · commercial_customer_review_state · commercial_customer_disposition · commercial_customer_note · commercial_customer_reviewed_at · commercial_customer_sources · commercial_customer_reconciliation_needed · commercial_contractor_review_state · commercial_contractor_disposition · commercial_contractor_note · commercial_contractor_reviewed_at · commercial_contractor_sources · commercial_contractor_reconciliation_needed · commercial_funding_review_state · commercial_funding_disposition · commercial_funding_note · commercial_funding_reviewed_at · commercial_funding_sources · commercial_funding_reconciliation_needed · commercial_fuel_review_state · commercial_fuel_disposition · commercial_fuel_note · commercial_fuel_reviewed_at · commercial_fuel_sources · commercial_fuel_reconciliation_needed · commercial_schedule_revision_review_state · commercial_schedule_revision_disposition · commercial_schedule_revision_note · commercial_schedule_revision_reviewed_at · commercial_schedule_revision_sources · commercial_schedule_revision_reconciliation_needed

Each project's last_checked is its record review date. Each source carries its own accessed date and, where the source states one, a source_date with its kind (for example published or page updated). The dataset metadata field generated dates the dataset-wide coverage statement in LICENSE.txt; it is not when the files were built, when a source was accessed or when a record was reviewed. No file here is dated by the moment you download it.

In the structured bundle, source notes are the public text of SMRMap's source notes. Pointers to SMRMap's own private saved copies are left out; every stated qualification is kept.

Projects matching your filters

The project list and Who is involved can download the projects that match the current filters as a reporting CSV: one row per project, every page of results, in the current sort order. It uses the same columns as reporting-projects.csv. It is not the 60-column projects.csv, it is not the complete JSON bundle, and it does not follow the projects ticked for comparison. It needs JavaScript. The full reporting file is sorted by project id; a matching download follows the sort on the page.

The file is UTF-8 with a byte-order mark so spreadsheet programs read accents. A text cell that begins with =, +, - or @ (after any leading spaces, control characters or invisible formatting characters), or with a control character, is written with one leading apostrophe so a spreadsheet shows it as text instead of running it as a formula. In the joined party columns that precaution is also applied to each value. This is a precaution, not a guarantee for every spreadsheet program; the exact text is in smrmap-dataset.json. For every question, including questions with no recorded answer, use project-relationships.csv.

In project-relationships.csv, source_url and citation_url belong to the recorded relationship. Sources for the question's reviewed statement are kept separately in review_source_urls; they do not establish a supplier role or cite an inherited design specification. Since 14 November 2026, source_url no longer falls back to those review sources.

Full projection columns, kept for the precomputed file

The matching button reads data/project-list.json. That file still has one CSV line per project in these columns, including the JSON sources list. The button uses the reporting lines stored beside them. These names are the previous projection, not a second copy of the facts: project_id project_name project_url country_code country stage capacity_summary capacity_review record_reviewed sources summary dataset_fingerprint build_date latest_dated_listed_source_publications latest_dated_actual_project_events listed_sources_without_publication_date listed_source_count commercial_customer_review_state commercial_customer_disposition commercial_customer_note commercial_customer_reviewed_at commercial_customer_sources commercial_customer_reconciliation_needed commercial_contractor_review_state commercial_contractor_disposition commercial_contractor_note commercial_contractor_reviewed_at commercial_contractor_sources commercial_contractor_reconciliation_needed commercial_funding_review_state commercial_funding_disposition commercial_funding_note commercial_funding_reviewed_at commercial_funding_sources commercial_funding_reconciliation_needed commercial_fuel_review_state commercial_fuel_disposition commercial_fuel_note commercial_fuel_reviewed_at commercial_fuel_sources commercial_fuel_reconciliation_needed commercial_schedule_revision_review_state commercial_schedule_revision_disposition commercial_schedule_revision_note commercial_schedule_revision_reviewed_at commercial_schedule_revision_sources commercial_schedule_revision_reconciliation_needed

Custom research requests

The files on this page are the standard public downloads, available to everyone under CC BY 4.0. If you need work beyond them, such as a source-linked comparison of projects you choose that answers your own questions in a format you specify, write to corrections@smrmap.com with the projects, the questions and the format you need.

Requests are considered individually, and any cost is discussed before work starts. There is no standard price, turnaround or monitoring service. A request for extra work does not change the license of the public data, which stays open to everyone.