<?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 Best address locator? in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/best-address-locator/m-p/99504#M5768</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Does anybody have an address locator they could share that works for geocoding simple tables of addresses in North American (USA) towns? I'm getting bogged down just trying to create a locator so I can geocode. Thanks, Alex&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 07 Sep 2016 21:28:09 GMT</pubDate>
    <dc:creator>AlexBullen1</dc:creator>
    <dc:date>2016-09-07T21:28:09Z</dc:date>
    <item>
      <title>Best address locator?</title>
      <link>https://community.esri.com/t5/data-management-questions/best-address-locator/m-p/99504#M5768</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Does anybody have an address locator they could share that works for geocoding simple tables of addresses in North American (USA) towns? I'm getting bogged down just trying to create a locator so I can geocode. Thanks, Alex&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Sep 2016 21:28:09 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/best-address-locator/m-p/99504#M5768</guid>
      <dc:creator>AlexBullen1</dc:creator>
      <dc:date>2016-09-07T21:28:09Z</dc:date>
    </item>
    <item>
      <title>Re: Best address locator?</title>
      <link>https://community.esri.com/t5/data-management-questions/best-address-locator/m-p/99505#M5769</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I guess you could use ArcGIS Oniline. &amp;nbsp;Seems like there is a university in Texas that has a similar service as well. What part of creating a locator is bogging you down?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;edited after a millisecond google search: &amp;nbsp;&lt;A class="link-titled" href="http://geoservices.tamu.edu/Services/Geocode/" title="http://geoservices.tamu.edu/Services/Geocode/"&gt;Texas A&amp;amp;M Geocoder - Free online geocoding&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Sep 2016 11:41:04 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/best-address-locator/m-p/99505#M5769</guid>
      <dc:creator>JoeBorgione</dc:creator>
      <dc:date>2016-09-08T11:41:04Z</dc:date>
    </item>
    <item>
      <title>Re: Best address locator?</title>
      <link>https://community.esri.com/t5/data-management-questions/best-address-locator/m-p/99506#M5770</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Getting bogged down at selecting the proper reference data to create the locator. I don't know what to choose to make it work and there's not a lot of guidance from ESRI.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I did create a locator using our address point layer and it works okay. It won't infer addresses that aren't in the layer already. Is this normal?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Sep 2016 14:33:04 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/best-address-locator/m-p/99506#M5770</guid>
      <dc:creator>AlexBullen1</dc:creator>
      <dc:date>2016-09-09T14:33:04Z</dc:date>
    </item>
    <item>
      <title>Re: Best address locator?</title>
      <link>https://community.esri.com/t5/data-management-questions/best-address-locator/m-p/99507#M5771</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;It won't infer addresses that aren't in the layer already. Is this normal?&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Typically, yes.&amp;nbsp; This is normal behavior when using a point feature class as your reference data.&amp;nbsp; They like an exact match.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You might want to get some street centerline data as well, and use a composite where you look at the points first followed by the streets.&amp;nbsp; Typically streets are more forgiving; you won't get a 100% match but they will get you in the ballpark.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Sep 2016 15:01:56 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/best-address-locator/m-p/99507#M5771</guid>
      <dc:creator>JoeBorgione</dc:creator>
      <dc:date>2016-09-09T15:01:56Z</dc:date>
    </item>
    <item>
      <title>Re: Best address locator?</title>
      <link>https://community.esri.com/t5/data-management-questions/best-address-locator/m-p/99508#M5772</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the tips. I made another locator out of my centerline feature and then made a composite out of the two. Will proceed forward with this locator.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Sep 2016 21:59:14 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/best-address-locator/m-p/99508#M5772</guid>
      <dc:creator>AlexBullen1</dc:creator>
      <dc:date>2016-09-13T21:59:14Z</dc:date>
    </item>
    <item>
      <title>Re: Best address locator?</title>
      <link>https://community.esri.com/t5/data-management-questions/best-address-locator/m-p/99509#M5773</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Let us know how it works out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With respect to the original title (Best Address Locator)&amp;nbsp; I would say the best one is the one that works for you and gives you the desired results...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Sep 2016 22:15:21 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/best-address-locator/m-p/99509#M5773</guid>
      <dc:creator>JoeBorgione</dc:creator>
      <dc:date>2016-09-13T22:15:21Z</dc:date>
    </item>
    <item>
      <title>Re: Best address locator?</title>
      <link>https://community.esri.com/t5/data-management-questions/best-address-locator/m-p/99510#M5774</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Alex&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;from above comments look like you are using composite address locator,&lt;/P&gt;&lt;P&gt;its works for you or still getting slowness issue in that.&lt;BR /&gt;&lt;BR /&gt;In our environment we are using composite address locator which are mamade upsing point address data.&lt;BR /&gt;And its work fine and accurate for us&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Sep 2016 07:03:51 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/best-address-locator/m-p/99510#M5774</guid>
      <dc:creator>Anonymous User</dc:creator>
      <dc:date>2016-09-14T07:03:51Z</dc:date>
    </item>
    <item>
      <title>Re: Best address locator?</title>
      <link>https://community.esri.com/t5/data-management-questions/best-address-locator/m-p/99511#M5775</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So far so good, thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Sep 2016 14:14:21 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/best-address-locator/m-p/99511#M5775</guid>
      <dc:creator>AlexBullen1</dc:creator>
      <dc:date>2016-09-14T14:14:21Z</dc:date>
    </item>
  </channel>
</rss>

