How do the ComponentMeasurements function computed " Area" and "Length" properties relate to the "Count" property in terms of pixels ?


In nuce; while both "Count" and "Area" can be both considered as metrics for the area covered by an object in a given black and white image (i.e. Bit type), they do not account for it in the same way.

"Count" literally and simply counts the number of pixels forming the object sensu stricto.

“Area” counts the same pixels but score them according to their relative localization to each other based on some 2*2 neighborhood rules. In this case, I believe one should not disable the CornerNeighbors option of ComponentMeasurements which is by default True.

For an exhaustive answer please follow the link below:


| improve this answer | |
  • 2
    $\begingroup$ Thank you for reporting on that answer. Since links are likely to age and break, however, it would be welcome if you could briefly summarize the answer you linked to. $\endgroup$ – MarcoB Nov 16 '16 at 4:56

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.