<?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: Addresses not matching to streets though ranges and data are complete in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/geocoding-addresses-not-matching-to-streets-though/m-p/157007#M8778</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Noticed some addresses are not geocoding streets even though the data is complete for the address file and the street feature class used for the Address Locator.&amp;nbsp; Went into the interactive window thinking it would yield us some results but nothing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We rebuilt the locator thinking that would correct it but no dice.&amp;nbsp; Is there a new bug out there in 10.3? &lt;IMG src="https://community.esri.com/legacyfs/online/emoticons/plain.png" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 01 May 2015 17:09:49 GMT</pubDate>
    <dc:creator>LorneWoods</dc:creator>
    <dc:date>2015-05-01T17:09:49Z</dc:date>
    <item>
      <title>Geocoding: Addresses not matching to streets though ranges and data are complete</title>
      <link>https://community.esri.com/t5/data-management-questions/geocoding-addresses-not-matching-to-streets-though/m-p/157007#M8778</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Noticed some addresses are not geocoding streets even though the data is complete for the address file and the street feature class used for the Address Locator.&amp;nbsp; Went into the interactive window thinking it would yield us some results but nothing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We rebuilt the locator thinking that would correct it but no dice.&amp;nbsp; Is there a new bug out there in 10.3? &lt;IMG src="https://community.esri.com/legacyfs/online/emoticons/plain.png" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 May 2015 17:09:49 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/geocoding-addresses-not-matching-to-streets-though/m-p/157007#M8778</guid>
      <dc:creator>LorneWoods</dc:creator>
      <dc:date>2015-05-01T17:09:49Z</dc:date>
    </item>
    <item>
      <title>Re: Geocoding: Addresses not matching to streets though ranges and data are complete</title>
      <link>https://community.esri.com/t5/data-management-questions/geocoding-addresses-not-matching-to-streets-though/m-p/157008#M8779</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Special characters and apt/ste/blg in the address can cause geocoding those entries to fail.&amp;nbsp; Could you provide the locator and some sample data for others to test?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Steven&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 May 2015 17:48:30 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/geocoding-addresses-not-matching-to-streets-though/m-p/157008#M8779</guid>
      <dc:creator>StevenGraf1</dc:creator>
      <dc:date>2015-05-01T17:48:30Z</dc:date>
    </item>
    <item>
      <title>Re: Geocoding: Addresses not matching to streets though ranges and data are complete</title>
      <link>https://community.esri.com/t5/data-management-questions/geocoding-addresses-not-matching-to-streets-though/m-p/157009#M8780</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It appears that it is an issue with the single address field.&lt;BR /&gt;&lt;BR /&gt;Our work around:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Standardize the single line address and parse out into individual fields.&lt;/LI&gt;&lt;LI&gt;Create a new field and concatenate the address data into one address.&lt;/LI&gt;&lt;LI&gt;Geocode on the newly concatenated single line field.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The addresses that were not geocoding now appear in the correct location.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 May 2015 19:31:40 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/geocoding-addresses-not-matching-to-streets-though/m-p/157009#M8780</guid>
      <dc:creator>LorneWoods</dc:creator>
      <dc:date>2015-05-06T19:31:40Z</dc:date>
    </item>
    <item>
      <title>Re: Geocoding: Addresses not matching to streets though ranges and data are complete</title>
      <link>https://community.esri.com/t5/data-management-questions/geocoding-addresses-not-matching-to-streets-though/m-p/157010#M8781</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm curious with your correction; you are using a single address field locator on linear features? Can you provide a screen shot or two that shows your data and locator? I use single address field locators for points and polygons but ranges for streets. Or did I completely mis read your post and you cleaned up your addresses?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hey Steven- thats got to be the best avatar ever! &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 May 2015 23:48:36 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/geocoding-addresses-not-matching-to-streets-though/m-p/157010#M8781</guid>
      <dc:creator>JoeBorgione</dc:creator>
      <dc:date>2015-05-06T23:48:36Z</dc:date>
    </item>
  </channel>
</rss>

