English

Bug: Dual Ranges address locators created with ArcGIS for Desktop 10.1 and higher do not return matches

Description

Dual Ranges address locators created with ArcGIS for Desktop 10.1 do not return matches, regardless of whether or not a zone is used to build the locator, when used in ArcGIS for Desktop or when published as a service to ArcGIS for Server.

Cause

The default setting for the 'Match with no zone' property in the Address Locator Properties under Geocoding Options is set to No.

Workaround

There are two options to fix this problem. One option fixes a specific address locator, and the other option permanently sets the default setting of the 'Match with no zone' property to Yes so that all address locators are created with the property set as Yes/true.

For a Specific Address Locator

1. In ArcCatalog or the Catalog window, right-click the address locator.
2. Click Properties.
3. In the Geocoding Options section, change 'Match with no zones' from No to Yes.
Address Locator Properties - Geocoding options

[O-Image] Address Locator Properties

Permanently Set the 'Match with no zones' Default Setting to Yes/true

1. In an XML or text editor, open the USAddress.lot.xml file located in the 'c:\program files\arcgis\desktop10.x\locators' or 'c:\program files(x86)\arcgis\desktop10.x\locators' folder.

Note:
Substitute '10.x' in the address above to match the version of ArcMap in use.


2. Change the two occurrences of the following tag from false to true.

Before
Code:
<prop name="supportsOptionalZone" type="Boolean">false</prop>

After
Code:
<prop name="supportsOptionalZone" type="Boolean">true</prop>

Any new address locators created will have this setting applied by default.

Note:
At ArcGIS for Desktop versions 10.2 and higher, there are approximately two to four occurences of the 'supportsOptionalZone' property. New search methods have been added over time that include this property.

Related Information