Geocoder Transformer - Rejected addresses

Worth a try: URL encoding the address string, because of the spaces. So RIO VISTA would become RIO%20VISTA

How many adresses do you need to geocode? You could also consider the built-in transformer Geocoder with OpenStreetMap. Recommended to use only for small datasets

Alternative approach can be to use a hard coded string in the Street Adress to test whether it works in your workspace.

We have around 168K addresses which have to be geocoded.

Unfortunately we have to use our own locators for this workflow. For the past several years, we’ve had a SystemCaller calling a python file that’s leveraging ArcPy to call an offline locator in FME; however, I was really hoping we could “upgrade” the workflow to be able to use a geocoding service that’s uploaded to Portal using the Geocoder transformer. 

I’ve tried hard coding the string as well - and I got the same results.

I was able to get an HTTPCaller to work against the geocoder service in FME, but it was very slow compared to running the file directly in ArcGIS Pro - yet faster than the SystemCaller which we’ve been using. The downside is that I’m not getting the same functionality that we currently are getting from the SystemCaller or just running it directly in Pro.

Is the Geocoder transformer is doing essentially the same thing as the HTTPCaller?