none
REST Address Matching Issues

    Question

  • Was there any kind of system update made or any kind of known issues with address matching introduced in the last day or so?

    The service is always returning values, but if I run the same file back-to-back-to-back I'm getting very different results each time.  Some addresses return 'high' or 'medium' on subsequent attempts.  And there is essentially no pattern I can see to even provide a test case.  Overall, there is degradation though as the geocoding rate is dropping as a result.  

    Anyone else experiencing anything similar?

    Friday, October 26, 2018 5:40 PM

All replies

  • I'm surprised I haven't heard anything from anyone.  Am I alone in this?  Account specific?  It is so very easy to replicate the issue, as mentioned just not consistently.  If I throw 100 good address at it then maybe 15 of them fail.  If I run it again, maybe 12 or 20.  Each time different.  If I take those that fail and re-run them they succeed.  Sometimes on the next try, sometimes after a few tries.  Same input...different results.  It is as if some servers are returning 'high' matches as expected and others are returning up hierarchy 'medium' matches for the same request.

    Below is one example for the team.  But I can make this succeed/fail (and back and forth) on seemingly about ANY address I wish to.  This issue has been reported by many users each on their own machines/networks and it is not specific to any 1 PC/firewall/network, etc.

    IDENTICAL REQUEST AS BELOW, BUT WITH FAILED ‘MEDIUM’ RESPONSE (UP HIERARCHY FALLBACK)…

    request: https://dev.virtualearth.net/REST/v1/Locations/US/CA/92084/Vista/771 E VISTA WAY?o=xml&inclnb=1&key=MYKEY

    returned data: <?xml version="1.0" encoding="utf-8"?><Response xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/search/local/ws/rest/v1"><Copyright>Copyright © 2018 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>0ced4b37a0324eb9970a376e96081384|CO389F482F|7.7.0.0|Ref A: 7230C10087404D45BE7D56484F7A46F8 Ref B: CO1EDGE0116 Ref C: 2018-10-26T20:28:49Z</TraceId><ResourceSets><ResourceSet><EstimatedTotal>1</EstimatedTotal><Resources><Location><Name>92084, CA</Name><Point><Latitude>33.2183799743652</Latitude><Longitude>-117.226768493652</Longitude></Point><BoundingBox><SouthLatitude>33.1617584228516</SouthLatitude><WestLongitude>-117.262992858887</WestLongitude><NorthLatitude>33.2694854736328</NorthLatitude><EastLongitude>-117.147270202637</EastLongitude></BoundingBox><EntityType>Postcode1</EntityType><Address><AdminDistrict>CA</AdminDistrict><AdminDistrict2>San Diego County</AdminDistrict2><CountryRegion>United States</CountryRegion><FormattedAddress>92084, CA</FormattedAddress><Locality>Vista</Locality><PostalCode>92084</PostalCode></Address><Confidence>Medium</Confidence><MatchCode>UpHierarchy</MatchCode><GeocodePoint><Latitude>33.2183799743652</Latitude><Longitude>-117.226768493652</Longitude><CalculationMethod>Rooftop</CalculationMethod><UsageType>Display</UsageType></GeocodePoint></Location></Resources></ResourceSet></ResourceSets></Response>

    IDENTICAL REQUEST AS ABOVE, BUT WITH A SUCCESSFUL ‘HIGH’ RESPONSE TO ROOFTOP…

    request: https://dev.virtualearth.net/REST/v1/Locations/US/CA/92084/Vista/771 E VISTA WAY?o=xml&inclnb=1&key=MYKEY

    returned data: <?xml version="1.0" encoding="utf-8"?><Response xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/search/local/ws/rest/v1"><Copyright>Copyright © 2018 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>11c6bfd418a44afbab53588a5574fb12|CO389F482F|7.7.0.0|Ref A: 2F209F055511461B812D83D307DDC95E Ref B: CO1EDGE0510 Ref C: 2018-10-26T20:30:14Z</TraceId><ResourceSets><ResourceSet><EstimatedTotal>1</EstimatedTotal><Resources><Location><Name>771 E Vista Way, Vista, CA 92084</Name><Point><Latitude>33.20889</Latitude><Longitude>-117.23476</Longitude></Point><BoundingBox><SouthLatitude>33.2050272824293</SouthLatitude><WestLongitude>-117.24091536032</WestLongitude><NorthLatitude>33.2127527175707</NorthLatitude><EastLongitude>-117.22860463968</EastLongitude></BoundingBox><EntityType>Address</EntityType><Address><AddressLine>771 E Vista Way</AddressLine><AdminDistrict>CA</AdminDistrict><AdminDistrict2>San Diego County</AdminDistrict2><CountryRegion>United States</CountryRegion><FormattedAddress>771 E Vista Way, Vista, CA 92084</FormattedAddress><Locality>Vista</Locality><PostalCode>92084</PostalCode></Address><Confidence>High</Confidence><MatchCode>Good</MatchCode><GeocodePoint><Latitude>33.20889</Latitude><Longitude>-117.23476</Longitude><CalculationMethod>Rooftop</CalculationMethod><UsageType>Display</UsageType></GeocodePoint><GeocodePoint><Latitude>33.2091387724646</Latitude><Longitude>-117.23534673652</Longitude><CalculationMethod>Rooftop</CalculationMethod><UsageType>Route</UsageType></GeocodePoint></Location></Resources></ResourceSet></ResourceSets></Response>

    Friday, October 26, 2018 8:41 PM
  • I just ran the test file and 100% worked (same file that had the random 8, or 10, or 15 bad ones before with each test).  

    Anybody have any insight for me by chance?  Did an issue get worked out perhaps?

    Thanks.

    Friday, October 26, 2018 10:05 PM
  • Hello,

    I can confirm Microsoft Spatial Data Services (specifically Geocoding) had an unscheduled maintenance cycle which exhibited the unexpected and undesired effect you observed. The issue was detected and corrected in a span of a few hours, which overlap with the timeline of your observation.

    We apologize for the inconvenience, please let us know if you experience any more such inconsistencies.

    Regards,

    Florin Teodorescu

    Monday, October 29, 2018 9:02 PM
  • Thanks for the update Florin!
    Monday, October 29, 2018 9:50 PM
    Owner