<?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: set XY values to two decimal places in polygon feature class in Standards and Interoperability Questions</title>
    <link>https://community.esri.com/t5/standards-and-interoperability-questions/set-xy-values-to-two-decimal-places-in-polygon/m-p/222715#M100</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;With shapefiles, locations are stored in binary floating point. In the geodatabase, coordinates are stored in internal integer coordinates (based on xy domain and resolution) and reported as binary floating point. So even if you wanted to, it would be impossible to save coordinates to exactly 0.01 precision as this cannot be represented exactly in binary coding.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 24 May 2016 06:27:25 GMT</pubDate>
    <dc:creator>curtvprice</dc:creator>
    <dc:date>2016-05-24T06:27:25Z</dc:date>
    <item>
      <title>set XY values to two decimal places in polygon feature class</title>
      <link>https://community.esri.com/t5/standards-and-interoperability-questions/set-xy-values-to-two-decimal-places-in-polygon/m-p/222712#M97</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would like to check with you, in Polygon feature class, how to set the XY values precision only two decimal places without rounding up. I have tried to set XYResolution to 0.01 to store only two decimal digits. But the value is rounded up and changed the position. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any setting to create a polygon feature class by truncating two decimal places of original XY values?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Eg, X= 0.389 ,&amp;nbsp; Y= 2.467 to X = 0.38 , Y = 2.46&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Dec 2015 09:47:56 GMT</pubDate>
      <guid>https://community.esri.com/t5/standards-and-interoperability-questions/set-xy-values-to-two-decimal-places-in-polygon/m-p/222712#M97</guid>
      <dc:creator>tinyMee</dc:creator>
      <dc:date>2015-12-30T09:47:56Z</dc:date>
    </item>
    <item>
      <title>Re: set XY values to two decimal places in polygon feature class</title>
      <link>https://community.esri.com/t5/standards-and-interoperability-questions/set-xy-values-to-two-decimal-places-in-polygon/m-p/222713#M98</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A href="http://desktop.arcgis.com/en/desktop/latest/tools/environments/xy-tolerance.htm" title="http://desktop.arcgis.com/en/desktop/latest/tools/environments/xy-tolerance.htm"&gt;XY Tolerance (Environment setting)—Help | ArcGIS for Desktop&lt;/A&gt; There is no mention of either rounding or truncation.&amp;nbsp; I suspect rounding would be used to enable rounding up or down to ensure features meet.&lt;/P&gt;&lt;P&gt;1.0061 1.0059&amp;nbsp; with truncation would yield 1.006 and 1.005&amp;nbsp; with rounding would yield 1.006 and 1.006&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Dec 2015 10:35:31 GMT</pubDate>
      <guid>https://community.esri.com/t5/standards-and-interoperability-questions/set-xy-values-to-two-decimal-places-in-polygon/m-p/222713#M98</guid>
      <dc:creator>DanPatterson_Retired</dc:creator>
      <dc:date>2015-12-30T10:35:31Z</dc:date>
    </item>
    <item>
      <title>Re: set XY values to two decimal places in polygon feature class</title>
      <link>https://community.esri.com/t5/standards-and-interoperability-questions/set-xy-values-to-two-decimal-places-in-polygon/m-p/222714#M99</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Could you give us a clue as to why you would want to do this?&lt;/P&gt;&lt;P&gt;It sounds like a strange requirement, especially the truncation rather than rounding.&lt;/P&gt;&lt;P&gt;If you have some experience with python, you could read the existing polygon geometries and write out another set of coordinates which have been truncated to the precision you require.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 May 2016 06:28:48 GMT</pubDate>
      <guid>https://community.esri.com/t5/standards-and-interoperability-questions/set-xy-values-to-two-decimal-places-in-polygon/m-p/222714#M99</guid>
      <dc:creator>NeilAyres</dc:creator>
      <dc:date>2016-05-03T06:28:48Z</dc:date>
    </item>
    <item>
      <title>Re: set XY values to two decimal places in polygon feature class</title>
      <link>https://community.esri.com/t5/standards-and-interoperability-questions/set-xy-values-to-two-decimal-places-in-polygon/m-p/222715#M100</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;With shapefiles, locations are stored in binary floating point. In the geodatabase, coordinates are stored in internal integer coordinates (based on xy domain and resolution) and reported as binary floating point. So even if you wanted to, it would be impossible to save coordinates to exactly 0.01 precision as this cannot be represented exactly in binary coding.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 May 2016 06:27:25 GMT</pubDate>
      <guid>https://community.esri.com/t5/standards-and-interoperability-questions/set-xy-values-to-two-decimal-places-in-polygon/m-p/222715#M100</guid>
      <dc:creator>curtvprice</dc:creator>
      <dc:date>2016-05-24T06:27:25Z</dc:date>
    </item>
  </channel>
</rss>

