<?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 Rematch issues (ArcPro) in ArcGIS Pro Questions</title>
    <link>https://community.esri.com/t5/arcgis-pro-questions/geocoding-rematch-issues-arcpro/m-p/582737#M25673</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There's a process I do once a month for someone where I take an excel sheet, geocode the addresses, export it back out with an additional field that we have in our own geolocator.&amp;nbsp; Easy peasy.&amp;nbsp; Lately,&amp;nbsp;since the last upgrade I did, when I rematch addresses, it doesn't fill them with the manually matched information.&amp;nbsp; I find a good match, I hit the checkbox, it gets removed from the unnmatched list, but the results table itself remains unchanged.&amp;nbsp; I even hit the little "save edits" box.&amp;nbsp; The preivously unnmatched addresses *still* look unnmatched, even though the rematch dialogue says they're all good.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I used to do this all the time, what am I missing?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 18 Sep 2018 19:01:55 GMT</pubDate>
    <dc:creator>KimberlyMeinert</dc:creator>
    <dc:date>2018-09-18T19:01:55Z</dc:date>
    <item>
      <title>Geocoding Rematch issues (ArcPro)</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/geocoding-rematch-issues-arcpro/m-p/582737#M25673</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There's a process I do once a month for someone where I take an excel sheet, geocode the addresses, export it back out with an additional field that we have in our own geolocator.&amp;nbsp; Easy peasy.&amp;nbsp; Lately,&amp;nbsp;since the last upgrade I did, when I rematch addresses, it doesn't fill them with the manually matched information.&amp;nbsp; I find a good match, I hit the checkbox, it gets removed from the unnmatched list, but the results table itself remains unchanged.&amp;nbsp; I even hit the little "save edits" box.&amp;nbsp; The preivously unnmatched addresses *still* look unnmatched, even though the rematch dialogue says they're all good.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I used to do this all the time, what am I missing?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Sep 2018 19:01:55 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/geocoding-rematch-issues-arcpro/m-p/582737#M25673</guid>
      <dc:creator>KimberlyMeinert</dc:creator>
      <dc:date>2018-09-18T19:01:55Z</dc:date>
    </item>
    <item>
      <title>Re: Geocoding Rematch issues (ArcPro)</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/geocoding-rematch-issues-arcpro/m-p/582738#M25674</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So, I just thought of something.&amp;nbsp; We recently moved from 10.3 to 10.6 and subsequently published our geolocator to our Portal rather than in SDE.&amp;nbsp; Could that have something to do with it?&amp;nbsp; It can't transpose the information from the geolocator to the resulting feature class?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Sep 2018 19:09:48 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/geocoding-rematch-issues-arcpro/m-p/582738#M25674</guid>
      <dc:creator>KimberlyMeinert</dc:creator>
      <dc:date>2018-09-18T19:09:48Z</dc:date>
    </item>
    <item>
      <title>Re: Geocoding Rematch issues (ArcPro)</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/geocoding-rematch-issues-arcpro/m-p/582739#M25675</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It sounds like you are running into &lt;A href="https://support.esri.com/en/bugs/nimbus/QlVHLTAwMDExNjMyMw=="&gt;BUG-000116323&lt;/A&gt;.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Sep 2018 21:43:25 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/geocoding-rematch-issues-arcpro/m-p/582739#M25675</guid>
      <dc:creator>ShanaBritt</dc:creator>
      <dc:date>2018-09-18T21:43:25Z</dc:date>
    </item>
    <item>
      <title>Re: Geocoding Rematch issues (ArcPro)</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/geocoding-rematch-issues-arcpro/m-p/582740#M25676</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ah!&amp;nbsp; Yes, that's probably it.&amp;nbsp; That didn't come up in my search.&amp;nbsp; Thank you, at least I know it's a "thing".&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Sep 2018 12:57:36 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/geocoding-rematch-issues-arcpro/m-p/582740#M25676</guid>
      <dc:creator>KimberlyMeinert</dc:creator>
      <dc:date>2018-09-19T12:57:36Z</dc:date>
    </item>
    <item>
      <title>Re: Geocoding Rematch issues (ArcPro)</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/geocoding-rematch-issues-arcpro/m-p/582741#M25677</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am running Pro 2.2.4 and still have the same issue. Hard to promote a product when it doesn't work right. Ugh.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Jan 2019 14:01:12 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/geocoding-rematch-issues-arcpro/m-p/582741#M25677</guid>
      <dc:creator>SharonJanzen</dc:creator>
      <dc:date>2019-01-22T14:01:12Z</dc:date>
    </item>
  </channel>
</rss>

