Skip to content
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

Time travel in South Africa :-) #2

Open
ThimoNeubauer opened this issue Mar 26, 2020 · 1 comment
Open

Time travel in South Africa :-) #2

ThimoNeubauer opened this issue Mar 26, 2020 · 1 comment

Comments

@ThimoNeubauer
Copy link
Contributor

With todays data the "T_2 over X days" plots looks funny:

image

I guess it's yet another special case in the input data...

@gluap
Copy link
Owner

gluap commented Mar 26, 2020

The cause is the following: All but the last point come from a data table labeled only with the calendar date. Because the time when the number of cases was "Measured" is unknown but most (big) countries report multiple times per day, it is assumed that the number of cases labelled 2020-03-23 is actually a value close to midnight in the evening of 2020-03-23 thus really "2020-03-24 00:00". The last point comes from a realtime API that actually delivers a time stamp when the point was taken. As we see South Africa hasn't delivered data since yesterday ~11am. Because that last point is timestamp-aware and the others are not it shows this "special" behaviour until the first data value on the new day is reported.

I've been thinking about adding a plausibility check to address the issue (essentially discarding the realtime point if it's older than the latest from the time series) but so far it wasn't pressing enough.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants