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

Data appears heterogenous; some is not up to date #1058

Open
ballcoach12 opened this issue Mar 19, 2020 · 3 comments
Open

Data appears heterogenous; some is not up to date #1058

ballcoach12 opened this issue Mar 19, 2020 · 3 comments

Comments

@ballcoach12
Copy link

@ballcoach12 ballcoach12 commented Mar 19, 2020

It is unclear from reviewing the Confirmed Cases data set whether the United States data is being tracked only by state or my state/county. There are entries for both, and it isn't clear which one should be used for modeling. Also, data for Hamilton County, TN is inaccurate. Three cases have been confirmed and are not in the file according to county/state. I assume that these cases are in the state-only tally.

@yetzt
Copy link

@yetzt yetzt commented Mar 19, 2020

See #1054

@apsteinmetz
Copy link

@apsteinmetz apsteinmetz commented Mar 19, 2020

Agreed. Is the local data disaggregated state data so using local and state level is double counting?

@Sleekery
Copy link

@Sleekery Sleekery commented Mar 20, 2020

After 3/10/20, they started keeping track in the US by state only, no county/city level. You'll have to aggregate pre-3/10/20 data into states first. Hint: they're the only values in Province/State with commas. Filter by that, split by commas, and then map US postal codes to states.

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

Successfully merging a pull request may close this issue.

None yet
4 participants