Very cool, thanks for sharing! I hadn't heard of RSSBus before.
This is great!!
Cool! Now if only Google docs wasn't blocked at Piedmont.
2 of 2 people found this helpful
Nice. I had tried RSSbus in the past but never got it to work. Guess I'll have to try again. Of course, I'd like this as a native connector some day. Did anyone submit this to the ideas forum?
Reading through the documentation, it looks like there is a method to tunnel through a firewall via a proxy. I haven't tried that -
Francois, I haven't tried the oauth authentication yet, or the 64-bit drivers. I just used the Google (deprecated) client authentication.
The vertices tab on the sheet is quite small. I didn't try the "archive" tab yet (it's huge, almost 6 months of analysis of the "#tableau" twitter hashtag. My test spreadsheet is probably of interest to folks too: It's a Twitter archiver caled Tags. Instructions for Tags here.
Note to all, I have no relationship with the vendor; and I am certainly not in a strict test environment. I'll probably fork out for the full version ($60 USD), as I've been using syncdocs in the past - and being able to collaborate on the cloud makes this worthwhile for me.
1 of 1 people found this helpful
Great work - thisis going to be big fun for many people!
1 of 1 people found this helpful
Very Cool! I tried it out and got it to connect to some test Google Spreadsheet. Thanks for sharing. This will allow me to put even more data into my Gdrive
Anyone else try this and had every column come in as "String."
E.g. dates and numbers are 'abc'
I also got a warning with a huge list (176 warnings) of functions and aggregations that are "Unsupported " by this OBDC driver.
Any thoughts on what might be going wrong?
I don't know why you're seeing all fields as having type String, but you can change the data type by right-clicking on one field or a selection of fields and choosing the appropriate type under the Change Data Type submenu.
As for the ODBC warnings, these are due to the driver either lacking support or failing to declare support for various features Tableau requires for a good experience. The best practice in this case is to create a Tableau Data Extract, which will load all of your data into the fully-functional Tableau Data Engine. While many users may wish to have a live connection experience for cloud data sources such as Google Spreadsheets, this ODBC connector provides a useful stepping stone until Tableau decides to create a first-class connector for Google Spreadsheets.
Note that I cannot comment on our roadmap, nor the priority / possibility of such a feature.
Implementation of the ODBC drive worked great. Changes to the Google Spreadsheet updates within a few seconds in Tableau once you refresh the live connection.
I tried another approach using SyncDocs. This option worked as well. But there were some issues getting the documents to sync correctly.
Allan, just to heap the praise - your are filled with the powers of awesome. Thanks for sharing. And the rest of you for testing and validating.
So I did some more testing after procuring the driver(s) from RSSBus.
=importJSON("https://api.flightstats.com/flex/flightstatus/rest/v2/json/airport/tracks/SFO/arr?appId=<MYAPPID>&appKey=<MYAPPKEY>&includeFlightPlan=false&maxPositions=1&extendedOptions=includeDeltas"&GoogleClock(),) which pulls the arrivals at San Francisco in JSON format. The GoogleClock() parameter refreshes the data in the sheet, rather than use a trigger.
I then installed the RSSBus drivers: they come with 32-bit and 64-bit drivers and support oauth 2.0 connections to Google Spreadsheets.
I then use the generic ODBC connection in Tableau and selected the 64-bit DSN, added my sheet name (dbname) and my Google credentials, and then selected the table. I didn't select the ODBC pooling connections parameter.
Tableau successfully connected and populated both dimensions and measures. As these were formulae in the sheet, the field names were given aliases, so I had to look at the underlying data to rename them sensibly.
Although Tableau prompted me to create an extract, I didn't need to.
After a bit of faffing renaming the fields and connecting to a custom TMS using ESRI's RESTful mapping service "World Navigation Charts" this appeared:
I was then able to refresh the connection to get the latest tracks.
Next up, I spun up an evaluation copy of Tableau server on my localhost. I was able to publish to the server fine, but because the connection was generic ODBC, I got an error message; which I reported to Tableau support. Even though I had the DSN and driver on my localhost, it wasn't able to establish a connection.
Support was excellent, within an hour I got a response to try using python and a batch script, but I'm going to have to wait until Tableau brings a native connector down the pipeline to enable Server-side automatic refresh, as I'm unconvinced the batch file would be able to pump the update fast enough.
So all in all, it's a good stop gap for those using desktop...and IMHO worth $60. Next up will try Splunk to stream the JSON in...
Has anyone found one for the Mac version?