none
Geocoding suddenly stopped returning valid responses for some common addresses RRS feed

  • Question

  • Sometime between 4/20/17 17:00 EST and 4/21/17 17:00 EST the geocoding of a number of addresses in NYC stopped returning successful results.  These are all odd because we have geocoded each of them hundreds of times successfully. 

    1 Centre St, New York,NY 10007  (Interestingly, if changed to 1 Centre, New York, NY 10013, which is the wrong zip code but gives the correct Lat/Long)
    11 Park Pl, New York, NY 10007
    2 Lafayette Street, New York, NY 10007
    280 Broadway, New York, NY 10007

    Note that we had many Queens based addresses that stopped working too.  In those cases the hyphenated house numbers (that are typical and standard practice only for Queens) no longer worked.  We had to remove the hyphen to get them to work.  Ex: 120-55 Queens Blvd, Kew Gardens, NY 11415 now only works as 12055 Queens Blvd, Kew Gardens, NY 11415.

    What could be going on?  Has something changed that we are not aware of?

    Here is an example of the call that is failing.  We tried [1 Centre St ,MANHATTAN,NY 10007]

    POST http://dev.virtualearth.net/webservices/v1/geocodeservice/geocodeservice.svc HTTP/1.1
    Content-Type: text/xml; charset=utf-8
    SOAPAction: "http://dev.virtualearth.net/webservices/v1/geocode/contracts/IGeocodeService/Geocode"
    Host: dev.virtualearth.net
    Content-Length: 1078
    Expect: 100-continue
    Accept-Encoding: gzip, deflate

    HTTP/1.1 100 Continue

    <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body><Geocode xmlns="http://dev.virtualearth.net/webservices/v1/geocode/contracts"><request xmlns:a="http://dev.virtualearth.net/webservices/v1/geocode" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"><Credentials xmlns="http://dev.virtualearth.net/webservices/v1/common"><ApplicationId>BINGKEYMASKED</ApplicationId><Token i:nil="true"/></Credentials><Culture i:nil="true" xmlns="http://dev.virtualearth.net/webservices/v1/common"/><ExecutionOptions i:nil="true" xmlns="http://dev.virtualearth.net/webservices/v1/common"/><UserProfile i:nil="true" xmlns="http://dev.virtualearth.net/webservices/v1/common"/><a:Address i:nil="true" xmlns:b="http://dev.virtualearth.net/webservices/v1/common"/><a:Options><a:Count i:nil="true"/><a:Filters><a:FilterBase i:type="a:ConfidenceFilter"><a:MinimumConfidence>High</a:MinimumConfidence></a:FilterBase></a:Filters></a:Options><a:Query>1 Centre St,MANHATTAN,NY 10007</a:Query></request></Geocode></s:Body></s:Envelope>

    Response
    <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
      <s:Body>
        <GeocodeResponse xmlns="http://dev.virtualearth.net/webservices/v1/geocode/contracts">
          <GeocodeResult xmlns:a="http://dev.virtualearth.net/webservices/v1/geocode" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
            <BrandLogoUri xmlns="http://dev.virtualearth.net/webservices/v1/common">http://dev.virtualearth.net/Branding/logo_powered_by.png</BrandLogoUri>
            <ResponseSummary xmlns="http://dev.virtualearth.net/webservices/v1/common">
              <AuthenticationResultCode>ValidCredentials</AuthenticationResultCode>
              <Copyright>[truncated]Copyright \302\251 2017 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 f</Copyright>
              <FaultReason i:nil="true" />
              <StatusCode>Success</StatusCode>
              <TraceId>e8ed461a87fd42bb8ea01629d6094f14|BN20130719|7.7.0.0|</TraceId>
            </ResponseSummary>
            <a:Results xmlns:b="http://dev.virtualearth.net/webservices/v1/common" />
          </GeocodeResult>
        </GeocodeResponse>
      </s:Body>
    </s:Envelope>

    Friday, April 28, 2017 11:51 PM

Answers

  • I believe the SOAP service end of life announcement was made a year or two ago. Although we have been recommending against using that service for well over 6 years now and only left it on for old legacy apps. 

    Since you are a licensed customer, you should contact the Bing Maps Enterprise support team when you have issues. They will be able to provide more assistance and track issues to resolution for you. You can find contact details at https://www.microsoft.com/maps/support.aspx


    [Blog] [twitter] [LinkedIn]

    Monday, May 1, 2017 9:21 PM
  • I just tested all of these with the Bing Maps REST services and they returned the correct result each time. I suspect there is one of two issues you are encountering.

    • You are using the legacy soap services which are nearing end of life (will be turned off at the end of June). 
    • You are using a basic Bing Maps account/key and are exceeding the free limits which results in your account being rate limited and/or blocked.

    [Blog] [twitter] [LinkedIn]

    Saturday, April 29, 2017 3:56 AM

All replies

  • I just tested all of these with the Bing Maps REST services and they returned the correct result each time. I suspect there is one of two issues you are encountering.

    • You are using the legacy soap services which are nearing end of life (will be turned off at the end of June). 
    • You are using a basic Bing Maps account/key and are exceeding the free limits which results in your account being rate limited and/or blocked.

    [Blog] [twitter] [LinkedIn]

    Saturday, April 29, 2017 3:56 AM
  • Thank you Ricky for your reply. 

    We should be well within our paid usage limits so the second bullet point shouldn't be the case.  And anyway if that were the case we'd see the calls work at times where at other times they didn't.  And were it usage limits then all addresses would fail...which is not the case at all.  So we can rule that one out.

    I think it's possibly the first bullet point. When was this announced?  I found the announcement (https://www.bingmapsportal.com/announcement/index?redirect=true&wa=wsignin1.0) but don't see any posting date except the 2017 copyright mark at the bottom.

    However, that doesn't explain why suddenly, between 4/20/17 and 4/21/17, these particular addresses suddenly stopped working and continue to fail, unless the retirement is already underway before the June 30th date.  Is there any possibility of this, or a way to confirm this is not the case?

    Monday, May 1, 2017 8:36 PM
  • I believe the SOAP service end of life announcement was made a year or two ago. Although we have been recommending against using that service for well over 6 years now and only left it on for old legacy apps. 

    Since you are a licensed customer, you should contact the Bing Maps Enterprise support team when you have issues. They will be able to provide more assistance and track issues to resolution for you. You can find contact details at https://www.microsoft.com/maps/support.aspx


    [Blog] [twitter] [LinkedIn]

    Monday, May 1, 2017 9:21 PM
  • Thanks again Ricky. 

    I have contacted the support team and confirmed that these revealed some data issues with a recent major data update that they implemented.  So with the four addresses listed above, the responses using SOAP should be coming back with a confidence of High but instead suddenly started coming back as Medium, even though they are spot on addresses.  We filter for only high so that has something to do with it.  They are working on resolving the data issues.

    As for using SOAP we will be converting over to REST for our geocoding.

    Wednesday, May 3, 2017 6:12 PM