Spatial Join Slow and Returns Inverted Results Using KML or SQL Spatial Data Imported from Shapefile or GeoJSON | Tableau Software

KNOWLEDGE BASE

Spatial Join Slow and Returns Inverted Results Using KML or SQL Spatial Data Imported from Shapefile or GeoJSON

Published: 06 Aug 2018
Last Modified Date: 02 Jan 2019

Issue

When using a data source based on a Shapefile or GeoJSON file that was imported into SQL Server, visualizations based on the resulting geographies may appear inverted, and the join slower than expected.

Environment

Tableau Desktop
Spatial Joins
Shapefiles
GeoJSON
SQL Server

Resolution

When you import Shapefiles into SQL Server, intentionally reverse the vertex order. For more information, see Working with Invalid Data and the SQL Server 2008 Geography Data Type at MSDN.

Cause

The vertex order convention of Shapefiles is the reverse of the vertex order specified by SQL Server.

Additional Information

For more details on how Tableau handles vertex ordering, see Supporting advanced spatial analytics with changes to lines and polygon edges in Tableau.

Discuss this article... Feedback Forum

Click here to return to our Support page.

Open a new case

Click here to go to our Support page.

Get detailed answers and how-to step-by-step instructions for your issues and technical questions.

Find and share solutions with our active community through forums, user groups and ideas.

Browse a complete list of product manuals and guides. Available online, offline and PDF formats.

Learn how to master Tableau’s products with our on-demand, live or class room training.

All Support

SUPPORT BY PRODUCT

TOOLS & DOWNLOADS

INFORMATION

ASSISTANCE