idea Create Locator, additional options when creating in ArcGIS Pro Ideas

Create Locator, additional options when creating

feralcatcolonist_old — Mon, 27 Jun 2022 22:18:49 GMT

Currently, the Create Locator Tool does not allow you to set up options during its creation. This has the tendency to create gotchas, or additional unnecessary clicks after re-running a creation task.

Exposing all/some of the locator properties during geoprocessing creation prevents this redundant work for locators that must be recreated frequently.

Specifically:

Match scores

Intersection Connectors

Match with no zones

Suggestions for partial subaddresses

Re: Create Locator, additional options when creating

ShanaBritt — Sat, 16 Jul 2022 04:32:52 GMT

@feralcatcolonist_old Most of those locator properties can be set programmatically using the Python Geocoding Module. https://pro.arcgis.com/en/pro-app/latest/arcpy/geocoding/locator-class.htm#P_GUID-B617A31C-2B5E-427F-BBEB-B52C1667CC51

If you open the History pane from the Analysis ribbon, you can right-click the previously run Create Locator tool that created the locator and select Save as a Python script, which can help you automate the process if you are familiar with writing scripts using ArcPy and Python.

Re: Create Locator, additional options when creating

feralcatcolonist_old — Mon, 18 Jul 2022 17:11:10 GMT

I can definitely do that the Python way and super happy to know that's an option! For the non-Python folks in the Esri-verse I think it would be a great addition to have a collapsible "advanced options" area within the GP tool dialogue.

Re: Create Locator, additional options when creating

feralcatcolonist_old — Tue, 16 Aug 2022 00:41:25 GMT

@ShanaBritt, it doesn't look like the "match with no zones" attribute is exposed in the Locator class, can you confirm?

Re: Create Locator, additional options when creating

ShanaBritt — Thu, 18 Aug 2022 16:06:27 GMT

@feralcatcolonist_old That is correct the "Match with no zones" property is not available in the Python Geocoding Module. However, I'd like to get a better understanding as to why you need to use it. Where will the locator be used? How will the locator be used (batch geocoding a table or single address searches in Pro, MapViewer, or some other app)?

The property is a legacy property designed for locators that did not support suggestions before ArcMap 10.3 and locators built in Pro with either the Create Locator or Create Feature Locator tool automatically support suggestions so that as you type the address or place you are presented with suggestions to choose from and select to take you to the location.

Re: Create Locator, additional options when creating

feralcatcolonist_old — Thu, 18 Aug 2022 16:41:00 GMT

@ShanaBritt, our locator uses the address and road centerline roles and contains information for our municipality, county, zip codes, etc. Additionally our locator contains information about neighboring municipalities in a buffer around our own.

We've found that the results are significantly improved with match outside of zone; otherwise a user must type in all the comma separated information like city, county, zip for appropriate results. I'm unsure why this is the case, for the longest time I thought our geocoder was broken until I started using this setting.

Re: Create Locator, additional options when creating

ShanaBritt — Thu, 18 Aug 2022 17:24:14 GMT

@feralcatcolonist_old If the locator is being used in what sounds like a geosearch scenario where someone just types the address, they should be getting suggestions for addresses that show the zone information and then they would just select the suggestion. So if the locator is built with zones (municipality, county, zip codes) the default setting is 'No' for 'Match with no zone'. If the locator is used in the Locate pane of ArcGIS Pro or the MapViewer, when the user starts to type the address w/o the zone suggestions are displayed. The suggestions returned are based on location and the center of the map is used for location is no zone is included. If the locator is used as a service the location parameter should be included in the requests.

If the locator is used for batch geocoding, the zone is required in the address in order to get results returned with the default setting for the locator you are creating. Batch geocoding does not make use of location, the location comes from the zone. We recommend batch geocoding with at least one zone or using suggestions if you are entering an address w/o zone when the locator supports zones.

Are your users using the locator in ArcGIS Pro? MapViewer? Mobile App?

-Shana

Re: Create Locator, additional options when creating

feralcatcolonist_old — Thu, 18 Aug 2022 17:36:20 GMT

The main use case for us is within our Cityworks application, so users will input an address or multiple addresses within their web mapping application (or through the mobile respond application) and it sends a call to the geocode service which then provides them options to select.

There are some areas where a person may not know specifically which zone they are in (especially newer employees) so it not always feasible to specify the zone. And when we are batch geocoding with data provided from our regional partners sometimes we are only provided with the first line of an address and need to be able to find likely matches around us (no rules on similarly named streets between neighboring municipalities.

Re: Create Locator, additional options when creating

ShanaBritt — Thu, 18 Aug 2022 18:39:50 GMT

@feralcatcolonist_old Do you know what request is used in the application that is sent to the geocode service, findAddressCandidates or geocodeAddresses? You may need to use Fiddler or something like it to see the contents of the requests, but if location was included in the request I suspect they should get suggestions returned from the service. I don' t have any experience with Cityworks to know what's going on behind the scenes.

Re: Create Locator, additional options when creating

feralcatcolonist_old — Sun, 21 Aug 2022 19:28:39 GMT

@ShanaBritt, it looks like the request is being routed through the Cityworks application server so it is obfuscated from the client. This is what the tail-end looks like searching for an address:
250 W FIRST ST

Without having the match outside of zone options, when you search the same location (250 W FIRST ST) you will return 0 results. In order to return any results, you have to append almost the entirety of the municipal name. One of those results is the address without the municipal name, which will not match 1:1 in the search bar as noted above.

So although the toggle might be a legacy function, it is absolutely necessary for faster, better matching searches (within Cityworks at least).

Re: Create Locator, additional options when creating

ShanaBritt — Wed, 24 Aug 2022 17:17:29 GMT

@feralcatcolonist_old Does the Cityworks app not show suggestions the same way that ArcGIS Pro does?

If your locator built with zone and 'match with no zone' set to the default of 'No' is used in ArcGIS Pro Locate pane, do you get suggestions when you enter '250 W First'? Also are zones specified for each role in the field mapping for the locator? You should have a zone assigned to each role in the multirole locator. It looks like from the screenshot that one candidate includes zone while the other does not. I cannot tell which candidate is coming from the PointAddress role or the StreetAddress role. I believe the lacking of zone for one of the roles is the cause of the behavior you are seeing when 'Match with no zone' is set to 'No'.

It is possible to build a locator w/o zone and use it to batch geocode addresses w/o zones, in this case the default 'Match with no zone' property is set to 'Yes'.

Re: Create Locator, additional options when creating

BlakeTerhune — Mon, 12 Dec 2022 19:16:22 GMT

Another request from 2017 for the same thing. Thanks for posting @feralcatcolonist_old

Provide ArcPy functionality to modify all address ... - Esri Community

Re: Create Locator, additional options when creating

LisaBuckleton_dtwd — Tue, 07 Feb 2023 08:07:39 GMT

More comprehensive geoprocessing tools are desired for setting locator properties programatically.

I am building an ArcGIS Pro model to periodically recreate several locators. Simply rebuilding the locators is not an option, because the location and/or structure of the source data is is too variable. This requires the locator to be recreated, not just rebuilt.

Most locator properties cannot be set in a model. Having to set these properties manually is irksome because 1) this relies on the user to remember that manual changes are required and 2) to effect the changes requires the user to work between and ArcPro session and a (potentially very lengthy) document.

Embedding such settings within a model provides both consistent setting of the parameters as well as 'self-documenting' code (which informs and assists when the locator needs to be modified).

Re: Create Locator, additional options when creating

ShanaBritt — Wed, 08 Feb 2023 18:15:55 GMT

@LisaBuckleton_dtwd

You should be able to use the ArcPy Geocoding Module to create a script to update the properties of the locator and create a script tool from it that can be used in Model Builder.

Re: Create Locator, additional options when creating

LisaBuckleton_dtwd — Wed, 15 Feb 2023 07:39:23 GMT

Thanks for responding ShanaBritt. However, my point is that the locator properties should be settable via a model tool, rather than having to write python code.

Re: Create Locator, additional options when creating

j_rsg — Fri, 14 Apr 2023 17:02:29 GMT

I would like to be able to set locator properties for disconnected near intersections. See this thread:

https://community.esri.com/t5/arcgis-pro-questions/prevent-near-street-intersections-from-being/td-p/1250956

Allowing you to specify a distance tolerance for a near intersection (with a 0 value essentially disabling the near intersection option) would be useful and prevent invalid intersections from being geocoded. On the flip side, being able to set a larger tolerance would help out @mhudson.

An additional option to disable intersections not physically connected would also be beneficial. There are many cases where geocoding a highway overpass over a street would not be a desireable outcome.