Geographic Information Systems Stack Exchange is a question and answer site for cartographers, geographers and GIS professionals. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am working with a shapefile that has many small, detailed polygons. After exporting it to a feature class in a geodatabase, I found that some operations (for example, Snap in the Editing Toolbox) seemed to be hanging. Based on previous experience, I thought that geometry errors were causing my processes to hang. I ran the "Repair Geometry" tool several times until "Check Geometry" no longer identified any errors. Every operation I have performed on the feature class since has re-introduced more geometry errors. Simply using the "Project" tool to project the feature class into a projected coordinate system caused "Check Geometry" to report a multitude of errors (mostly self-intersections) on features that were not identified as having errors on my initial attempt to clean this feature class.

Is there any hope that I can fix this shapefile? Running several "Repair Geometry" processes after every geoprocessing operation is an unattractive option due to the size of this dataset.

Additionally, could something besides these errors be causing my processes to hang?


share|improve this question

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.