Many hate pie charts. Others love them. I think they’re useful but have limitations. Most of these are just feelings though, maybe accompanied by an Edward Tufte quote. We need facts. Robert Kosara and Drew Skau provide some in their recent studies on how we read pie charts. There appears to be a good chance people don’t read the things correctly.

But I found Kosara’s follow-up more interesting. He dug up a paper that he and his student Caroline Ziemkiewicz wrote a few years ago on square pie charts. Instead of filling a circle to represent proportion, the square pie chart fills a — wait for it — square.
Read More

As an introduction to a series on gun deaths in America, FiveThirtyEight uses a straightforward grid view to show the breakdowns. Each square represents a single gun death, and as you click through, the squares are colored to show various groups. For example, the above represents gun deaths from homicide in blue, about half of which are young men and two-thirds of that subgroup are black.

Sometimes it’s more useful to break the data down to its elements.

Ben Orlin of Math With Bad Drawings explains the pitfalls of using summary statistics — mean, median, and mode — to make decisions in life. Aggregates like these are meant as wideout overviews. Look deeper for details.

Road trips are fun, but it can be hard to enjoy yourself when you end up in a place during its hottest or coldest day of the year. Wouldn’t it be nice to travel across the country and have nice weather every single day? This road trip is for you.
Read More

R has found its way into a good number of news groups who do data journalism. Andrew Flowers for FiveThirtyEight talks about how they use the statistical computing language throughout their workflow.

R is used in every step of the data journalism process: for cleaning and processing data, for exploratory graphing and statistical analysis, for models deploying in real time as and to create publishable data visualizations. We write R code to underpin several of our popular interactives, as well, like the Facebook Primary and our historical Elo ratings of NBA and NFL teams. Heck, we’ve even styled a custom ggplot2 theme. We even use R code on long-term investigative projects.

Clive Thompson for Smithsonian Magazine gives a quick history lesson on infographics.

[D]ata visualization was rare because data was rare. That began to change rapidly in the early 19th century, because countries began to collect—and publish—reams of information about their weather, economic activity and population. “For the first time, you could deal with important social issues with hard facts, if you could find a way to analyze it,” says Michael Friendly, a professor of psychology at York University who studies the history of data visualization. “The age of data really began.”

Thompson uses “infographic” but really means “data visualization” most of the time, but still a good overview.

And while we’re on the topic of old visualization stuff, you should also check out Scott Klein’s newsletter, Above Chart. The history provides fine context for where visualization is at now.

Last year the New York Times interviewed Justin Bieber, Diplo, and Skrillex about how they put together their song Where Are Ü Now. NYT coupled the video with data visualization elements that helped you understand what the artists talked about. Pretty great.

Now here’s what happens when you switch out the original song and insert the Seinfeld theme song.

what if Bieber diplo and skrilex created the seinfeld themehttps://t.co/BUTOrNDwGQ

— Seinfeld Current Day (@Seinfeld2000) July 4, 2016

Also pretty great.

Drought continues to trudge along. My grass is just about dead, save a few hearty patches clinging on to the last few drops in the soil. Sad state of affairs it is. Drought is not static though. The boundaries move and the levels change, which is what John Nelson mapped in an overlay of five years of drought in the United States, based on data from the Drought Monitor.

We’ve seen this as small multiples and animated maps, but I like how this static boundary version gifts a sense of shift without actually moving.

Grab the aggregated data here.

Musicmap is an attempt to show the history of music over time and how it came to be what it is today.

Musicmap attempts to provide the ultimate genealogy of popular music genres, including their relations and history. It is the result of more than seven years of research with over 200 listed sources and cross examination of many other visual genealogies. Its aim is to focus on the delicate balance between comprehensibility, accuracy and accessibility.

Be sure to zoom in for the details of how genres and sub-genres are connected. Click on any group for samples, playlists, and written history.

Glenn McDonald attempts to graph the musical space in its entirety on a two-dimensional scale. He calls it Every Noise at Once.

This is an ongoing attempt at an algorithmically-generated, readability-adjusted scatter-plot of the musical genre-space, based on data tracked and analyzed for 1491 genres by Spotify. The calibration is fuzzy, but in general down is more organic, up is more mechanical and electric; left is denser and more atmospheric, right is spikier and bouncier.

Click on the genres for music samples, if you are like me and are not sure what rap metalcore or ghettotech sounds like. [Thanks, Namir]

FiveThirtyEight published their election forecast tracker this week, and it’s a beaut. It starts with the standard state map and most importantly the probability of each candidate winning the presidency. But after that, you can look into much detail on a state-by-state basis.

They currently give Hillary Clinton a 79 percent chance of winning and Donald Trump a 21 percent chance. I think many interpret this as Clinton is practically a lock, but it’s actually far from it. That 21 percent is freakin’ high.

As much as I want to forget, let’s remember that the Cleveland Cavaliers only had an 11 percent chance of winning the title, and I think we know what happened there.

In any case, check out the tracker. I like it. And find more details on where the numbers come from in the user’s guide.

Meredith Reba, Femke Reitsma and Karen C. Seto compiled a dataset of urban settlements between 3700 BC and AD 2000. It’s the first of its kind, and while not comprehensive, it does provide a view into growth around the world. Max Galka put together the straightforward map above to display the data.

Best part is you can download the data and have a go yourself. [via kottke]

I typically don’t care much about code releases, but every interactive chart I make these days uses Mike Bostock’s JavaScript library D3.js. It get more fun the more you use it. And it just got better with a 4.0 release.

D3 4.0 is modular. Instead of one library, D3 is now many small libraries that are designed to work together. You can pick and choose which parts to use as you see fit. Each library is maintained in its own repository, allowing decentralized ownership and independent release cycles. The default bundle combines about thirty of these microlibraries.

More importantly:

Small files are nice, but modularity is also about making D3 more fun. Microlibraries are easier to understand, develop and test. They make it easier for new people to get involved and contribute. They reduce the distinction between a “core module” and a “plugin”, and increase the pace of development in D3 features.

Nice.

Hollywood has been talking gender equality in the movies more than usual lately, so Hanah Andersen and Matt Daniels for Polygraph looked into the matter from a data perspective.

We didn’t set out trying to prove anything, but rather compile real data. We framed it as a census rather than a study. So we Googled our way to 8,000 screenplays and matched each character’s lines to an actor. From there, we compiled the number of words spoken by male and female characters across roughly 2,000 films, arguably the largest undertaking of script analysis, ever.

We have another data point on the way, so it might suddenly go silent around these parts soon. There was a sursprising amount of downtime with the first data point, with naps and feeding and such, so I was able to keep going. But I expect my hands to be more full this time, because, well, two data points.