<?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' workspace not respected in WFStoFeatureClass GP tool in Geoprocessing Questions</title>
    <link>https://community.esri.com/t5/geoprocessing-questions/memory-workspace-not-respected-in/m-p/1095802#M25808</link>
    <description>&lt;P&gt;yes... it is just a workspace and it will work if you have Pro installed on the machine you are running the notebook from. (you can import arcpy right?)&lt;/P&gt;</description>
    <pubDate>Mon, 06 Sep 2021 23:10:36 GMT</pubDate>
    <dc:creator>DanPatterson</dc:creator>
    <dc:date>2021-09-06T23:10:36Z</dc:date>
    <item>
      <title>'memory' workspace not respected in WFStoFeatureClass GP tool</title>
      <link>https://community.esri.com/t5/geoprocessing-questions/memory-workspace-not-respected-in/m-p/1095477#M25803</link>
      <description>&lt;P&gt;I'm trying to utilize the in memory workspace in Pro using the GP tool &lt;STRONG&gt;arcpy.conversion.WFSToFeatureClass&amp;nbsp;&lt;/STRONG&gt;but when I use &lt;STRONG&gt;r"memory"&lt;/STRONG&gt; as the&amp;nbsp;&lt;EM&gt;out_path,&lt;/EM&gt; instead of placing the feature class into memory, it creates a file geodatabase on disk&amp;nbsp;&lt;STRONG&gt;&amp;lt;Result C:\\data\memory.gdb&amp;gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;A different tool,&amp;nbsp;&lt;STRONG&gt;arcpy.conversion.FeatureClassToFeatureClass&lt;/STRONG&gt; uses the same variable for the same purposes,&amp;nbsp;&lt;EM&gt;out_path,&amp;nbsp;&lt;/EM&gt;respects it and places the result into&amp;nbsp;&lt;STRONG&gt;&amp;lt;Result 'memory\myfcname'&amp;gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Clearly, the tools don't work the same way concerning outputting to memory, but the documentation provides no indication as such. Can anyone shed any light if there is a work around for this issue? I really want to use the in memory workspace for the WFS conversion to Feature Class. Thank you!&lt;/P&gt;</description>
      <pubDate>Mon, 15 Nov 2021 20:36:25 GMT</pubDate>
      <guid>https://community.esri.com/t5/geoprocessing-questions/memory-workspace-not-respected-in/m-p/1095477#M25803</guid>
      <dc:creator>alex_friant</dc:creator>
      <dc:date>2021-11-15T20:36:25Z</dc:date>
    </item>
    <item>
      <title>Re: 'memory' workspace not respected in WFStoFeatureClass GP tool</title>
      <link>https://community.esri.com/t5/geoprocessing-questions/memory-workspace-not-respected-in/m-p/1095494#M25804</link>
      <description>&lt;P&gt;You could use your project Scratch gdb instead of "memory".&amp;nbsp; At least it won't clutter a critical or project gdb with throwaway calculations.&lt;/P&gt;&lt;P&gt;Not all things are "faster" using the memory workspace btw, if your intent is to speed processes up.&lt;/P&gt;</description>
      <pubDate>Sat, 04 Sep 2021 00:55:02 GMT</pubDate>
      <guid>https://community.esri.com/t5/geoprocessing-questions/memory-workspace-not-respected-in/m-p/1095494#M25804</guid>
      <dc:creator>DanPatterson</dc:creator>
      <dc:date>2021-09-04T00:55:02Z</dc:date>
    </item>
    <item>
      <title>Re: 'memory' workspace not respected in WFStoFeatureClass GP tool</title>
      <link>https://community.esri.com/t5/geoprocessing-questions/memory-workspace-not-respected-in/m-p/1095792#M25806</link>
      <description>&lt;P&gt;If you're not in Pro, but rather in a stand-alone jupyter notebook, can you still designate a "scratch" gdb?&lt;/P&gt;</description>
      <pubDate>Mon, 06 Sep 2021 20:42:42 GMT</pubDate>
      <guid>https://community.esri.com/t5/geoprocessing-questions/memory-workspace-not-respected-in/m-p/1095792#M25806</guid>
      <dc:creator>alex_friant</dc:creator>
      <dc:date>2021-09-06T20:42:42Z</dc:date>
    </item>
    <item>
      <title>Re: 'memory' workspace not respected in WFStoFeatureClass GP tool</title>
      <link>https://community.esri.com/t5/geoprocessing-questions/memory-workspace-not-respected-in/m-p/1095801#M25807</link>
      <description>&lt;P&gt;I keep C:\temp\scratch.gdb for things like this and purge it every few months or when I remember to. You could always just creat a scratch gdb in your notebook and delete it when you are done &amp;nbsp;&lt;/P&gt;&lt;P&gt;Seems like the memory workspace has had problems. I used in_memory in python 2.x &amp;nbsp;but I’ve never used the newer memory workspace.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 06 Sep 2021 22:39:50 GMT</pubDate>
      <guid>https://community.esri.com/t5/geoprocessing-questions/memory-workspace-not-respected-in/m-p/1095801#M25807</guid>
      <dc:creator>JoeBorgione</dc:creator>
      <dc:date>2021-09-06T22:39:50Z</dc:date>
    </item>
    <item>
      <title>Re: 'memory' workspace not respected in WFStoFeatureClass GP tool</title>
      <link>https://community.esri.com/t5/geoprocessing-questions/memory-workspace-not-respected-in/m-p/1095802#M25808</link>
      <description>&lt;P&gt;yes... it is just a workspace and it will work if you have Pro installed on the machine you are running the notebook from. (you can import arcpy right?)&lt;/P&gt;</description>
      <pubDate>Mon, 06 Sep 2021 23:10:36 GMT</pubDate>
      <guid>https://community.esri.com/t5/geoprocessing-questions/memory-workspace-not-respected-in/m-p/1095802#M25808</guid>
      <dc:creator>DanPatterson</dc:creator>
      <dc:date>2021-09-06T23:10:36Z</dc:date>
    </item>
  </channel>
</rss>

