topic Re: Geocoding unmatched addresses with different locator in Data Management Questions

Geocoding unmatched addresses with different locator

deleted-user-F4cUDEZyawYe — Mon, 31 Jan 2011 12:03:21 GMT

I geocoded 200k+ customer addresses and created two feature classes from the results. One feature class contains only the addresses that coded to the street level, and the other contains addresses that coded to city/state or zip centroid (or no match). I want to run this second feature class through another locator and have it look at a different field for street address, but cannot figure out how to do it. I tried exporting the feature class as a shapefile, but can't select it when I try to use the geocoding tools.

Re: Geocoding unmatched addresses with different locator

JoeBorgione — Tue, 01 Feb 2011 15:46:26 GMT

Just a guess; you'll need to get rid of the attributes that the geocoding process creates and adds to the features.

Re: Geocoding unmatched addresses with different locator

KimOllivier — Thu, 03 Mar 2011 20:59:21 GMT

I find you have to export the unmatched addresses as a table, not a featureclass which has null shapes for the unmatched addresses. Open the table of the featureclass, make a selection STATUS = 'U' , hide the generated fields and export. (9.3, haven't tried 10.0)

I wish we could just switch locators and rematch the filtered set, with a tag for which geocoder that matched the address instead of just an "A", it would be much tidier. You would think that you could change the "active" locator in the geocoding toolbar and that would then be used. I know that composite locators are designed to do this, but I need to pause and consider the errors, maybe do a global fix before running another locator.