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+diana&category=&location=&distance=&f=html
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
ArcGIS Online Health Dashboard yesterday there was issues, perhaps this may be the cause?
Hi Chris,
Looking at your Geocode service, the other two streets do exist. "E Diana Dr" and "E Diana Pl".
Suggest generates a list of SUGGESTED matches for the input text". "E Diana" is very much a valid input. That to me explains why you see the other two.
This link might help.
Hi Anthony,
Thanks for your response. You are correct; we do have a Diana Place and Diana Drive. So if I asked for suggestions on 'E Diana', I would expect to get those results.
However, when I ask for suggestions on '1240 E Diana' (as a user would type in), I would expect to see only one match, as Diana Place and Diana Drive have different address ranges (2500 blocks). In my opinion, the suggestions do not work correctly.
Another example, if you search for our City Hall (200 S Anaheim), it gives suggestions that include units 10, 101, 102, etc. But these units do not exist. This makes it very misleading to the user because it implies that those are valid addresses/matches.
Thanks, but I'm not using the ArcGIS Online geocoding service, I am using one that is hosted on my own server.
His Chris,
Thanks for the reply. I tested the Geocode Service in a Web App Builder Application and I now see the behaviour you described. It does present the other two Suffixes (Place and Drive). Clicking on them leads to nothing as they aren't valid candidates. The question then is why do those two show up if they are not valid options.
Can you share a screenshot of the Address locator properties. The "Geocoding Options" to be specific.
Good to know I'm not just seeing things!
Here are the geocoding options for the address locator in question:
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.
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
I haven't heard anything about them fixing this, I think they consider it more of a feature than a bug. The work around I used was to abandon using a locator and instead use a search dijit on the map layer in the map service. This also allows suggestions and didn't throw up any false ones. More info here.
Hi All,
Anyone found a solution for this? I am also having this issue while using the search widget on portal.
Subin
This looks like a similar issue to issue #181310.
The ArcGIS Geocoding team is aware of this issue, it was a limitation of the original implementation of the suggestions capability. We have already implemented a new suggestions strategy (which is available to test in the current release of the World Geocoding service). The new strategy verifies the house number as you type and only shows address suggestions for addresses with a verified house number. If the house number cannot be verified it shows a suggestion for a street name. We are working to support this new suggestions strategy for locators that organizations build with ArcGIS.
It's almost a year later and we are experiencing the "phantom unit numbers" on a 10.5.1 locator service that hits our address points. More specifically, if you type "400 Main S" it'll return these suggestions:
400 MAIN ST
400 MAIN ST, APT 1001
400 MAIN ST, APT 1002
400 MAIN ST, APT 1003
There are no address points with unit numbers at 400 Main St... no 1001 or 1002, only 400 Main St. Additionally, there are no unit numbers of 1001 or 1002 at any house number on Main St (our Main St is only a few blocks).
The ArcGIS Geocoding team are currently working on a solution for improving suggest results for locators organizations build from data. We are targeting the solution for release for the first half of 2019.
Jeff:
You say first half of 2019, so does this mean this issue will be fixed (at least improved) with ArcMap 10.7?
We have addressed some of the problems with suggestions from geocode services in ArcGIS Pro 2.3. There is a new tool called Create Locator that will create locators that:
Pro 2.3 will ship with support to build locators with the Create Locator tool for US, US territories, and Canada. We will be working on releasing additional countries in upcoming releases. If you have access to ArcGIS Pro 2.3 beta, you can test out creating locators with the Create Locator tool and testing out the suggestion in ArcGIS Pro or as a service.
The installed help is included with the beta where the Geocoding help has been update, which can be found under Help > Data > Geocoding . The "Build your own locator" book is geared towards the Create Locator tool, which has its own help topic under Tool Reference > ArcGIS Pro tool reference > Geocoding toolbox.
The locators created with the Create Locator tool in ArcGIS Pro cannot be added to ArcMap.
If you publish the locator to ArcGIS Server or Portal (federated) you can access the service in ArcMap through an ArcGIS Server connection in ArcMap/ArcCatalog.
Share to federated portal:
Share to ArcGIS Server via Python (Pro): Requires a publisher or administrator ArcGIS Server Connection file that is created in ArcMap or ArcGIS Pro. http://pro.arcgis.com/en/pro-app/arcpy/functions/creategeocodesddraft.htm
http://pro.arcgis.com/en/pro-app/help/projects/connect-to-a-gis-server.htm#GUID-E3F3174D-3895-4BFC-9443-8676D2D4964B
ArcGIS Pro 2.3 went live today, now you will be able to create locators with the Create Locator tool that when published as a service will return valid house numbers for addresses when using the suggest operation or autocomplete. They will also return suggestions locally in the Locate pane. The new tool supports building locators for the US, Canada, and US Territories and supports English, French, and Spanish languages. We will be working on releasing additional countries and languages in upcoming releases. The Geocoding section of the help has been overhauled as well and the following topics would be a good place to start reading before using the tool.
Shana:
Will this same capability be added to ArcMap 10.7 address locators when that version of the software is released?
Michael:
The Create Locator tool will only be available in ArcGIS Pro and the locators created with the tool can be published to ArcGIS Server 10.6.1 or later, where they can then be used in ArcMap 10.7 as services. The locators cannot be used locally in ArcMap. You can still use the Create Address Locator tool in ArcGIS Pro to create locators that can be used locally in ArcMap, but when published as a service the suggestion problem will still be present.
Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
