Custom geocoding in Tableau - Deep Dive

Overview - Custom geocoding

What is it?

Custom geocoding is the process of adding your own geographic data to Tableau so it can recognize and map locations that are not included in its default map database. This lets you visualize places like new cities, custom regions, or specific points of interest. It involves creating a file with location names and their coordinates, then importing it into Tableau.

Why it matters

Without custom geocoding, Tableau can only map locations it already knows, which limits your ability to analyze data tied to unique or new places. Custom geocoding solves this by letting you expand Tableau’s map knowledge, so you can see your data in the right geographic context. This helps businesses make better decisions by understanding location-specific trends that standard maps miss.

Where it fits

Before learning custom geocoding, you should understand basic Tableau mapping and geographic roles. After mastering it, you can explore advanced spatial analytics and integrate external GIS data for richer insights.

Mental Model

Core Idea

Custom geocoding lets you teach Tableau new place names and their exact locations so it can map data beyond its built-in geography.

Think of it like...

It's like giving a GPS device a new address book with places it didn’t know before, so it can guide you there accurately.

┌───────────────────────────────┐
│ Tableau Default Map Database   │
│  (Known Locations & Coordinates)│
└──────────────┬────────────────┘
               │ Import Custom Geocoding File
               ▼
┌───────────────────────────────┐
│ Custom Geocoding File          │
│  (New Location Names + Lat/Lon)│
└──────────────┬────────────────┘
               │ Tableau merges data
               ▼
┌───────────────────────────────┐
│ Enhanced Map Visualization    │
│  (Includes Custom Locations)  │
└───────────────────────────────┘

Build-Up - 7 Steps

1

Foundation

Understanding Tableau Geographic Roles

Concept: Learn what geographic roles are and how Tableau uses them to map data.

Tableau assigns geographic roles like Country, State, City, or Zip Code to your data fields. These roles tell Tableau how to place your data on a map. For example, if a column is assigned the City role, Tableau looks up that city’s location to plot it. Without the correct role, Tableau cannot map the data properly.

Result

You can create basic maps by dragging geographic fields onto the view, and Tableau automatically plots known locations.

Understanding geographic roles is key because custom geocoding builds on this system to add new locations Tableau doesn’t know.

2

Foundation

Basics of Tableau Mapping and Data Visualization

Concept: Learn how Tableau creates maps from geographic data and visualizes data points.

When you drag a geographic field to the view, Tableau uses its built-in map database to find coordinates and plot points. You can add data layers like color or size to show values. Tableau supports different map types like filled maps, symbol maps, and density maps.

Result

You can visualize data on maps for known locations, like countries or cities, using Tableau’s default capabilities.

Knowing how Tableau maps data helps you see why adding new locations with custom geocoding is necessary when your data includes unknown places.

3

Intermediate

Creating a Custom Geocoding File

🤔Before reading on: do you think a custom geocoding file needs only location names or also coordinates? Commit to your answer.

Concept: Learn how to prepare a CSV file with location names and their latitude and longitude for Tableau.

A custom geocoding file is a CSV with columns for Location Name, Latitude, and Longitude. You can export locations from other sources or find coordinates online. The file must use exact names matching your data for Tableau to link them correctly. For example: Location,Latitude,Longitude MyTown,40.7128,-74.0060 NewRegion,34.0522,-118.2437

Result

You have a file ready to import into Tableau that defines new geographic points.

Knowing that both names and coordinates are required prevents errors where Tableau can’t place new locations on the map.

4

Intermediate

Importing Custom Geocoding into Tableau

🤔Before reading on: do you think importing custom geocoding replaces Tableau’s default map or adds to it? Commit to your answer.

Concept: Learn how to add your custom geocoding file to Tableau so it recognizes new locations alongside default ones.

In Tableau Desktop, go to Map > Geocoding > Import Custom Geocoding. Select your CSV file. Tableau merges your locations with its default map database. After import, your new locations can be used in maps just like built-in ones.

