Batch geocoding response times

7 posts / 0 new
Last post
adrianlara
Batch geocoding response times

Are there any current, known, and/or suspected issues with sending batch geocoding requests of the max 100 per batch? I keep getting 504's telling me the server didn't respond in time. 

I'm not sure if it matters, but I've recently changed most of my apps request input formats from key-value-pairs to JSON. Also, I'm only returning a maxResults of 1.


adrianlara
Batch geocoding response times

Note that the time out also happens outside of my application - I get a 504 when I send a batch request of 100 addresses within Postman.


MQBrianCoakley
There are no issues currently
There are no issues currently. Can you post a sample request that is failing?

adrianlara
Sorry - I'm not able to pass

Sorry - I'm not able to pass along the actual requests.

I will say I parsed out all of the following special/reserved characters out of addresses before putting the addresses into my JSON object - ;/?:@=&<>#%{}|"\^~[]`
This didn't fix the issue, but it was a change I made along the way towards finding a "fix".

In addition, I lowered my addresses per batch to be 50 and was able to send ~30+ batch requests in a row successfully. I thought to do this because I sent out some manual requests (via Postman) with less than 100 addresses that worked/returned geocoded results. Address counts in the 90's were inconsistent in when they'd return results or fail, so I just dropped it down to 50 to be conservative.

Note, that the addresses in the 30+ batch requests of max size 50 were the same addresses I was trying to run through when the batch size was 100.


MQBrianCoakley
Are the addresses in the US?

Are the addresses in the US? Are they single line or separate components? Are they properly formatted valid addresses?

Batches of 100 addresses should work fine unless three is something unexpected.


adrianlara
The addresses are all in the

The addresses are all in the US. They're single line but vary in how much data they have which leads to extra commas within the address string (i.e 123 Fake Street, , New York City, New York, 00000).


MQBrianCoakley
It sounds like the data is
It sounds like the data is already in 5-box format and then converted to single line. Try using the 5-box format which will eliminate the potential conversion errors and processing time of converting from single line to 5-box by the geocoder.