-
Notifications
You must be signed in to change notification settings - Fork 30
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: autocomplete for osm search #20
Comments
Maybe it would help if we limit this to administrative boundaries, but that's still much too much data to be simply preloaded like the hot projects list… |
osmnames could be an option, although I think they don't directly provide the geometries like nominatim does. |
@tyrasd Have you considered running the Pelias API created by Mapzen or even hosted Pelias geocode.earth? |
thanks for the hint, but as far as I can see, it also doesn't return the full geometry of the search results, does it? |
Ah, sorry, I misunderstood the problem. Pelias returns the Mapzen |
after digging around a bit, I found https://whosonfirst.org/browse/ which seems to be still operational and offer the kind of stuff we would need, for example https://data.whosonfirst.org/101/751/119/101751119.geojson |
Autocomplete should also work for arbitrary region search (like for the hot projects). There are a couple of osm-based search engines (photon, mapzen, mapbox) with autocomplete support, but none of these provides the full geometry of the search results (e.g. an OSM-object-id to fetch the full geometry from). This currently leaves only nominatim, which on the other hand sadly doesn't support autocomplete.
Hints/Ideas for how to tackle this are welcome! 🙇
The text was updated successfully, but these errors were encountered: