none
matchCode and matchConfidence changes? RRS feed

  • Question

  • Hi, there,

    we were using searchManager.geocode with where: '12107 Berlin' (as an example) for quite a long time.

    The resulting location is still the same but in recent searches we get matchCode Ambiguous and matchConfidence Medium whereas before it was matchCode Good and matchConfidence High for the same search. Searching for the exact name '12107, BE, Deutschland' as returned in the first query gives matchCode Good and matchConfidence Low (!)...

    Did anything change regarding the search of postcodes?

    Where could one read about such changes in the API - is there a documented version history somewhere?

    What would be the right way to search for a postcode to get matchConfidence High again?

    Thanks a lot - Mark

    Tuesday, January 8, 2019 11:32 AM

All replies

  • Hi Mark,

    Bing Maps updates data regularly, in fact we have data drops on a weekly and biweekly basis.  In the case of Postal codes, I am surprised that you would see a change however.  Is it specific to the region or are you seeing a general change in confidence across all calls?

    Sincerely,

    IoTGirl

    Tuesday, January 8, 2019 10:43 PM
    Owner
  • Hi, IoTGirl,

    I did test postal codes for several regions in Germany - is there local responsibility for the data?

    Thanks a lot - Mark

    Tuesday, January 8, 2019 11:37 PM
  • Mark,

    Can you provide the url (minus key info) that you are using for your example above?  I want to see if we can reproduce what you are seeing exactly so we can determine if there was a recent change that would have impacted this.

    Thanks,

    Justin

    Wednesday, January 9, 2019 1:11 AM
  • Justin, 

    thanks for looking into that, too.

    This is indeed very interesting. 

    I had to doublecheck first, so my answer took some time - sorry.

    We are using code like in 

    https://www.bing.com/api/maps/sdkrelease/mapcontrol/isdk/searchbyaddress

    - I modified the code as following:

    var map = new Microsoft.Maps.Map(document.getElementById('myMap'), {
        /* No need to set credentials if already passed in URL */
        center: new Microsoft.Maps.Location(47.624527, -122.355255),
        zoom: 8 });
    Microsoft.Maps.loadModule('Microsoft.Maps.Search', function () {
        var searchManager = new Microsoft.Maps.Search.SearchManager(map);
        var requestOptions = {
            bounds: map.getBounds(),
            where: '12107 Berlin', // 12107, BE, Deutschland: Medium Ambiguous
            // where: '12107, BE, Berlin', // 12107, BE, Deutschland: Low Ambiguous
            callback: function (answer, userData) {
                map.setView({ bounds: answer.results[0].bestView });
                map.entities.push(new Microsoft.Maps.Pushpin(answer.results[0].location));
    			alert(answer.results[0].name + ': ' + answer.results[0].matchConfidence + ' ' + answer.results[0].matchCode);
            }
        };
        searchManager.geocode(requestOptions);
    });
    

    Your question made me check URL-search, too:

    http://dev.virtualearth.net/REST/v1/Locations?q=12107,&%20;BE,%20;Berlin&output=xml&key=BingMapsKey

    (returns <Confidence>High</Confidence> <MatchCode>Good</MatchCode>)

    and

    http://dev.virtualearth.net/REST/v1/Locations?q=12107%20;Berlin&output=xml&key=BingMapsKey

    (returns <Confidence>High</Confidence> <MatchCode>Ambiguous</MatchCode>).

    Can you explain the differences?

    Thanks - Mark

    Friday, January 11, 2019 5:31 PM
  • Thanks for the details Mark   We are looking into this and will respond back with what we find out.
    Wednesday, January 16, 2019 1:14 AM
  • Do you have an update for me, Justin?

    Thanks a lot - Mark

    Tuesday, January 29, 2019 3:12 PM
  • anything?
    Thursday, February 7, 2019 1:54 PM