I am trying to use the "Tabulate Area 2" tool in the following update:


I have overlapping polygons in which I'd like to calculate the area of lake coverage, hence why the original "Tabulate Area" will not work.

Here is a picture of the output table when I run "Tabulate Area 2":

enter image description here

The feature zone is working fine, using the ID column I am inputting, but the feature class is using ObjectID and not using any other attribute, see the example below:

enter image description here

The areas that it is calculating are not in metres, I think they are in decimal degrees.

How can I change the class field the "Tabulate Area 2" tool is using for my feature class? and How can I make this tool calculate area in metres?

I am using ArcGIS 10.1 with an ArcView license.

closed as off-topic by Andre Silva, Jochen Schwarze, LaughU, whyzar, Vince Feb 25 at 15:36

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "This problem cannot or can no longer be reproduced. Changes to the system or to the asker's circumstances may have rendered the question obsolete, or the question does not include a procedure to enable potential answerers to reproduce the same symptoms. Such questions are off-topic as they are unlikely to help future readers, but editing them to include more details can lead to re-opening." – Andre Silva, Jochen Schwarze, LaughU, whyzar, Vince
If this question can be reworded to fit the rules in the help center, please edit the question.

  • 1
    To make calculations in metres first project both layers. Does class data has any other integer (or text) fields in addition to OBJECTID_12? If not it answers first part of your question – FelixIP Jan 26 '15 at 19:32
  • 1
    I used the "Project" tool to change the layers to UTM and now I am getting area values in metres, that issue is now solved. I have added fields to the class in text and integer, but the class field will not select any other fields, it keeps defaulting to ObjectID_12. – JC11 Jan 26 '15 at 20:59
  • 1
    I'd say just forget this add-ins. Go intersect to layers, output to feature in gdb. Export to shapefile and bring dbf file in Excel. Insert pivot table (rows=first input IDs), columns=second input IDs (pick string or integer), totals of shape_area – FelixIP Jan 26 '15 at 21:25
  • Forgot to mention, you'll get much more accurate estimates because spatial analyst tools are working with rasters, i.e. they first convert polygons, this result in sometimes rough approximation of original shape. – FelixIP Jan 26 '15 at 21:35