Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Duplicated UN/LOCODEs #11

Open
salim-b opened this issue Mar 28, 2024 · 0 comments
Open

Duplicated UN/LOCODEs #11

salim-b opened this issue Mar 28, 2024 · 0 comments

Comments

@salim-b
Copy link

salim-b commented Mar 28, 2024

There are various geographical locations that have multiple UN/LOCODEs assigned. One example is the Swiss municipality Schönenbuch that has two entries in locodes/CH.csv that only differ in the change date and the LOCODE itself (SBC vs. SOH).

This raises the following questions:

  1. Why are there multiple UN/LOCODEs per entity in the first place? Are those "coding errors"?

  2. Is there a "best practice" on how to handle such duplicates? Should we e.g. always take the entry with the most recent change date1?

Footnotes

  1. Although that particular heuristic wouldn't suffice to resolve all duplicates since there are entries that don't even differ in the change date but only the LOCODE.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant