none
Why am I getting random geocoding failures? RRS feed

  • Question

  • So in performing a number of geocodes using unstructured queries, I'm getting random failures (missed geocodes, zero results). Take this example:

    http://dev.virtualearth.net/REST/v1/Locations?include=queryParse&query=111%20genesee%20st,%20buffalo%20ny,%2014202&key=<insert key here>

    Run that in a browser. You'll likely get an answer on the first request. Now hit f5. Maybe try it a few times. Doesn't have to be fast, we're not trying to spam the service. But hit it a few times. Somewhere in the first 10 or so there will be a failure. You'll get zero results back.

    Now if you have a series of addresses, and run each one in sequence, you'll miss a few. It's as bad as 10 out of 100 - so it's not that I'm hitting the same address over and over again, because I'm getting failures with a completely new address.

    Why does this happen? My guess is maybe some sort of load balancing roulette is going on and I'm getting the bad server now and then. But it makes creating a reliable application *really* difficult.

    (ps, it's pretty funny that your "OMG NO LINKS UNTIL VERIFIED" freakout includes URLs that go TO YOUR OWN SERVICE)

    Wednesday, February 26, 2014 1:25 PM

Answers

  • This has been answered several times. If you are getting empty results you are likely being rate limited. Rate limiting occurs when the frequency of request are such that your account could exceed the free terms of use. Rate limiting also occurs on all trial and basic (non-enterprise) keys when the service is under a lot of load. This is done to prioritize Enterprise (licensed/paying customer) requests. If you look at the header of the response you will see a flag there that indicates the request has been rate limited. This is documented on this page: http://msdn.microsoft.com/en-us/library/ff701703.aspx

    http://rbrundritt.wordpress.com

    Wednesday, February 26, 2014 3:22 PM

All replies

  • This has been answered several times. If you are getting empty results you are likely being rate limited. Rate limiting occurs when the frequency of request are such that your account could exceed the free terms of use. Rate limiting also occurs on all trial and basic (non-enterprise) keys when the service is under a lot of load. This is done to prioritize Enterprise (licensed/paying customer) requests. If you look at the header of the response you will see a flag there that indicates the request has been rate limited. This is documented on this page: http://msdn.microsoft.com/en-us/library/ff701703.aspx

    http://rbrundritt.wordpress.com

    Wednesday, February 26, 2014 3:22 PM
  • Thanks for the answer. I did try the search bar but I don't speak Microsoft apparently; I couldn't find anything.

    It's too bad the no-result answer is not more informative - it would he helpful to know whether or not my requests are limited because of something I'm doing or if  the service is under a lot of load. That would be good to know.

    Wednesday, February 26, 2014 4:05 PM