I'm using ArcGIS Pro 3.2.1
I have a feature service feature class with 13 polygons and another feature service feature class with 73,061 lines.
When using pairwise clip, not all of the lines are clipped to the polygons. It seemingly clips random lines.
The example above shows when all 13 polygons are active and the line file is clipped to the polygon. The red lines are what is clipped and the green lines are not.
Below is when only 1 of the polygons is selected and pairwise clip is used.
When only one of the polygons is selected, pairwise clip works as expected.
When using the regular clip tool, this issue doesn't occur. All 13 polygons can be selected and the lines will be clipped as expected. Is this a limitation of the pairwise clip tool? Is this some sort of overflow error or Langton's Ant situation? When should Pairwise Clip be used vs Clip?
BUG-000152658 for ArcGIS Pro (esri.com)
It may apply to one of your polygons perhaps
Thanks. I think you might be right. A coworker of mine suggested that it could be since it's multi-part polygon too. It's strange that the pairwise clip doesn't work how I'd expect but the regular clip tool does. It may have something to do with how it's parallel processing/indexing.
Thanks again!
BUG-000152658 was addressed in ArcGIS Pro 3.1. An automated test for the issue was added to our test harness and it has been passing since the fix was installed back in 3.1.
If you are still seeing the problem can you please bring it to the attention of our support analyst so we can investigate?
Thx. Ken
Hi Ken,
When I initially ran into this bug, I was on ArcPro 3.2.1 so it seems to me that the 3.1 version did not actually fix it. I haven't used the Pairwise clip tool since, and have just stuck with the traditional clip tool with no issue. I think that multipart features might be what's causing that issue that I was experiencing. Next time I need to clip something, I'll try both tools and compare them
Hi, were in ArcGIS Pro 3.3.6 and its still having the same problem. Is there a fix in the works or a suggested tool to use?
Thanks for reporting @JasminDominguez1 . Is this also happening for you with feature services? It may be that some setup with your feature service is causing the problem. Could you contact your support representative with your case that reproduces the issue so we can investigate? They should be able to verify if your setup for feature services is correct and if not how to fix it. If it's then still an issue we'll be able to investigate and hopefully find a solution to help everyone.
If you are seeing this outside of a feature service (fgdb, shp files, etc) could you please provide us with an example of the data used when the issue occurs as well as complete details on your tool parameters and GP environments used?
Thanks! Ken