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.
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.
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 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).
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.
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:
1723 of them by Mike Bostock! 
 number is made up but almost certainly close.
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.
amazing example 1:
cool example 2:
 - http://noflojs.org/dataflow-noflo/demo/
You could also check out my slides from one of my d3 talks (with interactive examples):
D3 based profile visualization of interests and stages of needs in each field.
More about what it means here: http://www.doerhub.com
Anyway, recall problems aside, this gallery is fantastic.
Opened link, saw huge list of text links, closed.
You know, it would be cool if the list of d3 examples was itself a cool interface powered by d3.