Assemble an ACS table file without losing its geographic keys

Download the matching parts

For a table-based summary file, save the data file, release-specific table labels and the matching geography file. Record the product, year and retrieval date for all three. A codebook from a newer release may parse the columns correctly but assign the wrong meaning to a line.

Validate the join before analysis

Read geographic identifiers as text, preserve leading zeros and retain the full summary-level identifier. Check uniqueness at the intended area-by-table grain before joining. Join labels onto the data rather than trusting row order. Count unmatched keys in each direction; some entries in the broad geography file can legitimately be absent from one table.

Hypothetical reconciliation

A subset contains four distinct area keys. Its label extract has five rows because one of those keys occurs twice. A join can produce five output rows from four data rows even though no estimate is missing. Resolve why the key is duplicated; deleting the last row by position can conceal a mismatch in geography level. After repair, verify four distinct keys and four results.

Preserve estimate, margin and annotation columns together during reshaping. For one area, independently compare its label and estimate with the published table. Archive a small field map from output names back to original column names so a later change in the file layout is detectable.

Primary source checked 7 November 2026: U.S. Census Bureau: ACS table-based summary files.

Use this in your study: Check the universe and hierarchy of a table.