none
Sporadic results with reverse geocoding endpoint (sometimes results, sometimes not) RRS feed

  • Question

  • Hi,

    I'm trying to use the reverse geocoding endpoint.  About 30% of the time the response includes a result, 70% of the time it does not.

    See examples below.

    Is this a known issue?

    Thanks,

    Scott

    URL: 

    http://dev.virtualearth.net/REST/v1/Locations/47.64054,-122.12934?o=xml&key=[your-bing-maps-key]

    Empty Response (about 70%):

    <?xml version="1.0" encoding="utf-8"?>
    <Response xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.microsoft.com/search/local/ws/rest/v1">
      <Copyright>Copyright © 2012 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.</Copyright>
      <BrandLogoUri>http://dev.virtualearth.net/Branding/logo_powered_by.png</BrandLogoUri>
      <StatusCode>200</StatusCode>
      <StatusDescription>OK</StatusDescription>
      <AuthenticationResultCode>ValidCredentials</AuthenticationResultCode>
      <TraceId>7af2b0886cbb4ddcab3872c201f9e507|EWRM003314|02.00.82.300|EWRMSNVM003155</TraceId>
      <ResourceSets>
        <ResourceSet>
          <EstimatedTotal>0</EstimatedTotal>
          <Resources />
        </ResourceSet>
      </ResourceSets>
    </Response>

    Filled Response (about 30%):

    <?xml version="1.0" encoding="utf-8"?>
    <Response xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.microsoft.com/search/local/ws/rest/v1">
      <Copyright>Copyright © 2012 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.</Copyright>
      <BrandLogoUri>http://dev.virtualearth.net/Branding/logo_powered_by.png</BrandLogoUri>
      <StatusCode>200</StatusCode>
      <StatusDescription>OK</StatusDescription>
      <AuthenticationResultCode>ValidCredentials</AuthenticationResultCode>
      <TraceId>4c2069db3a7b46aab77685eac6151436|EWRM001660|02.00.82.300|EWRMSNVM002558, EWRMSNVM003175</TraceId>
      <ResourceSets>
        <ResourceSet>
          <EstimatedTotal>1</EstimatedTotal>
          <Resources>
            <Location>
              <Name>1 Microsoft Way, Redmond, WA 98052</Name>
              <Point>
                <Latitude>47.640570402145386</Latitude>
                <Longitude>-122.12937377393246</Longitude>
              </Point>
              <BoundingBox>
                <SouthLatitude>47.636707684574709</SouthLatitude>
                <WestLongitude>-122.13701709146854</WestLongitude>
                <NorthLatitude>47.644433119716062</NorthLatitude>
                <EastLongitude>-122.12173045639638</EastLongitude>
              </BoundingBox>
              <EntityType>Address</EntityType>
              <Address>
                <AddressLine>1 Microsoft Way</AddressLine>
                <AdminDistrict>WA</AdminDistrict>
                <AdminDistrict2>King Co.</AdminDistrict2>
                <CountryRegion>United States</CountryRegion>
                <FormattedAddress>1 Microsoft Way, Redmond, WA 98052</FormattedAddress>
                <Locality>Redmond</Locality>
                <PostalCode>98052</PostalCode>
              </Address>
              <Confidence>Medium</Confidence>
              <MatchCode>Good</MatchCode>
              <GeocodePoint>
                <Latitude>47.640570402145386</Latitude>
                <Longitude>-122.12937377393246</Longitude>
                <CalculationMethod>Interpolation</CalculationMethod>
                <UsageType>Display</UsageType>
                <UsageType>Route</UsageType>
              </GeocodePoint>
            </Location>
          </Resources>
        </ResourceSet>
      </ResourceSets>
    </Response>




    Tuesday, October 23, 2012 7:51 PM

Answers

  • I suspect you are using a basic or trial key. If that is the case then you are likely making a lot of requests and being rate limited. I was only able to reproduce this using a basic key and making a lot of requests in a short period of time.

    http://rbrundritt.wordpress.com

    Wednesday, October 24, 2012 3:06 PM

All replies

  • I'm currently testing and finding about 1 out ever 5or so requests are returning an empty result. I've escalated this to our development team for investigation.

    http://rbrundritt.wordpress.com

    Wednesday, October 24, 2012 11:15 AM
  • I suspect you are using a basic or trial key. If that is the case then you are likely making a lot of requests and being rate limited. I was only able to reproduce this using a basic key and making a lot of requests in a short period of time.

    http://rbrundritt.wordpress.com

    Wednesday, October 24, 2012 3:06 PM
  • It can't be rate limiting, since the first few calls I made to the endpoint resulted in the erratic response.  It was only after a few unsuccessful attempts that I was able to get a successful one.

    That, and I just tried 3 requests today, the third one of which failed.  I hope it's not rate limiting at 3 requests.

    It must be something else.  I also noted an "Internal Server Error" that was returned with one of the responses.  The other responses are a mix of the examples above, even with the same URL.

    Richard, do you think there might be a bad server in the pool that handles these requests, causing the sporadic errors?

    - Scott

    Wednesday, October 24, 2012 8:17 PM