Since I upgraded to 3.2, the Google GeoCoding node no longer seem to work. In previous verions I used the Google node, and it worked flawlessly, but since the 3.2 upgrade I have recieved the following error:
"ERROR GoogleAddressGeocoder 0:3 Execute failed: ws.palladian.extraction.location.geocoder.GeocoderException: Received status code OVER_QUERY_LIMIT"
Did I incorrectly configure KNIME to use this node? Have I reached a cumulative limit of my queries using this node? Has Google's terms changed?
I was able to get the MapzenGeocoder to work, but if possible I would like to have more than one option.
Good suggestion, but this occurs on the first run of the day. I use to run into this limit prior to upgrading so I was well aware of it. Thanks for your comment, but I afraid it's something else
sorry, I have just re-tried with a larger dataset and can confirm the error. I'll see whether there is a possible fix, but this will probably take some while. Thanks for reporting so far!
I think Google has become more restrictive now and allow the 2,500 queries only with a valid API key. This is just an assumtion though. However, we currently do not allow supplying an API key for the node.
Feel free to check out the other options as mentioned above (Mapquest, Mapzen).
true, Mapzen is dead and we will remove / deprecate the node in a future release of the Palladian nodes.
The task to add API key support to the Google Geocoder is on my list. I’ve also heard this wish several times during the current KNIME Summit here in Berlin. I’ll try to release an update soon.