Ugh, I clicked a few of the earthquake examples (did a similar viz in the past) and saw that none of them was working.
Then looking at the curl responses one gets, "Due to the Federal government shutdown, usgs.gov and most associated web sites are unavailable. Only web sites necessary to protect lives and property will be maintained."
One can only wish they saw these and similar APIs as important infrastructure that needs to remain functional.
Otherwise -- this is very helpful! Thanks so much for assembling the collection.
When I need to make graphics for research talks, I usually turn to TikZ  since I currently make talks using latex-beamer. But I'm always impressed when I look at D3.js and I think it would be great to have a more reliable way to add animations, as well as putting interactive content on my website.
Given that LaTeX math is important to me, should I make a serious effort to learn D3.js (and one of the HTML slide deck packages) or stick with LaTeX? Note that figures usually can't be directly reused between talks and papers anyway, but a modest amount of tweaking is usually enough. Using HTML/D3.js instead of latex-beamer for talks would probably make reuse in talks more difficult.
Does anyone know if there is a good D3 example of something like noflo ? Most of the graphs D3 has are great for data visualization but not as helpful if you're trying to build a system for interaction between nodes that you don't want bouncing all over the place.
Had some traffic to my site from random places in the world (Brazil, Sweden, India) and had no clue where it was coming from until I saw this thread in my twitter feed. Mine is the Facebook Mutual Friends one.
You could also check out my slides from one of my d3 talks (with interactive examples):
It's interesting that some of the NYT visualizations are static graphics that normally, back in the print-only days, been done in Illustrator. Here's a map of Chicago killings done by Mike Bostock et al:
I wonder if making static charts via D3js has some time-savings/production advantages when the dataset is large enough? Before you say "maybe they just wanted vector graphics that worked for high-res"...that's obviously a benefit, but not enough on its own to give the web devs a graphic that could've been done via the traditional means (many of the Times stories include static graphics as PNGs in the sidebar)
I think you're right that there's a quantity of data where using D3.js will start to be more productive than doing it manually in something like Illustrator. It's an instance of a trade off that we're all familiar with: at what point is it worth building a tool instead of doing the task manually? It's also worth bearing in mind that the point where it makes sense to use a tool is reached more quickly with proficiency in the tool - if you have Mike Bostock working for you I imagine most visualisations will be easier to produce with D3.js!
I think the other significant aspect is the speed of iteration. In my experience, producing good visualisations takes lots of iteration and those can take a lot of time if you have to alter each data item by hand. I've often reverted to paper and sketched out a revision that's way a few times before going back to the drawing program. I think it's likely that it's much quicker to iterate using D3.js (in the right hands).
It's important to factor in the importance of reusability. When someone makes a D3 visualization, it is infinitely reusable and hackable. So next time you want to make a map of killings in Chicago, you have it ready to go, and you just plug in the data, rather than having someone re-make it by hand. When you're a news organization, where speed is obviously of the essence, this investment has to be a no-brainer.
As Bostock's incredible skill is deployed on a variety of visualization problems, the New York Times builds a library of visualizations and templates that they can use for the foreseeable future, as long as the data is in the same format. That is incredibly valuable.
I work for a web news network startup, and I'm hacking together D3 visualizations specifically because they're reusable. We're based in Chicago, and plan on doing crime segments, and my visualization will take public CPD crime stats, display them (hopefully beautifully), and then encode them with ffmpeg for web video.
Back in the days, people used to draw graphic by hand. Then, tools like Illustrator help automate the creation of graphic. Vector graphic libraries are going to disrupt the landscape.
It is starting out as artisan tool for programmers to build data visualization. Overtime, we'll have reusable templates/components that speed up the creation process and reduce cost. Christophe's list is awesome. I reference it quite a bit :)
At some point, creating vector graphic will be just as fast as creating static graphic. Plus, much more flexibility.
My team is tinkering with such idea with http://vida.io. Here's a little demo video:
very cool, christophe, thanks for taking the time to compile this list.
The one thing that always astounds me about people who generate dataviz with d3 is that they almost never do anything interactive with it (filter, zoom, etc) and if they do, they won't use any of d3's insanely cool/easy transitions to make the visualization smoothly morph from one state to the next.
Really, if you're going to start messing around with d3, read about Mike Bostock's thoughts on change blindness and object constancy.