The Challenge from FlowingData

The 25 February posting from FlowingData issues a challenge to improve a chart from the Economist. I find that the Economist usually does pretty solid work and so improving their output is by no means easy. Regardless, I figured I would further delay starting my Friday work by spending 15–20 minutes on an attempt to improve the Economist’s work.

Original from the Economist vs. My Attempt

challenge-original

challenge-redux

I did not find a whole lot of flaws in their chart. Most unnecessary bits have been eliminated and we have a clean line chart. The semi-advantage allowed us all is that we do not have to follow the branding guidelines of the Economist. Initially, I attempted to do a straight grey-scale chart but found the overlapping lines could be a bit confusing. And so I added a hint of blue and then tinted lines when they overlapped to aid the reader in following each line.

I also eliminated the shaded Forecast area and replaced it with switching the solid lines of the historic data to a dashed line for forecast data. The exact shape of the lines may not be exact because I traced over the lines with the pen tool in Illustrator—but for these purposes that seemed reasonable to me.

The other ‘big’ change was more typographic in nature. I decided to highlight the countries and drop back the labels by making the latter grey.

Looking at the Haitian Earthquake

The BBC has posted an article addressing the causes for the horrible death toll in the Haitian earthquake last month. Charts and data-driven graphics supplement the text and provide a parallel, though not synchronous, visual story.

screenshot of BBC article

I applaud an intensive use of graphics, especially data-driven graphics, to better relate a story. Perhaps especially because not everybody can learn something simply by reading it. Many among us are instead visual learners, and by incorporating graphics into stories, be them online news articles, printed magazine articles, or interactive experiences, we can reach a larger audience and hopefully inform, impact, and influence said audience.

The graphics for the BBC article do some things well and some things not so well. Firstly, as a series, the graphics are varied well enough to not be overly repetitive. We have two sets of bar charts, three sets of area-of-circle charts (I presume), and what Nathan Yau at FlowingData called the everything chart. And if we look at the placement of the charts within the article (B for bar, A for area, and E for everything) we see A–B–E–A–B–A. The placement of the graphic types within the structure for the visual component of the article is sufficiently varied not to bore the audience.

Secondly, the graphics are well done through the restrained use of colour. Each graphic is composed of tints of grey and red. Grey is largely used as the base colour for the graphic while red or its tints accent the key elements of the visual argument. For example, when comparing the number of people dead among the affected people, a single square is coloured red. In the larger areas of grey for China and Italy, that single square or single person, while not lost, is not necessarily readily important. Instead, it serves as a link across the countries for when people look at Haiti and that red square stands out among fourteen other grey squares.

On a few other fronts, however, the graphics stumble where, if a bit more attention had been paid, they could have really strode to the front of the pack.

From the perspective of representing data, I have three qualms with the graphics. The first is somewhat minor—for it may have well been intentional. Although one of the underlying points of the article is the sheer difference in scale of the impact, the Italian earthquake is often difficult to visually compare in detail next to the Chinese and Haitian earthquakes. Why? Because the Italian numbers are visually insignificant. Could this have been resolved in a different fashion? Yes. However, as aforementioned that could have been an intentional design decision and I only point it out as something worth considering.

Secondly, and more importantly, I have concerns about the area-of-the-circle charts. Chief among those concerns is that nowhere is it specified that we are looking at area instead of, as is sometimes the case, the radius of the circle. This error is significant and I shall illustrate below. If we take, for the sake of example, a circle of radius 5 units and compare it to a circle of radius 10 units, we have a difference of 5 radius units. Circle 2 is, by one measure, twice the size of Circle 1.

And while some compare radii of circles, others instead compare areas of circle—as I assume but cannot be certain of in this instance. However, if we look at 5 units and 10 units as the radius for the areas of Circles 1 and 2, we arrive at a difference of four times the size.

diagrammatic explanation of radius vs. area

This is not a problem specific to this article—although it could have been partially solved by stating area comparison or providing a scale. Unfortunately, this problem appears with an unsettling degree of frequency. But the problem is also compounded because people are not the best judges of area. It is far easier for an individual to compare two bars and see one as twice the size than it is to compare the area of two circle and see the same difference.

The problem of comparing length to length times width for a datapoint has the fair counterpart of visual repetition aforementioned. One of the three circle charts could easily be replaced by a bar chart. The two others could also be replaced, albeit with a little more work. However, the article would then be visually boring for it would be replete with bar charts.

And so the problem of comparing areas is one to be handled carefully. This piece has some potentially serious problems in comparing data. However, the quick and easy fixes would make the piece less visually interesting and thus, perhaps, cause the reader to lose interest. And with interest lost, the reader clicks away and the article fails to make an impact. On a case-by-case basis, the designer must often make the decision between fidelity to data versus capturing the reader’s attention. And here, I think the pendulum swung just a bit too far to capture the reader’s attention.

My third major point of contention, however, concerns the data itself and an incongruity in the graphics. Understandably, the earthquake in Haiti is a recent event. And indeed, the rebuilding and thus the cost is a current and ongoing event. Therefore, nobody should expect any institution to have anything but cost estimates. The final graphic makes note of the fact that we have no hard figures and that all figures are estimates.

Yet, the graphic provides two visual estimates hinting at two substantially different figures. The straight cost is represented on a bar chart that states “estimated at several billion” but visually depicts $40 billion. The cost as relative to GDP includes an asterisk for a footnote that shows the cost as but $2 billion.

Using the estimates for an early comparison of the financial cost of the earthquake is perfectly valid so long as the numbers are noted as estimates—as they are here. However, one should use the same estimate consistently across the piece. Because here, the use of different estimates can be used to imply that the straight cost is nearly 15 times more than that of Italy’s cost. But when using the cost to compare the cost relative to the economy, Haiti’s straight cost is $500 million less than that of Italy’s cost. If anything, either the bar chart should have had no bar for Haiti, or made use of the dashed red line at the $2 billion line.

And so while I certainly have reservations about the graphics as a whole, I support the decision to use data-driven graphics to support the story and the argument.

And How Should I Begin?

I have measured out my life with coffee spoons…
—T.S. Eliot, The Love Song of J. Alfred Prufrock

Modern life in the Western world revolves around data that then becomes misinformation, disinformation, or, more rarely, information. In theory, we use this information to inform our decision-making process and then live fitter, happier lives. (Please hold all comments about how well the theory of Communism is working in the Soviet Union until the end.) However, for most of us, gleaning any kind of information from row after row after column after column of data is too laborious and too time consuming to be worth our time. And so most of us have turned to an emerging field that is known by many names but is perhaps best described as data visualisation.

Data can come in many different forms. It can be the gross domestic product of the United States. It can be the preferred term for carbonated beverages across the state of Pennsylvania. (Although I think we can all agree it is soda, not pop.) Data can be the route of Philadelphia’s regional rail lines. (And how late they happen to be on any given day.) Data can even be the price paid for a cup of tea in a bookstore.

And with all these different forms, one can have perhaps an even greater number of forms in which that data is visualised—either alone or in comparison to other datapoints. One can look at the GDP of the US as part of a bar chart against the GDPs of China and India. One can look at a map of Pennsylvania and see the barbaric lexicon near Pittsburgh in their preference for pop. One can look at a non-geographic map of SEPTA’s regional rail lines and all the stops of the Main Line. (And the lines coloured not by their destination but their on-time-ness.) One can even see the price of a cup of tea printed on a piece of paper in an itemised list. And each of those forms and the many, many others has inherent benefits and drawbacks. Each can be used appropriately. Or not. Some look good. Others not.

An interesting dividing line in this nascent field concerns the efficiency of any visualisation in communicating the data. Some statisticians argue for stripped down charts and tables with relatively little care put towards the aesthetics of the visualisation. On the other side, some designers care more for what many non-designers call the ‘prettification’ of data. That is to say, placing care towards the presentation and legibility of the visualisation perhaps at the expense of clearly communicating all the data. So where do I stand? Well damn it, Jim, I’m a designer, not a statistician. While I do believe in maintaining a level of fidelity to the data, that data must still be clearly communicated to reach the designated audience. The piece in question must still grab the attention of the audience enough to get them to delve into the layers of data.

The ultimate goal of this blog is to examine data visualisations, information graphics, charts, whatevers and break them down to see what may have been done well and not so well—all from my aforenoted perspective. Naturally, some may disagree and I wholly encourage dissent from the party line. My party line. If you find something interesting, please send it my way.

Modern life in the Western world revolves around data. Data that we create each and every day. We are aware of some of the data we create while we remain ignorant of some other data. We create it through every click of the mouse. Every swipe of a card. Every change of a channel. Every mobile phone dialed. Each and every day our lives are broken down into rows and columns. We may no longer measure our lives in coffee spoons, but we measure them nonetheless.