I run into this all the time and I don't know why this keeps happening. However, my solution is simple. Go into your environments and set the processing extent to "union of all inputs". That should take care of your problem.
Empty output error can be due to a definition query on something that changes due to the geoprocessing tool. In other words, if there are no longer any records that satisfy it.
I also turn off background geoprocessing, in every map, every time, unless it is needed. This usually causes a more generic 99999 error, though, not empty output. Really don't get why something so problematic as this is the default. Pretty much all tools that change an existing file will fail due to locking issues. I concur with turning off the indexing service too, because it eats up too much processing.
I'm having the same issue with the select by location tool, and repair geom didn't do the trick
-selected layer is a line feature layer from an oracle spatial table
-selecting layer is a query layer from oracle spatial point table, layer containing only 1 point resulting form query => saved to disk with the copy features tool
-relation is intersect, with a radius of 50m
ArcgGIS version is 10.1 fyi
No sde used
What am I missing here?? I first thought it was due to differences in the geometry fields, because I had the same error with a self-drawn point feature class.
Weird thing is that it DOES work with a previously exported point form the database, which has exactly the same schema as the one I'm querying now...
Should I try a different export tool to materialize the query layer?
Would love some help on this! 🙂
Thanks!
Repair geometry worked for me too!Thank you for the answer!
Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.