topic Re: Intersect (Analysis) does not like "memory" workspaces. Is this a bug? in ArcGIS Pro Questions

Intersect (Analysis) does not like "memory" workspaces. Is this a bug?

Cristian_Galindo — Fri, 25 Nov 2022 08:05:51 GMT

I am using ArcGIS Pro 2.9, and trying to make some basic spatial operations.

Two sets of features were selected from a geodatabase, and using them, an intersection will be performed.

As it is not intended to persist this objects, the script use the "in_memory" workspace (it was done for the version 2.1 thinking in ArcDesktop).

Today, in an attempt to update the script with the new characteristics of the version 2.9, I found that the intersect tool does not like the memory workspaces.

Here is my evidence:

reading the documentation of the intersect tool, it does not mention a restriction for this kind of datasets.

Is this a bug? How do I report it?

Re: Intersect (Analysis) does not like "memory" workspaces. Is this a bug?

HannesZiegler — Thu, 15 Dec 2022 22:17:56 GMT

@Cristian_Galindo are you able to contact Technical Support Services? They will be able determine whether this is a bug and can file an internal issue if it is.

Re: Intersect (Analysis) does not like "memory" workspaces. Is this a bug?

JoshuaBixby — Fri, 16 Dec 2022 14:57:26 GMT

Have you checked whether the issue is with selecting? If something isn't working correctly with Select, it may be there isn't anything selected for Intersect to operate on.

Re: Intersect (Analysis) does not like "memory" workspaces. Is this a bug?

Cristian_Galindo — Mon, 19 Dec 2022 09:29:32 GMT

As I posted as evidence, both scenarios are the same, the only difference is the location of the expected result. but in order to provide more evidence, i ran the scripts against an smaller dataset, and print the results:

Re: Intersect (Analysis) does not like "memory" workspaces. Is this a bug?

Cristian_Galindo — Mon, 19 Dec 2022 09:34:41 GMT

After some trial and error (not you pity documentation) I found that Intersect tool does not like "memory" (modern, state of the art) workspaces as INPUT, it does not care about the output:

Re: Intersect (Analysis) does not like "memory" workspaces. Is this a bug?

Cristian_Galindo — Mon, 19 Dec 2022 10:15:09 GMT

Additional Note:
The tool MakeRouteEventLayer does not like either the "memory" workspaces as input.

The documentation: https://pro.arcgis.com/en/pro-app/2.9/tool-reference/linear-referencing/make-route-event-layer.htm

does not state this.

Re: Intersect (Analysis) does not like "memory" workspaces. Is this a bug?

RandyMcGregor_BMcD — Fri, 11 Apr 2025 12:41:32 GMT

I'm experiencing this today, 4-11-2025. Getting an error message that it can't create the in memory output. The thing is this tool has worked before. There is something about the intersect tool that creates conflict with in memory outputs.

Re: Intersect (Analysis) does not like "memory" workspaces. Is this a bug?

RandyMcGregor_BMcD — Fri, 11 Apr 2025 15:44:16 GMT

Turns out the input line feature had a VERY long name. I exported to a feature class with a shorter name and it worked - successfully created an in memory output. To clarify, this is the actual name of the file. Changing the layer name in the table of contents didn't help.