<?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 Processing Extent  - same as layer should honour selection in ArcGIS Pro Ideas</title>
    <link>https://community.esri.com/t5/arcgis-pro-ideas/processing-extent-same-as-layer-should-honour/idi-p/950635</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Many raster processing tools honour the environment setting&amp;nbsp;&lt;EM&gt;&lt;STRONG&gt;Processing Extent&lt;/STRONG&gt;&lt;/EM&gt;, for which one of the options is&amp;nbsp;&lt;EM&gt;Same as layer XXX&lt;/EM&gt; where XXX is the layer. But this layer may have a selection on it and in reality this is the what I want the extent to be (e.g. a single selected country polygon from a world dataset).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Almost all &lt;/STRONG&gt;geo-processing tools honour selections&amp;nbsp;but why is this incredibly important environment setting ignoring a selection?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example if you run extract by attribute and set the extent to be a polygon layer with a selection &lt;SPAN&gt;(e.g. a single country polygon from a world dataset)&lt;/SPAN&gt;&amp;nbsp;the resulting raster still has the extent of the original world raster.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Either tools need to be able to identify a dataset has a selection and the processing extent is set to that (preferred option as that behaviour is inline with all other tools) or may be the list needs an addition option, something like &lt;EM&gt;Same as Selection in layer XXX.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The current clunky and unnecessary work around is to export the selection to a separate dataset and use that as the extent. This adds an overhead to processing time for large models/scripts.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 16 Nov 2016 12:16:53 GMT</pubDate>
    <dc:creator>DuncanHornby</dc:creator>
    <dc:date>2016-11-16T12:16:53Z</dc:date>
    <item>
      <title>Processing Extent  - same as layer should honour selection</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/processing-extent-same-as-layer-should-honour/idi-p/950635</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Many raster processing tools honour the environment setting&amp;nbsp;&lt;EM&gt;&lt;STRONG&gt;Processing Extent&lt;/STRONG&gt;&lt;/EM&gt;, for which one of the options is&amp;nbsp;&lt;EM&gt;Same as layer XXX&lt;/EM&gt; where XXX is the layer. But this layer may have a selection on it and in reality this is the what I want the extent to be (e.g. a single selected country polygon from a world dataset).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Almost all &lt;/STRONG&gt;geo-processing tools honour selections&amp;nbsp;but why is this incredibly important environment setting ignoring a selection?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example if you run extract by attribute and set the extent to be a polygon layer with a selection &lt;SPAN&gt;(e.g. a single country polygon from a world dataset)&lt;/SPAN&gt;&amp;nbsp;the resulting raster still has the extent of the original world raster.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Either tools need to be able to identify a dataset has a selection and the processing extent is set to that (preferred option as that behaviour is inline with all other tools) or may be the list needs an addition option, something like &lt;EM&gt;Same as Selection in layer XXX.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The current clunky and unnecessary work around is to export the selection to a separate dataset and use that as the extent. This adds an overhead to processing time for large models/scripts.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Nov 2016 12:16:53 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/processing-extent-same-as-layer-should-honour/idi-p/950635</guid>
      <dc:creator>DuncanHornby</dc:creator>
      <dc:date>2016-11-16T12:16:53Z</dc:date>
    </item>
    <item>
      <title>Re: Processing Extent  - same as layer should honour selection</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/processing-extent-same-as-layer-should-honour/idc-p/950636#M7116</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A much more efficient&amp;nbsp;way to set the extent to a selection is to use &lt;A href="http://pro.arcgis.com/en/pro-app/tool-reference/data-management/feature-envelope-to-polygon.htm"&gt;Feature Envelope To Polygon&lt;/A&gt; to create an extent dataset based on just the extent of each feature, and then set the extent to that. If your features are complex, this would be much faster than copying them all.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Nov 2016 06:50:04 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/processing-extent-same-as-layer-should-honour/idc-p/950636#M7116</guid>
      <dc:creator>curtvprice</dc:creator>
      <dc:date>2016-11-17T06:50:04Z</dc:date>
    </item>
    <item>
      <title>Re: Processing Extent  - same as layer should honour selection</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/processing-extent-same-as-layer-should-honour/idc-p/950637#M7117</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hmmm sounds like you have been down this road before? This is not a tool I use regularly but a great idea! The only&amp;nbsp;issue I can see with&amp;nbsp;this tool is that its an &lt;EM&gt;Advance&lt;/EM&gt; level license tool so for people who do not have that level this approach won't help them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Certainly a work around I will adopt. Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Nov 2016 09:50:09 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/processing-extent-same-as-layer-should-honour/idc-p/950637#M7117</guid>
      <dc:creator>DuncanHornby</dc:creator>
      <dc:date>2016-11-17T09:50:09Z</dc:date>
    </item>
    <item>
      <title>Re: Processing Extent  - same as layer should honour selection</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/processing-extent-same-as-layer-should-honour/idc-p/950638#M7118</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Duncan, I got thinking about this and posted a Python script and Model Builder tool that you may find useful.&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.esri.com/docs/DOC-9021-model-builder-geoprocessing-example-extent-of-selected-features?sr=search&amp;amp;searchId=d35a2567-0aa1-4ccb-a3c6-a5b794858db5&amp;amp;searchIndex=0"&gt;https://community.esri.com/docs/DOC-9021-model-builder-geoprocessing-example-extent-of-selected-features?sr=search&amp;amp;searchId=d35a2567-0aa1-4ccb-a3c6-a5b794858db5&amp;amp;searchIndex=0&lt;/A&gt;‌&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 19 Nov 2016 21:22:49 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/processing-extent-same-as-layer-should-honour/idc-p/950638#M7118</guid>
      <dc:creator>curtvprice</dc:creator>
      <dc:date>2016-11-19T21:22:49Z</dc:date>
    </item>
    <item>
      <title>Re: Processing Extent  - same as layer should honour selection - Status changed to: In Product Plan</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/processing-extent-same-as-layer-should-honour/idc-p/1344138#M26765</link>
      <description>&lt;P&gt;Thanks for the idea.&amp;nbsp;We have redesigned the control in ArcGIS Pro 3.2, and we plan to add more enhancements in upcoming releases.&amp;nbsp; This is an objective for the &lt;A href="https://pro.arcgis.com/en/pro-app/latest/help/analysis/geoprocessing/basics/extent-control.htm" target="_self"&gt;geoprocessing extent&lt;/A&gt; control in the near term.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 31 Oct 2023 20:28:57 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/processing-extent-same-as-layer-should-honour/idc-p/1344138#M26765</guid>
      <dc:creator>MargaretCrawford</dc:creator>
      <dc:date>2023-10-31T20:28:57Z</dc:date>
    </item>
    <item>
      <title>Re: Processing Extent  - same as layer should honour selection - Status changed to: Implemented</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/processing-extent-same-as-layer-should-honour/idc-p/1432482#M30089</link>
      <description>&lt;P&gt;This is implemented in ArcGIS Pro 3.3. See &lt;A href="https://community.esri.com/t5/arcgis-ideas-blog/your-ideas-in-arcgis-pro-3-3/bc-p/1431910" target="_blank"&gt;Your Ideas in ArcGIS Pro 3.3&lt;/A&gt; for a full list of all user ideas you can look forward to! And be sure to check out the &lt;A href="https://www.esri.com/arcgis-blog/products/arcgis-pro/announcements/whats-new-in-arcgis-pro-3-3/" target="_blank"&gt;release blog&lt;/A&gt; and what’s new &lt;A href="https://pro.arcgis.com/en/pro-app/latest/get-started/whats-new-in-arcgis-pro.htm" target="_blank"&gt;help topic and video&lt;/A&gt; to learn more about all the new features and functionality in the release.&lt;/P&gt;</description>
      <pubDate>Fri, 10 May 2024 16:13:30 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/processing-extent-same-as-layer-should-honour/idc-p/1432482#M30089</guid>
      <dc:creator>KoryKramer</dc:creator>
      <dc:date>2024-05-10T16:13:30Z</dc:date>
    </item>
  </channel>
</rss>

