-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Pluggable geocoder in feature_list.js #3711
Comments
Good suggestion, I agree... |
Could the current nominatim service be used if we add a function geocode?
And in nominatim.js
|
Btw, what's the correct/best way of making a service pluggable for the developer without modifying the library code? |
Everything in the So after we fix the issues in this ticket, it should ideally be as easy as a line like this before your page initializes the iD context object. iD.services.geocoder = replacementService; |
Great! And I just want to thank you for the great work you and everyone else that has contributed to iD has done! |
We are using Pelias as a geocoder over openstreetmap data and would like to extract the functionality in feature_list.js to be able to use a pluggable geocoder instead of directly calling nominatim.
I'm thinking that it could be a service that can be setup in the context in the same way as the nominatim service.
A simple API like the one below could be enough
The simplest way to do introduce this would be to:
I know that nominatim is more or less the standard but it would be nice to be pluggable in this regard and I don't think it would be intrusive to the users in any way. The default service would of course be Nominatim.
The text was updated successfully, but these errors were encountered: