AnsweredAssumed Answered

Erase tool doesn't erase all inputs

Question asked by jpramuk on Jan 12, 2018
Latest reply on Jan 12, 2018 by Dan_Patterson

Like • Show 0 Likes0
Comment • 8

When I execute the Erase Tool in ArcGIS it does not erase all of the features in the input class. The Input and Erase features are both polygons. I have attempted multiple times, hoping it was just a fluke.

Here is what I have tried so far:

1) I have selected out the specific features from the input that aren't being erased and attempted to run the Erase with those, but the output shapefile ends up being completely empty.

2) Using the Clip tool instead. The effects are the same.

3) Made sure when I run the Erase that no random features are accidentally selected.

4) Repair Geometry of input.

5) Rebuild Spatial Index of input.

Does anyone have experience about how to fix this problem?

jpramuk Jan 12, 2018 1:10 PM

Correct Answer

Hey Dan Patterson so I found out what the problem was. I needed to change the Processing Extent within the Environments to "Union of Inputs." I thought you may be interested in the solution. Thank you so much for your help though!

See the reply in context

No one else had this question

Outcomes

Dan_Patterson

Jan 12, 2018 10:33 AM

Erase—Help | ArcGIS Desktop

Erase just erases what is under the erase feature.

Perhaps you could show your situation.

You should also check that you aren't working with multipart features as well,

Actions

jpramuk @ Dan_Patterson on Jan 12, 2018 11:05 AM

By input, I mean Erase Feature. Sorry for the confusion. I have Dissolved my erase feature and made sure the output of that is not as a multi-part feature. Here is a visual of what is going on:

These are the two feature classes (shapefiles) that are being put into the Erase Tool.

Here is what I am running on the tool:

Here is the output:

If you look at the bottom of the polygon, that is where I am having problems.

Actions

Dan_Patterson

@ jpramuk on Jan 12, 2018 11:12 AM

Run Repair Geometry and Multipart to singlepart on the dissolved files prior to running erase. I never trust anything.

Also... try featureclasses in a geodatabase to boot.

1 person found this helpful

Actions

jpramuk @ Dan_Patterson on Jan 12, 2018 11:25 AM

Thanks for the response! I have already run the Repair Geometry and it didn't fix the problem... When running the Multipart to Singlepart Tool, the output did not contain the 3 polygons that aren't working correctly in the Erase Tool. I'm thinking there has to be a correlation between these two outcomes.

Actions

Dan_Patterson

@ jpramuk on Jan 12, 2018 11:38 AM

As I suspected. By chance is that file with the missing fiddly bits part of a larger file? There is something amiss with the geometry and I am surprised that repair geometry didn't stumble onto it

Actions

jpramuk @ Dan_Patterson on Jan 12, 2018 1:01 PM

So here is what I have done to get the Cities data I am currently using:

State_Cities > Select by Location (within county) > Export Data > Cities_frank

So yes, the data was originally part of a larger data set, but I created a completely new shapefile from the cities that reside in the county that I am currently studying. What are you thinking is the problem in that case?

Actions

jpramuk @ Dan_Patterson on Jan 12, 2018 1:10 PM

2 people found this helpful

Actions

Dan_Patterson

@ jpramuk on Jan 12, 2018 2:28 PM

Well.. that would certainly do it ... the bits were completely missing

Actions

8 Replies

Dan_Patterson Jan 12, 2018 10:33 AM
Mark Correct
Correct Answer
Erase—Help | ArcGIS Desktop
Erase just erases what is under the erase feature.
Perhaps you could show your situation.
You should also check that you aren't working with multipart features as well,
Like • Show 0 Likes0
Actions
- jpramuk @ Dan_Patterson on Jan 12, 2018 11:05 AM
  Mark Correct
  Correct Answer
  By input, I mean Erase Feature. Sorry for the confusion. I have Dissolved my erase feature and made sure the output of that is not as a multi-part feature. Here is a visual of what is going on:
  
  These are the two feature classes (shapefiles) that are being put into the Erase Tool.
  
  Here is what I am running on the tool:
  
  Here is the output:
  
  If you look at the bottom of the polygon, that is where I am having problems.
  Like • Show 0 Likes0
  Actions
  - Dan_Patterson @ jpramuk on Jan 12, 2018 11:12 AM
    Mark Correct
    Correct Answer
    Run Repair Geometry and Multipart to singlepart on the dissolved files prior to running erase. I never trust anything.
    Also... try featureclasses in a geodatabase to boot.
    1 person found this helpful
    Like • Show 0 Likes0
    Actions
    - jpramuk @ Dan_Patterson on Jan 12, 2018 11:25 AM
      Mark Correct
      Correct Answer
      Thanks for the response! I have already run the Repair Geometry and it didn't fix the problem... When running the Multipart to Singlepart Tool, the output did not contain the 3 polygons that aren't working correctly in the Erase Tool. I'm thinking there has to be a correlation between these two outcomes.
      Like • Show 0 Likes0
      Actions
      - Dan_Patterson @ jpramuk on Jan 12, 2018 11:38 AM
        Mark Correct
        Correct Answer
        As I suspected. By chance is that file with the missing fiddly bits part of a larger file? There is something amiss with the geometry and I am surprised that repair geometry didn't stumble onto it
        Like • Show 0 Likes0
        Actions
        jpramuk @ Dan_Patterson on Jan 12, 2018 1:01 PM
        Mark Correct
        Correct Answer
        So here is what I have done to get the Cities data I am currently using:
        
        State_Cities > Select by Location (within county) > Export Data > Cities_frank
        
        So yes, the data was originally part of a larger data set, but I created a completely new shapefile from the cities that reside in the county that I am currently studying. What are you thinking is the problem in that case?
        Like • Show 0 Likes0
        Actions
        jpramuk @ Dan_Patterson on Jan 12, 2018 1:10 PM
        Unmark Correct
        Correct Answer
        Hey Dan Patterson so I found out what the problem was. I needed to change the Processing Extent within the Environments to "Union of Inputs." I thought you may be interested in the solution. Thank you so much for your help though!
        2 people found this helpful
        Like • Show 1 Like1
        Actions
        Dan_Patterson @ jpramuk on Jan 12, 2018 2:28 PM
        Mark Correct
        Correct Answer
        Well.. that would certainly do it ... the bits were completely missing
        Like • Show 0 Likes0
        Actions

GeoNet

The Esri Community

Erase tool doesn't erase all inputs

Outcomes

Related Content

Recommended Content