Skip to main content
  • EN

We are using HTTPCaller to batch geocode thousands of records, but we are running into an issue with special characters that are causing the HTTPCaller transformer to fail. As a workaround, we've been using multiple (20+ at this point) String Replacement transformers to catch and modify the special characters before going to HTTPCaller.

 

Geocoding the same input table using the Geocode Table wizard in ArcGIS Pro completes without issue.

 

Are there certain characters that HTTPCaller cannot handle, or is there a better or more robust workaround than using String Replacements? Can anyone offer insight into why the input table geocodes successfully in ArcGIS Pro without any data sanitization/cleansing in ArcGIS Pro, but fails in HTTPCaller?

 

Thanks in advance for any help you can over.

 

@natalie_campos​ @acueva​ 

First of all, try using FME 2022+ if possible, as it has extended unicode support.

Secondly, make sure to URL-encode your strings properly, as there are some cases where the HTTPCaller won't do it for you automatically:

imageFor debugging HTTP transmissions, I highly recommend using Telerik Fiddler.

First of all, try using FME 2022+ if possible, as it has extended unicode support.

Secondly, make sure to URL-encode your strings properly, as there are some cases where the HTTPCaller won't do it for you automatically:

imageFor debugging HTTP transmissions, I highly recommend using Telerik Fiddler.

Thank you @david_r​. We'll look into this recommendation on our side. I appreciate your help.

Thank you @david_r​. We'll look into this recommendation on our side. I appreciate your help.

For the record, this change resolved our issue. Thank you.

Reply


Community Stats

30,117
Posts
114,317
Replies
37,748
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.