Tableau Maps and Spatial Analytics: From Basic Choropleths to Custom Spatial Data

Tableau's mapping capability extends well beyond the filled choropleth maps that most users encounter first. The full range includes point maps, density maps, custom polygon boundaries, spatial joins against geographic files, and integration with spatial data from GIS systems. Understanding which mapping type to use for each analytical question — and how to implement the non-obvious ones — expands what is possible in geographic analysis.

Built-in Geographic Roles

Tableau recognises geographic dimensions automatically when they match built-in geographic roles: Country, State/Province, County, City, ZIP/Postal Code, CBSA, Congressional District, and several others. When a dimension has a geographic role assigned, dragging it to the view produces a map automatically.

Geographic role limitations to understand:

**Geocoding accuracy**: Tableau's built-in geocoding maps geographic names to coordinates using a reference database. City names that are not unique (there are many cities named Springfield in the US) may geocode to the wrong location. Verify geocoding results for critical analyses, especially at sub-state levels.

**Country-level specificity**: Tableau's built-in geographic roles are detailed for the US but less granular internationally. UK postcodes, Australian postcodes, German postal codes, and sub-national administrative divisions outside major countries have varying levels of coverage. Supplement with latitude/longitude coordinates for international analyses where built-in geocoding is incomplete.

**Custom territories**: When your analytical geography does not match administrative boundaries — sales territories, delivery zones, regional groupings — built-in geographic roles do not apply. Use calculated fields to assign custom territory names to records, then use those names as the geographic dimension with a custom shape file defining the territory boundaries.

Map Types and Their Analytical Use Cases

**Filled maps (choropleths)**: Shade geographic regions by a continuous measure or discrete dimension. Best for: ratio metrics that are meaningfully comparable across regions of different size (infection rate per 100,000, revenue per customer, not absolute counts that scale with population or area). Worst for: absolute counts that correlate with region size — large geographic areas with high counts look dominant even if they are not per-capita outliers.

**Point maps**: Plot individual records at their geographic coordinates. Best for: individual incidents, customer locations, retail locations, events. Reveals spatial patterns and clustering that aggregated regional maps hide. Limitation: at high density, points overlap and obscure patterns — use transparency or density calculation.

**Density maps**: Kernel density estimation visualising concentration of points. Best for: identifying hotspots in large point datasets (crime locations, customer concentration, incident distribution). The density surface communicates pattern without individual point overlap.

**Path maps**: Connect points with lines in order, showing routes or flows. Use a path order dimension and an origin/destination structure. Applications: delivery routes, customer journey paths, flight routes.

**Symbol maps**: Plot symbols at geographic locations sized by a measure. Best for: comparing a metric across discrete locations (bubble size = revenue, locations = store coordinates). More accurate than choropleth for absolute count comparison because symbol size is directly proportional and not confounded by region area.

Custom Polygon Boundaries

When your analytical geography does not match Tableau's built-in boundaries, use custom polygon data. The workflow:

1. Obtain the boundary data in a Tableau-compatible format. Tableau supports Spatial files: .shp (Shapefile), .kml (Google Earth), .gpkg (GeoPackage), .geojson, .mif (MapInfo), .tab (MapInfo TAB), and WKT (Well-Known Text in a database or CSV).

2. Connect to the spatial file as a data source, or add it to an existing data source via a spatial join. Tableau's spatial file connector reads the boundary geometry directly.

3. Join the spatial boundary data to your analytical data on the geographic identifier (region ID, territory name, postal code) that is common to both.

4. Drag the geometry field to the Detail or Color marks card. Tableau renders the custom polygons.

Common sources for custom boundary data:

- National statistical agencies (US Census TIGER/Line, UK ONS boundary files, ABS in Australia) for administrative boundaries

- Government open data portals for custom administrative definitions

- Self-generated territory files from GIS software when territory definitions are organisational rather than governmental

Spatial Functions for Analysis

Tableau's spatial functions enable calculations using geographic data directly in calculated fields:

**DISTANCE()**: Calculates the distance between two geographic points. DISTANCE([store_location], [customer_location], 'km') calculates driving distance approximation. Useful for: proximity analysis, service area identification, assignment of customers to nearest location.

**MAKELINE()**: Creates a line geometry connecting two points. Use for origin-destination flow maps.

**MAKEPOINT()**: Creates a point geometry from latitude and longitude values. When your data has lat/lon columns rather than a recognised geographic dimension, MAKEPOINT(latitude, longitude) creates a spatial field that Tableau can map.

**BUFFER()**: Creates a circular polygon around a point at a specified radius. Useful for: service area visualisation, proximity zone analysis.

**Spatial joins in the data source layer**: Connect two spatial data sources on a geographic relationship rather than an attribute join. The option "Intersects" joins features from one layer to features in another layer that they overlap geographically — useful for assigning points to polygons (which territory is this customer in?) or identifying features that overlap (which census tracts intersect my sales territory?).

Map Background and Presentation

Tableau's default map background is provided via Mapbox. Several background options are available in Map > Map Layers:

**Normal**: Standard street map with labels — appropriate for most business mapping

**Light**: Minimal base map — appropriate when the data overlay is the focus and roads/labels are distracting

**Dark**: Dark background — effective for density maps and point maps where bright colours on dark contrast well

**Outdoors**: Topographic detail — appropriate for geographic features analysis

**Satellite**: Aerial photography — appropriate when physical features matter

**None**: No background — use your own background via WMS server or custom image background

For formal reports and publications, adjust the map layers to hide unnecessary detail (remove transit lines, highways, labels) that does not add analytical value to your specific map. Map > Map Layers controls each layer's visibility.

Our Tableau consulting practice builds spatial analytics solutions from simple geographic visualisations to complex custom polygon analyses — contact us to discuss your mapping requirements.

A former Microsoft data architect audits your data foundation, identifies your top priorities, and sends you a written plan. Free. No pitch.