<?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>topic Re: Memory vs in_memory support: Differences and supported geoprocessing tools? in Python Questions</title>
    <link>https://community.esri.com/t5/python-questions/memory-vs-in-memory-support-differences-and/m-p/1607890#M74071</link>
    <description>&lt;P&gt;The only geoprocessing tool that's ever given me trouble with the memory workspace was &lt;A href="https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/project.htm" target="_self"&gt;Project&lt;/A&gt; and that might've been fixed over the years. In general, if the tool doesn't operate on a whole workspace, a feature dataset, or anything that has to reside in a feature dataset then it'll work with the memory workspace. Don't use "in_memory" unless you still need ArcMap compatibility.&lt;/P&gt;</description>
    <pubDate>Mon, 21 Apr 2025 23:25:15 GMT</pubDate>
    <dc:creator>DavidSolari</dc:creator>
    <dc:date>2025-04-21T23:25:15Z</dc:date>
    <item>
      <title>Memory vs in_memory support: Differences and supported geoprocessing tools?</title>
      <link>https://community.esri.com/t5/python-questions/memory-vs-in-memory-support-differences-and/m-p/1607820#M74068</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;A colleague of mine has noted that she has "&lt;SPAN&gt;&lt;EM&gt;found that some arcpy or arcgis api tools only work with 'in_memory' instead of 'memory'.&lt;/EM&gt; ", and that switching from one to the other sometimes gets the intended result (versus failing).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Would anyone have any information on how the two workspaces differ? The documentation here is pretty light:&amp;nbsp;&lt;A href="https://pro.arcgis.com/en/pro-app/latest/help/analysis/geoprocessing/basics/the-in-memory-workspace.htm" target="_blank" rel="noopener"&gt;Write geoprocessing output to memory—ArcGIS Pro | Documentation&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Something that would be extremely helpful is a list of which geoprocessing tools support which workspace(s).&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;It looks like the page&amp;nbsp;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/1371"&gt;@JoshuaBixby&lt;/a&gt;&amp;nbsp;mentioned &lt;A href="https://community.esri.com/t5/arcgis-api-for-python-questions/in-memory-for-geoprocessing-in-arcgis-pro/m-p/856066/highlight/true#M4007" target="_blank" rel="noopener"&gt;here&lt;/A&gt; got folded into the current Write geoprocessing to memory page:&amp;nbsp;&lt;A href="https://community.esri.com/t5/arcgis-api-for-python-questions/in-memory-for-geoprocessing-in-arcgis-pro/m-p/856073/highlight/true#M4014" target="_blank" rel="noopener"&gt;Re: in_memory\ for geoprocessing in ArcGis Pro? - Esri Community&lt;/A&gt;&amp;nbsp; In that post, he noted that&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;&lt;SPAN&gt;&lt;EM&gt;In Pro 2.4.x and newer (possibly 2.3.x too), "memory" should store data sets in-memory when using the interactive Python window in Pro while "in_memory" will store data sets on disk.&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;He also noted&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;The original in-memory workspace, i.e., "in_memory", is actually only in memory when run out of process, not when run within the ArcGIS Pro application.&amp;nbsp; The&lt;A title="https://pro.arcgis.com/en/pro-app/tool-reference/appendices/using-the-in-memory-output-workspace.htm" href="https://pro.arcgis.com/en/pro-app/tool-reference/appendices/using-the-in-memory-output-workspace.htm" target="_blank" rel="nofollow noopener noreferrer"&gt;Considerations when using the in_memory workspace—Appendices | Documentation&lt;/A&gt;covers this topic.&lt;/P&gt;&lt;P&gt;If you want intermediate data sets to be in actual memory while using the ArcGIS Pro application, you need to use the newer in-memory workspace, i.e., "memory".&amp;nbsp; Just be aware, older ArcPy tools that require the workspace to be set using arcpy.env.workspace don't support either in-memory workspace with ArcGIS Pro.&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;On the same forum thread, another user noted similar behaviour while doing viewshed analysis:&amp;nbsp;&lt;A href="https://community.esri.com/t5/arcgis-api-for-python-questions/in-memory-for-geoprocessing-in-arcgis-pro/m-p/1018127/highlight/true#M5453" target="_blank" rel="noopener"&gt;Re: in_memory\ for geoprocessing in ArcGis Pro? - Esri Community&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Unfortunately, all the links in this thread now point back to that same documentation page:&amp;nbsp;&lt;A href="https://community.esri.com/t5/python-questions/working-with-in-memory/m-p/1050176/highlight/true#M60865" target="_blank" rel="noopener"&gt;Solved: Re: Working with in_memory? - Esri Community&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/280469"&gt;@JenniferMcCollom1&lt;/a&gt;&amp;nbsp;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/245727"&gt;@JenniferMcCollom&lt;/a&gt;&amp;nbsp;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/260431"&gt;@Stacey_Crowe&lt;/a&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 21 Apr 2025 20:14:17 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/memory-vs-in-memory-support-differences-and/m-p/1607820#M74068</guid>
      <dc:creator>AlfredBaldenweck</dc:creator>
      <dc:date>2025-04-21T20:14:17Z</dc:date>
    </item>
    <item>
      <title>Re: Memory vs in_memory support: Differences and supported geoprocessing tools?</title>
      <link>https://community.esri.com/t5/python-questions/memory-vs-in-memory-support-differences-and/m-p/1607890#M74071</link>
      <description>&lt;P&gt;The only geoprocessing tool that's ever given me trouble with the memory workspace was &lt;A href="https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/project.htm" target="_self"&gt;Project&lt;/A&gt; and that might've been fixed over the years. In general, if the tool doesn't operate on a whole workspace, a feature dataset, or anything that has to reside in a feature dataset then it'll work with the memory workspace. Don't use "in_memory" unless you still need ArcMap compatibility.&lt;/P&gt;</description>
      <pubDate>Mon, 21 Apr 2025 23:25:15 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/memory-vs-in-memory-support-differences-and/m-p/1607890#M74071</guid>
      <dc:creator>DavidSolari</dc:creator>
      <dc:date>2025-04-21T23:25:15Z</dc:date>
    </item>
    <item>
      <title>Re: Memory vs in_memory support: Differences and supported geoprocessing tools?</title>
      <link>https://community.esri.com/t5/python-questions/memory-vs-in-memory-support-differences-and/m-p/1608090#M74075</link>
      <description>&lt;P&gt;Given it has been nearly 6 years since ArcGIS Pro 2.4 was released, I would take any documentation and comments from back then with a grain of salt, even if they were accurate/correct at the time.&amp;nbsp; The "memory" workspace has continually, albeit slowly, improved over the releases.&amp;nbsp; For all intents and purposes, "in_memory" is now a legacy artifact that should not be used.&lt;/P&gt;</description>
      <pubDate>Tue, 22 Apr 2025 14:25:23 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/memory-vs-in-memory-support-differences-and/m-p/1608090#M74075</guid>
      <dc:creator>JoshuaBixby</dc:creator>
      <dc:date>2025-04-22T14:25:23Z</dc:date>
    </item>
  </channel>
</rss>

