We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Consider using Nominatim for the search component.
The text was updated successfully, but these errors were encountered:
If we adhere to the Usage Policy, why not? It shall not be hard to implement -- adding a new parser in the components/search.service shall be sufficient. It can be then configured (enabled) via the searchProvider param in HsConfig. The Nominatim API is described here: https://nominatim.org/release-docs/develop/api/Search/
searchProvider
Sorry, something went wrong.
Hm, the biggest road block would probably be the auto-complete search. Never mind, it was just an idea from JiKa.
There are also commercial alternatives. Most of them have a free tier which may be suitable for us in like 99 % cases. See https://www.geoapify.com/pricing/ or https://rapidapi.com/GeocodeSupport/api/forward-reverse-geocoding/pricing . An app would specify an authorisation token anyway, so if some HSL app would need more geocoding search, it can go into a paid plan as needed.
jmacura
FilipLeitner
fzadrazil
No branches or pull requests
Idea/Question
Consider using Nominatim for the search component.
The text was updated successfully, but these errors were encountered: