i created a web app (using flex api) that does batch geocoding. It loads an csv file into a datagrid, run the batch geocode, sends the addresses in an array and extract the result in a datagrid. It shows the result in the map.
The app is using an address locator rest service deployed in our server from a composite address locator(it is not using any online address geolocator)
However here is the issue:
when the app geocodes about 200 records in a batch, it brings the result (about 1.5 minute) and loads all points to the grid and the map. when it tries to do geocode about 900 records, it keeps busy for about 2 minute and brings a error message ("unexpected < encountered at location 5" faultcode:null, faultdetail:null)..However if i try a second time, it brings same message. I try third time, it brings the results.
It looks like when it errors out (i donot know exactly what error it is), it does not bring any record. but the records that are already geocoded, are in the cache memory. A second try brings more geocode results on the cache memory but since all records are not geocoded, it brings error message. A third try reaches these cache memory faster and does the remaining geocodes.
I need to know is there a better way for batch geocoding:
1) whether any server side optimization
2) any way to catch the error before it is timeout and get the result that are being done
3) any other way to send the input (such as creating multiple tasks with smaller inputs).
Thanks
