Problems with address locator created using an address point file (no rematch option)

Question

My boss created an address locator file based off of the address point layer we maintain. I've used it a few times, but every time when I choose the "rematch" option, nothing happens. And when she (my boss) tries it, she gets an error message saying the file is corrupt (file I'm trying to rematch). When using a centerline-based address locator in the past, I've always been able to rematch those that didn't automatically match the first time.

So I have two questions: 1) Should an address locator based off an address point file be able to allow rematching?
And 2) If not, is there any way to copy a feature from layer A to layer B, which has all the attribute data but no point? Basically for the ones that didn't automatically geocode, but there is an address point for that feature, I want to be able to copy the address point and paste it into the record that already has all the attribute info.

KimOllivier · Answer

Then when I chose the rematch bottom on the geocoding toolbar, I get an error that says "There was an error reading the geocoding information from this dataset".

So it looks like the 'rematch' button silently fails. At least when you use the geocoding toolbar you get some feedback.

...But what does it mean? I cannot find any error message like that in the Help. I have seen it myself and it does not have an error number either.
Also what does accessing the original locator do? Because I do have access to it.

You cannot rematch if you cannot see the locator. But if you have just used it, then it must be available.

Maybe post the field schema you are geocoding, or say the first few records?

KristinBullock · Answer

Rematching is possible with any locator, but only the one you used to part-match in the first place.

You presumably have the geocoding toolbar open.
You also have to highlight the target layer to get the rematch button to be enabled. It is grey already so watch carefully.

If some of the fields have been deleted or renamed then the rematch will not open.
You can also have trouble if you have fields that clash with the names that are added during geocoding.

For example I used the census tract id as a postcode, but I also had a postcode field. I get errors trying to rematch because the census id is longer than the postcode. So I need to rename the postcode first.

You also need access to the original geocoder, if your login profile is different, maybe you cannot access the locator.

If you want to rematch the records with a different locator, then you have to open the table, select status = 'U' and export the selected records to a new table. Exporting the featureclass will not work because you cannot geocode a featureclass (Why Esri?). Also delete the additional fields added if they are not the same in the next locator. It's all a lot of trouble. The solution is to create a composite locator so that you can match to several locators at once. When rematching you can pick one of them in the rematch.

If I'm following you correctly (and I'm not positive I am) I found only one field in the original table that may have possibly clashed with a field added during the geocoding. My table has an ID field, and a Ref_ID field was added. So I changed the name of the ID field in the original table, reran the geocode, came up with the same number of unmatched records. When the option to rematch came up, I clicked and it went away not having done anything. Then when I chose the rematch bottom on the geocoding toolbar, I get an error that says "There was an error reading the geocoding information from this dataset".

Also what does accessing the original locator do? Because I do have access to it.

Thanks, in the meantime I'll try the last part of your post.

KimOllivier · Answer

Rematching is possible with any locator, but only the one you used to part-match in the first place.

You presumably have the geocoding toolbar open.
You also have to highlight the target layer to get the rematch button to be enabled. It is grey already so watch carefully.

If some of the fields have been deleted or renamed then the rematch will not open.
You can also have trouble if you have fields that clash with the names that are added during geocoding.

For example I used the census tract id as a postcode, but I also had a postcode field. I get errors trying to rematch because the census id is longer than the postcode. So I need to rename the postcode first.

You also need access to the original geocoder, if your login profile is different, maybe you cannot access the locator.

If you want to rematch the records with a different locator, then you have to open the table, select status = 'U' and export the selected records to a new table. Exporting the featureclass will not work because you cannot geocode a featureclass (Why Esri?). Also delete the additional fields added if they are not the same in the next locator. It's all a lot of trouble. The solution is to create a composite locator so that you can match to several locators at once. When rematching you can pick one of them in the rematch.