none
Geocode Service return wrong results RRS feed

  • Question


  • Hi ,

    I am using Silverlight Bing Map Plugin in my application. I am using the GeocodeService for search based on location.
    When I do a search for the location"Issy-les-Moulineaux" in France it gives me two results.

    1. Issy-les-Moulineaux, IdF, France
    (48.823921203613281, 2.2624800205230713)

    2. Issy-les-Moulineaux, IdF, France
    (48.821140289306641, 2.2512400150299072)
     
    This is wrong.This should return only one result. Can you suggest what is the root cause of this wrong result.

    See the WSDL below.

    <?xml version="1.0" encoding="utf-8"?>
    <wsdl:definitions xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:wsa10="http://www.w3.org/2005/08/addressing" xmlns:tns="http://dev.virtualearth.net/webservices/v1/geocode" xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:i0="http://dev.virtualearth.net/webservices/v1/geocode/contracts" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema" name="GeocodeService" targetNamespace="http://dev.virtualearth.net/webservices/v1/geocode" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
      <wsp:Policy wsu:Id="CustomBinding_IGeocodeService_policy">
        <wsp:ExactlyOne>
          <wsp:All>
            <msb:BinaryEncoding xmlns:msb="http://schemas.microsoft.com/ws/06/2004/mspolicy/netbinary1" />
            <wsaw:UsingAddressing />
          </wsp:All>
        </wsp:ExactlyOne>
      </wsp:Policy>
      <wsdl:import namespace="http://dev.virtualearth.net/webservices/v1/geocode/contracts" location="http://dev.virtualearth.net/webservices/v1/metadata/geocodeservice/GeocodeService1.wsdl" />
      <wsdl:types />
      <wsdl:binding name="BasicHttpBinding_IGeocodeService" type="i0:IGeocodeService">
        <soap:binding transport="http://schemas.xmlsoap.org/soap/http" />
        <wsdl:operation name="Geocode">
          <soap:operation soapAction="http://dev.virtualearth.net/webservices/v1/geocode/contracts/IGeocodeService/Geocode" style="document" />
          <wsdl:input>
            <soap:body use="literal" />
          </wsdl:input>
          <wsdl:output>
            <soap:body use="literal" />
          </wsdl:output>
          <wsdl:fault name="ResponseSummaryFault">
            <soap:fault use="literal" name="ResponseSummaryFault" namespace="" />
          </wsdl:fault>
        </wsdl:operation>
        <wsdl:operation name="ReverseGeocode">
          <soap:operation soapAction="http://dev.virtualearth.net/webservices/v1/geocode/contracts/IGeocodeService/ReverseGeocode" style="document" />
          <wsdl:input>
            <soap:body use="literal" />
          </wsdl:input>
          <wsdl:output>
            <soap:body use="literal" />
          </wsdl:output>
          <wsdl:fault name="ResponseSummaryFault">
            <soap:fault use="literal" name="ResponseSummaryFault" namespace="" />
          </wsdl:fault>
        </wsdl:operation>
      </wsdl:binding>
      <wsdl:binding name="CustomBinding_IGeocodeService" type="i0:IGeocodeService">
        <wsp:PolicyReference URI="#CustomBinding_IGeocodeService_policy" />
        <soap12:binding transport="http://schemas.xmlsoap.org/soap/http" />
        <wsdl:operation name="Geocode">
          <soap12:operation soapAction="http://dev.virtualearth.net/webservices/v1/geocode/contracts/IGeocodeService/Geocode" style="document" />
          <wsdl:input>
            <soap12:body use="literal" />
          </wsdl:input>
          <wsdl:output>
            <soap12:body use="literal" />
          </wsdl:output>
          <wsdl:fault name="ResponseSummaryFault">
            <soap12:fault use="literal" name="ResponseSummaryFault" namespace="" />
          </wsdl:fault>
        </wsdl:operation>
        <wsdl:operation name="ReverseGeocode">
          <soap12:operation soapAction="http://dev.virtualearth.net/webservices/v1/geocode/contracts/IGeocodeService/ReverseGeocode" style="document" />
          <wsdl:input>
            <soap12:body use="literal" />
          </wsdl:input>
          <wsdl:output>
            <soap12:body use="literal" />
          </wsdl:output>
          <wsdl:fault name="ResponseSummaryFault">
            <soap12:fault use="literal" name="ResponseSummaryFault" namespace="" />
          </wsdl:fault>
        </wsdl:operation>
      </wsdl:binding>
      <wsdl:service name="GeocodeService">
        <wsdl:port name="BasicHttpBinding_IGeocodeService" binding="tns:BasicHttpBinding_IGeocodeService">
          <soap:address location="http://dev.virtualearth.net/webservices/v1/geocodeservice/GeocodeService.svc" />
        </wsdl:port>
        <wsdl:port name="CustomBinding_IGeocodeService" binding="tns:CustomBinding_IGeocodeService">
          <soap12:address location="http://dev.virtualearth.net/webservices/v1/geocodeservice/GeocodeService.svc/binaryHttp" />
          <wsa10:EndpointReference>
            <wsa10:Address>http://dev.virtualearth.net/webservices/v1/geocodeservice/GeocodeService.svc/binaryHttp</wsa10:Address>
          </wsa10:EndpointReference>
        </wsdl:port>
      </wsdl:service>
    </wsdl:definitions>


    Thanks

    Retheesh R

    Wednesday, November 21, 2012 6:10 AM

Answers

  • This is a known issue that has been logged as a bug by the geocoding team.

    http://rbrundritt.wordpress.com

    Wednesday, November 21, 2012 7:17 PM

All replies

  • This is a known issue that has been logged as a bug by the geocoding team.

    http://rbrundritt.wordpress.com

    Wednesday, November 21, 2012 7:17 PM
  • Hi Richard,

    Thanks for the reply.

    Do you have any information on ETA?

    Is there any workaround for this?

    Thanks

    Retheesh R


    • Edited by Retheesh RP Thursday, November 22, 2012 3:08 PM Added one more question.
    Thursday, November 22, 2012 11:10 AM