<?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 New online geocoder url returns different x,y co-ordinates for the same address in ArcGIS Online Questions</title>
    <link>https://community.esri.com/t5/arcgis-online-questions/new-online-geocoder-url-returns-different-x-y-co/m-p/355608#M17907</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Several years back we used the following Service URL to geocode addresses: arcweb.esri.com/services/v2/AddressFinder&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We upgraded our application to the new URL for geocoding: premiumtasks.arcgisonline.com/Server/services/Locater/TA_Addresses_NA/GeocodeServer&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Recently we noticed that the for the same physical building address the new ESRI geocode service returns slightly different x,y co-ordinates. This is causing problems for us as we use the x,y co-ordinates as a key in our application database and are unable to reconcile our data with older records.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We need some help in identifying the cause of the problem and the steps required to resolve it.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 05 May 2010 17:26:40 GMT</pubDate>
    <dc:creator>VaishaliShah</dc:creator>
    <dc:date>2010-05-05T17:26:40Z</dc:date>
    <item>
      <title>New online geocoder url returns different x,y co-ordinates for the same address</title>
      <link>https://community.esri.com/t5/arcgis-online-questions/new-online-geocoder-url-returns-different-x-y-co/m-p/355608#M17907</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Several years back we used the following Service URL to geocode addresses: arcweb.esri.com/services/v2/AddressFinder&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We upgraded our application to the new URL for geocoding: premiumtasks.arcgisonline.com/Server/services/Locater/TA_Addresses_NA/GeocodeServer&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Recently we noticed that the for the same physical building address the new ESRI geocode service returns slightly different x,y co-ordinates. This is causing problems for us as we use the x,y co-ordinates as a key in our application database and are unable to reconcile our data with older records.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We need some help in identifying the cause of the problem and the steps required to resolve it.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 May 2010 17:26:40 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-online-questions/new-online-geocoder-url-returns-different-x-y-co/m-p/355608#M17907</guid>
      <dc:creator>VaishaliShah</dc:creator>
      <dc:date>2010-05-05T17:26:40Z</dc:date>
    </item>
    <item>
      <title>Re: New online geocoder url returns different x,y co-ordinates for the same address</title>
      <link>https://community.esri.com/t5/arcgis-online-questions/new-online-geocoder-url-returns-different-x-y-co/m-p/355609#M17908</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;The underlying data used in the ArcGIS Online locator service is updated about every three months. For this reason, some locations may change (due to updates in the data) and therefore it is not a recommended practice to use XY coordinates as keys in your database. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;-Molly&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 May 2010 19:42:49 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-online-questions/new-online-geocoder-url-returns-different-x-y-co/m-p/355609#M17908</guid>
      <dc:creator>MollyZurn</dc:creator>
      <dc:date>2010-05-07T19:42:49Z</dc:date>
    </item>
  </channel>
</rss>

