topic Re: Geocoding with custom locator - suggestions are missing in ArcGIS Pro Questions

Geocoding with custom locator - suggestions are missing

MichailMarinakis1 — Fri, 08 Apr 2022 11:17:12 GMT

Hi all,

we are using a custom locator based on local data. The data are quite extensive and with a lot of information.

We have on our data a street entry with the following attributes:

Street name = 'Ruy'

Full street name = 'Rue Ruy'

Prefix type = 'Rue'

etc.

When we search for a street address using the suggest method and we use Text = 'Ruy', we receive zero suggestions. The same with the findCandidates.

If we search with the Text = 'Rue Ruy' we receive all the related results, same behaviour in findCandidates.

We would like to receive all the related results, even if the user is typing 'Ruy'. We have tried to use wildcards, changing the minimum match/candidate score to very low values, Match with no zones is set to yes, but no luck so far.

It seems like the query works as if it is: Text like 'Ruy%', instead of Text like '%Ruy%'

We have noticed also, that Single line Address Field is the FullAddress .
Is there any way to retrieve suggestions as if we were searching Text like '%Ruy%' ? That would be the best solution for us 😄

Or is there any other way to improve this results?

Re: Geocoding with custom locator - suggestions are missing

ABishop — Fri, 08 Apr 2022 12:57:17 GMT

Hello Michail,

Not sure if this is still the case, but I found this thread that seems to line up with the issues you are having:

https://community.esri.com/t5/arcgis-pro-questions/is-it-possible-to-use-suggestions-in-locate-with/m-p/744769#M32590

Re: Geocoding with custom locator - suggestions are missing

MichailMarinakis1 — Fri, 08 Apr 2022 14:20:48 GMT

Hi Amanda,

thank you for your reply! We have already published our locator to a Geocoding service in our ArcGIS Server and portal. This behaviour is reproducible in the geocoding service, when we use the REST API.

Hope it is more clear now :-).

Re: Geocoding with custom locator - suggestions are missing

ABishop — Fri, 08 Apr 2022 14:25:37 GMT

OK that's good news! I also saw a post about custom formats for geocoding addresses. This thread may be of some interest also: https://community.esri.com/t5/arcgis-pro-questions/how-can-we-get-custom-output-formats-address-for/m-p/1159666#M53464

Re: Geocoding with custom locator - suggestions are missing

MichailMarinakis1 — Fri, 08 Apr 2022 14:35:16 GMT

We have published with ArcGIS Pro 2.8 to a federated ArcGIS Server 10.9.1.

We are not wishing to have any custom format on the locator, mostly to have more flexibility in the suggestions 😉

Re: Geocoding with custom locator - suggestions are missing

MichailMarinakis1 — Mon, 11 Apr 2022 09:05:49 GMT

Tagging @ShanaBritt. Any help or hint about the subject is more than welcome 🙂

Re: Geocoding with custom locator - suggestions are missing

ShanaBritt — Mon, 11 Apr 2022 20:53:38 GMT

@MichailMarinakis1 Are you able to provide more details about the locator?

1. Were you using the Create Locator tool to build the locator? If so, which role and country?

2. Is the full street name mapped in the field mapping of the locator?

If it's possible to send the locator and a small sample of the data with just the address info that would be most helpful in trying to figure out what's going on to better answer your question.

Re: Geocoding with custom locator - suggestions are missing

MichailMarinakis1 — Tue, 12 Apr 2022 08:35:13 GMT

Hi @ShanaBritt ,

thank you for your reply! Here are the answers to your questions:

Yes, we have been using the Create Locator tool to build the locator. Country is Belgium and the roles are included in the attachment below.
Yes, the full street name is mapped. I include screenshots of the field mapping of the locator for all the attributes of the Street Address role.

It's going to be a bit difficult to send here a small sample. If you think it is necessary, I will dedicate some time for that.

In the attachments you can find the .loc file, further screenshots from the CreateLocator tool, and how the data look like.