Create Composite Address Locator doesn't set spatial reference

[MichaelFashoway]

I have a composite address locator based on four address locators, all stored in ArcSDE (v10). Since there is no way to rebuild a composite locator to refresh the data, I created a model that rebuilds each participating address locator, deleted the composite locator, then recreates the composite locator. However, the Create Composite Locator tool doesn't set the spatial reference based on the first participating locator. Each time I create the composite, I must go into the properties and set it manually. Any ideas why this is?

Thanks,
Michael

[ZacharyStauber]

I have the same problem, except worse.  When I create a composite address locator with Python, then go into its properties and set the spatial reference, the "OK" button becomes grayed out and I can't save the change.

[BradNiemand]

What version of ArcGIS are you using?  Do you have any service packs installed?

Brad

[MichaelFashoway]

I have the same problem, except worse.  When I create a composite address locator with Python, then go into its properties and set the spatial reference, the "OK" button becomes grayed out and I can't save the change.

Seems things have gone from bad to worse. The OK button is now disabled for me, too.

I'm using v10, Sp3.

[ErickLobao]

I have a composite address locator based on four address locators, all stored in ArcSDE (v10). Since there is no way to rebuild a composite locator to refresh the data, I created a model that rebuilds each participating address locator, deleted the composite locator, then recreates the composite locator. However, the Create Composite Locator tool doesn't set the spatial reference based on the first participating locator. Each time I create the composite, I must go into the properties and set it manually. Any ideas why this is?

Thanks,
Michael

Is it necessary to create a new composite locator in this situation?  It's not 100% clear to me if this is the case, but based off the esri documentation...

"The composite address locator stores only references to the participating address locators and geocode services; it does not contain the actual address information, indexes, and data of the individual locators."

It seems to me that if the participating address locators are simply refreshed then the composite locator should utilize the new indexes based off the updated / modified source data.

Is this a safe assumption?

[JoeBorgione]

I'm a little late on this discussion, but I'd like to make a suggestion with respect to the original post regarding:

         I have a composite address locator based on four address locators, all stored in ArcSDE (v10).

Don't store you locators in SDE.  Create a separate folder and store them there.  When I publish locators, I don't publish them to default root folder either.  I have a virtual folder called (of all things) Locators.

I don't know if this will resolve the issue you are having, but ever since I've stopped storing locators in any type of geo-database, I've led a much more prosperous and fulfilling life....  (see this thread.)