Custom geocoding in Tableau - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to load a custom geocoding CSV file in Tableau.

Tableau

LOAD DATA FROM '[1]' AS CustomGeo

Drag options to blanks, or click blank then click option'

Amap_data.csv

Bcustom_geocoding.csv

Clocations.csv

Ddefault_geocoding.csv

Attempts:

3 left

💡 Hint

Common Mistakes

Using the default geocoding file name instead of the custom one.

Using unrelated CSV file names.

Tableau requires the custom geocoding file to be loaded from the correct CSV file, usually named custom_geocoding.csv.

2fill in blank

medium

Complete the calculation to create a custom latitude field using the data column.

Tableau

FLOAT([[1]])

Drag options to blanks, or click blank then click option'

ALatitude

BLongitude

CCity

DCountry

Attempts:

3 left

💡 Hint

Common Mistakes

Using Longitude instead of Latitude.

Using non-numeric columns like City or Country.

Latitude values are used to create the custom latitude field, so the column Latitude is correct.

3fill in blank

hard

Fix the error in the custom geocoding join calculation to match the location field.

Tableau

[Location] = '[1]'

Drag options to blanks, or click blank then click option'

ACity

B[City]

CLocation

D[Country]

Attempts:

3 left

💡 Hint

Common Mistakes

Using field references inside the string.

Using incorrect field names.

The join condition should compare the [Location] field to the string 'City' without brackets, so City is correct.

4fill in blank

hard

Fill both blanks to create a calculated field that converts longitude and latitude to numbers.

Tableau

FLOAT([[1]]) + FLOAT([[2]])

Drag options to blanks, or click blank then click option'

ALongitude

BLatitude

CCity

DCountry

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-numeric fields like City or Country.

Mixing up Latitude and Longitude.

Longitude and Latitude fields must be converted to float numbers for calculations.

5fill in blank

hard

Fill all three blanks to create a custom geocoding join condition matching city, state, and country.

Tableau

[CustomGeo].[City] = [Data].[[1]] AND [CustomGeo].[State] = [Data].[[2]] AND [CustomGeo].[[3]] = [Data].[Country]

Drag options to blanks, or click blank then click option'

ACity

BState

CCountry

DRegion

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect field names like Region instead of Country.

Mixing up the order of fields.

The join condition must match City, State, and Country fields correctly between custom geocoding and data tables.

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