Composite Locator Not Properly Locating Address Points

mpboyle · ‎08-12-2016

We have a composite geocode service that is not properly locating address points. If I enter an address within the search bar of one of our apps built with WAB, the address will show in the suggestions, but if I click on it, I will be taken to somewhere that is not the address that's listed. And, in some cases, the address is not listed at all in the suggestions box.

There are other locators within the composite locator that are working, for example, one of the locators allows the ability to search by parcel number. This locator is working fine. Another allows you to search by place name, and again, this one is working fine.

I have already deleted and re-created the address point locator (with Suggestions enabled), and re-published the service. Still getting the same results where addresses are not locating properly.

System Details

ArcGIS Desktop 10.3
ArcGIS Server 10.3
Address locator style = US Single House with Subaddress

Below are a couple sample searches. The first 2 screenshots show that when searching for an address, it appears that the suggestion is finding the address, but will take you to the wrong location. The second 2 screenshots demonstrate that the locator using place locations is working.

Any ideas what the issue is with our address locator and why it is not working properly?...why it's not locating at the correct location?

1) Searching for 1801 Whispering Pines Ct SW Cedar Rapids IA --- shows in the suggestions box.

2) Search result when I click on the suggestion. I'm taken to 1720 Whispering Pines Ct SW.

1) Searching for Linn County Community Services Building --- shows in suggestions box. Search fails.

2) Search result takes me to the correct location. Search works.

ShanaBritt · ‎01-24-2019

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. The locators also support suggestions locally in ArcGIS Pro via 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.

Anonymous User · ‎01-28-2019

Shana Britt‌ awesome, thanks!

So, question for you... I read Tips for improving geocoding quality. It says..

Match out of range
If you want to match to a street segment even if the street number doesn't exist on the line segment in your data but is within a reasonable threshold and is likely to exist, set the Match out of range property to true. This will ensure that you don't miss a potential match because the data isn't 100 percent up to date.

So is this the 'toggle' for the 'ghost' Suggestions that will be (slightly) out-of-range? Also, is this a new property that is only present for these new type of Locators published from Arc Pro to 10.6.1? I looked at my locators (from ArcMap 10.6.1 to Server 10.6.1) and did not see this property. Thanks again for all the info!

ShanaBritt · ‎01-28-2019

Kevin:

The 'Match out of range' setting only applies to the new locators created with the Create Locator tool in Pro 2.3. The 'Match out of range' setting only applies to Find operations and not suggestions. The performance and quality topics mentioned above relate to the new locators created with the Create Locator tool in Pro 2.3.

LeonZhong · ‎02-28-2019

Hi Shana,

When publishing locator created with ArcGIS Pro 2.3 to ArcGIS Server 10.6.1, it works fine with minor issue (custom output fields didn't work correctly), definitely NO FAKE address anymore.

But the composite address locator which has locator from ArcGIS Pro didn't work properly on ArcGIS Server 10.6.1. The find candidate address operation didn't return all the output fields.

Any idea?

Thank you,

BradNiemand · ‎03-01-2019

Leon,

The locators created from the Create Locator tool will work when published to 10.6.1 but custom output fields will not because they were not implemented until after that version of the software was already released. You will be able to see custom output fields in Pro 2.3 and when published to 10.7 server.

Brad

LeonZhong · ‎03-01-2019

Hi Brad,

Thank you for your reply.

The issue for composite locator still exist. Below is the result from composite locator published as a geocode service on ArcGIS Server 10.6.1. You can see there is no output for many output fields, like AddNum, StName.

I also published a participating locator on same machine, no problem at all:

Can you look into this?

Thank you,

Leon

BradNiemand · ‎03-01-2019

Leon,

I have reproduced the issue with locators created with the Create Locator geoprocessing tool and used withing a composite that is published to 10.6.1 server not displaying attributes in the standard output fields. This is reproducible in 10.7. We will look into the possibility of a patch to fix this issue for 10.7. Custom output fields will not be supported for 10.6.1 though as mentioned in a thread above.

Brad

LeonZhong · ‎03-04-2019

Thank you, Brad.

Looking forward to having the patch to fix it..

Leon

Anonymous User · ‎03-22-2019

After we get this patch for Server 10.6.1 will Pro 2.3 / 2.4 be able to simply publish a working locator, with working Suggest? I ask because we probably won't update until Server 10.7.1 comes out next year. So I hope we can finally have a geocoder locator with working auto complete again. That would be very appreciated by the public.

BradNiemand · ‎03-22-2019

Kevin,

My statement above was contradicting and I have corrected it. It stated that it DID work in 10.7 and we would potentially patch 10.6.1 but then stated that "Custom output fields will not be supported for 10.6.1 though as mentioned in a thread above."

The quoted statement above is correct and the other comment should have been that it DIDN'T work in 10.7 either and we actually have created a patch that will go live for 10.7 in the next few days. It is not possible to patch 10.6.1 because it is not a patch, it is completely new functionality that went in 2.3 which corresponds to the 10.7 release, not 10.6.1. The locators will still function in 10.6.1 but custom output fields will not be supported.