Options for live-updating visualizations

Datawrapper can update your charts, choropleth maps, and tables automatically, without republishing. This can be used e.g. in election nights when you get new data every hour and want to avoid that all charts have to be re-published. Every time a user updates a website with your visualization, it will freshly get the data from the CSV. 

This article gives an overview of the options you'll see when wanting to link an external dataset, no matter if you do so in a chart, table, or map.

πŸ‘‰ To create a live-updating chart or table, visit this article.
πŸ‘‰ To create a live-updating choropleth map, visit this article.
πŸ‘‰ To learn more about live-updating visualizations in general, visit this article.

Two options to create live-updating visualizations

Datawrapper gives you two ways to link external data:
  1. Use Datawrapper server: Here, we try to make it as easy for you as possible to publish charts based on live data. You will need to put your CSV somewhere on the web. We will periodically download it and upload it to our server, from where it will be served to the chart viewers. The data will be updated in increasing intervals, depending on when you last published the chart (every minute in the first 24h, every hour in the next 29 days). After 30 days, your visualization won't update automatically anymore. You can republish the chart any time to reset the update period.
  2. Serve data file directly: This is a good option for advanced users. The data file will be served directly from your server, giving you maximum control over the cache time and update intervals. Note that your server needs to support CORS (cross-origin resource sharing), HTTPS, and also needs to be ready to handle high loads.

In the rest of the article, we'll look at these two options in detail:

1. Use Datawrapper server

To use this option, you'll need to give Datawrapper the URL to a CSV: 

Where can you host a CSV?

  • on your own website
  • on Github: If you're a Github user, you can upload CSVs there or access CSVs that other Github users have uploaded (for example, try to copy and paste this Buzzfeed CSV). For Datawrapper, you need the URL of the "raw" CSV. To get this, click on the file name of a CSV on Github, then click on "Raw" on the right. Wait until the new site is loaded, then copy and paste the URL into Datawrapper. 
  • on Google Sheets: We already offer a Google Sheets Import option in our Upload step, but if you add your Google Sheets there, it won't update as soon as you add new data. If you update your data in your Google Sheet often and want to see the changes in the chart without needing to click "Publish" every time, select the option Link external dataset.

    Make sure that Link Sharing is activated for your Google Sheet. To do this, click on the "Share" button at the top right corner: 
     Make sure that "Anyone with the link" is selected and click on "Copy link". Then paste this into Datawrapper. If you want to upload data from one specific sheet, you can also copy the url of that sheet once the sharing is enabled: 

    Note: If you're using a link to a published google sheet, make sure to activate your sharing permissions, as by default the published sheet will not be accessible by Datawrapper unless you do so. 
    If you link to a Google Sheet, make sure to select "Use Datawrapper server". If you choose "Serve data file directly", your chart will seem to work at first, but eventually break because Google doesn't allow that many requests ( see their documentation).

How does all of that work? 

Downloading the data freshly from a CSV each time a user sees a Datawrapper chart is a bit tricky, technology-wise (you'll see this in the 2nd part of this article). To make it easier, we take care of the complicated stuff for you. We decided to throw in a free data hosting service. From your website, Github or Google Sheets, we copy the CSV to our own server in certain intervals (every minute on the first day, then every hour the next 29 days), and your Datawrapper chart will pull the data from there:

If you don’t want to sweat about all these technical terms (HTTPS, CORS, and high traffic) and want to have full control; or if you need a higher update frequency, we still offer you the complicated way:

2. Serve data file directly

The more advanced version doesn't go the detour. It pulls the data directly from your CSV every time one of your readers opens a website with a chart:

To make that possible, your external data file needs to be publicly accessible under a URL that supports cross-origin resource sharing (CORS), HTTPS and can deal with high traffic. Then enter the URL of the data file you uploaded in Datawrapper. For testing purposes, you can copy and paste this URL: https://static.dwcdn.net/test-data/movies.csv

To allow CORS requests from Datawrapper, the server where your external data lives needs to set the Access-Control-Allow-Origin header in the response. The header can be set to * to allow access by all domains, or otherwise, if you want to limit access, which may be better for security reasons, you can specifically whitelist Datawrapper's domain - https://datawrapper.dwcdn.net/.

Again, Datawrapper will immediately test if the URL is configured correctly. If everything is green, your data was imported successfully:

After uploading the data, you will be able to see the data in  Step 2: Check & Describe, as usual. If you change the data there, the changes in step 2 won't be overridden when the data is freshly pulled from the server. However, if you change cells in step 2 and the updated data contains new rows, the cell will jump and your data will be a mess. There's no problem changing the column names, though, especially if the number of columns stays the same. 

After publishing your chart, you'll have a live chart, that will always load the data from the URL you entered.