topic Re: Geocoding Service- Rebuild Locators workflow in Developers Questions

Geocoding Service- Rebuild Locators workflow

RajuGopinath — Tue, 23 Aug 2016 14:03:08 GMT

We are migrating from ArcGIS Desktop/Server 10.1 to 10.3.1. Now, noticed a big change with Geocoding Service - Rebuilding locators and ESRI never mentions about what the new workflow should be?

We have reference data changing every night- so have to rebuild locators every night to have an accurate address search for our website. In 10.1 ArcGIS Server, our workflow was :

Stop Geocoding Service
Update reference data and Rebuild all locators including Composite locator
Start Geocoding service- !!!!!boom all update appears

With 10.3.1, ESRI won't allow rebuilding composite locator. Instead suggest recreating it.

So, my question is Should we have to republish/overwrite Geocoding service every night if we've to recreate Composite locator every night? What's the workflow?

Or can this composite locator copied over to server which can be consumed by geocoding service?

Any thoughts?

Re: Geocoding Service- Rebuild Locators workflow

JoeBorgione — Tue, 23 Aug 2016 14:15:06 GMT

From what I understand, the composite doesn't need to be rebuilt which is why you aren't "allowed' to. For my application, I prefer not to register the data with the server so consequently I copy everything over to it. That way you don't need to shut down the published service; you just overwrite it. Your mileage may vary....

Re: Geocoding Service- Rebuild Locators workflow

RajuGopinath — Tue, 23 Aug 2016 14:25:27 GMT

Thanks- can you please elaborate your answer?

So, basically you need to rebuild all other locators, recreate composite and then overwrite geocoding service?

Is that what you meant by copying data over (copying composite locator as a part of overwrite service)?

Unfortunately, we need to do this every night.

Re: Geocoding Service- Rebuild Locators workflow

JoeBorgione — Tue, 23 Aug 2016 14:52:29 GMT

Sure:

I have a stack of individual locators that are maintained as their respective data changes. Within that stack are a couple that don't change (like freeways), but the others, streets, address points, common name points are always in a state of flux.

When you publish a composite, or any other service for that matter, you can do it one of two ways:

1. If you register the data the services use with the ArcGIS server, the published service is linked to the original data.

2. If you do not register the the data the services use with the ArcGIS server, all that data is packaged up and sent to the ArcGIS Server.

With the first option, in order to rebuild a locator, you must shut the service because there will be a lock on the locator. I chose to go with the second option as it allows me a bit more flexibility with my work flow. I don't want any connection with ArcGIS server and the original data sources. If the workspace where the original data sources reside has some sort of failure, I need my geocoding services to remain up and running. [I use the term workspace instead of hard drive or machine, as everything I do is in the virtual environment.]

I can update data, I can rebuild and test locators, I can add or delete locators from the composite; basically whatever I want, without impacting the services. When I'm happy with what I have, I simply publish the composite, and off it all goes, replacing the old with the new. With respect to your question, no I do not re-create the composite. There is no need. You can do this nightly. You can do this every two weeks; montly, yearly. You can do this as often as you like.

I hope this clarifies it for you.

Re: Geocoding Service- Rebuild Locators workflow

RajuGopinath — Tue, 23 Aug 2016 15:30:17 GMT

Thanks Joe

Re: Geocoding Service- Rebuild Locators workflow

LeoLadefian5 — Mon, 01 May 2017 16:24:31 GMT

Hi Joe, it's my understanding that any change in the data requires a locator to be rebuilt. How do you handle the rebuilding if the data is still attached to the service/ geocoder? It still needs to be stopped correct? Or are you republishing the service with every change?

Re: Geocoding Service- Rebuild Locators workflow

JoeBorgione — Mon, 01 May 2017 16:55:55 GMT

Yes, if the data is still attached to the service/geocoder in any way, shape or form, you need to stop the service in order to make your updates.

Re: Geocoding Service- Rebuild Locators workflow

LeoLadefian5 — Mon, 01 May 2017 20:08:08 GMT

So if my data is not connected to the locator, (only being copied to the server), how is the data being updated?

Re: Geocoding Service- Rebuild Locators workflow

JoeBorgione — Mon, 01 May 2017 20:33:03 GMT

Not sure I follow your question. You'd be doing any an all updates to the source data. Once you make your edits to the source data, you have to rebuild the locator, and republish it. I suggest recreating the locator though; it's easy in model builder. Rebuilding locators in 10.3.1 didn't work. I don't know what version you are working with or if the problem got fixed.

From my earlier post:

2. If you do not register the the data the services use with the ArcGIS server, all that data is packaged up and sent to the ArcGIS Server.

...I can update data, I can rebuild and test locators, I can add or delete locators from the composite; basically whatever I want, without impacting the services. When I'm happy with what I have, I simply publish the composite, and off it all goes, replacing the old with the new. ...

Leo Ladefian‌

Re: Geocoding Service- Rebuild Locators workflow

LeoLadefian5 — Mon, 01 May 2017 20:59:30 GMT

Gotcha, I was trying to create a workflow that didn't involve republishing, I guess it's just one more step.

Re: Geocoding Service- Rebuild Locators workflow

PatrickThorsell — Wed, 25 May 2022 21:01:53 GMT

Anyone know of a script that rebuilds geocoders?