Open rhaimann opened 4 years ago
In addition to rhaimann’s relevant remarks. Line 89 of the table, Martinique is a French department (Province), country France. Thanks all for the work.
While I would love to have already had this, I must admit I would be annoyed as I spent a long time writing code to fix all of these things, so I would have to completely rewrite those sections.
Either way, we will need some translation table for a specific purpose In addition, a continent column or an empty column would be super useful to give continent situation. I'm collaborating with UNDP in Africa and other regions to publish data by continent. In the meantime, I'm using translation table
Thanks again for the great work it's invaluable!
+1 for country codes!
Until then could we please change from short-form "Czechia" to the correct form "Czech Republic". Big Thanks!
Surely there are too many embedded workflows now and we should all use a translation table? I’m referencing Geonames for population, area and continent as well. Each refresh requires teaks to the mapping table. Not perfect but only a few minutes effort each day.
Surely there are too many embedded workflows now and we should all use a translation table? I’m referencing Geonames for population, area and continent as well. Each refresh requires teaks to the mapping table. Not perfect but only a few minutes effort each day.
My workaround also. Last night's download and update went without needing any manual tweaks on my end. Fingers crossed.
I have had the same problems and reported as issue #1199. I also had issues parsing the date fields and the names of States/Provinces are also not systematic.
I have some Python code I used for another project that can generate ISO3166 country codes from the country names. I have used it for data from UN and World Bank and other sources. It's available "as is" from this gist: https://gist.github.com/mok0/933578535d9cd4dddb93a1f7d9ead2e5
Thanks
Unfortunately I’m crunching data and translating with excel
Not skilled in Python
I have had the same problems and reported as issue #1199. I also had issues parsing the date fields and the names of States/Provinces are also not systematic.
I have some Python code I used for another project that can generate ISO3166 country codes from the country names. I have used it for data from UN and World Bank and other sources. It's available "as is" from this gist: https://gist.github.com/mok0/933578535d9cd4dddb93a1f7d9ead2e5
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
Surely there are too many embedded workflows now and we should all use a translation table? I’m referencing Geonames for population, area and continent as well. Each refresh requires teaks to the mapping table. Not perfect but only a few minutes effort each day.
If we could all share data for country translation and region indicators that would help
i did the translation and regionalization for worldometer population count, i can share it if we have a repository
@Olivier-Bertrand looks like this will be much cleaner with the next release - at that point we should be able to integrate to other sources with much less effort!
Thanks for the hard work. Post-processing the data has been challenged by a few country name issues. For example, the designation of the regions of Congo seem to vary. The asterisk after Taiwan poses a challenge for some encodings. The use of US varies from most other designations for the United States. I would humbly suggest using the ISO 3-alpha codes for each country/region being tracked if possible, such as those used by various agencies (https://worldmap.harvard.edu/data/geonode:country_centroids_az8, https://datahelpdesk.worldbank.org/knowledgebase/topics/125589-developer-information, https://www.nationsonline.org/oneworld/country_code_list.htm) . I am using country populations to assess relative effects felt in each nation and comparing national responses with those relative effects. Absolute quantities are not able to capture the relative effects felt within national or regional boundaries. Hence, doing joins with other databases is useful, which requires a field that can do a join. The country name field in your dataset cannot join with population datasets without manual post-processing, nor can available GIS data be joined with the country names in your dataset without manual post-processing.