<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: What&#8217;s Wrong With this Financial Bubble Chart?</title>
	<atom:link href="http://flowingdata.com/2009/02/26/whats-wrong-with-this-financial-bubble-chart/feed/" rel="self" type="application/rss+xml" />
	<link>http://flowingdata.com/2009/02/26/whats-wrong-with-this-financial-bubble-chart/</link>
	<description>Strength in Numbers</description>
	<lastBuildDate>Sun, 12 Feb 2012 04:57:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Cartographer</title>
		<link>http://flowingdata.com/2009/02/26/whats-wrong-with-this-financial-bubble-chart/#comment-24759</link>
		<dc:creator>Cartographer</dc:creator>
		<pubDate>Fri, 06 Mar 2009 15:51:03 +0000</pubDate>
		<guid isPermaLink="false">http://flowingdata.com/?p=1386#comment-24759</guid>
		<description>RE: Size of a graduated point symbol

Using graduated point symbols to symbolize a range of quantitative values is not as straight forward as one might think.  I offer two reasons.  

First, point symbols cover areas of page or screen space while the underlying data are usually referenced to a linear scale (Tufte, 1983, commented on this when he introduced his &quot;lie factor&quot;).  Such a mismatch does, indeed, require a PI-based conversion so that symbol areas will increase linearly with data (and not so that symbol radii or diameters increase linearly with data).

Second, but more complicated, cognitive psychologists have found that humans tend to systematically underestimate the sizes of point symbols when they read them.  That finding lead Flannery (1971) to develop a method for adjusting point symbol sizes to compensate for this observed human tendancy.  Today, we call it the Flannery Compensation Method.

All that said, the graphic at hand is too darn big to allow readers to make any effective comparisons.  Chart junk - plain and simple.

References cited
Flannery JJ (1971) &quot;The relative effectiveness of some common graduated point symbols in the presentation of quantitative data&quot;.  The Canadian Geographer 8(2): 96-109.

