Faulty ArcGIS Address Locator
We are using a product that makes use of ArcGIS Runtime Engine 10.2. In attempting to find a particular address using the World Geocode Service (ArcGIS Online), I'm receiving nonsensical results: Looking up: 100 Woodside Cr NW, Airdrie / Result: (1) 100 Woodside Cres NW, Airdrie, Alberta, T4B -- 87% (2) 100 Woodside Cir NW, Airdrie, Alberta, T4B -- 100% Why does the locator return a lower match score percentage for the "correct" street type and assign a higher match score percentage to an "incorrect" street type? I can tell you from the outset, that the street data I'm using comes from a GIS vendor that has no intention of altering the way they designate their street types: Street types will always be 2 characters.
I would be isolating the issue with the World Geocode Service first.
When I pass your string over to the findAddressCandidates method on the World Geocode Service with no other parameters
The 1st correct result returned:
address: “100 Woodside Cir NW, Airdrie, Alberta, T4B”,
And I think that is what you were expecting?
Therefore I would be inspecting the request that is being fired from your Product. This could have whatever logic they decided to include into the app to perhaps make use of additional GeoCode Service parameters (e.g. limit results with bounding box, proximity bias, append a country code into the request, etc).
If it is an Esri product and you have no option to configure, then let them know. If it is a partner product, let them know.
If you can access the Runtime Code that makes the geocode request, include that, along with some information on the requests being made from the app into your original question.
- Database Administration Tutorials
- Programming Tutorials & IT News
- Linux & DevOps World
- Entertainment & General News
- Games & eSport