Count overlapping feature failed

FadyHabib · ‎10-31-2024

I got failed execute when I try to run this tool although it took several minutes then I tried to use the repair geometry tool and tried count tool again but still failed and got invalid topology so what should I do ?

KenHartling · ‎10-31-2024

Would you be able to share the data so we can investigate?

FadyHabib · ‎11-01-2024

I got the data from this link when I’ve tried to do this tutorial. The last time my laptop got freeze after took like 30 minutes to run this tool.

https://learn.arcgis.com/en/projects/cartographic-creations-map-arctic-sea-ice/

KenHartling · ‎11-04-2024

If I follow the tutorial and select Month = 9, which selects 43 features, and then run CountOverlap it works as expected, and fairly quickly.

However, if I do not perform a selection and try to run CountOverlap on the entire data set it will cause an out of memory failure (which may hang your machine) due to the massive amount of overlap in the entire dataset. It even ran out of memory on my machine with 256GB of RAM. I'd guess that the original tutorial authors did not intend you to run on the entire dataset.

vivianleilani

I am having a similar issue with this data, specifically when I try to Count Overlapping Features on month = 6. I receive the following errors:

WARNING 000117: Warning empty output generated.

ERROR 160196: Invalid Topology

Failed to execute (CountOverlappingFeatures).

It works perfectly fine for the other months, but something about month 6 doesn't work, and the Check Geometry Tool returns no errors. Any help would be appreciated!

KenHartling

Hi @vivianleilani .

I am unable to reproduce what you are seeing with Month = 6 selected on the IceExtent feature class. Below is how I ran it... using the downloaded FGDB from the tutorial.

If how I ran it is different from how you did, please let me know.

It would also be good to get what version of Pro you are using, as well as the amount of RAM, available disk and CPU specs from the machine you are running on.

Thx. Ken

KenHartling

@vivianleilani I did a bit more testing and I was able to reproduce the problem with a different selection from yours (Month = 7).

I've entered a bug into our system and will push for it to be resolved in ArcGIS Pro 3.7.

Thanks for re-reporting the issue.

Ken