Tooltips can now contain worksheets themselves – “viz within a viz”.Integration with Mapbox: the use case shown was to allow custom map backgrounds to use, including a satellite view.You could visualise this using a shapefile as per the previous bullet – but you will also be able to interactively define them within Tableau itself. Custom geographic territory creation: perhaps your sales territory consists on a hand-selected bunch of postcodes.These files, usually output by GIS tools, are a way to represent any custom geographic shapes. Various clever people (many from the Information Lab) have worked out ways to replicate this type of functionality in Tableau or with the help of external tools like Alteryx – but a native import will make life much easier, and hopefully faster. A connector to allow connection to spatial data files –.Great for those of us without a pure US focus. New native geospatial geographies: a bunch of new granular postcode level geocoding information – I think polygon – data for 76 countries.For instance if you have a scatterplot showing 1000 customers, then you can type in the name of one of them and it will show up, without having to play around with complicated filtering workarounds. Data highlighter: search and highlight particular points on charts interactively.It sounds like simple stuff, but there’s a lot of “why can’t I do it in Tableau given it’s so easy in Excel” text table type stuff that one hears going around, especially amongst novice users and those consumers as-yet unversed in the benefits of less textual data viz. I can’t imagine using this all that much, but there are certainly occasions where nothing beats a text table, so more options are always welcome. Enhancements to the text table visualisation, particularly to exclude totals from any heatmap and optionally move totals to the top of the table.This might reduce the need for a lot of preprocessing or data duplication, which is done today either on the IS side or using other analyst ETL type tools.
An example of someone joining a SQL server to an Excel table was shown if I recall correctly. not blends) from tables on different databases or even database technologies.
#TABLEAU READER 9.2 WINDOWS#
Today’s custom SQL option has caused a little confusion in recent times in my experience as the newish Excel connector does not support it (but you can always use the legacy one instead, at least on Windows machines). This will help speed up a lot of users’ data preparations I’m sure and eliminate the more basic use of the custom SQL option too perhaps.
#TABLEAU READER 9.2 HOW TO#
They had trawled Tableau Public to see what was being used and managed to work out how to handle most/all of them. Can now understand hundreds of different date formats.Here’s an example that was auto-interpreted correctly into a single tall table. Improvements to the automatic data cleanup feature recently released that can import Excel type files that are formatted in an otherwise painful way for analysis.The features were divided up into 6 main categories improvements to: After a couple of conversations, I have marked with “9.2?” those features that seem likely to be in 9.2, but I understand that nothing is set in stone, so stuff may change before release. Some are to come in version 9.2 within probably a few weeks the bulk in future versions – one imagines version 10 sometime late next year. Most of these features were live-demoed so are presumably fairly far along in the development pipeline.
#TABLEAU READER 9.2 PLUS#
Any errors are of course of my own doing…it was a tiring week- plus them being features “in development” means Tableau makes no absolute promises as to what will actually end up included. Having been lucky enough to attend the huge (*) Tableau #data15 conference a couple of weeks ago – and by now managed to recover mostly – I have noted down some information from the keynote presentation and beyond of what features are likely to appear in nearby versions of Tableau.
0 kommentar(er)
