I have a number of google geocoder transformers in sequence which amongst other things take in the rejected outputs from the previous geocoder transformer. This works fine apart from the first geocoder in the sequence which doesnt carry a rejected count despite not passing the full input count.
Has anyone come across this before?
Any help appreciated!
I have seen this issue before.
The geocoder can not handle records that are delivered to it too fast.
Solved the issue using the Decelerator transformer.
Give it a try.
Another issue to consider is the limitation of the geocoder service to handle too many requests (depending on if you are using business key or not)
Thanks for the responses @erik_jan @itay- I'm aware of the daily free limits so always keeping under those; however even at a 20second delay per feature using the decelerator (only with a test 100 features), I still don't receive any rejected outputs (despite there being some as not everything is being passed through). Any slower delay will not be efficient for my task....
Do either of you have any other thoughts?
Thanks
You can always try the new Geocoder transformer in the 2017 Beta:
http://www.safe.com/support/support-resources/fme-downloads/beta/
Hi @itay - the 2017 beta generic geocoder seems to sort the problem - many thanks!