Tableau 4.1 Introduces WMS Mapping Support

Posted by Elissa Fink on September 24, 2008

Great news for those of you who are into analytical mapping. Today, Tableau Software released version 4.1 which offers many new enhancements including the ability to use WMS (Web Map Service) map images as background maps for your data visualizations in Tableau Desktop. I personally like some of the satellite maps we've found. 4.1 also offers other enhancements, including Server performance improvements and Active Directory improvements.

WMS Support
Tableau 4.1 adds WMS support so you can retrieve custom maps from your own WMS servers. While the Tableau online and offline maps were carefully designed to display data effectively and beautifully for all kinds of data, the WMS support allows you to use Tableau with specialized maps that are custom to your organization.

As an example, here's a visualization using publicly available data about donations to the major presidential campaigns. You can see a pattern where Obama has much deeper financial support on the West Coast while McCain has more deeply penetrated areas throughout the central parts of the country. I put this ZIP level "dot density" map on top of a satellite image from the WMS Server at the Federal Geographic Data Committee (FGDC). The WMS address that you would use in Tableau Desktop is "http://clearinghouse1.fgdc.gov/scripts/ogc/ms.pl".
map presidential donations by ZIP code using satellite image as backdrop

Created by the Open Geospatial Consortium, WMS is an international standard for how maps can be dynamically retrieved from servers. Tableau supports servers that have implemented the WMS 1.1.1 specification. There are some public WMS servers available as well as a number of WMS-enabled server products your organization may already have such as software from ESRI, MapInfo, or others.

You can download a quick start guide with step-by-step instructions for using a WMS server in Tableau 4.1. Also, check out the Wikipedia entry on WMS; you'll find more information and links there.

Server Performance Improvements
Many customers using Tableau Server will see performance improvements with the Tableau 4.1 upgrade. Specifically pages may load faster when requesting a view. In addition, the server has improved data caching, which increases responsiveness during interactive sessions. Refresh the data cache at any time to reload from the underlying data source.

Single Logon for Multiple Sheets
Tableau Desktop now only asks you to logon to each database one time per workbook. The username and password provided are reused for each sheet that connects to the same server and database. For example, a workbook with three sheets, each connecting to different tables in the same database, will now only prompt you to login once instead of three times.

Active Directory Improvements
If you use Active Directory authentication with Tableau Server, the 4.1 release adds several new capabilities to help you configure domain information. You can now specify the domain nickname during installation and modify both full domain names and nicknames after the server is up and running.


More can be simpler when telling data stories

Posted by Jock Mackinlay on September 15, 2008
Filed under: data visualization

The Junk Charts blog had a posting about the importance of making a data view “as simple as possible but no simpler”, which used a great example from Professor Gelman’s recent book “Red State, Blue State, Rich State, Poor State”. His scatter view does clearly show the interaction of social and economic views. It is also relatively easy to see the social clustering. However, it is harder to see the economic cluster. I think you can add more to Gelman's data view to tell his story more effectively.

The following data view includes Gelman's scatter comparison of social and economic issues. It also contains two additional views integrated with the scatter. The social view on the right clearly shows the clustering that differentiates the red and blue states, with the battleground states between. In contrast, the economic view at the top shows a different clustering based on the economic status of the voters. In this case, adding more makes it simpler to tell the data story. (click here to download the packaged workbook)

Another way to add more to this data view is to back it with the raw data so that I could add to the story by creating new views. In particular, this view causes me to wonder what would happen if there is a shift in the relative importance of social and economic issues. Are there red and blue states that might turn into battleground states because they contain a large percentage of poor voters?


Going the Distance: Maps, Calculations, and the Summer Olympics

Posted by Raif Majeed on September 5, 2008

Now that the Olympics are done and the results are in, it's time to look at the data. Using Tableau maps and some creative exporting, I was able to ask new questions about who won and why.

This data intrigued me for a couple of reasons. First of all, I'm a sports fan. Second, I was inspired by the New York Times visualization of Olympic medal counts. (And by the way, they recently showed a screenshot of a medal treemap from ManyEyes as well.)

It's not easy to find a complete, historical, up-to-date, simply-formatted Olympics data set. Thanks to the work and guidance of Ross Bunker, one of the developers here, I was able to get something workable. Here I'll be looking at country-by-country medal counts for modern Olympic summer games.

First, here's a Tableau map showing how the various countries did in Beijing. The size of each pie represents the total medal count; the size of each pie slice represents gold, silver, and bronze medals respectively. As you probably heard, the US took home the most total medals, but China dominated the gold medal tally, and this certainly shows up here.

Geographic View by Medaling Country and Year

The overall geographic distribution of medaling countries is quite remarkable as well. I put the year on the Pages shelf, so if you download the packaged workbook you can flip through the years to see how the geographic distribution of medalists changes over time.

When I looked through that, I was particularly surprised by America's domination of the 1904 summer games -- so I wondered if there was some way to examine rankings by year and pick out the lopsided ones. After some more consultation with Ross, I was able to construct a table showing the top (N) countries by year. Here's a snippet:

The games that stood out as lopsided were the early ones -- when it wasn't so easy or compelling for athletes to travel to the Olympics, and the host country typically cleaned up -- and the ones boycotted by the US (Moscow, 1980) and the Soviet Union (Los Angeles, 1984).

Now this is where it got interesting. I was lamenting to Ross that we could not use auto-generated latitude and longitude in Tableau calculations, and he told me that, actually, you can do that. First, you generate a very basic map and put all the dimensions and measures of interest on the Level of Detail shelf. Then, you export data using one of the File => Export options and connect to the resulting data source.

In the packaged workbook, you'll see two "(Source)" maps that I exported data from. Now, by connecting to the exported data, I was able to compute the approximate distance they traveled by digging out some old spherical-trigonometry formulas. If you edit the [Distance (miles)] calculated field you'll see how I did it.

What's the distribution of distances traveled by medaling teams? Here it is, binned into 500-mile increments.

The fact that there are a handful of distinctive peaks is interesting at first, but after looking at individual underlying data I think it's mostly an artifact of the uneven distribution of Earth's population.

Another question: What's the joint distribution of distances traveled by teams and the medals they were awarded?

Here, each dot represents a medal type, country, and year -- for instance, the number of silver medals won by the Soviet Union in 1972 (Munich) is a single data point. We can see those distinct clumps again -- which I've annotated in general terms at the top. It's a mixed picture, but broadly speaking it seems that teams that travel less win more. In particular there is some advantage to being the home team, as one might expect, and as China showed this year. Now, is the advantage because more athletes will travel when the distances are shorter, or because they're better rested or more familiar with the surroundings? I don't have the data to fully answer those questions yet but I plan to keep digging.

And, finally, let me note my newfound admiration for Barbara Kendall of New Zealand, the world's longest-traveling summer Olympic gold medalist. In 1992, she traveled 12,000+ miles from New Zealand to Barcelona and won the women's sailboard competition. Or put another way, she's the orange dot all the way on the right.

[NOTE: This post was updated to correct some unclear wording in the second paragraph.]