topic Re: Dynamic data reference source for geocoding in Data Management Questions

Dynamic data reference source for geocoding

JaredYost — Mon, 04 Mar 2013 17:36:47 GMT

Is there a way to generate an address locator that will use dynamic data rather than using the standard data snapshot?

I manage the GIS data for a small municipality. We have addresses in a SDE database server. I have created a service for city employees to be able to update/fix addresses using a webmap editor. This creates a dynamic set of address data that updates regularly, often multiple times a week. From what I understand when you create an address locator it grabs a snapshot of your data to use. http://resources.arcgis.com/en/help/main/10.1/index.html#/The_geocoding_workflow/00250000000p000000/

This snapshot is static, any update from that point on in my reference data will not show up during a geocode request.

My guess is that the snapshot is done to reduce bottle necking and enhance performance through indexing.

Any Ideas on how to make it use dynamic data? I'm avoiding building a model/chron job and having it create a new service because I will have multiple continuously active applications pointing to the geocoding service.

Thanks

Re: Dynamic data reference source for geocoding

JaredYost — Tue, 05 Mar 2013 18:22:12 GMT

Well I have found the standard SOP is to run a rebuild.
However now I am running into a bug where it will not rebuild my locator at all even manually through toolbox. It gives me an error message saying my locator was built with a pre 9.2 ver. even though I built the address locator just moments ago with 10.1 sp1.

Re: Dynamic data reference source for geocoding

MichaelVolz — Tue, 05 Mar 2013 18:32:17 GMT

Could it be that you are using a custom .lot file as the basis for your address locator that was built pre 9.2?

Re: Dynamic data reference source for geocoding

JaredYost — Tue, 05 Mar 2013 18:36:10 GMT

Thanks for the reply, The laptop I am using has only had ver 10 and 10.1 on it. I cant imagine a way the .lot file would migrate? could it have been drug along with an old .mxd template?

Re: Dynamic data reference source for geocoding

MichaelVolz — Tue, 05 Mar 2013 18:40:36 GMT

How does an mxd work in with your address locator?

What type of locator are you trying to build (e.g.General - Single Field, US Address - Dual Ranges, etc.)?

Re: Dynamic data reference source for geocoding

JaredYost — Tue, 05 Mar 2013 18:53:32 GMT

.mxd was a red herring. Disregard

Ok I found my problem. Maybe it relates to yours. I was storing my locator in the sde database. I just rebuilt and tested by simply storing it in a web accessible folder and all is well, successfully rebuilt and was able to generate a service from it.

You might try storing your locator in a different place and retrying your script based method.

Thanks for the help.

Re: Dynamic data reference source for geocoding

MichaelVolz — Tue, 05 Mar 2013 19:10:52 GMT

Have you tried to rebuild your locator with a scheduled task? This is where I am having the issue. I can rebuild my locators in ArcCatalog as well as in a standalone python script, but the address locator gets corrupted every time I try to rebuild it when called as a Windows Server 2008 R2 scheduled task whether called directly from python or from a bat file that calls the python script.

Re: Dynamic data reference source for geocoding

JaredYost — Tue, 05 Mar 2013 20:11:07 GMT

That's my next step, I have a similar environment as well. It will probably take me a couple of days to get to it, will reply back here after I try.