I'm having a problem running the tabulate intersection tool.

2544
9
Jump to solution
09-17-2016 09:48 PM
EricBrossman
New Contributor III

Hello,

I'm using the tabulate intersection tool to determine areas of land cover polygons that fall within the band regions of a kernel density estimate of some points.  I have layered Barn Owl dispersal locations over land cover data and used a kernel density estimate to determine the area of each habitat polygon within each density band.  I used the Reclassify Tool to differentiate the density bands and converted them to polygons.  I used the Tabulate Intersection tool to determine the areas of each habitat polygon in the kernel density that intersected with the the total land cover available to the owls. 

For the most part, this was successful, however, a few times I've gotten a 00725 Error when running the Tabulate Intersection tool which states that the "Output table already exists."  I've tried changing the names but I still get the error.  I tried enabling the overwrite, I get a warning message that says the output table already exists. It generates a table but the table is empty.  I've tried running it under a new geo database but it still won't work.

 As I've stated before, sometimes it works and I get the desired output table without a hitch.  Does anyone have an idea where things might have gone wrong?  Let me know of any additional information you may need. 

Thanks again,

Eric

0 Kudos
1 Solution

Accepted Solutions
EricBrossman
New Contributor III

Thank you for your help but I'm still getting the same issues. When it works, I get the gridcodes for the habitats within the kernel density bands. When it doesn't work, the output table is blank. I've tried creating a new geodatabase but I keep getting the same error. I'm not using any special characters, just the default output table title. I haven't done anything different from when the operation is done successfully or when I get the error that the output table already exists. Let me know if there is any additional information you need. Thank you again, this forum has been extremely helpful to me.

View solution in original post

0 Kudos
9 Replies
NeilAyres
MVP Alum

Arc version, os etc.

Is there any difference between when it works and not?

Is everything going to a file geodatabase? No funny spaces or whatever in your data paths?

0 Kudos
EricBrossman
New Contributor III

As far as I can tell, there doesn't seem to be any difference from when it works and when I get the 000725 error. Yes, everything is going to a file geodatabase, I haven't used spaces or funny characters when naming the output table. I'm using the default name the tool assigns to the output table.

0 Kudos
DanPatterson_Retired
MVP Emeritus

I have seen similar "table already exists" issues before. try this

  • create, or move to a new location (folder or geodatabase)
  • when you more/copy the input files, but rename them on the way to their destination
  • work locally on your machine is implicit in the above since paths containing spaces or '.' or even unc paths seem to cause issues
EricBrossman
New Contributor III

Dan, could you elaborate on this: 

  • when you more/copy the input files, but rename them on the way to their destination
0 Kudos
EricBrossman
New Contributor III

Thank you for your help but I'm still getting the same issues. When it works, I get the gridcodes for the habitats within the kernel density bands. When it doesn't work, the output table is blank. I've tried creating a new geodatabase but I keep getting the same error. I'm not using any special characters, just the default output table title. I haven't done anything different from when the operation is done successfully or when I get the error that the output table already exists. Let me know if there is any additional information you need. Thank you again, this forum has been extremely helpful to me.

0 Kudos
DanPatterson_Retired
MVP Emeritus

Eric... the bullets still need examples.  You indicate that you think the names are correct, but we can't confirm.

If youare reusing the same name(s) between runs even with deleting/removing between steps it doesn't mean that file locks have been removed and 'arc' thinks it still exists.

Also, you have marked the question answered. A slip of the mouse?

0 Kudos
EricBrossman
New Contributor III

Yes, an accidental click.

It sounds like it's a bit tricky, arc thinking it's reusing the same output

table. Is the solution to create distinct names for each run so arc doesn't

get "confused"

0 Kudos
EricBrossman
New Contributor III

Hello Dan,

Thank you for your quick responses but I'm still having the same issues with the tabulate intersection tool and the 000725 Warning("Output table already exists").  I'm not using the same name in between runs, even when I delete the inputs from ArcMap.  I've tried creating a new geodatabase but I still get the same error for that particular run.  As far as I can tell there's nothing different from when the process works from when the error message is generated and the output table is empty.  I'm wondering if there maybe something with the extent environments?  Let me know if there is any additional information you need from me that would help with a solution.

Eric

0 Kudos
DanPatterson_Retired
MVP Emeritus

I don't know if tabulate intersection does projections on the fly.  I never rely on that in any event.  It would be a good idea to ensure that all the files you are using have the same coordinate system (projected preferable, if you need parameters from geometry) and that their extents do indeed overlap.  The Environments tab should be checked in each ArcToolbox tool prior to running a tool to confirm environment parameters.  Don't rely on global ones set at the geoprocessing level.  Also, at the bottom of each tool description in the help files, the environment parameters that are honored by the tool are generally given.

0 Kudos