<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Geocoding fast... and faster... in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/geocoding-fast-and-faster/m-p/99502#M5766</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I have 8 million address points for CA.&amp;nbsp; I have the zip locators that are used in my composite broken down my the first two digits of the zip code.&amp;nbsp; I apply a query to my input table in the composite to feed the records into the appropriate locator.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;A little work, but got the locator searching 400k points from 8 million and performance improved greatly.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 06 Apr 2011 21:02:46 GMT</pubDate>
    <dc:creator>AndrewDecker</dc:creator>
    <dc:date>2011-04-06T21:02:46Z</dc:date>
    <item>
      <title>Geocoding fast... and faster...</title>
      <link>https://community.esri.com/t5/data-management-questions/geocoding-fast-and-faster/m-p/99499#M5763</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;How to make geocoding faster?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I have a Composite Locator with 6 locators within: Parcel down to County.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I use it to geocode 1.5 million records each week. It takes upwards of 15-18 hours to complete.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;What can I do to improve the speed either within the locators or within the table being geocoded?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The only thing I can think of is to arrange/organize/index the table in some manner...&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Any thoughts are greatly appreciated.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Keith&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Mar 2011 18:04:15 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/geocoding-fast-and-faster/m-p/99499#M5763</guid>
      <dc:creator>KeithSandell</dc:creator>
      <dc:date>2011-03-25T18:04:15Z</dc:date>
    </item>
    <item>
      <title>Re: Geocoding fast... and faster...</title>
      <link>https://community.esri.com/t5/data-management-questions/geocoding-fast-and-faster/m-p/99500#M5764</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I found this Geocoding Blog entry that talks about ramping up the performance of address locators. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://blogs.esri.com/dev/blogs/geocoding/archive/2011/02/09/tuning-a-locator-for-improved-performance.aspx"&gt;http://blogs.esri.com/dev/blogs/geocoding/archive/2011/02/09/tuning-a-locator-for-improved-performance.aspx&lt;/A&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I'm working towards this. I'll touch base again with the results.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 28 Mar 2011 14:35:30 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/geocoding-fast-and-faster/m-p/99500#M5764</guid>
      <dc:creator>KeithSandell</dc:creator>
      <dc:date>2011-03-28T14:35:30Z</dc:date>
    </item>
    <item>
      <title>Re: Geocoding fast... and faster...</title>
      <link>https://community.esri.com/t5/data-management-questions/geocoding-fast-and-faster/m-p/99501#M5765</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;I found this Geocoding Blog entry that talks about ramping up the performance of address locators. &lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://blogs.esri.com/dev/blogs/geocoding/archive/2011/02/09/tuning-a-locator-for-improved-performance.aspx"&gt;http://blogs.esri.com/dev/blogs/geocoding/archive/2011/02/09/tuning-a-locator-for-improved-performance.aspx&lt;/A&gt; &lt;BR /&gt;&lt;BR /&gt;I'm working towards this. I'll touch base again with the results.&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Keith- that's a great blog post; thanks for sharing it!&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 28 Mar 2011 18:05:10 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/geocoding-fast-and-faster/m-p/99501#M5765</guid>
      <dc:creator>JoeBorgione</dc:creator>
      <dc:date>2011-03-28T18:05:10Z</dc:date>
    </item>
    <item>
      <title>Re: Geocoding fast... and faster...</title>
      <link>https://community.esri.com/t5/data-management-questions/geocoding-fast-and-faster/m-p/99502#M5766</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I have 8 million address points for CA.&amp;nbsp; I have the zip locators that are used in my composite broken down my the first two digits of the zip code.&amp;nbsp; I apply a query to my input table in the composite to feed the records into the appropriate locator.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;A little work, but got the locator searching 400k points from 8 million and performance improved greatly.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Apr 2011 21:02:46 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/geocoding-fast-and-faster/m-p/99502#M5766</guid>
      <dc:creator>AndrewDecker</dc:creator>
      <dc:date>2011-04-06T21:02:46Z</dc:date>
    </item>
    <item>
      <title>Re: Geocoding fast... and faster...</title>
      <link>https://community.esri.com/t5/data-management-questions/geocoding-fast-and-faster/m-p/99503#M5767</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Can't emphasize enough how much it helps to sort your reference data, as I've learned over the past little while.&amp;nbsp; Sorting you input data seems to have an even greater impact on speed but both are well-worth the step.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 May 2011 15:24:27 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/geocoding-fast-and-faster/m-p/99503#M5767</guid>
      <dc:creator>AndrewDecker</dc:creator>
      <dc:date>2011-05-13T15:24:27Z</dc:date>
    </item>
  </channel>
</rss>

