opensanctions / opensanctions/rigour
Support for unprocessed Libpostal address fields (e.g., unit, suburb, etc.)
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 67
- Forks
- 18
- Avg merge
- 13h 7m
- Merged PRs (30d)
- 15
Description
While working with address normalization, I noticed that rigour currently doesn’t utilize some Libpostal output fields such as:
- unit
- level
- suburb
...
These fields are often useful when dealing with international addresses or complex building/unit structures.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no repository file, test, or entry point, so start by locating rigour's address-normalization integration with Libpostal. Trace how existing Libpostal fields are handled, then define coverage showing that fields such as unit, level, and suburb are retained for complex or international addresses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100