The Create Locator tool will automatically set the "Match with no Zones" property to "Yes" if the locator is built with no administrative zones (city, state, postal, etc...). The Create Locator tool will default the property to "No" if any administrative zone is mapped when building the locator.
It is strongly recommended to map the administrative zones when building a locator and it is also strongly recommended that the "Match with no Zones" property is set to "No". With suggestions support in Pro the need for the "Match with no Zones" property is not as necessary because users have the ability to choose the suggested candidate without needing to enter the entire address or place. Setting "Match with no Zones" to "Yes" should only be done if there is a specific need that requires it.
@BradNiemandI opened a case because we were getting no results from ArcGIS Javascript 4.2x but in ArcGIS Pro and Webmaps we were receiving results. Going to the Geocoder Service Rest API, no results as well. We used a composite geolocator. One of the 5 geolocators should have come back with a result regardless of if two out of the 5 had Match with no zones set to No when it should be Yes. These locators were created in ArcGIS Pro 2.9. I'm wondering when this functionality came out because the "Match with no Zones" automatically being set didn't happen. The Composite Geocoder should have skipped that one locator and gone to the rest but it didn't. That's why I placed this in the ArcGIS Ideas page because the Geocoding option didn't actually get set automatically. Support Person Identified BUG-000148113 as a possible issue
Esri Case #03473800
Recap:
Checked that we do not get results on the single line locator from the REST end of the locator when looking up an address without a zone, same is working on the web map.
Compared the requests going for "find address candidates" using developer tools
We checked that we were able to get results in ArcGIS Pro as well.
Since the locator used was a composite locator, we checked all the individual locators and confirmed the zone inputs and made sure "Match with no zone" is yes.
There were two locators for which it was not set as "no. After correcting those, we recreated the composite locator and ensured that the "match to no zones" is set to "yes"
We published the locator and added the published locator in portal organization > settings > utility network > geocoding.
Confirmed that from the REST endpoint when looking for an address without a zone, we get the correct results. Crosschecked that from the web map as well.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
