Tableau maps visualize data geographically — by country, state, city, zip code, or custom geographic boundaries. This guide explains the different map types in Tableau, when to use geographic visualization, how to work with custom shapes and spatial files, and performance considerations for map-heavy dashboards.
Tableau maps visualize data geographically — encoding dimensions and measures as colors, sizes, or shapes on a geographic canvas. Unlike most Tableau chart types that require explicit configuration, geographic visualization is largely automatic when Tableau recognizes a field as a geographic role: country names, state names, city names, zip codes, latitude/longitude coordinates. The geographic role tells Tableau how to plot the field on a map.
Geographic Roles and Automatic Geocoding
Tableau maintains a built-in geocoding database covering countries, states/provinces, counties, cities, zip codes, and congressional districts for major countries. When a field is assigned a geographic role, Tableau looks up coordinates for each value in its geocoding database.
Geographic roles are assigned automatically when Tableau detects geographic field names (State, Country, Zip Code, City) or can be assigned manually: right-click a dimension, Geographic Role, and select the appropriate type. Fields with geographic roles generate a globe icon in the data pane.
Unrecognized values — unusual city spellings, small municipalities not in Tableau's database, custom territory names — appear as unknown geocodes. You can resolve these by mapping unknown values to known equivalents (Edit Locations) or by providing explicit latitude/longitude coordinates.
Map Types in Tableau
**Symbol maps:** Points placed at geographic locations, sized and/or colored by a measure. The classic use case: sales by city, with circle size representing revenue. Symbol maps work well when individual point locations matter and you have a moderate number of points (hundreds to low thousands — dense symbol maps become unreadable).
**Filled maps (choropleth):** Geographic regions filled with color intensity representing a measure. The classic use case: customer density by state, filled with a sequential color palette from light (low density) to dark (high density). Filled maps work well for aggregate comparisons across well-defined geographic boundaries (countries, states, counties). They fail when regions vary dramatically in size — a small state with high density and a large state with low density are hard to compare visually when the large state dominates the canvas.
**Density maps:** Heat map layer showing concentration of points rather than individual marks. Works well for large point datasets (millions of GPS coordinates, transaction locations) where individual marks overlap. The density layer blends nearby points into a heat gradient.
**Dual-axis maps:** Combining two layers — typically a filled map for background context and a symbol map layer for specific locations. A regional revenue filled map with city-level symbols layered on top. Created using dual-axis coordinates with two separate marks layers.
**Custom polygons:** Importing custom geographic boundaries as spatial files (Shapefile, GeoJSON, TopoJSON, KML) and using them as dimension members in a filled map. Used when Tableau's built-in administrative boundaries don't match your business geography — sales territories, distribution zones, custom regions.
Spatial Files and Custom Geographies
For geographic boundaries that Tableau doesn't include natively, you can connect to spatial files:
Supported spatial file formats: ESRI Shapefile (.shp with accompanying .dbf, .shx), GeoJSON (.geojson or .json), TopoJSON, KML, ESRI File Geodatabase, MapInfo Table.
Spatial files are connected to Tableau via Connect > Spatial File. Once connected, the geometry column appears as a spatial data type. Joining a spatial file to a data table (e.g., joining custom territory polygons to a sales table on territory_id) enables filled maps using custom boundaries.
For point data with latitude and longitude already in the source data, no spatial file is needed — use the coordinates directly as geographic fields (assign Latitude and Longitude roles to the respective columns).
Map Layers and Background Maps
Tableau's background maps come from Mapbox by default. Map layers (borders, streets, terrain, light, dark) are configured under Map > Map Layers in Tableau Desktop. Background maps require internet connectivity for Desktop and are always available in Tableau Server and Cloud (served through Tableau's infrastructure).
Offline map images: Tableau supports WMS (Web Map Service) servers as background map sources, enabling on-premises or custom background maps. Organizations in secure environments without internet access can configure a WMS server running a local tile cache.
Map washout: Use the Map > Background Map > Washout setting to reduce background map visual intensity, making data layers more prominent on the canvas.
Performance Considerations
Maps with many marks are performance-intensive. Symbol maps with 100,000+ marks trigger significant rendering load. Optimize by: aggregating data before visualizing (group cities into regions if granularity is not needed), using density maps for very high-volume point data, limiting visible marks with filters, and pre-aggregating geographic dimensions in the data source.
Filled maps using complex custom shapefiles (high-resolution polygon boundaries with thousands of vertices) render slowly. Simplify high-resolution shapefiles to reduce vertex count if rendering speed is problematic — most map use cases don't need millimeter-accurate boundaries.
Our Tableau consulting services covers geographic visualization design, custom spatial data integration, and dashboard performance optimization. Contact us to discuss your Tableau mapping requirements.
A former Microsoft data architect audits your data foundation, identifies your top priorities, and sends you a written plan. Free. No pitch.
Book a Call →