African scholarly publishers mapped using CartoDB with data input from Google Sheets
The map and the features on it are drawn by CartoDB. The data is taken from a Google Sheet that CartoDB syncs with every hour. Changes made in the Google Sheet will therefore take up to one hour to show up on the map itself. Changing existing data and creating new entries is both possible and will be updated on the map. New columns, however, will not appear on the map as only predefined column headers are taken into consideration by CartoDB.
Making changes can be done by editing the Google Sheet. The existing data has remained intact but is now followed by a number of columns that represent the CartoDB input. These are protected cells and must not be edited manually. Changes must be made in the original cells and will automatically update those that form the CartoDB input.
There are a few important formatting rules that must be followed:
- Never add a row above the current column headers. The headers in the CartoDB input section must remain the way they are for CartoDB to take them into consideration when drawing the map and its features. Changing the headers will result in an empty map.
- Always include http:// or https:// when entering links. For Facebook it must be https://. Failure to do so will cause CartoDB to consider it text rather than a link.
- The twitter handle must be just that (so
@UCTPress
rather thanhttps://twitter.com/uctpress
) - The coordinates but be divided by a comma:
latitude, longitude
. - Follow the rules in the column header comments. If absent, be consisent with existing entries. For example, a comment on the
website
column header dictatesn/a
must be entered when no website can be found. Themost recent title published
header has no such comment, but input must be consisent with existing entries and so also usen/a
. Failure to do so will cause unwanted input text to show up in the map's infobox.