How can I find pixel coordinates of a perimeter in a binary image?

15 visualizaciones (últimos 30 días)
Milad
Milad el 1 de Abr. de 2014
Comentada: Cam S el 18 de Jul. de 2019
Hi
I have a binary image which I have extracted the perimeter with bwperim() function. Now that I have the perimeter image I am trying to extract the coordinates of pixels in this perimeter.Here are the images:
The white perimeter illustrated in the second image is where I want to find the coordinates. Any Suggestions is appreciated.
Thanks
  3 comentarios
Image Analyst
Image Analyst el 3 de Mzo. de 2017
Editada: Image Analyst el 3 de Mzo. de 2017
mahesh, put this as an "Answer" below, not a comment up here. Also your entire code could be done in the single line
[rows, columns] = find(bwperim(img));
which is about the same at Nitin's accepted answer. However, neither that, nor your code will give the perimeter in a contiguous, connected way, like going clockwise around the region. It will give them on a column by column disconnected basis.
Cam S
Cam S el 18 de Jul. de 2019
yes exactly! how do you do that image analyst

Iniciar sesión para comentar.

Respuesta aceptada

Nitin
Nitin el 1 de Abr. de 2014
Assuming your image is a binary one:
[a,b]= find(I==1); % get the coordinates

Más respuestas (2)

Dishant Arora
Dishant Arora el 1 de Abr. de 2014
If you have a single blob the above answer would suffice but in case you have multiple objects use bwboundaries. It gives you the coordinates of boundary pixels.
doc bwboundaries
  3 comentarios
Dishant Arora
Dishant Arora el 1 de Abr. de 2014
First one is the co-ordinates of boundary pixels and second is a labelled image. What output do you get from find()?? Post your code.
Image Analyst
Image Analyst el 1 de Abr. de 2014
I agree with Dishant that bwboundaries is what you want , not bwperim followed by find. The difference in sizes between find and bwperim is probably due to bwboundaries "cutting corners" as it makes a 45 degree path while perim will give you all the rows and columns of the "L". Also find probably does not "follow the boundary" like bwboundaries does. With find you are not gauranteed that the pixel at the kth index is next to the pixel at the (k+1)st index since find probably goes in column major order like most things in MATLAB.

Iniciar sesión para comentar.


Arriana Nwodu
Arriana Nwodu el 13 de Ag. de 2018
So which code is correct? I tried all the ways listed and it didn't work

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by