none
Batch Geocoder Limitation

    Question

  • I read in few places that I can have a file 100mb that may contain upto 200,000 address to geocode. Is this for the paid version?

    I have a basic key and would like to geocode approximately 1000 addresses a day, at first i sent few (using a sample) it worked fine, then I tried doing a 172KB file (containing approximately 900), got a 503, tried the sample with few again, it worked. now even the sample does not work, I assume I exceeded some limitation either the number of batch submissions or something else, I currently do not have any pending jobs, all the ones that were sent were completed


    • Edited by .NETMaster Wednesday, October 30, 2013 2:54 AM
    Wednesday, October 30, 2013 2:54 AM

Answers

  • Yes, Enterprise licensed customers can upload 200,000 locations at a time. Non-licensed customers can only upload 50 locations at a time.

    If this is for a mobile or Windows 8 app then I suggest simply using the REST geocoding service rather than the batch geocoder. The processing time will likely be slightly faster with the REST services on such a small data set and the free terms of use for mobile and Windows 8 apps if 50,000 transactions a day.


    http://rbrundritt.wordpress.com

    Wednesday, October 30, 2013 8:45 AM
  • If you are using a basic key you will find that if you hammer the service with a lot of calls that many of them will return with empty results. The reason for this is that if you access the service with a frequency of requests which is likely to exceed the 50,000/day limit it will rate limit your results. So, with that, if you make 35 requests per minute or less, you shouldn't have any issues. That said, rate limiting typically is only implemented when our servers are under a lot of load and priority has to be given to paying customers.

    http://rbrundritt.wordpress.com

    Thursday, October 31, 2013 9:28 AM

All replies

  • Yes, Enterprise licensed customers can upload 200,000 locations at a time. Non-licensed customers can only upload 50 locations at a time.

    If this is for a mobile or Windows 8 app then I suggest simply using the REST geocoding service rather than the batch geocoder. The processing time will likely be slightly faster with the REST services on such a small data set and the free terms of use for mobile and Windows 8 apps if 50,000 transactions a day.


    http://rbrundritt.wordpress.com

    Wednesday, October 30, 2013 8:45 AM
  • how many rest calls can i do per second? is there a limitation?

    The data will be used for a mobile app, i am storing it in sql server then serve it on a mobile app

    Wednesday, October 30, 2013 6:51 PM
  • If you are using a basic key you will find that if you hammer the service with a lot of calls that many of them will return with empty results. The reason for this is that if you access the service with a frequency of requests which is likely to exceed the 50,000/day limit it will rate limit your results. So, with that, if you make 35 requests per minute or less, you shouldn't have any issues. That said, rate limiting typically is only implemented when our servers are under a lot of load and priority has to be given to paying customers.

    http://rbrundritt.wordpress.com

    Thursday, October 31, 2013 9:28 AM