FIPS Codes in Tableau and Power BI: Geographic Mapping Guide

Tableau and Power BI are the two most common BI platforms for visualizing US geographic data, and both support county-level mapping using FIPS codes. The setup differs between platforms, but the underlying requirement is the same: a clean 5-digit FIPS code stored as a string, properly associated with a geographic role. Getting this wrong results in unmatched geographies and counties that appear blank on the map.

In Tableau, assign the FIPS code field a geographic role of "County FIPS" (accessible by right-clicking the field → Geographic Role → County FIPS). Tableau expects a 5-digit string; if your codes are integers or have missing leading zeros, Tableau will fail to match them. Once properly configured, you can build filled maps, dot maps, and choropleth visualizations at the county level. For King County (53033), the code must appear as "53033" not 53033.

In Power BI, the built-in map visual uses Bing geocoding by default, which doesn't handle FIPS codes natively. For FIPS-based county mapping, the best approach is to use the ArcGIS Maps for Power BI visual or the Mapbox visual, both of which accept FIPS codes as join keys to Census boundary files. Alternatively, import a GeoJSON of US county boundaries and join on the FIPS field. The TIGER/Line shapefiles from the Census Bureau (converted to GeoJSON via mapshaper or QGIS) are the standard source for county boundaries.

For both platforms, the data preparation workflow is the same: ensure FIPS codes are 5-character strings, verify coverage using the FIPS search tool for any codes that don't match, and use our county FIPS reference to cross-check unexpected codes. For state-level maps, the 2-digit state FIPS codes from the state reference are the appropriate join key.