<?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 Geocoding Quite Slow and Stalling with Some Datasets in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/geocoding-quite-slow-and-stalling-with-some/m-p/616813#M34825</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;First I will explain how I created my compiled geocoder:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;1) Created a Main locator with locator style General - Single Field, use the address point feature class as a primary table together with the KeyField alias name with the exact address field.&amp;nbsp; I use Spelling Sensitivity 100, Min Candidate Score 100, and Min Match Score 100 for Address Locator Properties.&amp;nbsp; (I have also tried different values)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;2) Created a theoretical locator with locator style US Address - Dual Ranges, use a road network feature class as a primary table with From Left ,To Left, From Right, To Right, Street Name, Suffix Type, and Suffix Direction having alias names LEFT_FROM_ADDR, LEFT_TO_ADDR, RIGHT_FROM_ADDR, RIGHT_TO_ADDR, NAME, STREET_TYPE, AND OCTANT respectively. I use Spelling Sensitivity 65, Min Candidate Score 30, and Min Match Score 50, as well as Connectors: &amp;amp; @ l and for Address Locator Properties. I also have Side Offset: 11m and End Offset 10%.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;3) I use both of the above with 1 being my priority.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;When I attempt to geocode a table of 27490 records only approximately 3000 were done 16 hours later.&amp;nbsp; When I break that dataset up into quadrants I have had no difficulty with geocoding datasets with 4645 and 5095 records.&amp;nbsp; They are done in about 5 minutes.&amp;nbsp; I have a dataset with 5575 records that takes about 25 minutes longer, sometimes stalling at certain points in the process.&amp;nbsp; The fourth dataset with 6961 records does not work.&amp;nbsp; I have tried several times sometimes lowering some of the locator properties, etc; and it just will not work.&amp;nbsp; I have a feeling that same data is what is not allowing the the entire dataset to not work.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We do have access to another geocoder that consists of a main geocoder using US Address - Single House, an apartment locator, an alias locator, and Intersection locator.&amp;nbsp; This geocoder seems to have no difficulty, taking 15-20 minutes for the enitre dataset.&amp;nbsp; I cannot speak on the accuracy however.&amp;nbsp; As you can see I am very curious what is so wrong with the one I have created.&amp;nbsp; What is missing?&amp;nbsp; Is there an issue with using a point feature class and a polyline feature class together?&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Any advice would be appreciated.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Justin&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 15 Nov 2012 21:17:32 GMT</pubDate>
    <dc:creator>JustinSmith</dc:creator>
    <dc:date>2012-11-15T21:17:32Z</dc:date>
    <item>
      <title>Geocoding Quite Slow and Stalling with Some Datasets</title>
      <link>https://community.esri.com/t5/data-management-questions/geocoding-quite-slow-and-stalling-with-some/m-p/616813#M34825</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;First I will explain how I created my compiled geocoder:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;1) Created a Main locator with locator style General - Single Field, use the address point feature class as a primary table together with the KeyField alias name with the exact address field.&amp;nbsp; I use Spelling Sensitivity 100, Min Candidate Score 100, and Min Match Score 100 for Address Locator Properties.&amp;nbsp; (I have also tried different values)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;2) Created a theoretical locator with locator style US Address - Dual Ranges, use a road network feature class as a primary table with From Left ,To Left, From Right, To Right, Street Name, Suffix Type, and Suffix Direction having alias names LEFT_FROM_ADDR, LEFT_TO_ADDR, RIGHT_FROM_ADDR, RIGHT_TO_ADDR, NAME, STREET_TYPE, AND OCTANT respectively. I use Spelling Sensitivity 65, Min Candidate Score 30, and Min Match Score 50, as well as Connectors: &amp;amp; @ l and for Address Locator Properties. I also have Side Offset: 11m and End Offset 10%.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;3) I use both of the above with 1 being my priority.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;When I attempt to geocode a table of 27490 records only approximately 3000 were done 16 hours later.&amp;nbsp; When I break that dataset up into quadrants I have had no difficulty with geocoding datasets with 4645 and 5095 records.&amp;nbsp; They are done in about 5 minutes.&amp;nbsp; I have a dataset with 5575 records that takes about 25 minutes longer, sometimes stalling at certain points in the process.&amp;nbsp; The fourth dataset with 6961 records does not work.&amp;nbsp; I have tried several times sometimes lowering some of the locator properties, etc; and it just will not work.&amp;nbsp; I have a feeling that same data is what is not allowing the the entire dataset to not work.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We do have access to another geocoder that consists of a main geocoder using US Address - Single House, an apartment locator, an alias locator, and Intersection locator.&amp;nbsp; This geocoder seems to have no difficulty, taking 15-20 minutes for the enitre dataset.&amp;nbsp; I cannot speak on the accuracy however.&amp;nbsp; As you can see I am very curious what is so wrong with the one I have created.&amp;nbsp; What is missing?&amp;nbsp; Is there an issue with using a point feature class and a polyline feature class together?&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Any advice would be appreciated.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Justin&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Nov 2012 21:17:32 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/geocoding-quite-slow-and-stalling-with-some/m-p/616813#M34825</guid>
      <dc:creator>JustinSmith</dc:creator>
      <dc:date>2012-11-15T21:17:32Z</dc:date>
    </item>
  </channel>
</rss>

