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

It would be really nice and much appreciated if you keep naming convention and consistency #1333

Open
alanphilipm opened this issue Mar 24, 2020 · 3 comments

Comments

@alanphilipm
Copy link

@alanphilipm alanphilipm commented Mar 24, 2020

It would be really nice and much appreciated if you keep naming convention and consistency.

@yetzt
Copy link

@yetzt yetzt commented Mar 24, 2020

Agreed: #1326

@bsdunx
Copy link

@bsdunx bsdunx commented Mar 24, 2020

I've made a few other bug reports about consistency and standards, perhaps there should be a thread which contains all issues related to naming and data encoding used. I've been rewriting the same code over and over and I'm sure many others are dealing with this.

Lat and Long where changed again today, well just Long was changed to Long_, after being changed yesterday. We all appreciate the work being done to provide the data but it is frustrating to spend time re-fixing code.
#1390
#1391

@alanphilipm
Copy link
Author

@alanphilipm alanphilipm commented Mar 24, 2020

I am quite surprised that for such an important topic there is not a Data Quality Check in place.
Additionally, I checked all data sources mentioned on the code page and, I was not able to find the recovered values. Can someone here help me with this matter? I am wondering where this particular data is taken from or how is calculated here. I see many news channels from all over the world referring to the JHU dashboard, but now I am asking myself if the media aren't relying too much on this dashboard.

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
3 participants