<?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 ST_STARTPOINT &amp;amp; ST_ENDPOINT for multi-part features in ArcGIS Enterprise Ideas</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-ideas/st-startpoint-amp-st-endpoint-for-multi-part/idi-p/1176173</link>
    <description>&lt;P&gt;SDE.ST_GEOMETRY in Oracle:&lt;/P&gt;&lt;P&gt;Currently, the &lt;A href="https://desktop.arcgis.com/en/arcmap/latest/manage-data/using-sql-with-gdbs/st-startpoint.htm" target="_self"&gt;ST_STARTPOINT&lt;/A&gt; function can only be used for single-part features (aka a linestring).&lt;/P&gt;&lt;P&gt;If we try to use ST_STARTPOINT on multi-part features (multilinesting) then the function fails. We are forced to workaround that limitation by isolating a specific part/geometry from the multi-part feature, which only adds to the complexity and slowness of a query.&lt;BR /&gt;&lt;FONT face="courier new,courier" color="#0000FF"&gt;sde.st_startpoint(sde.st_geometryn(shape, 1))&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;It would be better if&amp;nbsp;ST_STARTPOINT would just get the first point &lt;STRONG&gt;of the first part&lt;/STRONG&gt; — by default.&lt;/P&gt;&lt;P&gt;The same applies to &lt;A href="https://desktop.arcgis.com/en/arcmap/latest/manage-data/using-sql-with-gdbs/st-endpoint.htm" target="_self"&gt;ST_ENDPOINT&lt;/A&gt;. It would be better if it would just get the last point &lt;STRONG&gt;of the last part&lt;/STRONG&gt; — by default. The workaround is too complicated/slow:&lt;BR /&gt;&lt;FONT face="courier new,courier" color="#0000FF"&gt;sde.st_endpoint(sde.st_geometryn(shape, sde.st_numgeometries(shape)))&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Could&amp;nbsp;ST_STARTPOINT and ST_ENDPOINT be improved with better support for multi-part features?&lt;/P&gt;&lt;P&gt;For what it's worth, if that enhancement were implemented, we would still have the option to get the startpoint or endpoint of a specific part, if we wanted to. So that functionality wouldn't be lost.&lt;BR /&gt;&lt;FONT face="courier new,courier" color="#0000FF"&gt;sde.st_startpoint(sde.st_geometryn(shape, &lt;FONT size="4"&gt;&lt;STRONG&gt;n&lt;/STRONG&gt;&lt;/FONT&gt;))&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Edit: The ST_PointN function has the same problem.&lt;/P&gt;</description>
    <pubDate>Wed, 06 Jul 2022 18:09:47 GMT</pubDate>
    <dc:creator>Bud</dc:creator>
    <dc:date>2022-07-06T18:09:47Z</dc:date>
    <item>
      <title>ST_STARTPOINT &amp; ST_ENDPOINT for multi-part features</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-ideas/st-startpoint-amp-st-endpoint-for-multi-part/idi-p/1176173</link>
      <description>&lt;P&gt;SDE.ST_GEOMETRY in Oracle:&lt;/P&gt;&lt;P&gt;Currently, the &lt;A href="https://desktop.arcgis.com/en/arcmap/latest/manage-data/using-sql-with-gdbs/st-startpoint.htm" target="_self"&gt;ST_STARTPOINT&lt;/A&gt; function can only be used for single-part features (aka a linestring).&lt;/P&gt;&lt;P&gt;If we try to use ST_STARTPOINT on multi-part features (multilinesting) then the function fails. We are forced to workaround that limitation by isolating a specific part/geometry from the multi-part feature, which only adds to the complexity and slowness of a query.&lt;BR /&gt;&lt;FONT face="courier new,courier" color="#0000FF"&gt;sde.st_startpoint(sde.st_geometryn(shape, 1))&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;It would be better if&amp;nbsp;ST_STARTPOINT would just get the first point &lt;STRONG&gt;of the first part&lt;/STRONG&gt; — by default.&lt;/P&gt;&lt;P&gt;The same applies to &lt;A href="https://desktop.arcgis.com/en/arcmap/latest/manage-data/using-sql-with-gdbs/st-endpoint.htm" target="_self"&gt;ST_ENDPOINT&lt;/A&gt;. It would be better if it would just get the last point &lt;STRONG&gt;of the last part&lt;/STRONG&gt; — by default. The workaround is too complicated/slow:&lt;BR /&gt;&lt;FONT face="courier new,courier" color="#0000FF"&gt;sde.st_endpoint(sde.st_geometryn(shape, sde.st_numgeometries(shape)))&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Could&amp;nbsp;ST_STARTPOINT and ST_ENDPOINT be improved with better support for multi-part features?&lt;/P&gt;&lt;P&gt;For what it's worth, if that enhancement were implemented, we would still have the option to get the startpoint or endpoint of a specific part, if we wanted to. So that functionality wouldn't be lost.&lt;BR /&gt;&lt;FONT face="courier new,courier" color="#0000FF"&gt;sde.st_startpoint(sde.st_geometryn(shape, &lt;FONT size="4"&gt;&lt;STRONG&gt;n&lt;/STRONG&gt;&lt;/FONT&gt;))&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Edit: The ST_PointN function has the same problem.&lt;/P&gt;</description>
      <pubDate>Wed, 06 Jul 2022 18:09:47 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-ideas/st-startpoint-amp-st-endpoint-for-multi-part/idi-p/1176173</guid>
      <dc:creator>Bud</dc:creator>
      <dc:date>2022-07-06T18:09:47Z</dc:date>
    </item>
    <item>
      <title>Re: ST_STARTPOINT &amp; ST_ENDPOINT for multi-part features</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-ideas/st-startpoint-amp-st-endpoint-for-multi-part/idc-p/1176175#M2834</link>
      <description>&lt;P&gt;Like this:&lt;/P&gt;&lt;PRE&gt;select&lt;BR /&gt;    sdo_lrs.geom_segment_&lt;STRONG&gt;end_pt&lt;/STRONG&gt;(&lt;BR /&gt;        sdo_geometry('MULTILINESTRING((1 2,3 4),(5 6,&lt;STRONG&gt;7 8&lt;/STRONG&gt;))')  )&lt;BR /&gt;from&lt;BR /&gt;    dual&lt;BR /&gt;&lt;BR /&gt;Result:&lt;BR /&gt;&lt;SPAN class=""&gt;{&lt;BR /&gt;"point" : {&lt;BR /&gt;"optimized" : false,&lt;BR /&gt;"directposition" : &lt;STRONG&gt;[7,8]&lt;/STRONG&gt;&lt;BR /&gt;}&lt;BR /&gt;}&lt;/SPAN&gt;&lt;/PRE&gt;&lt;P&gt;&lt;A href="https://livesql.oracle.com/apex/livesql/s/nim5rs77hz9dytq5qxbvox7xd" target="_new"&gt;https://livesql.oracle.com/apex/livesql/s/nim5rs77hz9dytq5qxbvox7xd&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 21 May 2022 08:00:23 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-ideas/st-startpoint-amp-st-endpoint-for-multi-part/idc-p/1176175#M2834</guid>
      <dc:creator>Bud</dc:creator>
      <dc:date>2022-05-21T08:00:23Z</dc:date>
    </item>
  </channel>
</rss>

