1 of 1 people found this helpful
The problem is the data type. Teradata basically allows long form/concatenation of X,Y as a LOB.
You may need to convert back to a VARCHAR.
Sorry to be of little help!
Hi Allan! I did not expect to get such a quick response. It was helpful. Thanks for sending a link to Teradata Developer Exchange site. Now I clearly see it is a Teradata odbc driver issue not Tableau and I need to ask Teradata if there is anything I can do about it or if they plan to fix it in the future. What is interesting enough I can bring this table and view the data in this column from the BTEQ that uses cliv2 connection. Thanks again!
You may be able to connect to the table of interest using a Custom SQL query, which you can write to extract the X and Y components as longitude and latitude. This way you will only expose the floating point values to Tableau instead of the raw geospatial data (which is potentially quite large), and you should no longer see that error message.
Hi Robert! Thank you very much! I was able to bring the table using the Custom SQL.
Here is the SQL with the extraction of X and Y coordinates in case if someone else has the same issue:
adr_pt.ST_X() as LONGITUTE,
adr_pt.ST_Y() as LATITUDE
I'm glad that worked! Thanks for following up here.
That's really useful!