Iso 3166 Country Code Download
Kam Bergmann
The codes in ISO 3166 are available on the Online Browsing Platform. The information on the OBP is always up to date and you can sign up for notifications to be informed when changes are made by clicking on the follow function in the top right-hand corner.
We also have a product, the Country Codes Collection, which you can preview free of charge on the OBP (where you will also find a decoding table). It contains the codes from Parts 1, 2 and 3 of ISO 3166 in three different formats (.xml, .csv, and .xls) for easy integration into your own systems. You will be notified when changes are made so you can download the latest versions. In this way, you can be sure that your database is always using the most up-to-date information from ISO.
The country codes can be represented either as a two-letter code (alpha-2) which is recommended as the general-purpose code, a three-letter code (alpha-3) which is more closely related to the country name and a three-digit numeric code (numeric-3) which can be useful if you need to avoid using Latin script.
The codes for subdivisions are represented as the alpha-2 code for the country, followed by up to three characters. For example ID-RI is the Riau province of Indonesia and NG-RI is the Rivers province in Nigeria. Names and codes for subdivisions are usually taken from relevant official national information sources.
Users of ISO country codes have the option to subscribe to a paid service that automatically provides updates and supplies the data in formats* that are ready-to-use for a wide range of applications. For more information, visit the ISO Store.
Following notification from the United Nations (UN), the ISO 3166 Maintenance Agency assigns alpha-2 and alpha-3 country code elements to new UN member states. The numeric country code is assigned by the UN.
However, the ISO 3166 Maintenance Agency may assign country codes to dependencies of countries that are member states of the UN. To be considered, some criteria, amongst others, include that the area be physically separated from its parent country and outside its territorial waters. Even if all criteria are met, the ISO 3166 Maintenance Agency may decide not to assign a code element, for example, due to the very limited number of official alpha-2 code elements available.
The ISO 3166-1 standard currently comprises 249 countries, 193 of which are sovereign states that are members of the United Nations. Many dependent territories in the ISO 3166-1 standard are also listed as a subdivision of their administering state in the ISO 3166-2 standard.
The sortable table below contains the three sets of ISO 3166-1 country codes for each of its 249 countries, links to the ISO 3166-2 country subdivision codes, and the Internet country code top-level domains (ccTLD) which are based on the ISO 3166-1 alpha-2 standard with the few exceptions noted. See the ISO 3166-3 standard for former country codes.
This is a complete list of all country ISO codes as described in the ISO 3166 international standard.
These codes are used throughout the IT industry by computer systems and software to ease the identification of country names.
We have compiled them in the quick reference table below in order to help our clients do quick conversions from the numeric or 2 letter code to any country name.
The ISO has specified two-letter ASCII codes for the world's countries. These are summarized in the ISO 3166 two-letter country-code standard, given below.As with the language codes, country codes are case-insensitive. You may notice that these are the codes used by the Internet domain name scheme for indicating the country domain of an Internet address. Absent from this list are the non-national names commonly used in domain naming schemes, such as ARPA (Old-style Arpanet--obsolete), COM (Commercial), EDU (Educational), GOV (Government), INT (International), MIL (U.S. Military), NATO (for NATO, soon to be obsolete),NET (Network) and ORG (Nonprofit organization).The use of these codes is discussed in Chapter 5 ofThe HTML Sourcebook, Third edition.
ADUC uses the c attribute to select a country in Country/region field under Address tab, and not the co attribute. If someone updates country in ADUC, co attribute would be changed to AD's version of country name if it was different from the ISO standard. Would issues arise from having two different name strings for one and same country?
Since I have no way to actually enumerate country names and codes of AD (that I know of), I've picked up a ISO-3166 .NET library to do that for me. But as noted before, there are discrepancies in country names like the one above.
With 99% certainty alpha2 and numeric codes will match with those in AD, but it's the names that cause me worry. AD itself does not seem to care what the co attribute is, it only looks at c and countryCode. Unless someone updates country in ADUC, that is.
In addition, New-ADUser and Set-ADUser does not even bother updating the co attribute when setting a country using their -Country parameter. If a user's country is set to one in ADUC, and then to another with Set-ADUser, the co attribute is not updated. This indicates it would be relatively safe to ignore the attribute altogether.
I know of only one instance where all three country attributes had to be set. We had a client who had (still has) directory synchronization to Azure Active Directory. User accounts would not sync to AAD unless all three country attributes were populated.
But then what about applications that may query AD for country attributes. By all logic such applications should only use alpha2 and numeric, because names are prone to change with time. But what do I know.
The users are government workers who need to record, search, reuse or exchange data which has worldwide geographical information. The systems that hold this data need to use accurate country information to provide consistent data between systems.
The ISO 3166 Maintenance Agency regularly updates the country codes based on information from the United Nations. The agency sends notifications of any changes they make to the standard so you can download the latest version.
Countries are listed alphabetically by name. When using the GS1 US Data Hub Product Import template, locate the country you need from this table and then enter the two-digit code, three-digit code, or numeric code in the Target Markets column for the appropriate products.
Need to enter more than one code? Separate the codes with the tilde (`) symbol, which is left of the "1" key on most keyboards.
ISO 3166-1-alpha-2 English country names and code elements. This list statesthe country names (official short names in English) in alphabetical order asgiven in ISO 3166-1 and the corresponding ISO 3166-1-alpha-2 code elements.
ISO 3166-1-alpha-2 English country names and code elements. This list states\\nthe country names (official short names in English) in alphabetical order as\\ngiven in ISO 3166-1 and the corresponding ISO 3166-1-alpha-2 code elements.
My main concern is, will one country ever adopt a numeric code that has been used for another in the past, such as can happen with alphanumeric 3166-1 codes? If not, then it seems like a perfect identifier for a primary key in a database...
This error message indicates that the user's address holds an invalid country code.
Alma is using ISO 3166-1 alpha-3 for country codes.
To check the user's country code:
1. In Alma, open the user account.
2. Go to "Contact Information" tab.
3. Click on the address.
4. See if the country code is a ISO 3166-1 alpha-3 valid code.
The country code ultimately is not a functional field. We recommend customers to adhere to ISO codes in their pre-migration cleanup efforts.
In order to correct the country code for external users, change the country data coming from the SIS to valid country codes. On the next users sync the address data in Alma will be overwritten and the issue will be resolved.
The SDTMIG v3.2 and earlier versions list the CDISC SDTM codelist "COUNTRY" as the terminology codelist to use for the Demographics domain variable COUNTRY. This codelist was retired in 2016-09-30 (Package 27) because it duplicated the ISO 3166-1 alpha-3 codes for the representation of names of countries and their subdivisions. Maintaining the SDTM "COUNTRY" codelist was not reasonable, since it duplicated content maintained by ISO.
For submissions using CDISC CT package 27 or later, submission values that were prepared using the CDISC SDTM "COUNTRY" codelist for DM.COUNTRY may not be those in the current version of ISO 3166-1 alpha-3
Please note that ISO 3166-1:2020 does not define the names of countries. This information instead comes from the United Nations, and the international standard draws from Terminology Bulletin Country Names and the Country and Region Codes for Statistical Use maintained by the United Nations Statistics Divisions.
For clarity, these subdivision codes are structured with the alpha-2 country code from ISO 3166-1, a hyphen, and then the code element of the subdivision name, expressed in either one, two or three alphabetical and/or numeric characters. For example, the code for New York State is US-NY.
SSL.com complies with U.S. law and therefore accepts the following two-letter ISO-3166 country codes. Please be sure to use any of the following international country codes in your certificate signing requests (CSR) that corresponds to the country of origin for the SSL.com certificate registrant. Click here for a list of export restricted countries or scroll to the bottom of this page.
The use of the ISO Standard 3166 for the definition of country code Top Level Domains began in 1986. The practice was first mentioned in RFC 920 (October 1984). The practice was also mentioned in RFC 1032 (November 1987) and with the further use of the alpha-2 codes prominently documented in RFC 1591 (March 1994). In 2000, the ICANN Board of Directors recognized the ISO 3166 Maintenance Agency as the authoritative entity for country code designations and officially adopted the use of ISO 3166-1 and the 3166-MA exceptional reserved list as the set of eligible designations for ccTLD assignment (September 2000). ISO 3166 is also used to determine the eligibility for an IDN ccTLD string under the IDN ccTLD Fast Track process.
df19127ead