<?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>idea Improve documentation for ST_GEOMETRY() constructor function in ArcGIS Enterprise Ideas</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-ideas/improve-documentation-for-st-geometry-constructor/idi-p/1180924</link>
    <description>&lt;P&gt;Regarding the docs for the ST_GEOMETRY() constructor function:&lt;BR /&gt;&lt;A href="https://desktop.arcgis.com/en/arcmap/latest/manage-data/using-sql-with-gdbs/st-geometry.htm" target="_blank" rel="noopener"&gt;https://desktop.arcgis.com/en/arcmap/latest/manage-data/using-sql-with-gdbs/st-geometry.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Idea for improving the docs:&lt;BR /&gt;When constructing a polygon via WKT: Could a blurb be added to the docs to make it clear that the last vertex of the polygon needs to be &lt;U&gt;&lt;EM&gt;exactly&lt;/EM&gt;&lt;/U&gt; the same as the first vertex of the polygon?&lt;/P&gt;&lt;P&gt;I don't think the docs currently include that information. Key details like that would be very helpful when troubleshooting issues.&lt;/P&gt;&lt;P&gt;I suppose this would apply to the&amp;nbsp;ST_GeomFromText() function too, which does something similar to ST_Geometry().&lt;/P&gt;</description>
    <pubDate>Fri, 10 Jun 2022 05:47:05 GMT</pubDate>
    <dc:creator>Bud</dc:creator>
    <dc:date>2022-06-10T05:47:05Z</dc:date>
    <item>
      <title>Improve documentation for ST_GEOMETRY() constructor function</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-ideas/improve-documentation-for-st-geometry-constructor/idi-p/1180924</link>
      <description>&lt;P&gt;Regarding the docs for the ST_GEOMETRY() constructor function:&lt;BR /&gt;&lt;A href="https://desktop.arcgis.com/en/arcmap/latest/manage-data/using-sql-with-gdbs/st-geometry.htm" target="_blank" rel="noopener"&gt;https://desktop.arcgis.com/en/arcmap/latest/manage-data/using-sql-with-gdbs/st-geometry.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Idea for improving the docs:&lt;BR /&gt;When constructing a polygon via WKT: Could a blurb be added to the docs to make it clear that the last vertex of the polygon needs to be &lt;U&gt;&lt;EM&gt;exactly&lt;/EM&gt;&lt;/U&gt; the same as the first vertex of the polygon?&lt;/P&gt;&lt;P&gt;I don't think the docs currently include that information. Key details like that would be very helpful when troubleshooting issues.&lt;/P&gt;&lt;P&gt;I suppose this would apply to the&amp;nbsp;ST_GeomFromText() function too, which does something similar to ST_Geometry().&lt;/P&gt;</description>
      <pubDate>Fri, 10 Jun 2022 05:47:05 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-ideas/improve-documentation-for-st-geometry-constructor/idi-p/1180924</guid>
      <dc:creator>Bud</dc:creator>
      <dc:date>2022-06-10T05:47:05Z</dc:date>
    </item>
    <item>
      <title>Re: Improve documentation for ST_GEOMETRY() constructor function</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-ideas/improve-documentation-for-st-geometry-constructor/idc-p/1181247#M2871</link>
      <description>&lt;P&gt;Interesting examples, thank you for this.&lt;/P&gt;&lt;P&gt;Putting the specific error message aside, I wonder if this ArcMap behavior is due to the coordinate system tolerance inherent in&amp;nbsp;&lt;A href="https://downloads.esri.com/support/whitepapers/ao_/J9655_Understanding_Coordinate_Management_Esri_Whitepaper.pdf" target="_self"&gt;spatial domain model&lt;/A&gt;&amp;nbsp;that&amp;nbsp;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/1126"&gt;@DerekLaw&lt;/a&gt;&amp;nbsp;mentioned in the other post.&lt;/P&gt;&lt;P&gt;WKT has no comparable "model" to discern tolerance, like ESRI products do. So any WKT representation must be exact, but data in ArcMap (perhaps your example coordinates) that fall within the tolerance are therefore considered topologically closed.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Jun 2022 20:03:58 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-ideas/improve-documentation-for-st-geometry-constructor/idc-p/1181247#M2871</guid>
      <dc:creator>Anonymous User</dc:creator>
      <dc:date>2022-06-08T20:03:58Z</dc:date>
    </item>
    <item>
      <title>Re: Improve documentation for ST_GEOMETRY() constructor function</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-ideas/improve-documentation-for-st-geometry-constructor/idc-p/1181266#M2873</link>
      <description>&lt;P&gt;In my opinion "back and forth" posts are often better for learning than simply reading a correct answer. Good insight that the ArcMap GUI could be hiding the closing point. Sometimes GUI sugar is difficult to peel back when you're dealing with more primitive types. I wouldn't have guessed that from the text since I can't see everything you're seeing.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Jun 2022 20:51:18 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-ideas/improve-documentation-for-st-geometry-constructor/idc-p/1181266#M2873</guid>
      <dc:creator>Anonymous User</dc:creator>
      <dc:date>2022-06-08T20:51:18Z</dc:date>
    </item>
  </channel>
</rss>

