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

au: split unit and housenumber #499

Closed
missinglink opened this issue Feb 2, 2022 · 1 comment · Fixed by #502
Closed

au: split unit and housenumber #499

missinglink opened this issue Feb 2, 2022 · 1 comment · Fixed by #502

Comments

@missinglink
Copy link
Member

I noticed some of the OA sources for AU come with the unit/housenumber concatenated:

Screenshot 2022-02-02 at 21 02 52

While its difficult to accurately split these slash delimited values internationally, it should be simple enough to do on a per-country basis.

There's already a conditional statement for AU which can be used to detect sources appropriately.

ref: https://auspost.com.au/content/dam/auspost_corp/media/documents/Appendix-01.pdf

Screenshot 2022-02-02 at 21 06 07

@missinglink
Copy link
Member Author

missinglink commented Feb 2, 2022

actually this may be better implemented in pelias/model as a post-processing script, which would allow it to work for any importer which produces records on the address layer, we could use the country result from PIP to decide on which strategy to use.

[edit] on reflection, it's mostly an issue with OA since OSM mappers usually split these fields out, we can port it over later if/when required.

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

Successfully merging a pull request may close this issue.

1 participant