←back to thread

77 points nateb2022 | 3 comments | | HN request time: 0.268s | source
1. Ameo ◴[] No.44506687[source]
I used this at a previous company with quite good success.

With relatively minimal effort, I was able to spin up a little standalone container that wrapped around the service and exposed a basic API to parse a raw address string and return it as structured data.

Address parsing is definitely an extremely complex problem space with practically infinite edge cases, but libpostal does just about as well as I could expect it to.

replies(2): >>44506724 #>>44508483 #
2. degamad ◴[] No.44506724[source]
Ditto - I was impressed with how well it handled the weird edge cases in our data.

They've managed to create a great working implementation of a very, very small model of a very specific subset of language.

3. ethan_smith ◴[] No.44508483[source]
Worth noting that libpostal requires ~2GB RAM when fully loaded due to its comprehensive data models. For containerized deployments, we reduced memory usage by ~70% by compiling with only the specific country models needed for our use case.