none
Poor consistency from the Bing SOAP Geocoder/Reverse Geocoder RRS feed

  • Question

  • Hi Forum,

    I'm a developer working with Bing Map API's here in Melbourne Australia, and I've recently switched over from the older MapPoint web services to the new SOAP APIs.

    What I and my users are noticing is that the new SOAP geocoder/reverse geocoder disagree with each other very often, to the point that the reverse geocoder is basically useless.

    The application that demonstrates the problem allows the user to drag a few pins on a map and see the associated address when they stop dragging. It also allows them to search for an address with the searched location being highlighted on the map.

    I'm getting results from the geocoder that indicate rooftop accuracy, however the reserve geocoder returns only "interpolated" values. The geocoder seems to give accurate results (compared to the aerial view or to address boundary data from an alternative mapping client) however the reverse geocoder is consistantly off by 2 to 20 house numbers, across my entire working region, and tends to return only a street name (no house number) for a large sub-set of cases. 

    My Questions:

    Is there any chance to get the two parts of the service to be running from the same data set for Melbourne, Australia? - As the geocoder obviously has the better data.

    I've already had to switch to the REST router to get access to features not provided by the SOAP router (side of street, avoid tolls), so can anyone tell me if the REST reverse geocoder is going to do a better job than the SOAP reverse geocoder? - I know this sounds silly, but my experience with the router has shown it could be true.

    It seems to me that the reverse geocoder has gotten much worse over the last week or so, have there been major changes for the Australian data, and if so can someone please roll them back?

    I know the mapPoint services are going end-of-life any time now, but is there any chance that they can be kept alive until the new services improve in quality?

    Regards

    LostDev


    Anybody?
    • Edited by LostDev Monday, September 19, 2011 10:42 AM Vague hope of a response
    • Moved by Ricky_Brundritt Saturday, March 10, 2012 11:10 AM (From:Bing Maps: Map Control and Web services Development)
    Tuesday, September 6, 2011 12:50 PM

Answers

  • I would definately recommend using the REST services. The SOAP services have not been updated in several years. The REST services are the main services for Bing Maps and should always be used instead of the SOAP services.
    http://rbrundritt.wordpress.com
    Wednesday, September 21, 2011 9:22 AM

All replies

  • I would definately recommend using the REST services. The SOAP services have not been updated in several years. The REST services are the main services for Bing Maps and should always be used instead of the SOAP services.
    http://rbrundritt.wordpress.com
    Wednesday, September 21, 2011 9:22 AM
  • Hi Richard and thanks for the response,

     I was able to test that the REST services were given the same results as the SOAP service by plugging my key and example lat/long pairs into the URL, still I will switch over when I can.

    My problem now is that the reverse geocoder now seems to be down for the count. I am getting a valid response with either 0 entries or blank data for every location in Australia that I have tested. It has been like this for at least 6 hours, as my testers reported the problem at 2pm and it is now 8pm AEST.

    To make sure it is not my code, I checked with the REST geocoder. For example:

    http://dev.virtualearth.net/REST/v1/Locations/-37.8663259,144.980327?o=xml&key=YourKeyHere

    Returns:

    <?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 © 2011 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>934c8ed651114dd4b5b132e6a571d6aa|BAYM001214|02.00.159.1700|BY2MSNVM001073, BY2MSNVM001077, BY2MSNVM001076</TraceId>
    - <ResourceSets>
    - <ResourceSet>
      <EstimatedTotal>0</EstimatedTotal>
      <Resources />
      </ResourceSet>
      </ResourceSets>
      </Response>
     
    That location is in a residential street that was working the other day.
     
    Thursday, September 22, 2011 10:14 AM
  • This is a known issue that our team is currently working on correcting.
    http://rbrundritt.wordpress.com
    Thursday, September 22, 2011 12:35 PM
  • Hi All,

    Is there any update or resolution for this fault?

    We currently use Bing maps geocoder for the reverse lookup of GPS positions for in vehicle monitoring systems and a large majority of the locations provided are showing up in Japan when the devices are actually located in Australia.

     

    Sunday, September 25, 2011 10:21 PM