Result

Tableau can now map your custom locations without errors or missing points.

Understanding that custom geocoding adds to, not replaces, Tableau’s map database helps avoid confusion and data loss.

5

Intermediate

Using Custom Geocoded Locations in Visualizations

Concept: Learn how to use your newly added locations in Tableau maps and dashboards.

After importing, assign the correct geographic role to your custom location field. Drag it onto the map view. Tableau plots these points using your custom coordinates. You can combine them with other data fields for color, size, or filters. This lets you analyze data tied to your unique places.

Result

Your dashboards now show data on maps including both standard and custom locations.

Knowing how to integrate custom locations into visualizations unlocks the full power of location-based analysis.

6

Advanced

Handling Hierarchies and Regions in Custom Geocoding

🤔Before reading on: do you think custom geocoding supports multi-level geographic hierarchies like Country > State > City? Commit to your answer.

Concept: Learn how to define hierarchical geographic data and regions using custom geocoding files.

You can create multiple custom geocoding files for different geographic levels, like regions or districts. Each file includes location names and coordinates. Tableau can link these levels if names match correctly, enabling drill-down maps. For example, a region file with region names and coordinates, and a city file with city names and their parent region names.

Result

You can build maps with custom geographic hierarchies, allowing detailed spatial analysis.

Understanding how to structure custom geocoding for hierarchies enables complex, multi-level geographic insights.

7

Expert

Troubleshooting and Optimizing Custom Geocoding

🤔Before reading on: do you think Tableau automatically updates custom geocoding when the source file changes? Commit to your answer.

Concept: Learn common issues with custom geocoding and best practices to maintain accuracy and performance.

Tableau does not auto-update custom geocoding after import; you must re-import if the file changes. Common issues include mismatched location names, missing coordinates, or duplicate entries causing mapping errors. To optimize, keep files clean, use consistent naming, and limit custom locations to what’s necessary to avoid slow map rendering.

Result

You maintain reliable, fast maps with accurate custom locations in Tableau.

Knowing these operational details prevents frustrating errors and ensures your custom geocoding works smoothly in production.

Under the Hood

Tableau’s mapping engine uses a built-in geographic database with location names linked to latitude and longitude coordinates. When you import custom geocoding, Tableau merges your location data into this database, extending its lookup table. During visualization, Tableau matches your data’s location names to this combined database to find coordinates and plot points on the map.

Why designed this way?

Tableau separates default and custom geocoding to keep the core map database stable and optimized. This design allows users to add new locations without altering Tableau’s internal data, reducing risk of errors and enabling easy updates. Alternatives like modifying the core database directly would be risky and complex.

┌───────────────┐      Import      ┌─────────────────────┐
│ User Data     │ ──────────────▶ │ Tableau Geocoding DB│
│ (Location Names)│                │ (Default + Custom)  │
└───────┬───────┘                └─────────┬───────────┘
        │ Match Location Names                 │ Lookup Coordinates
        ▼                                    ▼
┌─────────────────────┐              ┌───────────────────┐
│ Tableau Visualization│◀────────────│ Coordinates (Lat/Lon)│
│ (Maps, Dashboards)   │              └───────────────────┘

Myth Busters - 4 Common Misconceptions

Quick: Does importing custom geocoding overwrite Tableau’s default map data? Commit yes or no.

Common Belief: Importing custom geocoding replaces Tableau’s built-in map data completely.

Reality: Custom geocoding adds new locations to Tableau’s existing map database without replacing it.

Why it matters: Believing it replaces data can cause users to avoid custom geocoding for fear of losing default locations, limiting their mapping capabilities.

Quick: Can Tableau map a location if only the name is provided without coordinates? Commit yes or no.

Common Belief: Tableau can map any location if you provide just the name, even without coordinates.

Reality: Tableau needs latitude and longitude coordinates in custom geocoding to plot new locations accurately.

