- Build pipeline errors. A Census value misrouted, miscomputed, or attached to the wrong city. A growth field calculated against the wrong base year. A rank that doesn’t match the underlying sort.
- Broken provenance. A published number whose source file can’t be re-derived from the build manifest, or whose
source_*columns point to the wrong file. - Typos and content errors. Misspellings, broken internal links, mislabeled axes on charts, wrong vintage year on a page, incorrect last-built date.
- Methodology accuracy. A claim on the methodology page that doesn’t match what the build script actually does. The methodology and the build script must agree.
Corrections
Found a problem? Tell us.
Every City in the USA is a sourced data utility. If a number, a source link, or a methodology claim is wrong, the right move is to fix it on the record — not bury it.
What we’ll fix
What we won’t fix
- Census Bureau numbers themselves. If you believe a Census estimate for a specific city is wrong, that’s a dispute with Census. The Population Estimates Challenge Program is the official channel. We publish what Census publishes; we don’t reissue or override official figures.
- Census methodology disputes. Differential privacy, the cohort-component method, the blended base, raking to county totals — methodology disputes belong upstream with the Bureau’s Population Division, not in our editorial.
- Data the Census doesn’t publish. CDPs annually (other than Urban Honolulu), demographics, MCDs in V1, metro-area populations, sub-city tracts. The “What this is NOT for” section documents these deliberate exclusions; they aren’t bugs.
How to report
All corrections will go through the contact form.
The contact form is being built. It will route corrections to a managed inbox so they can be triaged and logged here. Until the form is live, there is no public correction channel.
Once the form is live, this section will show where corrections route and the typical triage time.
Public corrections log
Corrections will be logged here once the contact form is live and the first correction is received. The empty list is intentional — it will fill in over time as real corrections are submitted, reviewed, and applied.
Each entry will record what was wrong, when it was reported, when it was fixed, and which build manifest applied the fix. The log is the receipt — what was found, what changed, when.