Closed mullender closed 4 years ago
Thanks for the report! Looking at that now.
Thankfully I'm not affected by changes to that file - I use the data in https://github.com/CSSEGISandData/COVID-19/tree/master/csse_covid_19_data/csse_covid_19_daily_reports
BUT... everything is broken right now! It looks like they changed some column headers.
I pushed the fix for #4: https://covid-19.datasettes.com/covid/daily_reports
@simonw thank you very much for updating this so quickly! The datasette reports have been most helpful in tracking the changes over time in different geographies. And estimating the effects of implementing physical distancing policies.
@simonw it looks like the auto-update of the DB failed to publish? https://github.com/simonw/covid-19-datasette/runs/531356266?check_suite_focus=true
The Cloud Run publish task only runs if the database that was built differs from the database that is currently deployed. Since the task runs four times a day now sometimes it won't deploy because the data in https://github.com/CSSEGISandData/COVID-19/commits/master/csse_covid_19_data/csse_covid_19_daily_reports hasn't changed in the past six hours.
Here's the code that compares the SHA hash of the deployed version to the SHA hash of the newly built database:
I wrote a bit about how that works here: https://simonwillison.net/2020/Jan/21/github-actions-cloud-run/
That is interesting syntax, thanks for writing a blog post about it. In this case it turns out the source data itself is incorrect, not something you could do anything about.
The source project rearranged their csv files, and stopped updating the old ones :(
For the country data we need to source time_series_covid19_deaths_global.csv
Not sure where the US state data went.
Thanks a ton for providing this data through datasette!