postal-address
postal-address copied to clipboard
scaleway
:postal_horn: Parse, normalize and render postal addresses.
Hi, the lib intro sounds great, but I couldn't find any doc examples on how to actually use it. There's the API documentation at https://postal-address.readthedocs.io/en/develop/ , which is quite detailed...
By default, we rely on the ISO 3166-1 classification for country codes. This taxonomy is not up to date and some inaccuracies are currently hidden because we use common names...
Territory code aliases implementation is quite a mess, and to make it easier to maintain, use a [directed acyclic graph](https://en.wikipedia.org/wiki/Directed_acyclic_graph) to store the subdivision / country relationship as well as...
To help solve territory hierarchy, implement an utility to find the [lowest common ancestor](https://en.wikipedia.org/wiki/Lowest_common_ancestor) of several territory codes.
Once #1 is done, we might eventually include support for [NUTS subdivisions](https://en.wikipedia.org/wiki/Nomenclature_of_Territorial_Units_for_Statistics), if it make sense.
Postal codes requires their own parsing and normalization library. The idea is to render them under the `{country_code}-{postal_code}` scheme. The main motivation behind this feature is support for territorial exceptions,...
Package up all territory utilities into a proper `Territory` class. The goal of this class will be to reconcile and normalize territory taxonomies (ISO countries, subdivisions and european legacy country...
Hi @kdeldycke and @scaleway, Do you think we could use this library to create a Django `PostalAddressField`? Could you write some documentation, snippet or maybe a library for this?
We might be able to add support for territorial zones that are not countries or subdivisions per-se, like the European Union, or an This requires #6. Use case: implement territory...