topic Re: get feature count and length of feature classes using C# in ArcObjects SDK Questions

get feature count and length of feature classes using C#

ababreddy — Sun, 20 Jul 2014 13:45:15 GMT

hi, i have transport File geodatabase and feature data set and feature class like roads,driveways,sidewalks and parking lots. my requirement is i need to get feature count and lentgth of all feature classes in the excel using C#.can any one help?

Re: get feature count and length of feature classes using C#

TimothyHales — Mon, 21 Jul 2014 10:44:23 GMT

I've moved your post into the ArcObjects SDK space. You will get a much better answer here as the GeoNet Help is intended for community help and feedback. You can see more on the community structure, and what topics are under each space from the following documents:

GeoNet Community Structure

ArcGIS Discussion Forums Migration Strategy

Thanks!

Timothy

Re: get feature count and length of feature classes using C#

MirbazKhan_Ahmadzai — Mon, 21 Jul 2014 11:30:11 GMT

Go to TOC Layer Attribute table
Open table
right click on lenght field
click statistic

Look for sum, this is total sum of length

Note: this total length is just for one layer. do same process for another layer if you have
cheers,
Ahmadzai

Re: get feature count and length of feature classes using C#

FreddieGibson — Tue, 29 Jul 2014 16:07:46 GMT

I'm going to assume that you're using ArcObjects .NET. If you're wanting to accomplish this task in C# you could do this using Geoprocessing. You could probably complete this entire process using the Summary Statistics tool. You would just need to get the SUM for the length field of the features and also utilize Count. This would create a table for each individual feature you need to process. You would then be able to aggregate all of the outputs into a single table.

If you wanted more fine grain control you could try using cursors in ArcObjects as well. You would utilize a Search Cursor to aggregate the data about each feature and you could use an InsertCursor to push the results to an output table that you've created.

On the other hand, the easiest way to accomplish this would be to use Python. The workflows would be the same as the ArcObjects workflow, but you'd see a decrease in development overhead. I don't believe you'd see too much of a performance difference between the two options.