miguelcoba

miguelcoba

Hi,

I’m using 2-char country codes from `Cldr.Territory.country_codes/0` in Cldr.Territory package, but I need to get the corresponding 3-letter country code as specified in ISO 3166-1:2006 Alpha-3 code.

Is there a quick way to transform those using the Cldr package family or should I use another package or maybe fallback to a hardcoded map and fetch it from there? e.g.

@countries %{

US: “USA”,

MX: “MEX”


}

def country_code_alpha_3(country), do: Map.get(@contries, country)

Thanks in advance,

Miguel

Showing Posts 1 to 6

kip

kip

ex_cldr Core Team

CLDR does contain ISO 3166 Alpha 3 mappings but they aren’t exposed in ex_cldr_territories iirc.

I’ll take a look at working up a PR for this in the next day.

miguelcoba

miguelcoba OP

Thanks, Kip.

I didn’t mean to assign homework to you and of course there is no rush or obligation to do it. For now I’ll use a direct hardcoded map and if you release a patch with this I’ll update to use it.

Thanks for answering so fast!

kip

kip

ex_cldr Core Team

Perfectly fine - it’s been on the “must get around to this” list for a while. So I may as well get around to it :slight_smile: I should have something you can work with in the next 24 hours.

13
Post #3
arcanemachine

arcanemachine

Kip, you are a treasure to us all.

kip

kip

ex_cldr Core Team

I’ve published ex_cldr version 2.47.0 that adds Cldr.Config.territory_codes/0. I’ve also opened a PR to ex_cldr_territories for @Schultzer to consider.

For now you can use the new function as:

@territory_codes Cldr.Config.territory_codes()
def territory_codes do
  @territory_codes
end

The functions in Cldr.Config all read, decode and normalise data so you only want to do that once, at compile time, hence the module attribute approach.

Example

iex> Cldr.Config.territory_codes()
%{
  EA: %{},
  IM: %{alpha3: "IMN", numeric: "833"},
  XG: %{alpha3: "XGG", numeric: "979"},
  BH: %{alpha3: "BHR", fips10: "BA", numeric: "048"},
  JM: %{alpha3: "JAM", numeric: "388"},
  JO: %{alpha3: "JOR", numeric: "400"},
  NC: %{alpha3: "NCL", numeric: "540"},
  QO: %{alpha3: "QOO", numeric: "961"},
  QU: %{alpha3: "QUU", numeric: "967"},
  VN: %{alpha3: "VNM", fips10: "VM", numeric: "704"},
  YE: %{alpha3: "YEM", fips10: "YM", numeric: "887"},
  AG: %{alpha3: "ATG", fips10: "AC", numeric: "028"},
  XE: %{alpha3: "XEE", numeric: "977"},
  KR: %{alpha3: "KOR", fips10: "KS", numeric: "410"},
  BD: %{alpha3: "BGD", fips10: "BG", numeric: "050"},
  IT: %{alpha3: "ITA", numeric: "380"},
  AD: %{alpha3: "AND", fips10: "AN", numeric: "020"},
  SY: %{alpha3: "SYR", numeric: "760"},
  SA: %{alpha3: "SAU", numeric: "682"},
  SB: %{alpha3: "SLB", fips10: "BP", numeric: "090"},
  AN: %{alpha3: "ANT", fips10: "NT", numeric: "530"},
  NP: %{alpha3: "NPL", numeric: "524"},
  XY: %{alpha3: "XYY", numeric: "997"},
  BI: %{alpha3: "BDI", fips10: "BY", numeric: "108"},
  PL: %{alpha3: "POL", numeric: "616"},
  XA: %{alpha3: "XAA", numeric: "973"},
  AO: %{alpha3: "AGO", numeric: "024"},
  HT: %{alpha3: "HTI", fips10: "HA", numeric: "332"},
  ML: %{alpha3: "MLI", numeric: "466"},
  GY: %{alpha3: "GUY", numeric: "328"},
  CH: %{...},
  ...
}
11
Post #5
miguelcoba

miguelcoba OP

Thank you so much, @kip.

Updating my versions!

— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
RemyXRenard
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
samoloth
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
FlyingNoodle
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New

Other Trending Topics Top

JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
mhanberg
Hi everyone! The first release candidate for the Expert language server project is now available! We’ve published a press release detai...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews