none
Bing Maps Rest Service call delivers incomplete result

    Question

  • Hello,

    I am using the Bing Maps Rest Service for about two years now, almost without any  errors. Since last week we have an issue we can't explain.

    If you call the service this way you get two result variations.

    http://dev.virtualearth.net/REST/v1/Locations/49626%20DE?key=BingMapsKey&c=de

    Param 1 (49626%20DE) is a german zip code 

    Param 2 is a place holder for our key

    Result 1

    {"authenticationResultCode":"ValidCredentials","brandLogoUri":"http:\/\/dev.virtualearth.net\/Branding\/logo_powered_by.png","copyright":"Copyright © 2014 Microsoft and its suppliers. All rights reserved. This API cannot be accessed and the content and any results may not be used, reproduced or transmitted in any manner without express written permission from Microsoft Corporation.","resourceSets":[{"estimatedTotal":0,"resources":[]}],"statusCode":200,"statusDescription":"OK","traceId":"067f5423c29242b69069c91d6e460563|DB30012639|02.00.107.2300|DB3SCH010033011"}

    Result 2

    {"authenticationResultCode":"ValidCredentials","brandLogoUri":"http:\/\/dev.virtualearth.net\/Branding\/logo_powered_by.png","copyright":"Copyright © 2014 Microsoft and its suppliers. All rights reserved. This API cannot be accessed and the content and any results may not be used, reproduced or transmitted in any manner without express written permission from Microsoft Corporation.","resourceSets":[{"estimatedTotal":1,"resources":[{"__type":"Location:http:\/\/schemas.microsoft.com\/search\/local\/ws\/rest\/v1","bbox":[52.526575,7.607123,52.662869,7.810701],"name":"49626, NI, Deutschland","point":{"type":"Point","coordinates":[52.594722,7.708912]},"address":{"adminDistrict":"NI","adminDistrict2":"Osnabrück (Landkreis)","countryRegion":"Deutschland","formattedAddress":"49626, NI, Deutschland","locality":"Bippen","postalCode":"49626"},"confidence":"High","entityType":"Postcode1","geocodePoints":[{"type":"Point","coordinates":[52.594722,7.708912],"calculationMethod":"Rooftop","usageTypes":["Display"]}],"matchCodes":["Good"]}]}],"statusCode":200,"statusDescription":"OK","traceId":"9f598bd01d0f4c51afc526bb03265328|DB30012639|02.00.107.2300|DB3SCH010012827, DB3SCH010033711, DB3SCH010040314"}

    Result 2 is what we would expect.

    If we use a call without localization info (http://dev.virtualearth.net/REST/v1/Locations/49626?key=BingMapsKey) it has also these results.

    We get the same different results if we use it in javascript.

    http://dev.virtualearth.net/REST/v1/Locations/49626 DE?output=json&jsonp=searchServiceCallback&key=BingMapsKey&c=de

    Could you explain what is suddenly wrong with our call?

    Kind regards

    Knut Freyer

    Saturday, February 15, 2014 1:30 PM

Answers

  • I'm going to guess you are using a basic key and are being rate limited. If you look in the header of the response you will see a flag that indicates this. This is documented at the bottom of this page: http://msdn.microsoft.com/en-us/library/ff701703.aspx This means that your account is generating transactions at rate greater than the free terms of use. If you have an enterprise license then use an Enterprise key to correct this.

    http://rbrundritt.wordpress.com

    Saturday, February 15, 2014 3:30 PM
  • Free accounts are not always rate limited. Rate limited is usually implemented when there is a high volume of traffic on the servers. This is done to prioritize requests from Enterprise (paying) customers. Rate limiting can happen at the account level which means that creating a new key or using a different one might not make a difference.

    http://rbrundritt.wordpress.com

    Tuesday, February 18, 2014 9:51 AM

All replies

  • I'm going to guess you are using a basic key and are being rate limited. If you look in the header of the response you will see a flag that indicates this. This is documented at the bottom of this page: http://msdn.microsoft.com/en-us/library/ff701703.aspx This means that your account is generating transactions at rate greater than the free terms of use. If you have an enterprise license then use an Enterprise key to correct this.

    http://rbrundritt.wordpress.com

    Saturday, February 15, 2014 3:30 PM
  • Thanks for your quick answer.

    I have checked this out with different keys. At first with the standard key, then with one that is not used very often.

    But first I will check the response header and then I will report the result here.

    Sunday, February 16, 2014 10:36 AM
  • I have checked the header response and  the info value is sometimes  1, sometimes 0. I have prooved this with a new key, which definitly not exceeds the free terms of use. And it shows the same behaviour. The article says this can happen if the servers processing service requests are overloaded.  So what is the correct interpretation? Do you have any suggesstion?  

    Monday, February 17, 2014 9:13 PM
  • I have the same problem: I never had problems in the past, it started during last week for me - just like in Freyer's case, I also give German addresses as input and I get similar mixed results.

    Too much transactions? My website statistics don't show an unusual amount of activity. Nowhere near a peak. However https://www.bingmapsportal.com/ isn't working for me at the moment and I can't access the API usage reports. The page loads for ages and then gives a 404 error.

    I would use an Enterprise key if I were to be sure this would solve the problem, but with the amount of information I have it is difficult to say. If too much transactions were the problem - why now, when there is no unusual amount of activity on my website? And how would this explain the fact that multiple people (I met a few on twitter) seem to have the exact same problem starting at the exact same time?

    Tuesday, February 18, 2014 3:07 AM
  • We just started experiencing the same issue (except with US addresses). Months of usage with no problems, and now without any change in our traffic or usage, we're starting to get these rate limit failures.
    Tuesday, February 18, 2014 3:12 AM
  • Free accounts are not always rate limited. Rate limited is usually implemented when there is a high volume of traffic on the servers. This is done to prioritize requests from Enterprise (paying) customers. Rate limiting can happen at the account level which means that creating a new key or using a different one might not make a difference.

    http://rbrundritt.wordpress.com

    Tuesday, February 18, 2014 9:51 AM