behaviour of default input vs alternate input

PeterHanmore — Fri, 07 Jun 2013 11:42:26 GMT

I'm hoping someone in the forum can shed some light on these two questions. We have created (and published to ArcGIS Server) a customized locator service (v10 SP3) based on the default US single address locator template, and customized it with a list of alternate city names (<cityalias> section of the xml file).

Question 1) When I geocode an address in ArcMap using a local copy of the locator, it will correctly make use of the city aliases and give me a score of 100. When I publish the same locator to the server and geocode the same address using the same tool (find dialog->locations tab) I get a score of 64.63.
Does anyone know why I am seeing a difference?

Question 2) If I geocode an address using the 'Full Address' field on the REST interface, I get the same score as geocoding from arcMap to ArcGIS Server (score = 64.63). If I geocode using the 'Street' and 'City' fields on the REST interface, I get the same score as geocoding from ArcMap to the local locator (score = 11).
Why are the scores different? I would have thought that the scores should be the same no matter which way you give it an address. Does the locator use different logic for different input methods?

Thanks for any assistance.

topic behaviour of default input vs alternate input in Data Management Questions

behaviour of default input vs alternate input