<?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 Select Layer by Location — Intersect (DBMS) — Show SQL query definition in GP tool details in ArcGIS Pro Ideas</title>
    <link>https://community.esri.com/t5/arcgis-pro-ideas/select-layer-by-location-intersect-dbms-show-sql/idi-p/1365598</link>
    <description>&lt;P&gt;&lt;EM&gt;ArcGIS Pro 2.6.8; Oracle 18c 10.7.1 EGDB; SDE.ST_Geometry:&lt;BR /&gt;&lt;BR /&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Background:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;In the&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/select-layer-by-location.htm" target="_self" rel="nofollow noopener noreferrer"&gt;Select Layer By Location (Data Management)&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;docs, the&amp;nbsp;&lt;EM&gt;Relationship Parameter — Intersect (DBMS)&amp;nbsp;&lt;/EM&gt;section says:&lt;/SPAN&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;&lt;SPAN&gt;For the&amp;nbsp;&lt;SPAN class=""&gt;Relationship&lt;/SPAN&gt;&amp;nbsp;parameter, the&amp;nbsp;&lt;SPAN class=""&gt;Intersect (DBMS)&lt;/SPAN&gt;&amp;nbsp;option may provide better performance than the&amp;nbsp;&lt;SPAN class=""&gt;Intersect&lt;/SPAN&gt;&amp;nbsp;option when using enterprise geodatabase data; however, this option is only supported under specific conditions. If all conditions are met, the spatial operation will be performed in the enterprise geodatabase database management system (DBMS) rather than on the client.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;...The user connecting to the geodatabase must have privileges to&amp;nbsp;&lt;STRONG&gt;create a view in the database&lt;/STRONG&gt;&amp;nbsp;where the feature classes are stored.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;SPAN&gt;In other words, the tool creates a database view called&amp;nbsp;SELECTIONOUTPUTNAME.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Bud_0-1704230226788.png" style="width: 400px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/90342i380BB723B62EAB9E/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Bud_0-1704230226788.png" alt="Bud_0-1704230226788.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Bud_2-1704230226611.png" style="width: 400px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/90340iE17DFAE1ADE4EC21/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Bud_2-1704230226611.png" alt="Bud_2-1704230226611.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;PRE&gt;&lt;SPAN&gt;select "OBJECTID" from ( SELECT a.OBJECTID FROM INFRASTR.ACTIVE_TRANSPORTATION a,&lt;BR /&gt;INFRASTR.AGOL_PARKINGLOT b WHERE SDE.ST_INTERSECTS(a.SHAPE, b.SHAPE) = 1 ) esri_sql&lt;/SPAN&gt;&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Idea:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Rather than hide the SQL query definition in an obscure database view, allow the user to easily access the SQL by including the SQL as text in the GP tool details. Or something better.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Bud_4-1704230552265.png" style="width: 999px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/90344i98063CB4236A2C3D/image-size/large?v=v2&amp;amp;px=999" role="button" title="Bud_4-1704230552265.png" alt="Bud_4-1704230552265.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Use Cases:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Copy/paste the text for documentation purposes.&lt;/LI&gt;&lt;LI&gt;Use the SQL elsewhere. Spatial SQL queries can be tricky to write from scratch, especially when using unfamiliar spatial types. It would be helpful to grab SQL from a working query and then modify it for other purposes.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 04 Jan 2024 02:26:11 GMT</pubDate>
    <dc:creator>Bud</dc:creator>
    <dc:date>2024-01-04T02:26:11Z</dc:date>
    <item>
      <title>Select Layer by Location — Intersect (DBMS) — Show SQL query definition in GP tool details</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/select-layer-by-location-intersect-dbms-show-sql/idi-p/1365598</link>
      <description>&lt;P&gt;&lt;EM&gt;ArcGIS Pro 2.6.8; Oracle 18c 10.7.1 EGDB; SDE.ST_Geometry:&lt;BR /&gt;&lt;BR /&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Background:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;In the&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/select-layer-by-location.htm" target="_self" rel="nofollow noopener noreferrer"&gt;Select Layer By Location (Data Management)&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;docs, the&amp;nbsp;&lt;EM&gt;Relationship Parameter — Intersect (DBMS)&amp;nbsp;&lt;/EM&gt;section says:&lt;/SPAN&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;&lt;SPAN&gt;For the&amp;nbsp;&lt;SPAN class=""&gt;Relationship&lt;/SPAN&gt;&amp;nbsp;parameter, the&amp;nbsp;&lt;SPAN class=""&gt;Intersect (DBMS)&lt;/SPAN&gt;&amp;nbsp;option may provide better performance than the&amp;nbsp;&lt;SPAN class=""&gt;Intersect&lt;/SPAN&gt;&amp;nbsp;option when using enterprise geodatabase data; however, this option is only supported under specific conditions. If all conditions are met, the spatial operation will be performed in the enterprise geodatabase database management system (DBMS) rather than on the client.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;...The user connecting to the geodatabase must have privileges to&amp;nbsp;&lt;STRONG&gt;create a view in the database&lt;/STRONG&gt;&amp;nbsp;where the feature classes are stored.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;SPAN&gt;In other words, the tool creates a database view called&amp;nbsp;SELECTIONOUTPUTNAME.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Bud_0-1704230226788.png" style="width: 400px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/90342i380BB723B62EAB9E/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Bud_0-1704230226788.png" alt="Bud_0-1704230226788.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Bud_2-1704230226611.png" style="width: 400px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/90340iE17DFAE1ADE4EC21/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Bud_2-1704230226611.png" alt="Bud_2-1704230226611.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;PRE&gt;&lt;SPAN&gt;select "OBJECTID" from ( SELECT a.OBJECTID FROM INFRASTR.ACTIVE_TRANSPORTATION a,&lt;BR /&gt;INFRASTR.AGOL_PARKINGLOT b WHERE SDE.ST_INTERSECTS(a.SHAPE, b.SHAPE) = 1 ) esri_sql&lt;/SPAN&gt;&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Idea:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Rather than hide the SQL query definition in an obscure database view, allow the user to easily access the SQL by including the SQL as text in the GP tool details. Or something better.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Bud_4-1704230552265.png" style="width: 999px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/90344i98063CB4236A2C3D/image-size/large?v=v2&amp;amp;px=999" role="button" title="Bud_4-1704230552265.png" alt="Bud_4-1704230552265.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Use Cases:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Copy/paste the text for documentation purposes.&lt;/LI&gt;&lt;LI&gt;Use the SQL elsewhere. Spatial SQL queries can be tricky to write from scratch, especially when using unfamiliar spatial types. It would be helpful to grab SQL from a working query and then modify it for other purposes.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 04 Jan 2024 02:26:11 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/select-layer-by-location-intersect-dbms-show-sql/idi-p/1365598</guid>
      <dc:creator>Bud</dc:creator>
      <dc:date>2024-01-04T02:26:11Z</dc:date>
    </item>
  </channel>
</rss>

