-
Notifications
You must be signed in to change notification settings - Fork 13
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
UK not recognised as region by iso3166 package #33
Comments
Thanks @danielhuppmann - we've removed the openentrance package as a dependency to avoid #24, in lieu of using a smaller package iso3166; but it's flagged some inconsistencies between the two. For example, the country name in iso3166 for the UK are "United Kingdom of Great Britain and Northern Ireland" and not "United Kingdom" as it is in openentrance... |
Right, that was rather meant as a reference point for possible solutions. The openentance utility will not be maintained, but instead be re-built in a more stable manner in other packages. I'm having a similar problem with international country-names, where we use the pycountry package as a dependency of nomenclature. This PR IAMconsortium/nomenclature#262 adds a list of hard-coded overrides for readability and consistency with community standards. |
Okay, so a more direct question for you on this topic. Could you tell me what the recommended package or utility is to ensure compatibility with the IAMC template (and nomenclatures used within ECEMF and IAM-COMPACT), where the only function we need is to convert from ISO2 or ISO3 letter country codes. Options:
|
For clarification: the IAMC data format just requires a "region" column. The "nomenclature", i.e., the actual definitions of allowed values in each project, is defined for each project and are currently not always consistent across projects. In openENTRANCE and ECEMF, the list of allowed country names is explicitly defined here - this list currently only includes European countries. I'm not sure where such data would exist for iam-compact? I don't like the idea to force results to be reported directly in ISO3 codes, because this is very unwieldy for users. The current effort in the nomenclature package aims to have a standardized reference for all country names that can be used by any future projects, and we could add conversion tools between name and ISO2/ISO3 based on the pycountry-package (which seems to be more stable than py3166) with some agreed simplifications and addition(s), in particular Kosovo. There are currently four naming conflicts between pycountry and openENTRANCE:
FYI: Kosovo is not a universally recognized country and does not have an ISO3 code. |
The EU uses
UK
instead ofGB
as the 2-character code for the United Kingdom. This mapping is not included in the iso3166 Python package.The text was updated successfully, but these errors were encountered: