This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
As a Tableau user as well as an Alteryx user, I suggest Alteryx can support WKT (Well-known_text) as part of its spatial format, and support output spatial object in TDE file:1. it can output spatial object intotde file directly, as Tableau use WKT as a spatial object format in its TDE file. 2. WKT is essentially a standard string, which can lower downbarrier of handling andexchangingspatial data, and make spatial data more accessible. For example, it is easier to write spatil file to Exasol databse, which support WKT as spatial object.
For your information. I am aware that FME can output spatial object directly intotdefile(forexample:how-to-write-spatial-data-into-tableau-with-fme;tutorial-preparing-data-in-fme-for-tableau), while, currently, Alteryx don't have this function. So if one have a file withspatialobject (eg.postcode-string, its polygon-spatial object), it is straight forward to get a file with spatial object ready to use with FMEtdefilecreater, whereas, in Alteryx, itoutput thestring part only. [Currently, I amoutputinga spatial file, and combine the string with the spatial file, and let Tableautotransform the spatial object to WKT for me.]
A good article demonstrated how to workaround before Alteryx can help to do this inside current spatial object output. I think it shouldn't be too difficult for the Talents in Alteryx to integrate this inside Alteryx, hope it is heard by the Alteryx people.
If you know that you want to use this data in Tableau (and you have the Personal or Professional Edition of Tableau Desktop), you can take a shortcut and write your routes directly into a Tableau Data Extract (TDE) file using the TableauSDK (SDK = Software Development Kit). The SDK supports several languages (C, C++, Python, etc.). We used the Python version to turn the routes created usinggeographiclibinto a TDE.
A benefit of writing straight into a TDE is that the files are much smaller because coordinates for each route are compressed into our spatial data format as you drop them into the TDE."