This is the project we use at the University of Oxford to create embeddable visualizations for Our World in Data. It's not currently designed for immediate reuse as a full library, but you are very welcome to adapt any of our code or to send pull requests.
An example of what this can make (click for interactive):
The owid-grapher visualization frontend code can run isomorphically under node to render data directly to an SVG string, which is how the above image works!
Initial development setup
yarn in the repo root will grab the remaining dependencies.
Daily exports from the live OWID database are published here and can be used for testing:
|owid_metadata.sql.gz||Table structure and metadata, everything except data_values||~5 MB|
|owid_chartdata.sql.gz||All data values used by published visualizations||>100MB|
This sequence of commands will create a database, then download and import all OWID charts and their data:
mysql -e "CREATE DATABASE owid;" curl -Lo /tmp/owid_metadata.sql.gz https://files.ourworldindata.org/owid_metadata.sql.gz gunzip < /tmp/owid_metadata.sql.gz | mysql -D owid curl -Lo /tmp/owid_chartdata.sql.gz https://files.ourworldindata.org/owid_chartdata.sql.gz gunzip < /tmp/owid_chartdata.sql.gz | mysql -D owid
Since the full data_values table (including everything we haven't visualized yet) is really big (>10GB uncompressed), we don't currently have an export for it. If you'd like a copy please contact us.
cp .env.example .env and populate
.env with your database details. Then run
yarn setup to do an initial compilation.
yarn dev and head to
localhost:3030. If everything is going to plan, you should see a login screen! The default user account is "email@example.com" with a password of "admin".
You may (optionally) want to run a static build, which produces the public chart urls:
node dist/src/bakeCharts.js. You only need to run this static build manually after a database import, otherwise it happens automatically when a chart is updated.
If you need to make changes to the MySQL database structure, these are specified by typeorm migration files. Use
typeorm migration:create -n MigrationName and then populate the file with the SQL statements to alter the tables, using past migration files for reference if needed. Then run migrations with
typeorm migration:run. To access this CLI tool install typeorm globally using
npm i -g typeorm or use the repository executable at
You can run
yarn c to get a node REPL with the database connection opened and models preloaded into the context. Then you can e.g. inspect all charts:
await Chart.find(). Note that this depends on the
--experimental-repl-await option introduced in node 10.
owid-grapher is based around reactive programming using the libraries Preact and Mobx, allowing it to do pretty heavy client-side data processing efficiently. New code should be written in TypeScript. Visual Studio Code is recommended for the autocompletion and other awesome editor analysis features enabled by static typing.
The OWID tech stack has evolved over time as we have found really optimal ways of solving particular problems. We're now happy with the combination of React + Mobx + TypeScript + node and expect to be using these core tools for the foreseeable future. The MySQL database and data structure however is much older and we're interested in exploring alternatives that might allow us to work with large amounts of data more quickly and with more flexibility.