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

The layer being used as the Clip Features has been used before and worked fine, so I assume the issue is the layer I am trying to Clip (Input Features) - I keep receiving the same error when running the Clip tool :

Error999999: Error executing Function Invalid Topology [Topoengine Error]

The Clip tool has worked fine prior to this. After reading online similar queries regarding this error, the solution in the majority of cases was to change the Input Features to a shapefile - I have done this but receive the same error.

What is my best workaround for this issue?

share|improve this question
Very often these errors are a result of projection issues. – Aaron May 17 '13 at 16:36

Couple of suggestions:

  1. Run Check Geometry tool on your layer that you wish to clip, you could then follow that up with a Repair Geometry if it finds errors. You may wish to do that on a backed up copy.
  2. Check whether the coordinate systems are different. Perhaps you are trying to Clip a dataset in Decimal Degrees with a dataset that is in Meters or vice versa? If so, reproject the Decimal Degrees data into the coordinate system of the other.
share|improve this answer

Same Problem, using ArcGIS Desktop 10.2.2. (In case clipping big and irregullar shape)

Solution :

  1. Try to split into small part then clip it one by one, and yes it will take a lot of time and work, but it works.


  1. Try to clip it using QGIS (I use QGIS Desktop 2.6), I use QGIS and no need to split it one by one. just select area to clip using definition querry and clip.

I recommended try solution number 2.

share|improve this answer

ArcGIS often throws a topoengine error when it runs out of memory while running in 32 bit mode and performing overlay operations. To get around that I either chop-up the job or use 64 bit geoprocessing with lots of RAM and Repair Geometry on all input features (create local copies first if you don't want to mess up your inputs with the repair).

share|improve this answer

Your Answer


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

Not the answer you're looking for? Browse other questions tagged or ask your own question.