Custom geocoding in Tableau - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Custom Geocoding Files

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

A CSV file with latitude and longitude columns

B Excel file with ZIP codes only

C Tableau Data Extract (.hyper) file

D JSON file with address details

💡 Hint

Think about the simplest format Tableau can read for coordinates.

Tableau requires a CSV file containing location names and their corresponding latitude and longitude to import custom geocoding.

❓ dax_lod_result

intermediate

Result of Custom Geocoding Join in Tableau

You have a custom geocoding CSV with city names and coordinates. After joining it with your sales data on city name, what will Tableau display if a city in sales data is missing in the custom geocoding file?

A The city will appear at coordinates (0,0)

B The city will not appear on the map visualization

C The city will show with default Tableau coordinates

D Tableau will throw an error and stop loading

💡 Hint

Consider what happens when a join has no matching record.

If the city is missing in the custom geocoding file, Tableau cannot assign coordinates, so it excludes that city from the map.

❓ visualization

advanced

Best Practice for Visualizing Custom Geocoded Data

Which visualization approach best ensures accessibility and clarity when displaying custom geocoded points on a Tableau map?

A Use small, low-contrast dots without labels to avoid clutter

B Display all points as large overlapping circles with no interactivity

C Use distinct color-coded shapes with tooltips and high contrast colors

D Use only text labels without map background for simplicity

💡 Hint

Think about color contrast and user interaction for clarity.

Using distinct shapes and colors with tooltips improves clarity and accessibility, helping users understand the data points easily.

❓ data_modeling

advanced

Handling Multiple Locations per Entity in Custom Geocoding

You have a dataset where some customers have multiple store locations. How should you model your custom geocoding data in Tableau to accurately map all locations?

A Create one row per store location with customer ID and coordinates

B Create one row per customer with multiple latitude and longitude columns

C Aggregate all store locations into a single average coordinate per customer

D Use only the primary store location per customer and ignore others

💡 Hint

Think about how Tableau maps points and the granularity needed.

Tableau requires one row per location with coordinates to plot each store separately on the map.

🔧 Formula Fix

expert

Troubleshooting Custom Geocoding Import Errors

You imported a custom geocoding CSV into Tableau, but the map shows no points. Which of the following is the most likely cause?

A The CSV file contains extra columns with irrelevant data

B The custom geocoding file has more rows than the sales data

C The CSV file uses semicolons instead of commas as separators

D Latitude and longitude columns are named incorrectly or missing

💡 Hint

Check if Tableau recognizes the coordinate columns properly.

Tableau requires latitude and longitude columns with exact names to map locations. Incorrect or missing names cause no points to appear.

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