Study guide
9.2 Spatial Data & Mapping: Geographic Layers & Spatial Functions
Salesforce Certified Tableau Data Analyst Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Connecting to Data & The Logical Data Model
1.1 Data Connections: Live Connections vs. Hyper Extracts 1.2 The Tableau Data Model: Relationships vs. Physical Joins 1.3 Combining Data: Data Blending vs. Cross-Database Joins
2 Chapter 2: Tableau Prep Builder & Data Wrangling
2.1 Tableau Prep Architecture & Data Cleaning 2.2 Reshaping Data in Prep: Pivots, Splits & Wildcard Unions 2.3 Joins, Aggregations & Output Destinations in Prep
3 Chapter 3: Data Quality, Metadata & Field Configuration
3.1 Data Types, Roles, Organization & Default Properties 3.2 In-Desktop Data Cleaning: Splits, Data Interpreter & Source Replacement 3.3 Managing Slowly Changing Dimensions & Data Quality Warnings
4 Chapter 4: Tableau Fundamentals & Calculations
4.1 Dimensions vs. Measures & Discrete vs. Continuous 4.2 Mastering Dates: Discrete Date Parts vs. Continuous Date Truncations 4.3 Calculations: Logic, Strings, Nulls & Type Conversion 4.4 Aggregation Rules, Granularity & Dealing with the Asterisk (ATTR)
5 Chapter 5: Level of Detail (LOD) Expressions
5.1 Level of Detail Architecture & Scoping Syntax 5.2 FIXED LOD Expressions: Scoping & Baseline Benchmarks 5.3 INCLUDE & EXCLUDE LOD Expressions: Dynamic Granularity 5.4 Real-World LOD Patterns: Cohorts, First/Last Dates & Binning
6 Chapter 6: Table Calculations & Directionality
6.1 Table Calculation Mechanics: Addressing vs. Partitioning 6.2 Essential Table Calculations: Running, Window & Percent of Total 6.3 Navigation & Ranking Functions: LOOKUP, INDEX & RANK 6.4 Secondary & Nested Table Calculations: Multi-Level Scoping
7 Chapter 7: Statistical Analytics, Filtering & Order of Operations
7.1 The Tableau Order of Operations: From Extract to Display Filters 7.2 Sets, Set Actions & Combined Sets vs. Groups 7.3 Parameters, Parameter Actions & Dynamic What-If Analysis 7.4 Analytics Pane: Totals, References, Trends & Forecasts
8 Chapter 8: Chart Types & Comparative Visualizations
8.1 Comparison Visualizations: Bar Charts, Highlight Tables & Bullet Graphs 8.2 Part-to-Whole & Correlation Charts: Treemaps, Scatter Plots & Bubbles 8.3 Trend & Distribution Visualizations: Dual-Axis, Combos & Histograms
9 Chapter 9: Advanced Visualizations & Spatial Analysis
9.1 Specialized Visualizations: Waterfall, Gantt, Sparklines & Bump Charts 9.2 Spatial Data & Mapping: Geographic Layers & Spatial Functions 9.3 Visual Polish: Custom Palettes, Annotations & Viz in Tooltip
10 Chapter 10: Dashboard Design & Interactive Actions
10.1 Dashboard Layout, Devices & Visibility 10.2 Filter, Highlight & URL Actions 10.3 Advanced Interactivity: Parameter, Set & Navigation Actions 10.4 Stories & Visual Storytelling: Sequencing Analytical Narratives
11 Chapter 11: Tableau Server & Cloud: Architecture & Publishing
11.1 Tableau Server & Cloud: Sites, Projects, Roles & Permissions 11.2 Publishing Workbooks, Data Sources & Flows
12 Chapter 12: Data Governance, Security & Operations
12.1 Certification, Data Quality, Lineage & Permissions 12.2 Row-Level Security, Schedules, Subscriptions & Alerts
9.2 Spatial Data & Mapping: Geographic Layers & Spatial Functions
Key Takeaways Explain This Topic AI
Tableau mapping recognizes native geographic roles (Country, State, Zip Code, CBSA) and auto-generates Latitude (generated) and Longitude (generated) fields, but custom spatial functions require explicit numeric coordinates or geometry fields.
The Map Layers shelf (introduced in Tableau 2020.4) allows authors to add multiple independent spatial layers onto a map, each possessing its own mark type, color palette, size encoding, tooltip, and selection-locking control.
Custom geocoding extends Tableau's built-in geographic hierarchy using a directory of CSV files and a schema.ini definition, whereas spatial files (.shp, GeoJSON, KML) natively import spatial polygon and polyline geometries.
Tableau provides five core spatial calculations: MAKEPOINT() converts coordinates to points, MAKELINE() connects points into lines, DISTANCE() computes surface distance, BUFFER() creates circular boundary polygons, and INTERSECTS evaluates spatial overlap.
Spatial joins must be configured in the Physical Layer of the Data Model using the INTERSECTS operator, enabling point-in-polygon and buffer-containment joins without external GIS pre-processing.
Last updated: September 2026
9.2 Spatial Data & Mapping: Geographic Layers & Spatial Functions
Geographic analysis is one of Tableau's most visually compelling and analytically powerful capabilities. From simple regional sales choropleths to complex multi-tiered logistics models involving trade-area buffers and flight paths, spatial analytics allows organizations to uncover location-based patterns that tabular data obscures. For the Salesforce Certified Tableau Data Analyst, exam readiness requires a thorough mastery of background map layers, the modern Map Layers shelf , spatial file integration, and native spatial functions such as MAKEPOINT() , MAKELINE() , DISTANCE() , BUFFER() , and spatial joins using INTERSECTS .
Tableau Mapping Architecture & Background Maps
When a data source contains geographic fields (such as Country, State, City, or Postal Code), Tableau assigns them a Geographic Role (indicated by a globe icon). When an author double-clicks a geographic field, Tableau automatically places Longitude (generated) on Columns and Latitude (generated) on Rows, rendering a map canvas powered by Tableau's vector map service.
Background Map Styles
Authors can customize the visual tone of the base map via Map > Background Maps :
Light : The default clean, minimalist map style suitable for corporate executive dashboards.
Dark : High-contrast, dark-mode styling optimized for displaying brightly colored spatial points and heat maps.
Normal : Standard geographic presentation showing basic land cover and geopolitical borders.
Streets : High-detail street-level view displaying local roads, highways, and street names, ideal for local logistics.
Outdoors : Emphasizes natural terrain, elevation topography, water bodies, and parks.
Satellite : Photorealistic high-resolution orbital satellite imagery.
None : Strips the background map entirely, rendering spatial marks floating on a transparent canvas (frequently used for custom floor plans or non-Earth coordinate maps).
The Map Layers Pane
Accessed through Map > Map Layers , this configuration pane controls the contextual cartographic detail rendered beneath your data marks:
Base Elements : Toggle coastlines, land cover, country borders, country names, state/province borders, state names, county borders, and major roads.
Data Layer (U.S. Demographics) : Tableau includes built-in U.S. Census demographic overlays. Authors can shade census tracts, counties, or states by population density, median household income, per-capita income, age distribution, or racial demographics without needing external demographic datasets.
WMS & Mapbox Servers : If standard background maps are insufficient, authors can integrate third-party Web Map Services (WMS) or custom Mapbox studio styles via Map > Background Maps > Manage Maps .
The Multi-Layer Map Canvas (Map Layers Shelf)
Historically, Tableau authors who wanted to overlay multiple spatial elements (e.g., store locations on top of regional sales polygons) were constrained to Dual-Axis maps , which imposed a strict limit of exactly two visual layers. In Tableau 2020.4, Tableau revolutionized spatial analysis by introducing the Map Layers Shelf . +-------------------------------------------------------------------------+
- | MAP CANVAS |
- | |
- | +--------------------------+ |
- | | Add a Marks Layer | <-- Drag spatial pill over drop zone |
- | +--------------------------+ |
- | |
- +-------------------------------------------------------------------------+
- How the Map Layers Shelf Operates
Adding a Layer : When an active map exists on the worksheet, dragging any geographic or spatial field onto the canvas reveals a prominent visual drop zone in the upper-left corner labeled 'Add a Marks Layer' .
Dedicated Marks Cards : Dropping the field onto this target creates an entirely new, independent Marks card in the Marks deck.
Layer Stacking : Authors can add multiple spatial layers to a single map visualization and control each layer from its Marks card.
Independent Layer Controls
Each layer on the Map Layers shelf operates completely independently:
Capability Description & Analytical Value
Independent Mark Types Layer 1 can be a filled polygon (States), Layer 2 can be a Line (Delivery Routes), and Layer 3 can be a Shape or Circle (Warehouses).
Independent Color & Size Each layer has its own Color and Size shelves. Layer 1 can use a green sequential ramp for profit, while Layer 2 uses discrete categorical colors for route status.
Layer Reordering (Z-Order) Dragging layer headers up or down within the Marks card reorders the visual stack. Top layers render above bottom layers on the canvas.
Selection Locking Authors can click the lock icon on a layer to disable mark selection. For example, locking a background polygon layer allows users to lasso point marks without accidentally selecting the underlying state polygon.
Show/Hide Visibility Authors can toggle the eye icon to show or hide entire spatial layers dynamically without deleting the configuration.
Custom Geocoding vs. Spatial Data Files
When organizational data references geographic boundaries that Tableau does not recognize natively (such as custom sales territories, internal school districts, or global telecommunications zones), authors must extend Tableau's geographic capabilities.
1. Custom Geocoding Import
Custom geocoding allows authors to import a folder of structured CSV files and a schema.ini file into the Tableau Repository via Map > Geocoding > Import Advanced Geocoding... :
Can extend an existing hierarchy (e.g., adding custom sub-counties beneath States).
Can create an entirely new independent geographic role (e.g., 'Sales Region' containing North, South, East, West).
Limitation : Custom geocoding only supports latitude/longitude point coordinates; it cannot import custom polygon shapes or boundaries .
2. Native Spatial Files
To visualize complex boundaries, parcels, transit corridors, or environmental zones, authors connect directly to GIS spatial files:
Supported Spatial Formats : ESRI Shapefiles ( .shp ), GeoJSON ( .geojson / .json ), Google Earth KML ( .kml ), MapInfo TAB files, and TopoJSON.
The Geometry Field : When a spatial file is loaded, Tableau automatically generates a single spatial field named Geometry (or matching the shape column) containing vector point, polyline, or polygon data.
Native Spatial Functions in Tableau
Tableau provides a robust library of spatial calculations that allow analysts to construct points, build lines, measure distances, and establish buffer perimeters dynamically within calculated fields. MAKEPOINT(Lat, Lon)
- |
- v
- +-------------------+-------------------+
- | |
- v v
- MAKELINE(PointA, PointB) BUFFER(Point, Dist, 'miles')
- (Builds Route Lines) (Builds Trade Area Polygons)
- | |
- +-------------------+-------------------+
- |
- v
- DISTANCE(PointA, PointB, 'miles')
- (Computes Scalar Great-Circle Distance)
- 1. MAKEPOINT(latitude, longitude, [srid])
Converts raw numerical latitude and longitude coordinate values into a native Tableau spatial point geometry. // Constructing a spatial point for customer addresses
MAKEPOINT([Customer Latitude], [Customer Longitude])
Caution
Critical Exam Rule : MAKEPOINT() can only be executed on raw numerical fields present in your underlying data source. It cannot be called on Tableau's auto-generated Latitude (generated) or Longitude (generated) fields.
2. MAKELINE(start_point, end_point)
Generates a two-point spatial line geometry linking two spatial points. It takes two spatial point geometries (typically constructed using MAKEPOINT ) as inputs and produces a line that curves along the Earth's great-circle trajectory. // Visualizing non-stop flight paths between origin and destination airports
- MAKELINE(
- MAKEPOINT([Origin Lat], [Origin Lon]),
- MAKEPOINT([Dest Lat], [Dest Lon])
- )
- 3. DISTANCE(point1, point2, 'units')
Calculates the great-circle surface distance between two spatial points along the curvature of the Earth. The return value is a continuous numeric measure (scalar number).
- Supported Unit Strings : 'miles' , 'km' , 'meters' , 'feet' . // Calculating delivery distance in miles
- DISTANCE(
- MAKEPOINT([Warehouse Lat], [Warehouse Lon]),
- MAKEPOINT([Customer Lat], [Customer Lon]),
- 'miles'
- )
- 4. BUFFER(point, distance, 'units')
Generates a circular spatial polygon boundary around a designated spatial point at a specified radius distance. The output is a true spatial polygon geometry.
Supported Unit Strings : 'miles' , 'km' , 'meters' , 'feet' . // Generating a 15-mile service coverage zone around retail stores
- BUFFER(
- MAKEPOINT([Store Latitude], [Store Longitude]),
- 15,
- 'miles'
- )
- Spatial Joins: Joining on Intersection ( INTERSECTS )
One of the important advanced concepts on the certification exam is the Spatial Join . A spatial join combines two disparate datasets based on spatial location rather than a common alphanumeric key.
Configuring a Spatial Join in the Physical Layer
Spatial joins must be configured in the Physical Layer of the Tableau Data Model (double-click the logical table in the Data Source tab to access the physical join canvas):
Drag the primary spatial table (e.g., Store_Locations or Service_Areas.shp ) onto the canvas.
Drag the second spatial table (e.g., Customer_Addresses.csv ) adjacent to it.
In the Join configuration dialog, select the join type (Inner or Left).
In the Join Clause dropdown, select the spatial geometry field from the left table (or use a Join Calculation like BUFFER(MAKEPOINT([Store_Lat], [Store_Lon]), 10, 'miles') ).
In the operator dropdown, select Intersects .
Select the spatial point geometry from the right table ( MAKEPOINT([Cust_Lat], [Cust_Lon]) ). Physical Join Clause:
- +------------------------------------+------------+-----------------------------------+
- | Left Table Field / Calculation | Operator | Right Table Field / Calculation |
- +------------------------------------+------------+-----------------------------------+
- | BUFFER(MAKEPOINT(Lat, Lon), 10, m) | Intersects | MAKEPOINT(Cust_Lat, Cust_Lon) |
- +------------------------------------+------------+-----------------------------------+
- What Spatial Intersection Accomplishes
The INTERSECTS join condition matches every row where the spatial geometries physically overlap in real-world geographic space. In the example above, customer records are joined to store records only if the customer resides inside the 10-mile circular buffer of that store . This eliminates the need for expensive spatial database pre-processing or complex Pythagorean approximations.
Summary Table: Spatial Functions Reference
Function Syntax Input Arguments Output Data Type Analytical Use Case
MAKEPOINT(lat, lon) Numeric latitude, Numeric longitude Spatial Point Geometry Converting CSV coordinate columns into mappable spatial marks
MAKELINE(pt1, pt2) Spatial Point 1, Spatial Point 2 Spatial Line Geometry Visualizing supply chain shipping lanes and flight routes
DISTANCE(pt1, pt2, 'unit') Spatial Point 1, Spatial Point 2, Unit string Numeric Measure (Float) Filtering customers within a specified straight-line surface distance of a clinic
BUFFER(pt, dist, 'unit') Spatial Point, Numeric distance, Unit string Spatial Polygon Geometry Creating trade area circles for retail site selection
INTERSECTS(geom1, geom2) Spatial Geometry 1, Spatial Geometry 2 Boolean Spatial Predicate Physical layer join condition for point-in-polygon aggregation
- Practical Exam Scenarios & Common Traps
- Scenario 1: Attempting to Buffer Generated Coordinates
An analyst connects to an Excel sheet containing customer addresses. Tableau assigns geographic roles and creates Latitude (generated) . The analyst writes the calculation BUFFER(MAKEPOINT([Latitude (generated)], [Longitude (generated)]), 5, 'miles') . Tableau displays a red calculation error stating that the fields do not exist.
The Root Cause : Generated coordinates are synthesized dynamically by Tableau's internal geocoding engine at render time; they do not exist as physical numeric columns in the underlying data source and cannot be passed into MAKEPOINT() .
The Resolution : The analyst must obtain actual numeric latitude and longitude coordinates in the raw dataset, or export the geocoded data to a Hyper extract that materializes the coordinates.
Scenario 2: Spatial Joins in the Logical Layer
An analyst drags two tables onto the top-level Data Source canvas (the Logical Layer) and attempts to define a relationship noodle using Intersects . The analyst cannot find the Intersects operator.
The Root Cause : Relationships in the Logical Layer only support standard relational equality ( = ) and inequality operators. Spatial joins relying on INTERSECTS must be executed as physical joins .
The Resolution : Double-click the logical table to open the Physical Layer canvas, drag the second table in, and configure the join using the Intersects operator.
Symbol, Filled, and Density Maps
A symbol map places a mark at each geographic location and can encode a measure with color or size. It is suitable for cities, stores, or other point locations. A filled map colors geographic areas such as countries, states, or postal regions; it is appropriate when the geographic field has polygon boundaries and the question compares values by area. It is not the correct choice for every city-level point analysis.
A density map changes the Marks type to Density and displays concentrations of overlapping points. Use it when thousands of incidents or customer locations obscure one another as individual symbols. Density communicates concentration, not exact point values. Multiple marks layers let an author overlay compatible geographic roles or spatial fields—for example, territories below store symbols—and configure marks separately for each layer. Validate layer order, color, opacity, and spatial reference so one layer does not hide another.