Video | Tableau | Data prep | Data visualisation

Spatial support in Tableau Prep

Spatial data working natively inside Tableau, blended and built entirely in the browser, isn't that amazing?

Part ofTableau Prep Builder tutorial Jan-2020
Watch on YouTube
  • When uploading spatial files to Tableau Prep in the browser, you must use the zipped version since the server needs all the shapefile components in one go
  • Connect spatial geometry data at the very end of your flow, after data prep, joining on the best matching field such as state name
  • A left join keeps all your original records even when the spatial file contains extra regions that don't match
  • Adding spatial files barely affected runtime, with the flow completing in around seven seconds either way
  • Browser-based spatial files lose the link to a source file, so they won't auto-update from a SharePoint folder like a desktop connection might

Tableau Prep in the browser now lets you connect to spatial files directly and blend geometry data into an existing flow, so you can build a fully spatial workbook without leaving the browser or touching desktop tools.

Tim starts from an existing browser-based Prep flow producing a Superstore output and wants to add US state geometry so it can be mapped in a workbook, all built online.

The Breakdown
  1. Add a spatial file as a new input 0:28

    Use the plus icon and choose spatial file as the connection type; because Prep is running in the browser it asks you to upload the file rather than browse a server path.

  2. Always upload the zipped shapefile 0:47

    You must select the zipped version of the shapefile, not the unzipped folder of components, because the server needs everything bundled together in one upload.

  3. Join geometry at the end of the flow 1:24

    It makes most sense to bring the spatial data in as a late join, after your main data prep is done, joining it onto your primary output rather than earlier in the flow.

  4. Pick the best matching join field 2:00

    Check the default join field Prep suggests and correct it if needed — here the sensible match was the state name field rather than an initial mismatched key.

  5. Expect and handle unmatched records with a left join 2:34

    When the spatial file contains extra regions your main dataset doesn't have, a left join preserves every original row even though a handful of geometry records won't find a match.

  6. Tidy the flow and run it 3:26

    Reposition the join and any extra branches so the main flow stays central and inputs sit off to the side, then run the flow — publishing changes first if the output is already a published data source.

  7. Build the workbook straight from the browser 4:52

    Once run, the geometry field appears in the dataset; open a new browser-built workbook and double-click that field to render the spatial data natively, with no desktop step required.

  8. Know the tradeoffs 5:40

    Runtime was barely affected by adding spatial data, but a browser-uploaded spatial file loses its link to the source, so it won't auto-refresh from somewhere like a SharePoint folder the way a desktop connection would.

Worth Knowing
  • Unmatched records aren't always obvious — several US states/territories were missing from the base dataset and only surfaced once the spatial join was checked
  • A left join can silently drop unmatched spatial rows while still keeping all original data rows intact
  • Spatial files connected in the browser lose their live link to the original file, so updates to the source won't flow through automatically
  • Adding spatial data added negligible time to the flow run in this test
Use It When

Reach for this when you need to blend geographic boundary data into an existing dataset for mapping, and want to do the whole build — prep, join and visualisation — without leaving the browser.

How this Rollup was made provenance & method

A Rollup is drafted by AI from the video's transcript, then reviewed and edited by Tim. Everything used to produce this one is listed below — the model, the exact prompt, and the source video — so the process is transparent and reproducible.

Transcription
On-device — NVIDIA Parakeet v3 for recent videos, OpenAI Whisper large-v3 for earlier ones. The transcript never leaves the machine or gets published.
Drafting
Claude Sonnet 5 in the cloud, from that transcript.
Prompt
The exact Rollup prompt (v2) — the full system prompt, unedited.
Source video
Watch on YouTube
Drafted
5 July 2026 at 09:38
Reviewed & edited
5 July 2026 at 09:41 · by Tim Ngwena

Model + prompt + video is everything you'd need to recreate a Rollup like this yourself. The one thing we don't share is the transcript.

Rights. The video and its transcript are the property of TN Media Ltd. Unauthorised use or download is prohibited. © TN Media Ltd.