Skip to main content
Question

PythonCaller - GoogleGeocoder


farfar
Contributor
Forum|alt.badge.img+11
Hi All,    I have been playing with the GoogleGeocoder from the FMEpedia and I am  trying to geocode with cryptokey and clientID. All adresse are rejected with error :

 

"HTTP/1.1 403 Forbidden". 

 

I think the issu is an PythonCaller to retrieve encodedsignature.!

 

  Any help??? .    Thanks an advance.    regards, 

5 replies

david_r
Celebrity
  • July 5, 2013
Hi,

 

 

the Client ID and Crypto Key should not be specified unless you have a paid subscription to Google Maps Business.

 

 

Does it work if you omit these two fields?

 

 

David

farfar
Contributor
Forum|alt.badge.img+11
  • Author
  • Contributor
  • July 5, 2013
Hi,

 

Yes, it works when i omit these two fields. 

 

I det a free clientID and Crypto Key to geocode untill 15000 addresses. 

 

Is it necessary to paid to use clientID and crypt Key for these case?

 

 

Thanks.

 

 


david_r
Celebrity
  • July 5, 2013
Hi,

 

 

have a look at the terms of the Google Geocoder here:

 

 

"Use of the Google Geocoding API is subject to a query limit of 2,500 requests per day. (User of Google Maps API for Business may perform up to 100,000 requests per day.)"

 

 

David

farfar
Contributor
Forum|alt.badge.img+11
  • Author
  • Contributor
  • July 5, 2013
Hi,

 

So, i must paid to use Cleint ID and Crypto Key when i use Google Maps API for Business ? 

 

I need tested it with a free client ID and crypto key before that my company paie to use use it for a large requests (about 10 millions addresses to geocode).

 

Thanks in advance.

 

FarFar 

david_r
Celebrity
  • July 7, 2013
Hi,

 

 

this is a question you should be asking Google, the provider of the webservice.

 

 

But yes, the "Google Maps API for Business" is a product you will have to pay for. You can google it for more info.

 

 

David

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings