topic Re: in_memory\ for geoprocessing in ArcGis Pro? in ArcGIS API for Python Questions

in_memory\ for geoprocessing in ArcGis Pro?

LynnGaines — Tue, 08 Oct 2019 17:27:46 GMT

In Arc Pro 2.6, the message ERROR 000210: Cannot create output memory\example is returned after I run my geoprocessing script. The script is using Python 3.6.

I understand that Arc PRO is different from ArcMap in that it is 64-bit and does not block the application while a tool is running. I read, however, that the mulithreaded approach writes on-disk in PRO when using "in_memory\\example " and not to memory as I prefer. Using "memory\example", seemed to be the solution, but then it results in the error mentioned above.

Can you please help me in identifying a way to write to memory as I did in ArcMap with the goal of publishing? Below is a bit of the code that I used. Any help is appreciated.

#Import arcpy modules

from arcpy import MakeQueryLayer_management
from arcpy import CopyFeatures_management
from arcpy import env

#Local Variables

LPRMQ = r"memory\LPRMQ"

#Input/Output

PIDNum = arcpy.GetParameterAsText(0)

arcpy.SetParameterAsText(1, r"memory\LPR")

# Set Geoprocessing environments

arcpy.env.scratchWorkspace = "C:\\Users\\..."

arcpy.env.workspace = "C:\\Users\\..."

arcpy.MakeQueryLayer_management(DB, LPRMQ, "SELECT ...")

arcpy.CopyFeatures_management(LPRMQ, r"memory\LPR", "", "0", "0", "0")

Lynn

Re: in_memory\ for geoprocessing in ArcGis Pro?

Per_Åke_MattiasWallin — Fri, 11 Oct 2019 16:56:25 GMT

Lynn,

Just for testing- can you simplify your script? Can the issue be with your query layer? The arcpy.CopyFeatures_management() command to a memory feature works just fine for me. I am using ArcGIS Pro 2.4.2 by the way.

Re: in_memory\ for geoprocessing in ArcGis Pro?

LynnGaines — Tue, 15 Oct 2019 19:14:25 GMT

Thank you for your reply. I think the difference is using the interactive mode in PRO vs. standalone (arcpy from PyScripter). For some reason, 'memory\' stores data in .gdb and not on-disk.

Re: in_memory\ for geoprocessing in ArcGis Pro?

JoshuaBixby — Wed, 16 Oct 2019 03:16:12 GMT

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.

Looking over the code provided, I am guessing the problem is that you are prefixing your layer name with "memory." Query layers, feature layers, table views, etc... are stored in-memory by design, so having a layer name as r"memory\LPRMQ" carries a high risk of causing issues.

Re: in_memory\ for geoprocessing in ArcGis Pro?

JoshuaBixby — Wed, 16 Oct 2019 03:16:55 GMT

Sharing with Python‌ because this is an ArcPy question and not an ArcGIS API for Python question.

Re: in_memory\ for geoprocessing in ArcGis Pro?

LynnGaines — Wed, 16 Oct 2019 12:17:12 GMT

Joshua,

Thank you for your reply. I followed the example provided here in writing to memory. It looks similar to in_memory and I thought that it would provide the expected results. I was wrong. I believe that the example was using an interactive Python window.

Thank you also for sharing my question with the Python group.

Re: in_memory\ for geoprocessing in ArcGis Pro?

JoshuaBixby — Wed, 16 Oct 2019 12:57:49 GMT

Your use of "memory" with Copy Features is correct because that tool outputs a feature class. Make Feature Layer makes a feature layer within the application memory space, it doesn't output a data set.

What results do you get if you change the following line:

LPRMQ = r"LPRMQ"

Re: in_memory\ for geoprocessing in ArcGis Pro?

LynnGaines — Fri, 22 Nov 2019 15:36:52 GMT

Thank you Joshua for your response. Unfortunately, I had to abandon this project in Arcgis Pro due to time constraints. (It worked fine in ArcMap.) I will use your suggestion when I revisit in_memory in ArcPro and include my results.

Re: in_memory\ for geoprocessing in ArcGis Pro?

deleted-user-3K8mKpoPb261 — Fri, 20 Mar 2020 00:13:52 GMT

Has this issue been resolved? I'm running to the same issue using ArcGIS Pro 2.5

Re: in_memory\ for geoprocessing in ArcGis Pro?

deleted-user-3K8mKpoPb261 — Sun, 12 Dec 2021 10:35:01 GMT

I just switched back to 2.4 which fixed it. But this could be a bigger problem though.

Could someone try to replicate the issue by running the following script using ArcGIS Pro 2.5?

arcpy.env.workspace = 'in_memory'

Do something

Then check if there's anything in the workspace using
arcpy.ListFeatureClasses()‍‍‍‍‍‍

I haven't used community.esri.com this much (to ask questions) until I switched from ArcMap to ArcGIS Pro. It makes me wonder if there are enough advanced ArcGIS users who actually upgrade to the recent versions of the software.

Re: in_memory\ for geoprocessing in ArcGis Pro?

JoshuaBixby — Fri, 20 Mar 2020 14:21:57 GMT

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. The Considerations when using the in_memory workspace—Appendices | Documentation covers this topic.

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". 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.

Regarding advanced ArcGIS users, there are quite a few on GeoNet, including ones that do beta testing on versions of ArcGIS Pro that hasn't been released yet. That said, it doesn't take an advanced user to read the documentation.

Re: in_memory\ for geoprocessing in ArcGis Pro?

deleted-user-3K8mKpoPb261 — Fri, 20 Mar 2020 15:54:22 GMT

Thanks but I've actually read that documentation and already tried the new 'memory' workspace but as I mentioned above the issue wasn't solved until I downgraded to ArcGIS Pro 2.4

Re: in_memory\ for geoprocessing in ArcGis Pro?

JoshuaBixby — Fri, 20 Mar 2020 16:28:32 GMT

The problem for GeoNet readers is that you said you are having the same issue as the OP, but the code snippet you provided focused on a different issue than the OP's issue. If you want to provide more code, the error and trackback with Pro 2.5, then people can provide more specific feedback.

Re: in_memory\ for geoprocessing in ArcGis Pro?

James_Whitacre — Tue, 19 Jan 2021 21:18:48 GMT

Reviving this conversation...

I just had an issue where I was using:

temp_features = r'in_memory\Features_Temp'

Then I was updating code for ArcGIS Pro and changed it to:

temp_features = r'memory\Features_Temp'

The temp_features are being run through Viewshed 2 Tool. When run using 'in_memory\', everything works as expected. But when run through 'memory\', the tool fails with an '010471: No observers found in analysis extent.' error.

Any ideas why this may be? Thanks.

Re: in_memory\ for geoprocessing in ArcGis Pro?

JoshuaBixby — Wed, 20 Jan 2021 00:44:51 GMT

What version of Pro are you using? Prior to Pro 2.5, the memory workspace did not support any kind of raster dataset.

Re: in_memory\ for geoprocessing in ArcGis Pro?

James_Whitacre — Mon, 08 Feb 2021 19:47:11 GMT

@JoshuaBixby I am working with ArcGIS Pro 2.7, and I am not working with raster datasets in the memory space in this case. The 'temp_feature' variable is a feature class that is the input points for the Viewshed 2 tool.

Re: in_memory\ for geoprocessing in ArcGis Pro?

Ranga_Tolapi — Tue, 22 Apr 2025 03:21:49 GMT

https://www.esri.com/arcgis-blog/products/arcgis-pro/analytics/arcgis-pro-memory-workspace