I have a 10.3 geocoding service with suggestions enabled which is based on address points. The endpoint can be accessed here: http://gis.anaheim.net/arcgis/rest/services/AddressPointGeocoder/GeocodeServer
Everything works correctly except for the suggestions, which seem to be returning invalid matches. For example, if you test the Suggest functionality here: http://gis.anaheim.net/arcgis/rest/services/AddressPointGeocoder/GeocodeServer/suggest and type in 1240 E Diana, you get 3 suggestions: http://gis.anaheim.net/arcgis/rest/services/AddressPointGeocoder/GeocodeServer/suggest?text=1240+e+d...
but only one is valid (1240 E Diana Ave).
Where did the other two come from? Maybe I am misunderstanding how suggestions work, but I expected the geocoding service to query the data on the fly and only present valid matches.
-Chris
I will recommend you open a support case to have us look into this with more detail.
This link might help.
Been watching the thread Chris and I'm not sure I can be much further help other than what Anthony suggested by playing with your (score/sensitivity) percentages here. Side question here is are you building a composite locator and/or was the locator rebuilt before you republished service?
Yes, I also have a composite locator that includes this locator. No, I did not rebuild the locator but I will try that after hours tonight. I have to stop the service otherwise there is a lock on the locator and it can't be rebuilt.
I am having the same issue with my hosted geocoding service. Did you ever figure out a solution to fix your's?
Unfortunately no fix was found. It has been classified as a bug by ESRI.
That figures. Thanks
I'm haveing the same issue. Any word on when ESRI will be fixing this bug? Is there a bug number?
This has not been fixed yet. The bug number is #BUG-000090968. The status shows as "In Product Plan".
Hello,
I have noticed the same issue in my 10.3.1 ArcGIS Server geocoding services. I tried in vain to find out the status of the bug using the provided bug number in the Support site...
Do you know if it is fixed in 10.4 or in 10.5?
Thank you for your help!
Yeon