Tufte ER (1983) &quot;The Visual Display of Quantitative Information&quot;  Graphics Press; Cheshire, CN.</description>
		<content:encoded><![CDATA[<p>RE: Size of a graduated point symbol</p>
<p>Using graduated point symbols to symbolize a range of quantitative values is not as straight forward as one might think.  I offer two reasons.  </p>
<p>First, point symbols cover areas of page or screen space while the underlying data are usually referenced to a linear scale (Tufte, 1983, commented on this when he introduced his &#8220;lie factor&#8221;).  Such a mismatch does, indeed, require a PI-based conversion so that symbol areas will increase linearly with data (and not so that symbol radii or diameters increase linearly with data).</p>
<p>Second, but more complicated, cognitive psychologists have found that humans tend to systematically underestimate the sizes of point symbols when they read them.  That finding lead Flannery (1971) to develop a method for adjusting point symbol sizes to compensate for this observed human tendancy.  Today, we call it the Flannery Compensation Method.</p>
<p>All that said, the graphic at hand is too darn big to allow readers to make any effective comparisons.  Chart junk &#8211; plain and simple.</p>
<p>References cited<br />
Flannery JJ (1971) &#8220;The relative effectiveness of some common graduated point symbols in the presentation of quantitative data&#8221;.  The Canadian Geographer 8(2): 96-109.</p>
<p>Tufte ER (1983) &#8220;The Visual Display of Quantitative Information&#8221;  Graphics Press; Cheshire, CN.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jess</title>
		<link>http://flowingdata.com/2009/02/26/whats-wrong-with-this-financial-bubble-chart/#comment-24586</link>
		<dc:creator>Jess</dc:creator>
		<pubDate>Mon, 02 Mar 2009 04:06:12 +0000</pubDate>
		<guid isPermaLink="false">http://flowingdata.com/?p=1386#comment-24586</guid>
		<description>@Keane, a pie chart would be too efficient and save space, where as a really tall image looks like there was more work involved.</description>
		<content:encoded><![CDATA[<p>@Keane, a pie chart would be too efficient and save space, where as a really tall image looks like there was more work involved.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Breaking Down the Budget &#171; Information Design at Penn</title>
		<link>http://flowingdata.com/2009/02/26/whats-wrong-with-this-financial-bubble-chart/#comment-24482</link>
		<dc:creator>Breaking Down the Budget &#171; Information Design at Penn</dc:creator>
		<pubDate>Fri, 27 Feb 2009 17:55:32 +0000</pubDate>
		<guid isPermaLink="false">http://flowingdata.com/?p=1386#comment-24482</guid>
		<description>[...] graphic, I was immediately reminded of an article about a similar graphic that I read yesterday on  Flowing Data. Nathan, the author of this article, asked Flowing Data readers to find flaws in this infographic. [...]</description>
		<content:encoded><![CDATA[<p>[...] graphic, I was immediately reminded of an article about a similar graphic that I read yesterday on  Flowing Data. Nathan, the author of this article, asked Flowing Data readers to find flaws in this infographic. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keane</title>
		<link>http://flowingdata.com/2009/02/26/whats-wrong-with-this-financial-bubble-chart/#comment-24402</link>
		<dc:creator>Keane</dc:creator>
		<pubDate>Fri, 27 Feb 2009 12:32:58 +0000</pubDate>
		<guid isPermaLink="false">http://flowingdata.com/?p=1386#comment-24402</guid>
		<description>The biggest flaw to me is the lack of comparison, why wasn&#039;t this done as a pie chart? The data represents percentages that make up a whole, with the remainder being profit.</description>
		<content:encoded><![CDATA[<p>The biggest flaw to me is the lack of comparison, why wasn&#8217;t this done as a pie chart? The data represents percentages that make up a whole, with the remainder being profit.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://flowingdata.com/2009/02/26/whats-wrong-with-this-financial-bubble-chart/#comment-24390</link>
		<dc:creator>John</dc:creator>
		<pubDate>Fri, 27 Feb 2009 02:09:05 +0000</pubDate>
		<guid isPermaLink="false">http://flowingdata.com/?p=1386#comment-24390</guid>
		<description>um...the percentages don&#039;t add up to 100%...someone give me a cookie</description>
		<content:encoded><![CDATA[<p>um&#8230;the percentages don&#8217;t add up to 100%&#8230;someone give me a cookie</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jess</title>
		<link>http://flowingdata.com/2009/02/26/whats-wrong-with-this-financial-bubble-chart/#comment-24388</link>
		<dc:creator>Jess</dc:creator>
		<pubDate>Thu, 26 Feb 2009 23:48:31 +0000</pubDate>
		<guid isPermaLink="false">http://flowingdata.com/?p=1386#comment-24388</guid>
		<description>lol, I think &#039;someone&#039; needs an &#039;internet&#039; &#039;hug&#039;.</description>
		<content:encoded><![CDATA[<p>lol, I think &#8216;someone&#8217; needs an &#8216;internet&#8217; &#8216;hug&#8217;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JR</title>
		<link>http://flowingdata.com/2009/02/26/whats-wrong-with-this-financial-bubble-chart/#comment-24387</link>
		<dc:creator>JR</dc:creator>
		<pubDate>Thu, 26 Feb 2009 23:27:16 +0000</pubDate>
		<guid isPermaLink="false">http://flowingdata.com/?p=1386#comment-24387</guid>
		<description>I could just picture that ******** making finger quotes in the air while saying &#039;colleague&#039;</description>
		<content:encoded><![CDATA[<p>I could just picture that ******** making finger quotes in the air while saying &#8216;colleague&#8217;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marty Alchin</title>
		<link>http://flowingdata.com/2009/02/26/whats-wrong-with-this-financial-bubble-chart/#comment-24384</link>
		<dc:creator>Marty Alchin</dc:creator>
		<pubDate>Thu, 26 Feb 2009 22:52:34 +0000</pubDate>
		<guid isPermaLink="false">http://flowingdata.com/?p=1386#comment-24384</guid>
		<description>The difference between a poor visualization and a typo isn&#039;t even one of how easily it can be fixed. It&#039;s about how easily it can be understood. Most typos and other spelling and grammar mistakes don&#039;t make text unintelligible. It&#039;s usually pretty easy to figure out what the intention was, without any loss of clarity. Sure, it looks a bit unprofessional, but the point still gets across.

A visualization like this one goes beyond that. Imagine an article written in two languages, alternating between them randomly. Those who know both languages, or how the writer thinks, would be able to interpret it just fine. But the rest of us would be left scratching our heads, at best. At worst, we might understand parts of it and *think* we understand other parts. It might seem just close enough to what we know that we think we get the point, but we&#039;re actually reading the wrong things into the text.

The purpose of both writing and data visualization is to convey information. If we don&#039;t do so in a way that conveys the information we intend, it&#039;s a failure. And personally, as author of not only a blog, but a book as well, I would most definitely want someone to call me out if I wrote something in a way that would cause this much confusion.</description>
		<content:encoded><![CDATA[<p>The difference between a poor visualization and a typo isn&#8217;t even one of how easily it can be fixed. It&#8217;s about how easily it can be understood. Most typos and other spelling and grammar mistakes don&#8217;t make text unintelligible. It&#8217;s usually pretty easy to figure out what the intention was, without any loss of clarity. Sure, it looks a bit unprofessional, but the point still gets across.</p>
<p>A visualization like this one goes beyond that. Imagine an article written in two languages, alternating between them randomly. Those who know both languages, or how the writer thinks, would be able to interpret it just fine. But the rest of us would be left scratching our heads, at best. At worst, we might understand parts of it and *think* we understand other parts. It might seem just close enough to what we know that we think we get the point, but we&#8217;re actually reading the wrong things into the text.</p>
<p>The purpose of both writing and data visualization is to convey information. If we don&#8217;t do so in a way that conveys the information we intend, it&#8217;s a failure. And personally, as author of not only a blog, but a book as well, I would most definitely want someone to call me out if I wrote something in a way that would cause this much confusion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathan Yau</title>
		<link>http://flowingdata.com/2009/02/26/whats-wrong-with-this-financial-bubble-chart/#comment-24383</link>
		<dc:creator>Nathan Yau</dc:creator>
		<pubDate>Thu, 26 Feb 2009 22:16:29 +0000</pubDate>
		<guid isPermaLink="false">http://flowingdata.com/?p=1386#comment-24383</guid>
		<description>I only posted this as a way to learn so that we can all improve, the creator of this graphic included.

@JR - Typos are one thing, and the fundamentals of data and infographics are another. Typos are simple mistakes that can be fixed easily while the above graphic did a poor job of representing the data and shows an incorrect interpretation. If this were a piece of art, then fine I wouldn&#039;t have been so critical, but this is an infographic that thousands of people saw and in turn, thousands probably made incorrect conclusions. That&#039;s a fact.

Like Jess said, this is the Internet, and we&#039;re all entitled to our opinions. Just like you are - who happened to post a comment here.</description>
		<content:encoded><![CDATA[<p>I only posted this as a way to learn so that we can all improve, the creator of this graphic included.</p>
<p>@JR &#8211; Typos are one thing, and the fundamentals of data and infographics are another. Typos are simple mistakes that can be fixed easily while the above graphic did a poor job of representing the data and shows an incorrect interpretation. If this were a piece of art, then fine I wouldn&#8217;t have been so critical, but this is an infographic that thousands of people saw and in turn, thousands probably made incorrect conclusions. That&#8217;s a fact.</p>
<p>Like Jess said, this is the Internet, and we&#8217;re all entitled to our opinions. Just like you are &#8211; who happened to post a comment here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ideas That Spread &#187; Blog Archive &#187; Infographics Galore</title>
		<link>http://flowingdata.com/2009/02/26/whats-wrong-with-this-financial-bubble-chart/#comment-24382</link>
		<dc:creator>Ideas That Spread &#187; Blog Archive &#187; Infographics Galore</dc:creator>
		<pubDate>Thu, 26 Feb 2009 22:12:21 +0000</pubDate>
		<guid isPermaLink="false">http://flowingdata.com/?p=1386#comment-24382</guid>
		<description>[...] abundance of graphical information out there is tremendous, especially trying to explain this credit crisis. If you haven&#8217;t seen [...]</description>
		<content:encoded><![CDATA[<p>[...] abundance of graphical information out there is tremendous, especially trying to explain this credit crisis. If you haven&#8217;t seen [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

