English

Bug: Geocoding does not match anything when a locator is built with no city, state, or zip fields mapped

Description

**This issue is addressed in ArcGIS 10 Service Pack 1.**

While building the locator completes without error, geocoding a table results in zero matches.

This can occur if the locator was built without a city, state and/or zip fields mapped and may also occur if the table to be gecoded does not have a city, state and/or zip fields.

Cause

This is a known issue verified with the following data/locator style scenarios:

Dual Ranges locator style: needs city, state and zip both mapped in the locator from the reference data and in the table to be geocoded.

US Address - Single House style: needs at least city both mapped in the locator from the reference data and in the table to be geocoded.

Workaround

Download and install ArcGIS 10 Service Pack 1 (SP1).

Note:
There is a link to ArcGIS 10 SP1 in the Related Information section.

    Related Information