-
Notifications
You must be signed in to change notification settings - Fork 605
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor for changes in upstream 24 March 2020 #36
Comments
cc @westmich |
@rufuspollock Thanks for tagging me on this. Any thoughts on the why? Are they having trouble keeping up with cases or is this data getting locked down? |
One of the major changes is the removal of recovered cases (#39). On this, I'm planning to remove |
Can you please leave the Recovered field in for the other countries which provide this info? |
@berndblasius we depend on the upstream here so we can't keep it I'm afraid.. |
Hi,
thanks for the info.
But I don't really understand the problem, for most countries
confirmed cases are given by Johns Hopkins University in the daily
reports.
Or do I miss something?
Best
Bernd
…On Thu, Mar 26, 2020 at 2:18 PM Anuar Ustayev ***@***.***> wrote:
@berndblasius we depend on the upstream here so we can't keep it I'm afraid..
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
@berndblasius they have announced that they will stop providing the recovered data sometimes soon |
@anuveyatsu one option is for us to write out the current recovered data to a separate file here and then integrate when we do the processing so it stays around and we don't have a breaking change? |
… province and date. refs datasets#47 refs datasets#36
There are changes upstream we need to handle (cf #33): CSSEGISandData/COVID-19#1250
us.csv
The text was updated successfully, but these errors were encountered: