Custom geocoding in Tableau - Step-by-Step Guide

Introduction

Custom geocoding lets you add your own location data to Tableau maps. This helps when Tableau's built-in map does not have your specific places or regions. You can show your unique areas on maps clearly.

When you want to map sales territories that are not standard regions.

When your data includes custom store locations not recognized by Tableau.

When you need to display delivery zones that differ from postal codes.

When your organization uses internal location codes not in Tableau's map.

When you want to combine your own geographic data with Tableau's maps.

Steps

Step 1: Prepare your custom geocoding file with location names and coordinates

- Outside Tableau (use Excel or text editor)

You have a CSV file with columns like 'Name', 'Latitude', and 'Longitude' ready to import

Step 2: Open Tableau and go to the Map menu

- Top menu bar, click Map

Map menu options appear

Step 3: Select 'Geocoding' then choose 'Import Custom Geocoding'

- Map > Geocoding > Import Custom Geocoding

A file dialog opens to select your custom geocoding CSV file

Step 4: Select your prepared CSV file and click Open

- File dialog window

Tableau imports your custom locations and adds them to the map data

Step 5: Use your custom location field in your worksheet for mapping

- Data pane, drag your location field to the Rows or Columns shelf or to the Marks card

Tableau plots your custom locations on the map using your geocoding data

Step 6: Adjust map layers or styles if needed

- Map > Background Maps or Map Layers pane

Map appearance updates to highlight your custom locations clearly

Before vs After

Before

Map shows only standard geographic locations without your custom areas

After

Map displays your custom locations like sales territories or store points accurately

Settings Reference

Import Custom Geocoding

📍 Map menu > Geocoding > Import Custom Geocoding

To add your own location data to Tableau maps

Default: No custom geocoding imported

Map Layers

📍 Map menu > Map Layers

To control what map details show behind your custom locations

Default: Streets and Borders enabled

Common Mistakes

Using a CSV file without latitude and longitude columns

Tableau needs coordinates to place locations on the map

Include latitude and longitude columns in your CSV for each location

Not matching location names exactly between your data and custom geocoding file

Tableau cannot link your data to the custom locations if names differ

Ensure location names in your data match exactly the names in the custom geocoding file

Summary

Custom geocoding lets you add your own locations to Tableau maps.

You import a CSV file with location names and coordinates via the Map menu.

Make sure your location names and coordinates are correct for accurate mapping.

Practice

1. What is the main purpose of custom geocoding in Tableau?

easy

A. To create charts other than maps

B. To change the color scheme of maps

C. To export maps as images

D. To add new or special locations not included in Tableau's default maps

Solution

1. Step 1: Understand Tableau's default map data

   Tableau has built-in locations but may miss some special or new places.

2. Step 2: Purpose of custom geocoding

   Custom geocoding lets you add these missing locations by providing coordinates.

3. Final Answer:

   To add new or special locations not included in Tableau's default maps -> Option D

4. Quick Check:

   Custom geocoding = add new locations [OK]

Hint: Think: Why add new places to a map? [OK]

Common Mistakes:

• Confusing custom geocoding with color or style changes
• Thinking it exports maps instead of adding data
• Assuming it creates non-map charts

2. Which file format is required to import custom geocoding data into Tableau?

easy

A. .csv (Comma-separated values)

B. .xlsx (Excel workbook)

C. .txt (Plain text file)

D. .json (JavaScript Object Notation)

Solution

1. Step 1: Identify Tableau's accepted custom geocoding format

   Tableau requires a CSV file with location names and coordinates for custom geocoding.

2. Step 2: Compare file types

   CSV is the standard for tabular data import in Tableau for geocoding, unlike Excel or JSON.

3. Final Answer:

   .csv (Comma-separated values) -> Option A

4. Quick Check:

   Custom geocoding file = CSV [OK]

Hint: Remember: CSV is simple table data for Tableau [OK]

Common Mistakes:

• Choosing Excel because it's common for data
• Thinking JSON or TXT are accepted for geocoding
• Confusing file formats for other Tableau features

3. Given this CSV snippet for custom geocoding:

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

What will Tableau do after importing this file?

medium

A. Show an error because coordinates are invalid

B. Replace all existing locations with MyTown and NewPlace

C. Add MyTown and NewPlace as mappable locations on Tableau maps

D. Ignore the file because it lacks population data

Solution

1. Step 1: Understand the CSV content

   The CSV has location names with valid latitude and longitude values.

2. Step 2: Tableau's behavior on import

   Tableau adds these locations to its map data without removing existing ones.

3. Final Answer:

   Add MyTown and NewPlace as mappable locations on Tableau maps -> Option C

4. Quick Check:

   Valid CSV adds locations [OK]

Hint: Valid coordinates + names = new map points [OK]

Common Mistakes:

• Thinking Tableau replaces all locations
• Assuming coordinates are invalid without checking
• Believing extra data like population is mandatory

4. You imported a custom geocoding CSV but Tableau does not show your new locations on the map. What is the most likely error?

medium

A. You forgot to restart Tableau after import

B. The CSV file has incorrect column headers like 'Lat' instead of 'Latitude'

C. Tableau does not support custom geocoding

D. The CSV file is too large for Tableau to process

Solution

1. Step 1: Check CSV format requirements

   Tableau requires exact column headers: 'Location', 'Latitude', and 'Longitude'.

2. Step 2: Identify common import issues

   Incorrect headers like 'Lat' cause Tableau to ignore the data.

3. Final Answer:

   The CSV file has incorrect column headers like 'Lat' instead of 'Latitude' -> Option B

4. Quick Check:

   Correct headers = data shown [OK]

Hint: Check headers match exactly: Location, Latitude, Longitude [OK]

Common Mistakes:

• Blaming file size without evidence
• Thinking Tableau lacks custom geocoding support
• Assuming restart is always needed

5. You want to map a new set of store locations in Tableau that are not recognized by default. Your CSV has duplicate location names but different coordinates. What is the best way to handle this in custom geocoding?

hard

A. Add a unique identifier to the location names to differentiate each location

B. Remove duplicates and keep only one coordinate per name

C. Import as is; Tableau automatically handles duplicates

D. Change all location names to the same name for simplicity

Solution

1. Step 1: Understand duplicate location issues

   Duplicate names with different coordinates confuse Tableau's mapping.

2. Step 2: Use unique identifiers

   Adding a unique ID or modifying names helps Tableau distinguish each location.

3. Step 3: Avoid data loss or confusion

   Removing duplicates or renaming all the same causes loss or errors.

4. Final Answer:

   Add a unique identifier to the location names to differentiate each location -> Option A

5. Quick Check:

   Unique IDs fix duplicate location issues [OK]

Hint: Make each location name unique to avoid confusion [OK]

Common Mistakes:

• Assuming Tableau auto-fixes duplicates
• Deleting duplicates losing data
• Using identical names causing map errors