[ 
https://issues.apache.org/jira/browse/CAMEL-12554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16506704#comment-16506704
 ] 

Juraj Borza commented on CAMEL-12554:
-------------------------------------

Hi,

I'd like to take up this issue. 

Note: camel-geocoder uses the soon-to-be-terminated free geoip in case the 
location is set to 'current' with this:

 
{code:java}
String json = 
exchange.getContext().getTypeConverter().mandatoryConvertTo(String.class, new 
URL("https://freegeoip.net/json/";));{code}
 

For the proper geocoding it's using [https://code.google.com/p/geocoder-java/] 
which is using Google Places API 
([https://developers.google.com/maps/documentation/javascript/reference/3/geocoder|https://developers.google.com/maps/documentation/javascript/reference/3/geocoder)]),
 which coincidentally is going to have _New pricing changes will go into effect 
starting July 16, 2018._ This means that it won't be possible to use the 
service without an API key. 

The API key support seems to be present in the library camel-geocoder uses, and 
as the users will have to use a Google API key, we could switch to Google 
Geolocation API for the 'current location' lookup as well using the same API 
key as opposed to switching to ipstack.com, where an API key is necessary as 
well.

In addition, there seems to be a community supported client library for Google 
Maps API Web Services at 
[https://github.com/googlemaps/google-maps-services-java] - which might be a 
better choice than the original geocoder-java one.

Cheers,

Juraj

> camel-geocoder - Use new API
> ----------------------------
>
>                 Key: CAMEL-12554
>                 URL: https://issues.apache.org/jira/browse/CAMEL-12554
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-geocoder
>            Reporter: Claus Ibsen
>            Priority: Major
>             Fix For: 2.22.0
>
>
> See
> [https://github.com/apilayer/freegeoip#readme]
> There is a newer API. Not sure if we have migrated already, but as the old 
> API is terminated in July 2018 then we dont have so much time.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to