-
-
Notifications
You must be signed in to change notification settings - Fork 375
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
Recovered Data Issue #64
Comments
|
Coming from CSSEGISandData/COVID-19. It’s due to the deprecations on the data files in the time series folder. They provided new files for deaths and confirmed cases but nothing for recovered. However, the updated data is available in the daily reports folder. We should switch the data source to these daily reports to stay accurate, but this is a massive change! |
Are you planning to do the required changes? If yes, what is the estimated time? |
Let's @pomber respond to this one :) |
A little bit more info: according to
The figures for const FILENAME_CONFIRMED = "time_series_covid19_confirmed_global.csv";
const FILENAME_DEATHS = "time_series_covid19_deaths_global.csv"; which I find a tad weird though... |
Yes, @pomber my charts are also broken due to this. Can you please look into this? 😅 |
Mine are as well ! 😃 |
Same here 😃 |
yeah, made a fallback in my code but please inform us when its fixed! you can as a fallback just put the previous day recovered in the variable so we do not have a problem!! |
@agaktr I adopted for same fallback mechanism. The code application will not break by this but the data will be outdated. |
@agaktr I did the same thing but if the country has more recovered cases today then the previous day, it won't be updated and will lead to false calculations. |
did the same as @agaktr and the others. reference for those using js |
Hi @pomber, can this issue be solved by any mean ? |
As far as I understand the changes from JHU CSSE, they have stopped publishing the recovered cases (at least for some countries). That's why you'll see I don't think using the last known number of recovered cases as a fallback instead of
I'm not sure why they (JHU CSSE) are still posting some And if you ask me, they are doing an outstanding job collecting the data, but they are not handling the breaking changes very well. |
I agree that the "last known number" isn't a good solution at all and breaks the calculations. So if I understood correctly, we shall wait for changes from JHU CSSE ? |
Yes. Meanwhile, make sure your apps support You can also read the whole thread or open issues for clarifications on the JHU repo. |
@pomber is there a way to get active cases from the source ? |
@chandan-reddy-k confirmed - recovered - deaths should give active, but now that recoveries are not available, not really :/. |
@ExpDev07 Yup that’s how I was doing but what I meant is CSSE is giving out daily reports and it has both active and recovered counts. So is there a way we can parse that file and get the values ? |
@chandan-reddy-k youd have to build a scraper that takes the daily reports and puts them in a queryable database. It’s a heavy task and not something you wanna do when just starting the app. This is why the timeline files were so great, you just make 3 HTTP requests, parse the CSV and you’re done. No scraping needed, it’s something you can do on the run (given you cache the results). |
JHU CSSE added a new File for recovered in the time_series. |
There’s still some issues with the recovery file. I have no idea what they’re even doing at this point. Contradicting announcements, format changes every day almost... |
All recovered data is null now. |
@awaisahmed119 A fix is on the go |
See #74 Should be fixed now. |
API gives null value in "recovered" field at date "2020-3-25" for all countries. |
Yep, that's because there isn't data reported for that day in the source csv. |
Recovered data is not available for 24/03/2020.
The text was updated successfully, but these errors were encountered: