Create Locator, additional options when creating

[feralcatcolonist_old]

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

[BlakeTerhune]

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

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

[LisaBuckleton_dtwd]

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).

[ShanaBritt]

@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.

[LisaBuckleton_dtwd]

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.  

[j_rsg]

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...

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.