Bing Bad Address Return Ok

landstar Fire 41 Reputation points
2021-09-24T14:19:34.49+00:00

I ran the Sample Bing Maps REST API request. I put in my key and a bad address. These:

When I run this address with my key "619 E. Memorial Rd, Oklahoma City, OK 73114" what I get is below. Now that seems to say

<Confidence>High</Confidence>
<MatchCode>Good</MatchCode>
Which is wrong, that address is not GOOD and does not even exist. I get one result back not a list of addresses
around that might match. There is another example below this.
<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 © 2021 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>b8f2544934984135a402cc596f3f0a27|CH0001B052|0.0.0.1|Ref A: DD0E489F12AC4CB4A1EE193404948DED Ref B: DM2EDGE0314 Ref C: 2021-09-22T15:32:02Z</TraceId> <ResourceSets> <ResourceSet> <EstimatedTotal>1</EstimatedTotal> <Resources> <Location> <Name>619 E Memorial Rd, Oklahoma City, OK 73114</Name> <Point> <Latitude>35.609198994441286</Latitude> <Longitude>-97.503353301940066</Longitude> </Point> <BoundingBox> <SouthLatitude>35.605336276870609</SouthLatitude> <WestLongitude>-97.509687859484032</WestLongitude> <NorthLatitude>35.613061712011962</NorthLatitude> <EastLongitude>-97.4970187443961</EastLongitude> </BoundingBox> <EntityType>Address</EntityType> <Address> <AddressLine>619 E Memorial Rd</AddressLine> <AdminDistrict>OK</AdminDistrict> <AdminDistrict2>Oklahoma County</AdminDistrict2> <CountryRegion>United States</CountryRegion> <FormattedAddress>619 E Memorial Rd, Oklahoma City, OK 73114</FormattedAddress> <Locality>Oklahoma City</Locality> <PostalCode>73114</PostalCode> </Address> <Confidence>High</Confidence> <MatchCode>Good</MatchCode> <GeocodePoint> <Latitude>35.609198994441286</Latitude> <Longitude>-97.503353301940066</Longitude> <CalculationMethod>InterpolationOffset</CalculationMethod> <UsageType>Display</UsageType> </GeocodePoint> <GeocodePoint> <Latitude>35.609154029128177</Latitude> <Longitude>-97.503353614445558</Longitude> <CalculationMethod>Interpolation</CalculationMethod> <UsageType>Route</UsageType> </GeocodePoint> </Location> </Resources> </ResourceSet> </ResourceSets> </Response>

When I run the address with my key "FooBar Memorial Rd, Oklahoma City, OK 73114" what I get is still the system thinking it is Confidence HIGH and Match is Good

<Confidence>High</Confidence>
<MatchCode>Good</MatchCode>

Again this is wrong, that address is wrong.
<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 © 2021 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>c3ad42936c764068b0b3f1d0335a73db|CH0001B075|0.0.0.1|Ref A: FA4411044F7E4C4C967EB37581928D17 Ref B: CH1EDGE1309 Ref C: 2021-09-22T15:35:46Z</TraceId>
<ResourceSets>
<ResourceSet>
<EstimatedTotal>1</EstimatedTotal>
<Resources>
<Location>
<Name>Memorial Rd, Oklahoma City, OK 73114</Name>
<Point>
<Latitude>35.606657</Latitude>
<Longitude>-97.5315034999963</Longitude>
</Point>
<BoundingBox>
<SouthLatitude>35.602794282429322</SouthLatitude>
<WestLongitude>-97.537837856308371</WestLongitude>
<NorthLatitude>35.610519717570675</NorthLatitude>
<EastLongitude>-97.525169143684238</EastLongitude>
</BoundingBox>
<EntityType>RoadBlock</EntityType>
<Address>
<AddressLine>Memorial Rd</AddressLine>
<AdminDistrict>OK</AdminDistrict>
<AdminDistrict2>Oklahoma County</AdminDistrict2>
<CountryRegion>United States</CountryRegion>
<FormattedAddress>Memorial Rd, Oklahoma City, OK 73114</FormattedAddress>
<Locality>Oklahoma City</Locality>
<PostalCode>73114</PostalCode>
</Address>
<Confidence>High</Confidence>
<MatchCode>Good</MatchCode>
<GeocodePoint>
<Latitude>35.606657</Latitude>
<Longitude>-97.5315034999963</Longitude>
<CalculationMethod>Interpolation</CalculationMethod>
<UsageType>Display</UsageType>
</GeocodePoint>
</Location>
</Resources>
</ResourceSet>
</ResourceSets>
</Response>

Windows Maps
Windows Maps
A Microsoft app that provides voice navigation and turn-by-turn driving, transit, and walking directions.
253 questions
0 comments No comments
{count} votes

Accepted answer
  1. IoTGirl 3,051 Reputation points Microsoft Employee
    2021-09-29T21:53:05.29+00:00

    I have given the answer in the other forum as well...

    I recommend you look at the result a little differently. The API is telling you that "<CalculationMethod>Interpolation</CalculationMethod>" means it is giving you a high confidence "Best Guess". Maybe this ENUM will help you? https://learn.microsoft.com/en-us/bingmaps/sdk-native/map-services-api/maplocationpointcalculationmethod-enumeration Your assumption is that "<CalculationMethod>Rooftop</CalculationMethod>" was used but the answer is telling you that the exact address could not be found so it is falling to less precise methods to get you an answer, the best one it can but warning you that it is using "Interpolation" to get it. Essentially, you need to read the confidence and the calculation method to understand the result.

    0 comments No comments

0 additional answers

Sort by: Most helpful