How GEOID and the fully qualified GEOID FQ link Census tables to maps
Summary
Census staff walked through the GEOID and fully qualified GEOID FQ fields, showing how concatenated codes plus summary level and geo-variant components enable reliable joins between data.census.gov CSV outputs and spatial files.
Kevin Holly explained the two primary geographic identifier types used in Census spatial products and why users should prefer the fully qualified GEOID when joining tabular outputs to spatial files.
"The first is the GEOID, and that's a concatenation of the geographic area codes that are required to uniquely identify a geography within a particular layer. The second type is the GEOID FQ — think of that FQ as fully qualified," Holly said, describing components such as summary level, geo variant and geo component. He used Fairfax County, Virginia (state FIPS 51, county code 059) as a worked example and demonstrated the longer FQ form that appears in data.census.gov CSVs.
Holly recommended the GEOID FQ for joins across vintages or when summary level disambiguation is needed, and said the Bureau encodes some vintage/variant information within the geo_variant component for geographies that change over data years (for example, congressional‑district vintages).
AI generated
The text on this page is AI generated. Summaries, highlights, analysis, and video transcripts are all produced from the original source material.
AI can make mistakes, so if you spot one, and we will fix it for everyone.
Note: the source content is unaltered by us. Any content source we link to, be it a video, an audio recording, or a document, is presented exactly as its publisher released it. That publisher is usually a government body, sometimes an individual official or another organisation.
