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

geocoding.type locality seems to vague #17

Open
pbougue opened this issue Oct 27, 2016 · 1 comment
Open

geocoding.type locality seems to vague #17

pbougue opened this issue Oct 27, 2016 · 1 comment

Comments

@pbougue
Copy link

pbougue commented Oct 27, 2016

At Kisio/CanalTP (on navitia API), we are integrating Points Of Interest from osm into our geocoder, trying to stick to the geocodejson-spec as much as possible.
We noticed that you use locality on api-adresse for example on Tour Eiffel, but it seems to vague and not fitting very well, so we would like to introduce poi to the list of possible geocoding.type.
So wanted to discuss about the opportunity of that...

@pbougue
Copy link
Author

pbougue commented Dec 22, 2016

We see 2 possibilities:

  • add a subtype like locality_type
  • extend type and add poi and public_transport:stop_area(which sticks to OSM)

For now on https://github.com/CanalTP/mimirsbrunn we will go with the second option.

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