Bug ID Number |
BUG-000144624 |
Submitted | November 17, 2021 |
Last Modified | June 5, 2024 |
Applies to | ArcGIS Pro |
Version found | 2.8.3 |
Operating System | Windows OS |
Operating System Version | 10.0 64 Bit |
Status | Will Not Be Addressed
The development team has considered the issue or request and concluded it will not be addressed. The issue's Additional Information section may contain further explanation.
|
Additional Information
The issue occurs because the 'Match with no zones' property is set incorrectly for how the locator is created. Regardless of which tool is used to build the locator, the locator has to be created without zones assigned in the field map, and the 'Match with no zones' property has to be set to 'Yes,' to search for and batch geocode addresses which do not include an administrative zone (city, neighborhood, zip code). The default setting for a locator created without zones is 'Yes'.
When geocoding the table, use the Single Field Input Address Fields option in the geocoding tool.
When the locator is published as a geocode service, the address without the zone can be searched and the suggestions and results are returned in Map Viewer. To get the best results when performing geocoding operations through REST requests to the geocode service, use the location parameter as described in the 'Proximity searches' section of the following help topic, https://developers.arcgis.com/rest/services-reference/enterprise/find-address-candidates.htm#ESRI_SECTION1_BE28ABC689464CF48249CF272DFED59C. In Map Viewer, the center of the map is used as the location in the requests which are made to the geocode service.
Workaround
Currently, the workaround is the inclusion of the zip code as the 'zone' when deployed as a service.
Steps to Reproduce