It’s ok to use word clouds if your goal is to encourage reading of a large set of otherwise unrelated words that are connected to one or two interesting values (and word count in a text doesn’t qualify as interesting).
This I tweeted yesterday and now I feel that if I encourage the (dangerous) use of word clouds, I have to explain this exception in a little more detail. Why is it sometimes ok to use a widely rejected visualization method, and most times not?
Using open source tools it is now super easy to make your own map tiles, and with a little extra work you can render them in whatever map projection you want. No more excuses to use Mercator! For example, here is a map we published today at The Upshot. It shows where prime-age women are working more or less then average, and includes data from county-level in the overview map down to every census tract once you zoom in. And all is nicely projected in Albers Equal-Area Conic, a projection widely adopted as standard for U.S. maps.
here’s how you do it
Never trust a statistic that you
haven’t visualized yourself.
It’s election time in Germany and, as usual, there are tons of opinion polls telling us who is going to win the election anyway. It is debatable whether or not pre-election polls are healthy for our democracy in general, but at least everybody agrees that the polls should be kind of neutral. And if they are not, the institutes publishing the polls should be blamed publicly.
But how do we know if an institute publishes ‘biased’ polls? You guessed it: with data. More precisely: with data and the unique power of data visualization.
Probably one of the most useful things about Cynthia Brewers color advice for cartography are the multihue color schemes. This post explains how you can create your own, using two new features of chroma.js: Bezier interpolation and automatic lightness correction.
This post is written to welcome dataset
, a new library to simplify working with databases in Python.
Let’s face it. Relational databases, such as MySQL, SQLite and PostgreSQL, are pretty cool – but nobody actually uses them. At least not in the day-to-day work with small to medium scale datasets. But why is that? Why do we see an awful lot of data stored in static files in CSV or JSON format, even though
- they are hard to query (you need to write a custom script every time)
- they are messy, as they cannot store meta data such as data types
- it is a pain to update them incrementally, say if some record has changed
click to read the answer :)
Currently I’m taking the wonderful course Computing for Data Analysis on Coursera, and in this weeks lecture I learned about how to define custom color palettes in R.
You can do this using the
colorRampPalette() function that comes with the grDevices package. Calling this function will return another function that you can call to generate the color palette.
If I was asked for the golden rule of information visualization, it would be:
“Show the most important thing first!”
Not second or third, but first! And what is the most important thing to show about the outcome of an election? Who actually won.
In political systems like Germany’s, where we have no party getting anywhere near 50% of the vote, the usual one-bar-per-party bar charts totally fail to answer this most important question.
For example, in the following chart we can see the number of seats won by different political parties – but this does not tell us who won the election.
While working on the soon-to-be-released map widget for Piwik (heck, it’s been over two years since the first sketches!) I implemented two map symbol clustering algorithms into Kartograph.js. Last year I wrote about why this is a good idea, and now I turned that advice into re-usable code.
In this post I want to share my findings after experimenting with different clustering techniques.
Icons are widely used in infographics such as maps and pictographs. So as a visualization designer, you’ll get to the point where you must choose which icons or pictograms to use. But please, choose wisely.
The reason I got to this topic is a recent post by Naomi Robbins about two opinions on the usefulness of pictographs. She reminded my of a critical article by Stephen Few, who stated that unit charts (another term for pictographs) are for kids, but not for serious information displays. My biggest complaint about his article is that he picked some of the worst imaginable examples to back up his arguments.
read how to do it better..
A few weeks ago, while I was driving several hours towards our camping vacation, I suddenly noticed this beautiful piece of data visualization right in front of me. Actually, I found it that beautiful that I had to remake it in Illustrator:
I was completely stunned by the clean and simple layout of this gauge chart. It shows everything I, as the driver, need to know such as: How fast am I driving at the moment, how far have I’ve been driving at all, when is it time to get a new car.
But then I realized that this tiny chart, despite its useful, intelligent design, violates some of the common rules of data visualization, so I thought it’s a good idea to write about it.