The Split tool splits input polygons where they overlap each other instead of just where they are crossed by the split polygons. This is frustrating because the tool help does not indicate this behavior. Is it possible to configure the Split tool to not split overlapping input features? Different tool or process? I attempted to create a model that iterates through each input feature before applying the split, but this seemed horribly slow/inefficient and I killed the process before it completed, so I'm not sure if it was even working. Thanks!
Solved! Go to Solution.
Hi Jeff, I have tested Split tool and I see what you described: when input features contain overlapping polygons, they are broken into polygons representing the non-overlapping areas and overlapping areas in the output; the overlapping areas are duplicated. I checked with our team, this behavior is by design. Perhaps a simple way to explain this is that the tool not only splits input features but also ensures the output features are topologically correct (or clean). This behavior has existed since the tool was created many years ago; some users do appreciate this behavior while others may not. The Clip tool used to have this behavior but not anymore. I would suggest the following:
I can make suggestions to our team:
Please let me know if you have further questions. Thanks.
Is it possible to post a picture of what you're talking about?
Hi Jeff, I have tested Split tool and I see what you described: when input features contain overlapping polygons, they are broken into polygons representing the non-overlapping areas and overlapping areas in the output; the overlapping areas are duplicated. I checked with our team, this behavior is by design. Perhaps a simple way to explain this is that the tool not only splits input features but also ensures the output features are topologically correct (or clean). This behavior has existed since the tool was created many years ago; some users do appreciate this behavior while others may not. The Clip tool used to have this behavior but not anymore. I would suggest the following:
I can make suggestions to our team:
Please let me know if you have further questions. Thanks.