3 ms·

Hi everyone, I'm Dave, one of the developers of D3plus (and Data USA itself). Thanks everyone for checking out our site. If anyone has any questions feel free t

• mshenfield 11y ago
  It is very snappy on my browser, especially for the amount of information that is being presented. How are you using d3plus, build tools, and local storage solutions (or service workers?) to accomplish this? I haven't explored it too much yet, but I'm enjoying the breadth and succinct presentation of all this information in one place.
  • davelandry 11y ago
    We use a very aggressive page caching, so that all of the text and statistics are pre-rendered when the page is requested. The visualizations only initiate when they are visible in the window. When that happens, they make an API call for the data and then initialize the D3plus visualization. All of the visualizations use shared attributes, for things like location names and industry colors/icons. Those API calls are stored in the browser using localforage. https://github.com/mozilla/localForage https://github.com/mozilla/localForage
• ar0b 11y ago
  Hi Dave, I was looking at this page http://datausa.io/profile/geo/pennsylvania/#housing http://datausa.io/profile/geo/pennsylvania/#housing I noticed that a lot of the ranges on the x-axis are not consistent. Is there a reason for that?
  • jaydub 11y ago
    Jon here - also worked on Data USA. Several of the visualizations use data from ACS summary tables and the axis in several of the visualizations reflect the underlying buckets provided by the Census Bureau.