nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Clip not working

FaithWebster

I have a peculiar problem. The clip tool is simply not running. My results say that the tool ran, but the output isn't created, and there are no messages.

I have moved all the data into the same geodatabase, and it's all in the same projection. I welcome any suggestions to what could be going on because I am at a loss.

Thank you GeoNet Community!

Encuentra más publicaciones etiquetadas con

Accepted answers

All comments

DanPatterson_Retired

All featureclasses, all in the same coordinate system for sure (?!)

Try a select by attribute and see if that works.

Make sure that you don't have any selections if you are expecting a complete clip.

And the clipping geometry is a polygon which can be used to clip, polylines, polygons or points

VinceAngelo

If your polygons have invalid ring geometry, Clip may produce bizarre results.

Try verifying both your Input and Clip layers with CheckGeometry_management

- V

FaithWebster

I double checked, and yes all of the data is in the same projection, and the input and clip features are in the same file geodatabase. I can try a select by location... but i'm not sure a select by attribute would do much. I am clipping line features using a polygon. I honestly have no idea what the issue is.

Thank you for your help.

FaithWebster

I will try that, but my clipping layer only has a single polygon, so no gaps or slivers or overlaps are possible...

DanPatterson_Retired

Checking the projection is one thing, but it is best to look at the numbers for both layer's 'extent'... In order to clip or intersect or any of the 'overlay' tools, the extents must intersect. if the bounding box of the layer being used to 'clip' the geometry doesn't overlap what is to be clipped, then nothing will occur.

VinceAngelo

The polygon can still be invalid in other ways (e.g., self-intersection).

- V

FaithWebster

So I tried just selecting by location, and then I was going to make a layer from selected features, but I got another weird result:

I think I might have a problem with ArcGIS...

VinceAngelo

Uninstall/reinstall couldn't hurt, but I expect the problem is with the data, not the software.

- V

DanPatterson_Retired

Faith... did you run a Check Geometry on the data as Vince suggested?

You might actually want to make a copy to a local simple folder in a test geodatabase there first.

jthomas

I am having the same problem with multiple tools in the toolbox. It happens on completely different datasets. It happens regardless of coordinate system matching. It happens on 3 different PCs in our office. It is usually fixable by rebooting PC but only temporarily - so it gets very frustrating. Closing and restarting ArcGIS doesn't help. Right now it's happening with Extract by Mask (for raster) but there have been about 10 tools doing this. It's happening on 10.5.1 right now and also happened on previous version of ArcMap and on previous PC to the one I got recently. The exact opposite problem also occurs (sometimes it generates and error and says it couldn't complete process, but it actually generated a completely valid output in the folder).

FaithWebster

Its a problem that i'm still having. running a repair works for a few days though... it seems to happen more if it's been a day or since i've restated my pc.

jthomas

Faith, what do you mean by running a repair? I'm curious to try same thing here. We just upgraded to 10.6.1 and I was disappointed to find that the problem is still happening on a daily basis for me. And I still have to reboot my machine every time to fix it. It has become a big time consumer. It's interesting that you have also been experiencing the issue for many months and how recent you restarted also affects you. You wouldn't happen to be using a cloud backup appliance system like Panzura would you?

DanPatterson_Retired

Repair.... Got to Windows Control panel, Add/Remove Programs, select arcmap and a 'Repair' will be one of the options

KeithAddison1

GDBs suffer from all kinds of geoprocessing failures. Move the data to shapefiles.

VinceAngelo

I have to point out that shapefiles are not an acceptable substitute for users with numeric NULLs, fieldnames longer than 10 characters, UTF-16 strings, strings exceeding 254 charcters, BLOB data, datetime fields with higher than day resolution, topologies, feature datasets, domains,.... Establishing correct spatial reference metadata can sometimes be a challenge, but getting the values right is much easier than trying to get by with a data format, created in the early 1990s, which lacks so many modern features.

- V

KeithAddison1

I agree, but deadlines mean I do what I know works instead of spending unknown hours trying to figure out what's not working, and then possibly having a solution. Hopefully I won't run into this do it right and look like and inefficient employee vs. do it quick & dirty proplem so much with Pro.

KarenRobine

I just read this. I'm having a problem with Clip in a Geoprocessing tool (part of a very large python script) running in 10.5.1. It runs perfectly in 10.4.1 and 10.6.1, so I think it's a bug in 10.5.1. Its happening on a very large dataset of NHD Flowlines (linear data). So I'm curious what version of software you ran into this problem with?

WilliamOlsen

I teach GIS at a University and have been running into this problem on and off for months in a computer lab setting. It happens with multiple functions and basically just runs the tool very fast and says it was completed, but no data gets produced. It does not seem to be related to projections, bad geometry, or the bounding coordinates. Changing default GDB, scratch workspace, default workspace or other environment settings does not help. Restarting the PC is the only option since the students do not have Admin. rights to run a repair.

If anyone knows what is causing this, please respond!

Thanks.

WilliamOlsen

Just an update in case anyone else runs into this....If you Disable Background Geo Processing, it appears to fix the issue.

FaithWebster

I'm on 10.5.1 too, and I'm inclined to agree with you about the bug

FaithWebster

wow! i will keep that in mind. thanks for the tip

AmandaNunley

Thank you so much William! I have been battling with this problem for over a year. My geoprocessing tools have been running successfully, but not creating the output datasets. Sometimes in happens in ArcMap, sometimes ArcCatalog.(This was still an issue at 10.7) But, turning off the background geoprocessing fixed the problem immediately! Thanks for your help!!

YacineBerrezel

Hello Faith, I had the same problem, try to reboot your device

winnerabiodun1

This worked just fine. Thanks for sharing

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.