NIM058244 for ArcGIS for Desktop

Numéro d’ID de bogue	NIM058244
Envoi	June 11, 2010
Dernière modification	June 5, 2024
S’applique à	ArcGIS for Desktop
Version trouvée	9.3.1
Système d’exploitation	Windows OS
Version du système d’exploitation	XP
Statut	Will Not Be Addressed

Informations supplémentaires

No Public Explanation

Solution de contournement

The behavior is actually correct. The user saw “duplicate candidates” because 9.2 and 9.3 geocoding standardizes the reference data and input addresses. When users create an address locator, there is an advanced option “Store standardized reference data in locator” in the Advanced Locator Properties. By default, this option is checked. When the locator is being built, the reference data including the alternate tables are standardized and indexed/stored in the locator. The standardization rule base contains rules to convert CH HILL to CHURCH HILLThe locator, thus, contains a record with the street name “CHURCH HILL” from the primary feature class, and a record from the alternate name table, also “CHURCH HILL” due to the reference data standardization. The input address “100 CHURCH HILL RD” or “100 CH HILL RD” is standardized to ““100 CHURCH HILL RD”. The street name “CHURCH HILL” is used to search the locator and both records, the one from the primary feature class and the one from the alternate table, are returned as perfect candidates.There are a few approaches to address this issue. Here are my suggestions:1. If the user un-checks the option in the Advanced Locator Properties dialog box before building the locator, he will see that geocoding “100 CHURCH HILL RD” or “100 CH HILL RD” will only return one candidate, i.e. the candidate from the primary feature class. The record from the alternate table will never be used.2. Strictly speaking, “CH HILL” is not an alternate name to “CHURCH HILL”. The standardization process will handle the name in various forms correctly. If the “CH HILL RD” record in the alternate name table is removed (and let standardization handles the names), the user doesn’t need to turn off the “Store standardized reference data in locator” option in the Advanced Locator Properties.3. If the user would prefer to keep the “CH HILL RD” record in the alternate name table, then I would suggest to modify the standardization so that “CH HILL” will not be standardized to “CHURCH HILL”. To do this:Open the expand.tbl file in the geocode folder with a text edit and comment out the line “CH CHURCH”. ; @(#)expand.tbl;CH CHURCH