<?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 Spatial Accuracy in Standards and Interoperability Questions</title>
    <link>https://community.esri.com/t5/standards-and-interoperability-questions/spatial-accuracy/m-p/709297#M368</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;What are there spatial accuracy issues between coverages, shapefiles and geodatabases?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Kobe&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 05 Oct 2010 15:51:01 GMT</pubDate>
    <dc:creator>KobeHarkins</dc:creator>
    <dc:date>2010-10-05T15:51:01Z</dc:date>
    <item>
      <title>Spatial Accuracy</title>
      <link>https://community.esri.com/t5/standards-and-interoperability-questions/spatial-accuracy/m-p/709297#M368</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;What are there spatial accuracy issues between coverages, shapefiles and geodatabases?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Kobe&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Oct 2010 15:51:01 GMT</pubDate>
      <guid>https://community.esri.com/t5/standards-and-interoperability-questions/spatial-accuracy/m-p/709297#M368</guid>
      <dc:creator>KobeHarkins</dc:creator>
      <dc:date>2010-10-05T15:51:01Z</dc:date>
    </item>
    <item>
      <title>Re: Spatial Accuracy</title>
      <link>https://community.esri.com/t5/standards-and-interoperability-questions/spatial-accuracy/m-p/709298#M369</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Kobe&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;This is quite a big topic, but the short story is coverages come in two flavours - having single or double precision coordinates - and use the concept of a fuzzy tolerance when geoprocessing against other coverages - coordinates within the tolerance of each other are considered identical.&amp;nbsp; Shapefiles are always double precision and have no concept of control over coordinate comparison tolerance - don't use them.&amp;nbsp; Geodatabases use a storage resolution for their features and an additional XY tolerance you use to model the accuracy of the data when making coordinate comparisons.&amp;nbsp; Because much geoprocessing functionality depends on coordinate comparison geodatabases are the recommended storage workspace for your data.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Oct 2010 15:31:29 GMT</pubDate>
      <guid>https://community.esri.com/t5/standards-and-interoperability-questions/spatial-accuracy/m-p/709298#M369</guid>
      <dc:creator>BruceHarold</dc:creator>
      <dc:date>2010-10-06T15:31:29Z</dc:date>
    </item>
  </channel>
</rss>

