<?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 Easier access to ST_GEOMETRY vertices in ArcGIS Enterprise Ideas</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-ideas/easier-access-to-st-geometry-vertices/idi-p/1188571</link>
    <description>&lt;P&gt;ST_GEOMETRY vertices should be easier to access (Oracle).&amp;nbsp;&lt;/P&gt;&lt;P&gt;Currently, ST_GEOMETRY vertices are obscured in a BLOB/LOB column within the shape object, which makes accessing the vertices difficult.&lt;/P&gt;&lt;P&gt;An alternative idea might be: store the vertex ordinates in a more transparent datatype, such as a&amp;nbsp;&lt;U&gt;varray&lt;/U&gt;,&amp;nbsp;a &lt;U&gt;nested table column&lt;/U&gt;, or&amp;nbsp;some other table collection datatype — as an&amp;nbsp;&lt;U&gt;additional/separate attribute within the &lt;EM&gt;&lt;STRONG&gt;existing&lt;/STRONG&gt;&lt;/EM&gt; SHAPE object&amp;nbsp;column&lt;/U&gt;&amp;nbsp;(not to be confused with creating an entirely new column in the &lt;EM&gt;table&lt;/EM&gt;).&lt;/P&gt;&lt;P&gt;That would make it a lot easier to work with ST_GEOMETRY vertices.&lt;/P&gt;&lt;P&gt;We're aware there are workarounds like cross joins and parsing WKT. But they're too clunky &amp;amp; slow. An easier-to-access collection datatype would be better.&lt;/P&gt;</description>
    <pubDate>Fri, 01 Jul 2022 13:43:34 GMT</pubDate>
    <dc:creator>Bud</dc:creator>
    <dc:date>2022-07-01T13:43:34Z</dc:date>
    <item>
      <title>Easier access to ST_GEOMETRY vertices</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-ideas/easier-access-to-st-geometry-vertices/idi-p/1188571</link>
      <description>&lt;P&gt;ST_GEOMETRY vertices should be easier to access (Oracle).&amp;nbsp;&lt;/P&gt;&lt;P&gt;Currently, ST_GEOMETRY vertices are obscured in a BLOB/LOB column within the shape object, which makes accessing the vertices difficult.&lt;/P&gt;&lt;P&gt;An alternative idea might be: store the vertex ordinates in a more transparent datatype, such as a&amp;nbsp;&lt;U&gt;varray&lt;/U&gt;,&amp;nbsp;a &lt;U&gt;nested table column&lt;/U&gt;, or&amp;nbsp;some other table collection datatype — as an&amp;nbsp;&lt;U&gt;additional/separate attribute within the &lt;EM&gt;&lt;STRONG&gt;existing&lt;/STRONG&gt;&lt;/EM&gt; SHAPE object&amp;nbsp;column&lt;/U&gt;&amp;nbsp;(not to be confused with creating an entirely new column in the &lt;EM&gt;table&lt;/EM&gt;).&lt;/P&gt;&lt;P&gt;That would make it a lot easier to work with ST_GEOMETRY vertices.&lt;/P&gt;&lt;P&gt;We're aware there are workarounds like cross joins and parsing WKT. But they're too clunky &amp;amp; slow. An easier-to-access collection datatype would be better.&lt;/P&gt;</description>
      <pubDate>Fri, 01 Jul 2022 13:43:34 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-ideas/easier-access-to-st-geometry-vertices/idi-p/1188571</guid>
      <dc:creator>Bud</dc:creator>
      <dc:date>2022-07-01T13:43:34Z</dc:date>
    </item>
  </channel>
</rss>

