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: 06 Aug 2018

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

Cause

The vertex order convention of Shapefiles is the reverse of the vertex order specified by SQL Server. 
Did this article resolve the issue?