You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 10, 2023. It is now read-only.
Agreed, this is an issue that should be fixed. More specifically, the issue appears to be with the Lookup Table's Combined_Key, (which refers to Yakutiya as "Sakha (Yakutia) Republic, Russia"). Whereas, the Lookup Table's Province_State refers to the same place differenty (i.e., "Sakha (Yakutiya) Republic"). The way JHU refers to Yakutiya is, however, consistent across the Lookup table as well as the web-data and the daily reports as far as the Province_State variable is concerned.
I've seen this issue occur before and I would wager it will come up again. I build around it by always recreating Combined_Key according to relevant string values.
The location is spelled as "Sakha (Yakutiya) Republic, Russia" in https://github.com/CSSEGISandData/COVID-19/blob/web-data/data/cases.csv, but spelled as "Sakha (Yakutia) Republic, Russia" in https://github.com/CSSEGISandData/COVID-19/blob/master/csse_covid_19_data/UID_ISO_FIPS_LookUp_Table.csv. The difference is very minor ("Yakutiya" vs "Yakutia") but it causes the UID lookup to fail and return an empty value, which causes my data processing to fail.
The cases.csv entry was added in commit d9cccd6, and the UID_ISO_FIPS_LookUp_Table.csv entry was introduced in commit b844f57.
Could you please fix one of them? According to Wikipedia, either spelling is acceptable.
Related: #2509
The text was updated successfully, but these errors were encountered: