How to cite

Cite the record, the release and the date. Releases are dated snapshots of the whole database (/data/releases/); the current one is 2026.10.20. Record pages carry their own citation and BibTeX in the sidebar.

The database

Retrofit Atlas (release 2026.10.20). A citable database of former malls and suburban sites, and what became of them. Ed. Hadi Irvani. https://retrofitatlas.org/ (accessed 2026-10-20).

@misc{retrofitatlas_2026_10_20,
  title = {Retrofit Atlas, release 2026.10.20},
  editor = {Hadi Irvani},
  howpublished = {\url{https://retrofitatlas.org/}},
  year = {2026},
  note = {Built on the public Retrofitting Suburbia map (Dunham-Jones and Williamson) and the sources listed on each record. Accessed 2026-10-20}
}

A record

Retrofit Atlas (2026). "<Site name>, <City, State>." Record <id>, release 2026.10.20, tier <tier>. https://retrofitatlas.org/<type>/<state>/<slug>/ (accessed 2026-10-20).

Copy buttons on every record page give the filled-in text and BibTeX. The Markdown twin of a record (…/index.md) ends with the same block.

The underlying research

When you rely on the curated tier, cite the authors as well: Dunham-Jones, E. and Williamson, J. (2011) Retrofitting Suburbia, updated edition, Wiley; and (2021) Case Studies in Retrofitting Suburbia, Wiley. The Atlas is built on their public map and is not reviewed or endorsed by them.

Versioning

Every deploy writes a release under /data/releases/YYYY-MM-DD/ with manifest.json (sha256 and row counts per file) and diff.json (site ids added, removed and changed since the previous release). The footer of every page names the release it was built from. The latest files stay at the usual /data/ paths. Record-level history: the changelog and /api/v1/changes.

Page generated with the site, release 2026.10.20. Corrections: the form or desk@retrofitatlas.org.