Reverse geocode issue RRS feed

  • Question

  • Hi,

    We are getting incorrect when do reverse geocode.

    First we do the geocode request to get the geocode. We have used following address.

    Street 1:            1184, D'evereux

    City:                   Boucherville

    State:                QC  

    Postal Code:    J4B 7T3

    While geocoding the above address we are getting the following coordinates: 

    Co ordinates

    Latitude:            45.57578

    Longitude:        -73.43609

    And while reverse geocoding using the above coordinates we are getting the following address:


    Street 1:            1184, D'evereux

    City:                   Longueuil

    State:                QC  

    Postal Code:    J4B

    City is getting changed to Longueuil, which is incorrect city must be Boucherville.

    Can you please let us know how to resolve this issue.



    Thursday, October 4, 2018 2:21 PM

All replies

  • Hello Balasaheb,

    Please try the full qualified address:

    Street: 1184 Rue d'Évreux

    City: Boucherville

    State: QC

    Postal:J4B 7T3

    Country: Canada

    NOTE: If this is still incorrect for you, please go to and use the feedback button on the lower left to explain what is incorrect.



    Thursday, October 4, 2018 3:54 PM
  • Hi,

    Thanks for your reply but it did not work. Can you please give us another solution to resolve this issue.




    Friday, October 12, 2018 8:44 AM
  • Hi Balasaheb,

    Can you provide the call you are making?  Did you give the feedback at the link above as I suggested?  Can you provide clarity as to what is incorrect after calling with the qualified address?



    Sunday, October 14, 2018 4:40 AM
  • Hi,

    Here is code that we are using.

    private void button16_Click(object sender, EventArgs e)        {

               // GeoCode("1184, D'evereux Boucherville, QC J4B 7T3", "<BingMapKey>");<o:p></o:p>

               // GeoCode("1184, D'evereux Boucherville, QC J4B 7T3,Canada", "<BingMapKey>"); 

                BingLocationResponse result = null;<o:p></o:p>

                string _bingMapsRESTUri = "{0}?key={1}"; 

                string formattedLocation = string.Format("{0},{1}", 45.57578, -73.43609); //bing maps requires Lat,Long  <o:p></o:p>

                string bingMapsKey = string.Empty;<o:p></o:p>

                var request = HttpWebRequest.Create(string.Format(_bingMapsRESTUri, formattedLocation, "<BingMapKey")) as HttpWebRequest; 

                try            {

                    using (var response = request.GetResponse() as HttpWebResponse)<o:p></o:p>


                        result = GetResult(response);<o:p></o:p>

                    }                <o:p></o:p>


                catch (Exception ex)<o:p></o:p>


                }            <o:p></o:p>



            public BingLocationResponse GetResult(HttpWebResponse response)<o:p></o:p>


                BingLocationResponse location = null;<o:p></o:p>

                if (response != null && response.StatusCode == HttpStatusCode.OK)<o:p></o:p>


                    //Deserialize the response and provide the address to the callback action  <o:p></o:p>

                    using (var stream = response.GetResponseStream())<o:p></o:p>


                        DataContractJsonSerializer serialiser = new DataContractJsonSerializer(typeof(BingLocationResponse));<o:p></o:p>

                        location = serialiser.ReadObject(stream) as BingLocationResponse;<o:p></o:p>



                return location;<o:p></o:p>


    We got the following response:

    addressLine:         "1184 Rue d'Évreux"

    adminDistrict: "QC"

    adminDistrict2: "Longueuil"

    countryRegion: "Canada"

    formattedAddress: "1184 Rue d'Évreux, Longueuil, QC J4B, Canada"

    locality:                 "Longueuil"

    postalCode:         "J4B"

    Can you please check and let us know how to resolve this issue.




    Monday, October 29, 2018 12:36 PM
  • Hi Balasheb,

    I have deleted your Bing Maps Key from your posting above.  You should not publish your key on a website like this.

    Note: As you are an Enterprise customer, you should follow up and use that method to report your error.



    Tuesday, October 30, 2018 5:15 PM
  • Hi,

    We are using batch geocode to get the latitude and longitude from address as shown in below link.

    It is working correctly for some of the address but some the address it gives incorrect results.

    For example for below address

    162 W 6th Campo CO 81029 US

    Here is the request that we have created

    <GeocodeFeed><GeocodeEntity Id='0b17fd08-15dd-e811-80e1-00155d061c08' xmlns=''>                     <GeocodeRequest Culture='en-US'>                     <Address  AddressLine="162 W 6th" District="" Locality="Campo" AdminDistrict="CO" CountryRegion="US" PostalCode="81029" FormattedAddress="162 W 6th  Campo CO  81029 US"/>                     <ConfidenceFilter MinimumConfidence='Medium'/>                                        </GeocodeRequest>                     </GeocodeEntity>

    and here is the response 

    <Address AddressLine="162 W 6th St" AdminDistrict="TX" CountryRegion="United States" District="Wharton County" FormattedAddress="162 W 6th St, El Campo, TX 77437" Locality="El Campo" PostalCode="77437" xmlns="" /><InterpolatedLocation Latitude="29.1900297653596" Longitude="-96.2651888032593" xmlns="" />

    It gives incorrect latitude and longitude as shown below. 

    Latitude: 29.19002977 and Longitude:-96.2651888

    but it should return below lat and long which is correct.

    Latitude: 37.05889 and Longitude:-102.36669

    Is anyone face such kind of issue and have solution for it.

    Waiting for your reply.



    Wednesday, October 31, 2018 3:24 PM
  • Hi Balasaheb,

    Individual location issues are not reported here.  Either report the error through the feedback on Map UI or use your enterprise support channel.

    Please look here: 

    THis is stated at the top of this forum here:



    Wednesday, October 31, 2018 5:58 PM
  • Horrible answer! Thanks for helping out those with the same issue!
    Thursday, February 20, 2020 4:57 PM
  • You are very welcome John!
    Thursday, February 20, 2020 9:19 PM