Why it matters: Missing coordinates cause Tableau to fail mapping, leading to confusion and incomplete visualizations.

Quick: Does Tableau automatically update custom geocoding when the source CSV file changes? Commit yes or no.

Common Belief: Once imported, Tableau keeps custom geocoding updated automatically if the source file changes.

Reality: Tableau requires manual re-import of the custom geocoding file to update changes.

Why it matters: Assuming automatic updates can cause stale or incorrect maps, misleading analysis.

Quick: Can custom geocoding handle hierarchical regions like Country > State > City by default? Commit yes or no.

Common Belief: Custom geocoding automatically understands and links hierarchical geographic levels without extra setup.

Reality: You must prepare and import separate files and ensure naming consistency to build hierarchies in custom geocoding.

Why it matters: Ignoring this leads to flat maps without drill-down capabilities, limiting geographic analysis depth.

Expert Zone

1

Custom geocoding files must use exact spelling and case matching for location names to link correctly; small differences cause unmatched points.

2

Tableau’s custom geocoding supports only point locations (latitude/longitude), not complex polygons or shapes, which require spatial files or extensions.

3

Performance can degrade if too many custom locations are added; it’s best to limit custom geocoding to essential places and combine with filters.

When NOT to use

Avoid custom geocoding when you need detailed area boundaries or polygons; instead, use spatial files like shapefiles or Tableau’s spatial connectors. Also, if your locations are standard and included in Tableau’s database, custom geocoding is unnecessary and adds complexity.

Production Patterns

Professionals use custom geocoding to map new store locations, custom sales territories, or emerging markets not yet in Tableau’s database. They maintain version-controlled geocoding files and automate re-imports during data refreshes to keep maps accurate in dashboards.

Connections

Spatial Data and GIS

Builds-on

Understanding custom geocoding helps grasp how geographic information systems (GIS) store and use location data, bridging simple point mapping and complex spatial analysis.

Data Cleaning and Preparation

Same pattern

Preparing custom geocoding files requires careful data cleaning and standardization, a skill shared with many data preparation tasks to ensure accurate analysis.

Address Autocomplete in Web Apps

Similar pattern

Both custom geocoding and address autocomplete rely on matching user input to known locations with coordinates, showing how location data powers diverse applications.

Common Pitfalls

#1 Using inconsistent location names between your data and custom geocoding file.

Wrong approach:

Location,Latitude,Longitude
New York City,40.7128,-74.0060
Los Angeles,34.0522,-118.2437

Data field contains 'NYC' instead of 'New York City'.

Correct approach:

Location,Latitude,Longitude
NYC,40.7128,-74.0060
Los Angeles,34.0522,-118.2437

Data field contains 'NYC' matching the custom geocoding file.

Root cause:

Mismatch in naming causes Tableau to fail matching locations, resulting in missing points on the map.

#2 Importing a custom geocoding file without latitude and longitude columns.

Wrong approach:

Location
MyTown
NewRegion

Correct approach:

Location,Latitude,Longitude
MyTown,40.7128,-74.0060
NewRegion,34.0522,-118.2437

Root cause:

Tableau requires coordinates to plot locations; missing them means Tableau cannot place points.

#3 Expecting Tableau to auto-update custom geocoding after editing the source file.

Wrong approach:

Edit CSV file externally and assume Tableau maps update automatically without re-import.

Correct approach:

After editing the CSV, re-import custom geocoding via Map > Geocoding > Import Custom Geocoding.

Root cause:

Tableau loads custom geocoding only at import; it does not watch for external file changes.

Key Takeaways

Custom geocoding extends Tableau’s mapping by adding new locations with names and coordinates.

You must prepare accurate CSV files with exact location names and latitude/longitude for Tableau to recognize them.

Importing custom geocoding adds to Tableau’s default map database without replacing it.

Custom geocoding supports building geographic hierarchies but requires careful file preparation and naming consistency.

Maintaining and updating custom geocoding files manually is essential to keep maps accurate and performant.