Bug: Geocoding does not match anything when a locator is built with no city, state, or zip fields mapped
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.
This is a known issue verified with the following data/locator style scenarios:
- Dual Ranges locator style: city, state and zip fields are required to be mapped in both the locator from the reference data and in the table to be geocoded.
- US Address - Single House style: at least the city field is required to be mapped in both the locator from the reference data and in the table to be geocoded.
This issue is addressed in ArcGIS 10 Service Pack 1. To download and install the service pack, refer to ArcGIS 10 (Desktop, Engine, Server) Service Pack 1.