nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Flexible Locator Suggestions Like ArcGIS World Geocoding Service

KyleGruber

When creating a street address locator with suggestions enabled, is there a way to include fields such as Predirection, Postdirection, Suffix, etc but not make them a required part of the geocoding process? For example, when I do this search with the World Geocoding Service:

World Geolocator Flexibility

Despite the fact that I'm not entering predirection as part of my inquiry, it's able to pull up 100 E Main and 100 W Main. Does this require custom logic outside of the standard locator calls, or possibly a point address locator needs to be part of a composite? I can't seem to achieve this using a Locator and Runtime SuggestAsync, even turning the minimum score down to 0.

Thanks!

Vind meer berichten getagd met

Accepted answers

KyleGruber

Anyone who comes across this thread, please see the corresponding runtime thread:

https://community.esri.com/thread/233047-mmpk-locator-discrepency-between-pro-and-runtime

All comments

ShanaBritt

Kyle:

If you would like to get suggestion behavior similar to what you are finding with the ArcGIS World Geocoding Service, I would suggest creating a locator using the Create Locator tool if you have access to ArcGIS Pro 2.3. The following resources should help with using the tool:

https://pro.arcgis.com/en/pro-app/help/data/geocoding/create-a-locator.htm

https://pro.arcgis.com/en/pro-app/help/data/geocoding/introduction-to-locator-roles.htm

https://pro.arcgis.com/en/pro-app/tool-reference/geocoding/create-locator.htm

KyleGruber

Shana,

Thanks for the suggestion, that's actually exactly what I'm using. The new Create Locator tool is great, it fixed the long running issue with range address locators suggesting street numbers that don't exist, unfortunately I don't see an obvious solution to the predirection/postdirection issue. I tried creating a composite locator with varying levels of mapped information, but it's causing a crash in the runtime that's noted here:

https://community.esri.com/thread/232024-access-violation-in-runtime-1005-with-mmpk-containing-composite-locator

I'll try playing around with Create Locator and the field mappings to see what I can come up with without creating a composite.

Thanks!

ShanaBritt

Kyle:

The Create Locator tool will allow you to create a single locator that references multiple datasets, but you can only use a role once in the locator. So you could have a single locator based on the PointAddress, StreetAddress (includes street ranges, street names, and intersections), and Postal roles. You would be able to test out the suggestions in the Locate pane of Pro without having to publish the locator as a service.

KyleGruber

Shana,

This is helpful, and I think I've gotten the behavior of the locator to where I want it, the problem then becomes the output. It seems as though the input and output are completely tied together.

So if I map just the From/To Address Numbers and Street Name in the Field Mapping, I'm able to enter 3113 HOW and get back 3113 S Howard Ave as an example. The problem is, there's seemingly no way to customize the output. The label I get back in both ArcGIS Pro and ArcGIS Runtime is 3113 HOWARD, USA.

How does a locator determine what to send back as the suggest "label"? I can't even figure out where it's getting USA as I'm not mapping country anywhere. Is this where the Custom Output Fields come into play?

Thanks!

Edit: I think I'm at the point where I have to put this back into the hands of the runtime team, although I'm still fundamentally lost on how the output of the locator is built.

https://community.esri.com/message/849365-mmpk-locator-discrepency-between-pro-and-runtime

BradNiemand

Kyle,

Are you using PreferredSearchLocation and passing in the center of your map as that location in your request? This will help give more flexible results because it will be looking at addresses that are close to your current location. All of our apps (Map Viewer, Pro, ArcMap) use PreferredSearchLocation when getting suggestions.

Brad

KyleGruber

Anyone who comes across this thread, please see the corresponding runtime thread:

https://community.esri.com/thread/233047-mmpk-locator-discrepency-between-pro-and-runtime

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.