February 19, 2017
This week, we looked at the EU potato sector. Seriously! We're creating vizzes about potato production. The original website has things kind of all over the place. First there's this table:
Then there are a few donuts chart, most of them look more or less like this one:
They also included a few bars charts and a line chart. All in all, it's quite colorful.
What works well?
- Donut charts are sorted
- Tables are good for looking up specific values
- Line chart provides context by comparing to an index of 100 to make yearly change easier to understand
- Inconsistent colors
- Hard to identify the "story" in the data; The story is buried in the article.
- Pretty busy overall; too much going on
- Tables are terrible for finding insight in the data
February 15, 2017
In this example, I'm using the same Superstore Sales I've used in previous Workout Wednesdays. Here are the guidelines:
- Match my colors.
- The user should be able to choose the level of detail they want for the date.
- The date axis format should not change, irrespective of the date level chosen.
- The user should be able to pick from the list of dimensions shown.
- The dimensions should be sorted from upper left to lower right based on the sales in the most recent time period.
- Match my tooltips. Note that they change based on the options the user selects. Pay attention to the date formats in particular.
- The title should update dynamically based on the date level and dimension selected.
- The end of each line should be labeled to the right of the last point.
- There should be a little circle on the end of each line.
- Each section of the trellis should include a label for the value of the dimension for that section. E.g., California should be on the upper left when you selected quarters by state.
- The dimension labels should be centered in each section.
- There should be no gridlines, but the zero line should be included.
- Each row should should have a light divider between them.
- My final view is 900x700.
February 14, 2017
February 13, 2017
This meant spending my Sunday morning find a new viz and data set. A quick google search turned up this infographic from KarBel Multimedia:Maybe some love or Valentine's Day dataset for #makeovermonday week 7? We love data. It's our day too. @TriMyData @VizWizBI— Staticum (@staticum) February 11, 2017
What I like:
- Color choices that match the theme
- Simple title that tells me what I'm about to see
- Proper sourcing
- Nice description that include a question that explains what the viz is about
- Donut chart works well here as it's only 2 slices
- Clear labeling
What could be improved:
- Why use bubbles to compare the sizes of the spending? A bar chart would be way easier to read.
- There's very little context. Is this spending increasing or decreasing?
- While the color choices work for the theme, this sure is A LOT of pink.
For my viz, I wanted to create a mobile version that looks at the historical spending trends in two groups: significant others and everyone else. I don't lover my effort this week (pardon the pun), but there's only so much time in a day. Lastly, special thanks to Eva for the color palette.
February 9, 2017
Conceptually, I knew exactly what I needed to do:
- Create separate measures for males and females
- Create additional measures to make them percentages by dividing by the population estimate
- Create an LOD for the national average for males and females
- Create additional measure to make them percentages
- Make the male axis reversed
- Set all of the axes scales to be equivalent (Emma didn't do this, but I think the axes should be the same on each side of the center)
- Create the calcs for the rows and columns of the trellis
- Add a filter for local authority and add that to the title
- Throw is all together in a dashboard size 1000x800
February 7, 2017
Aggregated extracts are an undervalued and underused feature in Tableau.Week 6 of #MakeoverMonday allowed us to work with 105M Chicago taxi trips from an Exasol data source. This is fantastic, until you need to publish the viz to Tableau Public which has a 15M record limit. The way to work around the 15M limit is by creating an aggregated extract, for which Tableau has created a great quick start guide here. In the video below, I show you how I created an aggregated extract with the Chicago taxi data.
Keep in mind, though, that your data has to be aggregatable. For example, if you do cohort analysis, you likely won't be able to aggregate the data and maintain the cohorts.
Why aggregated extracts?
- Smaller extracts
- Better performance
- Only contains the necessary dimensions
- Makes extract refreshes faster
- Reduces resource burden on your Tableau Server
Steps for Creating an Aggregated Extract
- Hide unused dimensions
- Add extract filters (optional)
- Aggregate the data for the visible dimensions
- Create the extract
February 6, 2017
What works well?
- Using a line chart to portray a time series rarely is a bad choice
- Nice simple labeling of the axes
- Title tells me what I'm looking at
- Red line on the grey background works well
- The y-axis is truncated, but the chart maintains a nice 3x2 ratio so that the line trends aren't too distorted.
- Scale of the y-axis is a bit odd; I like nice rounded numbers that make the math easy to do in my head
- There is SO much more data to work with; why limit to only trips?
- Could use a more impactful title
- Could use more context
Overall, another fun week. Tonight I get to introduce this to a bunch of new Tableau users at the #MakeoverMonday Live session at Tableau HQ in London. Can't wait to see what they come up with!
February 1, 2017
Below is the visualisation that I created. If you're reading this on a phone, tap on the image for the interactive version. Some requirements to keep in mind that are intentionally designed to make this tougher and to make you learn:
- All of the elements must be floating on a dashboard sized 650x650.
- You cannot use the Player dimension anywhere in the view.
- Match my colors including the background
- Create the legend (HINT: It's not an image)
- Match the tooltip (Note the stats that are displayed in the tooltip. This will be a bit tricky. Essentially you need to count the number of players that are contained within each band.)
- The viz should update based on the stat selected. The user should be able to choose between: Attempts, Completions, Interceptions, Touchdowns, and Yards
- The title should update dynamically based on the stat the user selects.
- Optional: Use Montserrat font (you can download it from Google fonts)
January 30, 2017
What works well?
- Good to add a note about rounding
- Citing the data source
- A clearer title that makes the message more evident
- Countries should be sorted in descending order
- Labels should include the %
- Pie chart is a bad choice for this many categories
- Too many colors
- Chart titles are confusing (to me at least)
January 26, 2017
Inspired by the visualisation by Harry Enten that I highlighted today on my sister site DataVizDoneRight, I decide to look at the New Zealand tourism data again and see if I could build a similar view. After all, no data visualisation is ever “complete”. I really like how this turned out (and thank you to Eva Murray for feedback).
I incorporated a legend on the upper right to make the bars easier to interpret. Basically the grey bar shows the 25th to 75th percentile of all of the regions and the red dot indicates the median of all regions. I’ve removed the total region from the view.
January 25, 2017
Nice challenge from Emma this week! She’s a massive NFL fan and since the Super Bowl is upon us, she decide to challenge us to create a common baseline chart that shows the passing yards for QBs in the NFL over the course of their careers. Go to her blog for the full challenge details.
First requirement was to filter to QBs that had played at least 3 seasons and had at least 2000 total passing yards. I did this by adding a data source filter. The benefit of doing this is that my Player list will now only include those that meet the criteria and I won’t need filters elsewhere.
Next, I created a LOD calc to get the first year for each QB.
I built upon that calculation with this calculation that gives me the number of seasons played per QB. This goes onto the Columns shelf.
The cumulative passing yards is merely a running total table calc set at the Year level. This goes on the Rows shelf.
I put Player on the detail shelf to get a line per QB. I also put Year and Yds on the Detail shelf since I need those for the tooltip.
Next was a parameter to pick a QB and use that to highlight the QB chosen. I then created a simple calculation that check the Player again the parameter and put that on the color shelf.
Last was the dot on the end of each line. To do that, I created a calculation that checks if it’s the end of the line and the player selected and, if so, return the cumulative passing yards. Since this is a nested table calc, it’s important to set both table calcs to compute using Year.
Some tidying up, adding the footnotes and I was done. I decided to float all elements on the dashboard to ensure they would render exactly as I wanted them to. Another fun week of learning something new! Thanks Emma!!
January 24, 2017
This week’s Makeover Monday data was too much fun to not continue to play with. I’ve kind of had a crush on barcode charts/strip plots since Makeover Monday week 44 last year when I created a barcode chart of Scotland deprivation.
Given how this week’s data needed to be viewed at the month, region, visitor type level in order to represent the index properly, I thought I’d give a barcode chart a try. Why do I think it works well in this case?
- By color-coding the overall index red, I can clearly see how it compares to all other regions.
- A barcode chart is great for showing distributions.
- The reference line at zero let’s me see how many regions are above and below the 2008 average.
- Having a row for each month allows me to see which months were more above the average than others, particularly within a year.
- This helps me see the big picture (spending has increased over time) while still giving me all of the details of all regions.
What do you think? Does it communicate well for you? Click on the image for the interactive version.
Tableau 10.2 is bringing us a new date parse feature. I had two perfect uses cases for this to give it a test. The first is file of WhatsApp messages that requires both splitting and a dateparse. Previously this had to be done either in Alteryx or via a split, then a complicated calculation.
The second example is the data set used in Makeover Monday week 3. If I had the dateparse feature when I created the Tableau extract, I wouldn’t have messed up the data for everyone.
No workbook to accompany the video this week. This short video itself should give you a good idea for how dateparse works.
January 23, 2017
- There was a region named “Total (all TLAs)” that represented the total but was mixed in with all of the other regions.
- The data was an index, which is calculated as a weighted number for each region, month, and visitor type.
- When using indexes in the dataset, using an average aggregation is appropriate as long as you only use it at the individual region, month, and visitor type level. You can’t use an average of the average to represent the total.
I saw a few people make the mistake of using an average of the average very early on (I won’t shame them publicly), so I thought it would be appropriate to explain averages of averages, why they don’t calculate “accurately", and how people should be using them.
I was looking at an article on Visual Capitalist last night and saw another story that caught my eye. It was a connected scatterplot of life expectancy vs. health care expenditure for OECD countries. Everything on it is well documented including the data source. So off I went to get the data for Life Expectancy and Health Care Expenditure from the World Bank. I wanted to rebuild this chart in Tableau.
One interesting note is that the original visualisation had data back to 1970, yet that data is nowhere to be found on the World Bank website nor is it documented where it came from. That’s not very good. I limited my re-creation to the data I knew was accurate, 1995-2013.
This didn’t take too awfully long to create in Tableau, with most of the time being spent fiddling with the country labels. I know they overlap the lines in a lot of places, but I think it still works. When you click on a line, you’ll see drop lines that reveal the values for that point and also highlight the whole line for that country.
As always, rebuilding a chart I like has been a good learning experience. This was the first time I used drop lines and it was fun figuring out how to get only certain points labeled and colouring everything just right.
Click on the image for the interactive version.
Already four weeks into another fun year of Makeover Monday. As it’s an even numbered week, it’s Eva’s week to pick the topic. I’m really enjoying her helping out with picking topics because it allows me to participate like everyone else. I don’t see anything ahead of time and have to read the article, interpret the data and build a viz all at once. When I pick the topics myself, I tend to think weeks ahead about what I want to create.
This week, Eva chose two charts that are basically the same. There’s one for international tourism spend and one for domestic. Here’s the international spend chart:
What works well?
- Title and subtitle make it easy to know what I’m viewing
- Source is clearly documented
- Colors are distinct enough that it’s clear we’re supposed to look at them individually
- Legend is out of the way
- Axes are clearly labeled
- Minimal gridlines that aren’t distracting
- Removing the vertical axis line
- Nice crisp font (Founders Grotesk)
What could be improved?
- Packed bars make it harder than necessary to follow a year across its months
- 100 is the baseline (see the subtitle), so why isn’t the chart the difference from the baseline?
- Overall too cluttered
- Are there more years that could be used for comparison?
- What was spending like before 2008? How do 2013-15 compare?
- Are we trying to understand the change within each month or the change across the years?
I must admit that I got sucked in by all of the detail Eva provided in the data set. I started by creating a view of the change in spending by year compared to the 2008 average. After all, this is the baseline, so we should be comparing to that. Anything above 100 is an increase compared to 2008; anything below 100 is a decline versus 2008. I wonder how many people are going to catch that subtlety in the data. I understood it after reading the notes that accompanied the chart.
This is what I came up with first. It show the change versus 2008 for each region. Click on the image for the interactive version.
But was I really doing a makeover of the original? No, I wasn’t. The original was look at the country total, so back to the drawing board I went. I really liked the look of the lines I had created so it wasn’t like I was completely starting over. What I wanted to show was:
- How did the overall spending change compared to 2008 for each visitor type?
- What was the change by year within each season? This would help me understand any seasons where tourism spending has decreased.
Overall, a really fun data set to play with and a lesson learned to not get sucked into the data too quickly. I need to think more holistically, think about the story I want to tell, search for idea, do some sketching, and move away from Tableau when I start. Basically, practice what I preach.
January 20, 2017
Sasha Pasulka has been a good friend of mine for many years and is moving to London from the US soon in her new role with Tableau. Like anyone else that’s moving to a new country, she finds the entire process is ridiculously overwhelming. Trying to find apartments from thousands of miles away, not knowing anything about neighbourhoods, can be an incredibly daunting task. To help her, I decide to build a viz in Tableau.
I started by using the London Crimes web data connector from Tableau Junkie, only to realise that it’s somehow not returning all of the data. It looks like it returns the data via a radius versus for an entire postcode.
No worries though. Instead I went to data.police.uk and downloaded all crimes from the Metropolitan Police Service. This returned a separate CSV for each month and it also wasn’t limited to just the London area. On the London Datastore I was able to find a list of all LSOAs in the London area. Great! All I needed to do was union all of the CSVs then join them to the London LSOAs. I love that I can do all of this straight inside Tableau now.
From there, it was a matter of building a simple visualisation that allows Sasha to pick boroughs and see the crimes in those areas. Note that I set the map to only display when there are 3 or fewer boroughs selected. did this because the map was simply too slow to draw the dots. Hopefully she likes it and makes it easier for her to settle in.
January 18, 2017
Last week on my Data Viz Done Right site, I wrote about a great small multiples visualisation created by Matt Stiles that shows U.S. unemployment compared to the national average for every State. I recreated Matt’s work in Tableau, and your challenge for this week is to do the same. Personally, I find trying to rebuild visualisations a great way to learn.
- My viz is 875x2150. Your’s doesn’t have to be this size, but I thought I’d provide it for guidance.
- I’m using the Source Sans Pro font, which you can download from Google Fonts. This is the font that Matt used in his version.
- The years should be displayed every 10 years.
- The axis line on for the year should be more distinct than the gridlines.
- The ends of each line should be colour-coded by whether it was an increase or decrease compared to the national average.
- You will need to calculate the national average. The national average needs to include the District of Columbia, but D.C. should not have its own chart.
- Values above the national average should start with a + and and below should start with a -
- The national average is the line you see at 0%.
- This is NOT a trellis chart, but if you think you can make it work as a trellis chart, go for it!
- The area above zero should be shaded. The hex code to use is #F7E6E2 and it should be shaded from 0- to +10%.
- Pay attention to the gaps between each State. I like how this gives it some breathing room.
This will be a very tedious exercise. To provide some context, this took me 2-3 hours to create. Don’t get discouraged and don’t feel like you have to do it all in one sitting. Basically, try to make yours look identical to mine.
Post an image on Twitter when you’re done and hashtag it with #WorkoutWednesday and please tag me so I see it. You can also comment below with a link to your workbook or with any questions you have. Good luck!