<?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 Re: Geocoding - issues  between coordinate system and layers archieve in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/geocoding-issues-between-coordinate-system-and/m-p/322406#M18440</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;You mention 'real address'; is this an indication of 'real location'?&amp;nbsp; How did you obtain the coordinates for your retailers?&amp;nbsp; If they were geocoded with an 'address' against a street layer of address ranges, your precision issues should be expected.&lt;BR /&gt;&lt;BR /&gt;Let's say we have a street layer and we match an address 150 Main St against it.&amp;nbsp; The geocoder looks for a street called Main ST and finds a segment that has a range of 100-200 on the even side and 101-199 on the odd side.&amp;nbsp; It's going to figure that address 150 is right in the middle of the block on the even side.&amp;nbsp; The reality might be that the building with 150 painted on the front door is actually at one end of the block.&amp;nbsp; &lt;BR /&gt;&lt;BR /&gt;Accuracy in geocoding is one thing; in my example above, the locator is accurate to the block.&amp;nbsp; If you want precision, that is a X,Y value that better represents the actual location of address 150, you'll need to match against a data source that is better precision built into it (like address points, derived from parcels, gps'd points etc) rather than interpolating against a linear feature.&lt;BR /&gt;&lt;BR /&gt;Hope this helps-&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Hello Mr. Joe,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You are right. It seem that is an issue regarding the roads layer. I&amp;nbsp; spoke to&amp;nbsp; IT Departament and they told me that problem can be solved by replacing the old layer with an updated one.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I was thinking to do this update&amp;nbsp; by myself, but I guess is not an easy job for an basic user.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;kalergi&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 06 Sep 2011 07:52:23 GMT</pubDate>
    <dc:creator>FlorianKalergi</dc:creator>
    <dc:date>2011-09-06T07:52:23Z</dc:date>
    <item>
      <title>Geocoding - issues  between coordinate system and layers archieve</title>
      <link>https://community.esri.com/t5/data-management-questions/geocoding-issues-between-coordinate-system-and/m-p/322404#M18438</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Good day everyone!&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I am using an ESRI Arch Map where I have a number of layers like: roads, cities &amp;amp; villages and counties. Above those, I have another layer where and I brought in it a series of coordinates which can help me to create a map where I can see all my retailers network.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;When I chose a retailer location on my map, the coordinates indicate a different position from the real adress of retailers. The difference is between 50-150 meters. &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I am triyng to find out what caused this type of errors?!&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I&lt;/SPAN&gt;&lt;STRONG&gt; must say that all my layers are converted in to &lt;SPAN style="text-decoration:underline;"&gt;Geodatabase Feature Class &lt;/SPAN&gt;and Geographic Coordinate System GCS WGS 1984.&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thank you in advance for your time and patience!&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Best regards,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Kalergi&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Sep 2011 13:31:18 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/geocoding-issues-between-coordinate-system-and/m-p/322404#M18438</guid>
      <dc:creator>FlorianKalergi</dc:creator>
      <dc:date>2011-09-02T13:31:18Z</dc:date>
    </item>
    <item>
      <title>Re: Geocoding - issues  between coordinate system and layers archieve</title>
      <link>https://community.esri.com/t5/data-management-questions/geocoding-issues-between-coordinate-system-and/m-p/322405#M18439</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;Good day everyone!&lt;BR /&gt;&lt;BR /&gt;When I chose a retailer location on my map, the coordinates indicate a different position from the real adress of retailers. The difference is between 50-150 meters. &lt;BR /&gt;I am triyng to find out what caused this type of errors?!&lt;BR /&gt;&lt;BR /&gt;Thank you in advance for your time and patience!&lt;BR /&gt;&lt;BR /&gt;&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;You mention 'real address'; is this an indication of 'real location'?&amp;nbsp; How did you obtain the coordinates for your retailers?&amp;nbsp; If they were geocoded with an 'address' against a street layer of address ranges, your precision issues should be expected.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Let's say we have a street layer and we match an address 150 Main St against it.&amp;nbsp; The geocoder looks for a street called Main ST and finds a segment that has a range of 100-200 on the even side and 101-199 on the odd side.&amp;nbsp; It's going to figure that address 150 is right in the middle of the block on the even side.&amp;nbsp; The reality might be that the building with 150 painted on the front door is actually at one end of the block.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Accuracy in geocoding is one thing; in my example above, the locator is accurate to the block.&amp;nbsp; If you want precision, that is a X,Y value that better represents the actual location of address 150, you'll need to match against a data source that is better precision built into it (like address points, derived from parcels, gps'd points etc) rather than interpolating against a linear feature.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Hope this helps-&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 04 Sep 2011 13:03:22 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/geocoding-issues-between-coordinate-system-and/m-p/322405#M18439</guid>
      <dc:creator>JoeBorgione</dc:creator>
      <dc:date>2011-09-04T13:03:22Z</dc:date>
    </item>
    <item>
      <title>Re: Geocoding - issues  between coordinate system and layers archieve</title>
      <link>https://community.esri.com/t5/data-management-questions/geocoding-issues-between-coordinate-system-and/m-p/322406#M18440</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;You mention 'real address'; is this an indication of 'real location'?&amp;nbsp; How did you obtain the coordinates for your retailers?&amp;nbsp; If they were geocoded with an 'address' against a street layer of address ranges, your precision issues should be expected.&lt;BR /&gt;&lt;BR /&gt;Let's say we have a street layer and we match an address 150 Main St against it.&amp;nbsp; The geocoder looks for a street called Main ST and finds a segment that has a range of 100-200 on the even side and 101-199 on the odd side.&amp;nbsp; It's going to figure that address 150 is right in the middle of the block on the even side.&amp;nbsp; The reality might be that the building with 150 painted on the front door is actually at one end of the block.&amp;nbsp; &lt;BR /&gt;&lt;BR /&gt;Accuracy in geocoding is one thing; in my example above, the locator is accurate to the block.&amp;nbsp; If you want precision, that is a X,Y value that better represents the actual location of address 150, you'll need to match against a data source that is better precision built into it (like address points, derived from parcels, gps'd points etc) rather than interpolating against a linear feature.&lt;BR /&gt;&lt;BR /&gt;Hope this helps-&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Hello Mr. Joe,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You are right. It seem that is an issue regarding the roads layer. I&amp;nbsp; spoke to&amp;nbsp; IT Departament and they told me that problem can be solved by replacing the old layer with an updated one.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I was thinking to do this update&amp;nbsp; by myself, but I guess is not an easy job for an basic user.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;kalergi&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Sep 2011 07:52:23 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/geocoding-issues-between-coordinate-system-and/m-p/322406#M18440</guid>
      <dc:creator>FlorianKalergi</dc:creator>
      <dc:date>2011-09-06T07:52:23Z</dc:date>
    </item>
  </channel>
</rss>

