Hi Agus,
This is related to your previous question, sorry I did not find the time
to answer yet :
The minsize parameter of the LSMSSegmentation step acts as a filtering :
all segments smaller that minsize are replaced by a background value. If
you want to consider all segments you have to set minsize to 0. Then you
can merge them with the LSLSSmallRegionsMerging tool.
Regards,
Julien
Le 20/01/2017 à 10:19, Agustin Lobo a écrit :
A command such as
otbcli_LSMSSegmentation -in filtered_range.tif -inpos
filtered_spat.tif -out segmentation.tif uint32 -ranger 3 -spatialr
5 -minsize 5 -tilesizex 256 -tilesizey 256
results on a segmentation.tif file with many patches that have a 0
value, including many isolated pixels. Why? A far as I understand,
values in segmentation.tif are just unique indices for each segment,
there should be no 0. I observe no weird values on either the input
image
or the MS filtered image for these patches. I include an snapshot in
which segments labelled 0 are
displayed as black
https://dl.dropboxusercontent.com/u/3180464/segmentationwith0s.png
Agus
--
Julien MICHEL
CNES - DSO/SI/2A
--
--
Check the OTB FAQ at
http://www.orfeo-toolbox.org/FAQ.html
You received this message because you are subscribed to the Google
Groups "otb-users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/otb-users?hl=en
---
You received this message because you are subscribed to the Google Groups "otb-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
