Geocoder question

[vchernetsky]

What is the long term strategy for OTP geocoder? I'm not talking about built in geocoder, but rather a proxy to Google, Bano and other geocoders. We are at AmigoCloud consider using OTP /geocode endpoint, but we need Bing geocoder. So I added BingGeocoder following the same framework as Google, Bano and GeocodeResource. But I'm wondering if this is the right direction long term. Some of that code doesn't seem to be used.

I guess I'm wondering what are you plans for maintaining those geocoders and if you are going to maintain that architecture or not. If so, would you be interested in us contributing BingGeocoder back to OTP?

[laurentg]

I'm not sure there is really a long-term plan for the current geocoder infrastructure; OTP being an open-source project the intrinsic plan is to follow what people are willing to do with the project :)

I would say that as long as the code meet a certain quality criteria a new geocoder implementation would be welcomed, especially that Bing is a well-known service. But of course this is only my personal opinion. As for the usage of geocoders, I do not know how often they are used, as the server side of OTP do not rely on it to run, only the provided default client will use it by default.

You may want to ask this question on the OTP mailing list instead, I'm not sure the issue tracker is followed by a lot of people.

[vchernetsky]

Thanks Laurent! This makes it clear. I'll keep using OTP geocoder.