Tableau 2020.2: ESRI web data connector in Tableau
Tableau 2020.2 lets you connect to Esri ArcGIS data with just a URL, then spatially join it across databases.
- The Esri ArcGIS server connector in Tableau 2020.2 lets you connect to location data just by pasting an ArcGIS server URL or Geo Service API URL.
- These connections always create an extract rather than connecting live, signalled by the two-cylinder icon, because of how Tableau needs to work with the spatial data.
- Spatial fields can return both polygons and multi-polygons within a single shape column, giving you mixed spatial types to work with.
- You can perform cross-database spatial joins using a spatial intersect rather than matching on equal columns, which is more reliable than trusting potentially error-prone city columns.
- Colour-coded bars (blue and orange) in the join interface indicate which connection each table is coming from, helping you track data across multiple sources.
Tableau 2020.2 adds a native Esri web data connector, so you can pull ArcGIS server data into Tableau with just a URL and then spatially join separate Esri connections without relying on matching text columns.
The demo connects to an ArcGIS server hosting government building and water service district boundary data, both accessed via Esri Geo Service API URLs.
- Find and open the Esri connector 0:00
Under the server connections list, look for 'Esri ArcGIS server' (separate from the generic web data connector, which is aimed at developers building their own connectors). This is your entry point for any ArcGIS-hosted spatial data.
- Connect with just a URL 0:41
Paste in an ArcGIS server URL or Geo Service API URL and hit connect; Tableau queries the API directly, so you don't need any other setup to get at the fields.
- Inspect the metadata before building 1:01
Once connected, check the fields view: Tableau auto-recognises geographic fields like address and city, and shape columns can contain both polygons and multi-polygons in a single field, so be aware you're working with mixed spatial types.
- Expect an extract, not a live connection 1:42
These connections always create an extract rather than connecting live, because of how Tableau needs to process the spatial data — you'll see this signalled by the two-cylinder extract icon.
- Build a basic spatial map 2:01
Double-click the shape field to generate a map, then colour by a boundary name field to see all areas at once; adjusting the background map style and washout makes it easier to read as you zoom in.
- Add a second Esri connection for cross-database work 3:03
You get the full capability set of the current Tableau version with any new connector, including relationships and cross-database joins — add a second Esri connection alongside the first to combine two spatial datasets. The coloured bars (e.g. blue vs orange) on tables show which connection each one came from, which helps you track data as things get more complex.
- Switch from relationship to a physical join for spatial intersect 4:40
Dragging a table straight out builds a relationship by default, which is the wrong tool here — for this you must go into the join canvas instead. There, join on the two shape fields but change the match condition from 'equal' to 'intersect', which acts like a spatial join and is more reliable than trusting potentially error-prone city columns.
- Visualise the joined result 6:53
Once joined, you can pull in a name field from one source alongside detail records from the other — e.g. seeing which buildings fall inside which service district — and combine this with the earlier map approach to visualise both boundaries and points on the same view.
- Esri connections always build an extract; they can't stay live because of how Tableau needs to process the spatial data.
- Shape fields can mix polygons and multi-polygons within the same column, so check metadata before assuming a single spatial type.
- Dragging a second table in by default tries to create a relationship, which throws a warning here — you need the classic join canvas and a spatial intersect condition instead of matching on shared columns like city.
Reach for this when you need to bring ArcGIS-hosted boundary or location data into Tableau quickly and want to relate two separate spatial datasets (like buildings and service districts) by actual geographic overlap rather than by matching potentially unreliable text fields.
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.