OK, and we want this in one single dataset right?
ATM we have this dataset http://datahub.io/core/co2-ppm with code for this here https://github.com/datasets/co2-ppm
But this is only annual and monthly from 1980
I suggest we create a new dataset e.g. co2-ppm-daily and create the scraper for this. Do you know python at all? If not we can help do this as we already have the srapers for this kind of file in co2-ppm ...
quick question regarding the sharable data links like https://datahub.io/core/co2-ppm/r/1.json
That link redirects to to https://pkgstore.datahub.io/core/co2-ppm/co2-annmean-mlo_json/data/5168771a128447a2d4c8a77e40844134/co2-annmean-mlo_json.json
Can I expect the second url to remain static? That is, can I request data from it in my web service and expect that it will keep working?
@rufuspollock @svetozarstojkovic Once the data is on datahub, how does the carbondoomsday frontend access it?
@titojankowski using r links you can as Svetozar said access via GET request. Re querying dataset files, there is some workarounds, e.g., we can organize resources in a way you can access data by year or decade. @rufuspollock any suggestions?
Also, please, remember that you can just embed graphs and tables from datahub
r links. These links redirect you to the latest available version of a resource. The second URL is static, however, it won’t get data update. Once data is updated, its hash is also changed and there will be a new URL for it. I would request the data using the first link so that you always have the latest data.
Also, some of the climate datasets only have data up to 2014. Will they at some point be updated?
Yes, it will be :smile:
co2-ppm-daily here - https://datahub.io/core/co2-ppm-daily - please check it out :smile:
