Ok....I just did a test and I verified that it is a multipart geometry problem.
The Shapefile class is providing the correct number of shapes. In this particular case, it is one feature (shape) that consists of 870 parts, each part being a little polygon. So, the geoprocessing functions do not work correctly on multipart geometries. I verified this by converting the multipart shapefile into a single part shapefile. Voila!, the Shapefile.Clip method works correctly and the Shapefile.NumShapes gives the correct number of single parts.
This is what I was trying to determine from the beginning with my initial question: "Do the geoprocessing functions have any limitations?"
Please....from now on answer with, "YES - THEY CANNOT HANDLE MULTI-PART GEOMETRIES"
The Shapefile class is providing the correct number of shapes. In this particular case, it is one feature (shape) that consists of 870 parts, each part being a little polygon. So, the geoprocessing functions do not work correctly on multipart geometries. I verified this by converting the multipart shapefile into a single part shapefile. Voila!, the Shapefile.Clip method works correctly and the Shapefile.NumShapes gives the correct number of single parts.
This is what I was trying to determine from the beginning with my initial question: "Do the geoprocessing functions have any limitations?"
Please....from now on answer with, "YES - THEY CANNOT HANDLE MULTI-PART GEOMETRIES"
