Recovered csv file rows not equal to those of confirmed and deaths

CSSEGISandData / COVID-19

Novel Coronavirus (COVID-19) Cases, provided by JHU CSSE

https://systems.jhu.edu/research/public-health/ncov/

29.14k stars 18.43k forks source link

Recovered csv file rows not equal to those of confirmed and deaths #2494

Open MZDN opened 4 years ago

MZDN commented 4 years ago

recovered csv file has 252 rows without headers https://github.com/CSSEGISandData/COVID-19/blob/master/csse_covid_19_data/csse_covid_19_time_series/time_series_covid19_recovered_global.csv
confirmed csv file has 266 rows without headers https://github.com/CSSEGISandData/COVID-19/blob/master/csse_covid_19_data/csse_covid_19_time_series/time_series_covid19_confirmed_global.csv
deaths csv file has 266 rows without headers https://github.com/CSSEGISandData/COVID-19/blob/master/csse_covid_19_data/csse_covid_19_time_series/time_series_covid19_deaths_global.csv Could you please clarify this?

Lucas-Czarnecki commented 4 years ago

It's been like this for a long time. Likely because JHU didn't start recording recovered cases at the same time as confirmed cases and deaths.

gottfriedhelms commented 4 years ago

If I remember correctly this specific issue started when suddenly the 14(?) canadian provinces were subsumed under one record in "recovered" but not in "confirmed" and "deaths".

HallidayDW commented 4 years ago

@MZDN:

Since your "issue" pertains to the Time Series data, this simply reflects a choice to not include (at least some) data rows that are all zeros (0).

My data aggregation and plotting routines have treated "missing" data rows as zeros (0), from the very beginning of these Time Series files (including the former format).