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

Handling name differences #25

Open
boldtrn opened this issue Dec 21, 2016 · 0 comments
Open

Handling name differences #25

boldtrn opened this issue Dec 21, 2016 · 0 comments

Comments

@boldtrn
Copy link
Member

boldtrn commented Dec 21, 2016

As reported in #24, we should try to return the same name for every geocoder.

How do we handle the different name entry? E.g. we could parse "restaurant":"Sushi Oji" and use this as name but we would overwrite the full display name: "Sushi Oji, Prinzregentenstraße 122, 81677 München, Deutschland" and potentially break existing apps... hmmh

Using different geocoders will give you different quality but the fields should be the same information. So if it is a POI the name field should contain just its name not the full address and if it is a street, then it could just contain the street name etc. having a field all_name or display_name with all information could be a nice addition though, which we would need for photon too then.

@karussell karussell changed the title Handling Namedifferencies Handling name differences Dec 21, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant