nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Erase Tool Increasing the Number of Polygons

Ed_

Question for ESRI

It seems that the Erase tool in ArcGIS Pro 3.6 increases the number of polygons in the output feature class. In my case the input feature class has 7167 polygons whereas the output has 14332. However, now the output feature class has a higher total shape_area than the input feature class. Why is that so? It seems that the Erase tool is creating duplicates which could be a bug?

Find more posts tagged with

Analysis

Desktop

Accepted answers

Ed_

Hi Dan the inputs are single part feature classes. I did try the Pairwise Erase tool and it increase the number of output polygons to a crazy amount (which were duplicates) in case of the Erase tool run

Edit: Never mind I reran the Erase tool and it did not generate any dupes, could be one time glitch. Anyways, rerunning the tool from the History pane fixed the issue.

All comments

DanPatterson

Erase (Analysis)—ArcGIS Pro | Documentation

you seem to be reporting the reverse of....

This tool may generate multipart features in the output even if all inputs are single part. If you don't want multipart features, use the Multipart To Singlepart tool on the output feature class.

In any event, it would be wise to check to see if the original file was multipart or singlepart to begin with.

You might also want to try to see if this tool produces the same result

Pairwise Erase (Analysis)—ArcGIS Pro | Documentation

again, on singlepart inputs not multipart.

Ed_

Edit: Never mind I reran the Erase tool and it did not generate any dupes, could be one time glitch. Anyways, rerunning the tool from the History pane fixed the issue.

DanPatterson

never seen that glitch, which begs the question about whether the data were locally stored in a file gdb (source and output) or whether it entailed other obstacles to its behaviour.

Ed_

input and output feature classes are in a local gdb and in both runs the input data and the output gdb stayed the same.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.