Hello Anna,

Somewhat unfortunately, the documentation for importing CSV data through the URL is somewhat buried in CODAP’s github site. You can find it here.

There is another gotcha however, namely that CODAP runs as a “secure” site with. As such, the site accessed by the URL parameter must also be secure. So the URL you would use will need to have the ‘https’ prefix as in

https://codap.concord.org/app/?url=https://mywebsite.com/fjdkfjk.csv

Here’s what Jonathan Sandoe has to say in an email to another user:

The issue is that the link is to an insecure http address and CODAP is running with an https URL. Browser rules (quite reasonably) prevent a secure page from loading an insecure file. I tried modifying the URL to “https://xyz.com/Sample.csv” but the server doesn’t appear to support https.

If you are affiliated with the owners of xyz.com in any way you could request that they support HTTPS. It’s probably a good idea for them anyway.

The other network bugaboo that limits CODAP’s ability to read data from a third party sources are same origin policies (CORS). Servers can be configured to restrict the ability of browser apps to read their data. If a CSV file’s server is configured in this way, CODAP will not be able to use it directly.

 

Hi Anna,

The basic idea of CORS is that the providers of a web resource should be able to control how other sites can use the resource. So, when the browser is asked for a resource that doesn’t have the same origin (server) as the requester, it first checks with the server. You can configure a server to let any origin use a resource or select origins. If you are using an Apache server and wish to let the contents of a directory be used by any origin you would create a file named ‘.htaccess’ in that directory. It should have the following line:

Header set Access-Control-Allow-Origin “*”

You could grant just the CODAP server this access by saying:

Header set Access-Control-Allow-Origin “codap.concord.org”

Jonathan