This is my control
To the right is Andy's viz
Choose your American States:
Wednesday, December 29, 2010
Tuesday, December 28, 2010
Starting in 2011, I'm making a mission out of creating tiny charts and dashboards. I'm exhausted from constantly looking at big, ugly charts and dashboards that fill up the screen but are mostly filled with whitespace and other useless junk. Keep reading below the viz to see more info.
In the two examples above: The Multigrain dashboard uses a calculated field and a parameter to change the Level of Detail (LOD) for the visual. This is *not* recommended at high data volumes as it will be quite slow. However, you should see decent performance at 5k to 5m records, depending on your data source. The nasty non-optimal calculation looks like this:
CASE [Select Granularity]
WHEN "Level 1" THEN [Prod Type1]+", "+[Segment]
WHEN "Level 2" THEN [Prod Type1]+", "+[Segment]+", "
WHEN "Level 3" THEN [Prod Type1]+", "+[Segment]+", "
+[Prod Type2]+", "+[Prod Type3]
+", "+[Prod Type4]+", "+[Customer Name]
WHEN "Level 4 - Warning!" THEN [Prod Type1]+", "+[Segment]
+", "+[Prod Type2]+", "+[Prod Type3]+", "+[Prod Type4]+", "
+[Customer Name]+", "+str([Order Id])+", "+str([Line Id])
I guess the good news here is that Moore's Law will keep catching up with this kind of lazy, non-performant analytics! :)
The second example, Quadriplot, came to me in a fitful waking state. I wanted to see how small I could make a 4-up dashboard without losing usability. It's debatable as to how successful I was. Nonetheless, the salient points to this dashboard are:
- The use of discrete Tableau Actions
- The use of the new 6.0 table calculations to show totals at the bottom
Monday, December 27, 2010
Those who know me, know me as a contrarian. Thus, with the arrival of 6.0, I'm going to highlight one of the oldest features in Tableau. This feature - known as "only show a background image when a field equals a value" does not appear to be documented anywhere. Perhaps in the Tableau user forums. I haven't had time to search... anyhoo, this happy little feature is one of my personal favorites. In the viz shown below, when you select a new value for the data set (Tableau's ubiquitous "coffee chain" data), the background image will change. I have randomly selected four satellite images, which have nothing to do with the data per se, but it demonstrates the point nicely.
Wednesday, November 10, 2010
Here are three things amongst many that I like about version 6.0. Let's start with combo charts. You can now have lines and circles and bars and shapes all on the same viz. No real limits here, except good common sense and taste. We'll be seeing lots of junk charts as a result of this feature set. You take the good with the bad. Below we have a disk drive viz, showing writes per second. The dotted line is a user-controlled moving average. Using a margin of error calculation, we have also shaded the upper and lower bands, which themselves are also controlled by the end user.)
Next up are variables (the example above had one). These are handy little helpers to make your calcs and visuals come to life. With this new parameter concept, Tableau provides specific datatype support for dates, strings, numbers, and booleans. Tons of nifty cool things you can do with these! In the next viz we are given the ability to select the fields we want to display. This is a quick and easy way to create one single visual which can serve many different purposes.
The third item I'm really enjoying is hierarchies in conjunction with the new super fast data engine (which replaces firebird).The viz below shows a hierarchy in action. Tableau Groups, Bins, Calculated fields and regular fields can all be added to a hierarchy. In our hierarchy, we even have a parameter-driven calculated field!
Tuesday, June 1, 2010
Tuesday, May 4, 2010
The example below shows state "Per Capita Income" and "Percentage of College Degrees" against all other states. The selected state is positioned at 0,0.
The data comes from http://www.census.gov/compendia/statab/rankings.html
More information describing how to do this is shown below the visual.
This was basically a self join on the table, where state <> state (not equal to). Then, I was able to create very simple calcs to create the X and Y coordinates for "other states" as compared to my selected state.
Here is a picture of the join:
and here is the actual data that I used. I had to combine the two statistics (income per capita, and percent BA degrees) into one table, as the census folks don't like handing out arbitrary cohort analytics to the general public!! :)
Monday, May 3, 2010
Monday, March 22, 2010
View The Example | View The Explanation
Wednesday, March 10, 2010
The data below comes from http://data.seattle.gov and this visual uses a simple police precinct image as the background.
The basic conclusion I can come to with this data is: overall, crime is quite a bit down year over year for 2008-2009. Nifty.
All Crime Data | Crime Decreases | Crime Increases
Monday, March 1, 2010
Author's Note, Dec 2010:This blog post is now obsolete by virtue of the fact that Tableau 6.0 has "parameters" - the entire subject of data explosion or data fanning is no longer a requirement.
original blog post
Quick start cheat notes:
- sample data is here
- make all joins "not equal to"
- set all filters to single-select (and make them global just for convenience)
Read the rest of the article below this dashboard, for the full details...
Use the sliders to interact
A discussion about "predictive modeling", or "forecast analysis", or, "what if analysis"
This entry discusses steps required to use Tableau to create what if or hypothetical analysis models. While not currently a core feature of the product suite (with the typical resulting marketing and sales splash as such), it turns out that with a little thought, and by following a few simple rules, you can create forecast models in Tableau. For the purposes of this discussion, I have used Xcelsius as a comparison, a tool that is commonly thought of as excellent for this type of analysis.
Products that provide extensive forecasting and predictive modeling algorithms are great tools for creating "what if" or hypothetical analysis - there's a great deal of heavy lifting going on to make this magic work. Some of the technical challenges involved include (not limited to):
All of the heavy lifting or number crunching needs to occur somewhere or at some point in the overall process
The user experience and software design thereof needs to provide compelling and useful tools for managing the input and output of the modeling.
There are some good software packages out there that provide forecast modeling and predictive analysis. A few worthy mentions include SAS, SPSS, the open source "R" package, and SAP’s Xcelsius (formally owned by Business Objects, who in turn purchased it from Infommersion, Inc, see nice history link here). From anecdotal evidence it appears that Xcelsius attempts to operate on one very small amount of data at a time, and then "explodes" this data out into a much larger data set - most likely in memory. General approaches to this type of modeling scenario include pre-processing possible values in a database engine, or, performing other in-memory processing.
Tableau can achieve this "exploded" data concept by creating table joins on all possible values - essentially a Cartesian join showing all possible combinations of data. There are a few simple tricks to make this work:
- Create all joins as "table1.fieldX <> table2.fieldY" (i.e. use the "not equal" type). Make sure no values will match, or else this does not work! See the excel file which shows the four sheets to join; as well, you can download the workbook shown above to see the joins.
- Any time you create calculated fields, make sure that they are non-aggregation calculations. See the workbook for the calculation called "potential value". Basically, you want row-by-row calculations at all times!
- And most importantly! Make sure you have single-select filters for all forecast or what-if variables which are controlling the "fact" data.
What does that last item 3 really mean? Let’s take a closer look at the sample excel data:
In the example excel file, we had three categories (K-12 School District, S&P 2000, and Federal Agencies) and 6 possible values (50k through 300k) for a total of 18 possible values.
By joining on a percentage between 1 and 100, the data gets exploded out to 1800. And by adding in a second variable called "blending", which ranges from -.21 percent to .21 percent (43 possible choices including zero), this further explodes the 1800 records out to 1800 times 43 = 77,400 records.
However, because our three Tableau filters for "blending", "percentage" and "variable" are all marked as single-value selections, we will only see 3 records at a time (the original three categories).
Exploring the workbook shown above by downloading it will help convey this point.
You can now start to guess why Xcelsius and possibly other products start to perform slowly when dealing with larger data. One of the reasons is the data explode factor involved. If instead of the above numbers, I wanted to apply a two-variable what if or forecast model on 500 types of values (500 customers showing sales, 500 products showing inventory, etc), and one variable ranged from 1 to 100, the second variable ranges from -30 to +30, then my data explode result would be 500 * 100 * 61 = 3,050,000 records! No matter how you slice and dice this problem - in memory vs. pre-calculated, oracle vs. sql server or some other database, java versus dot net- you will still be faced with this concept of data "explosion"...
Tableau can handle 3 million records, by the way...
Friday, February 26, 2010
A list of potentially terrible movies directed by "Alan Smithee" is located here.
Alan Smithee's Bio is located here.
ALL content on this blog is specifically authored and controlled by the one and only Alan Smithee.
Tuesday, February 23, 2010
In Tableau desktop, for an individual sheet, you can specify portrait or landscape mode for that sheet, from the File>Page Setup command. This setting will be honored once you publish to Tableau Server.
For example, the following link will auto-generate a PDF of a multi-page report. Notice that the output is already set to "landscape" mode:
Click here to view the multi-page PDF report
Whereas, this second link is the same exact information, but placed onto a dashboard which has been sized to 1100 x 850 (letter landscape). It will only print one page, and thus, a good chunk of the information is cropped and not visible:
Click here to view the single-page PDF dashboard
Again, this is all quite logical: it doesn't really make any sense to print a multi-page dashboard. Else, why call it a dashboard in the first place?
Friday, February 19, 2010
At the heart of this example is the fact that I created a public google calendar and then tried to understand the possible variables I could insert into the URL. This part turned out to be rather undocumented, and it's quite possible that google will change this over time, thus breaking this example. If you download the workbook, you will see a Tableau "action" URL which includes the fields from the example data inside the URL.
I also had to create a calculated field called "stringy month" which pads the month integer with a zero for months 1 through 9, simply because google is apparently not smart enough to deal with this. Again, you can download the entire workbook shown below to see this all in action. It's easier to see than it is to type.
To begin: click on one of the heat map squares shown below. Each square is a month and a year. Hover over each one to see the date, total fictitious sales, and fictitious profit.
Just for fun, I set all of the links to use the PNG picture output of the original visual. You can always create a dynamically generated PNG image from any Tableau visual simply be adding ".png" to the end of the URL. The same concept applies for PDF output.
Select a row below to view the PNG output of the original visual. Go to Tableau Public to view any of the original visualizations, all of which are interactive.
Thursday, February 18, 2010
You only need to know the direction (in degrees) and the wind speed.
The excel file which this book is connected to contains 100% ficticious data. No Wind Farm Corporations were harmed in the making of this workbook.
The X calculation for showing "east west" is:
And the Y calculation for "north south" is:
Wednesday, February 17, 2010
In the example below, the client wanted to see - for each utility registrant and each hour of the day - the averages of energy use, but also wanted to see the various averages as compared to the lowest average (I.E. the min of the averages) This solution also allows us to see percentage bands above this minimum. Plus, if you click on a bar segment you can see the exact percentage above the minimum. Nifty!
Tuesday, January 19, 2010
A few notes:
- I culled data for only the last ten years, and only for the snohomish area.
- The contractors who actually performed the contaminant samples often used different units of measure, as a result of using different testing methods. So I have placed a filter for UOM to help verify the test results. In plain english: the time trend and its 'median' value reported is bogus information if you mix your UOM types.
- I removed any concept of what testing method they used, what the baseline observable measurement was, etc.
- you can select a sample type, then lasso some data marks on the timeline to see individual sample reports.
- The Tableau tooltips are nicely formatted; take a look at those!
- clicking on the "links" item will show a bing map of the sample location. Hovering back over that same selected link item will also show two other links, to NIH.gov and wikipedia (for the contaminant in question)
- In short: this was mostly an experiment with Tableau features, as opposed to a deep dive into water quality and contaminant analysis.
Friday, January 8, 2010
With only a little bit of thought and care, you can create extremely polished dashboard widgets like the one shown below. I used just a small amount of HTML code to create a simple navigation scheme shown on the left below, which in turn points to various published visuals. Nice and easy!
If you speak arabic and see that there is something wrong from a technical point of view, let me know. If the translation is just 'terrible', then let microsoft know.