Hi Agus,
The readthedoc documentation export is experimental (Rashad did this a
while ago), and surely has some unsolved issues for now. If you refer to
the official documentation here :
https://www.orfeo-toolbox.org/CookBook/CookBooksu103.html#x136-6690005.6.7
You will see that the table is right. For instance :
precision
Float
Estimated precision of the colocalisation function (in pixels).
mfilter
Boolean
Filter points according to geographical or sensor based colocalisation
Regarding the precision parameter documentation, it is used at several
steps of the algorithm, as described in the Detailed Description of the
application :
"In this mode, the corresponding spatial bin in the second image is
estimated using geographical transform or sensor modelling, and is
padded according to the user defined *precision*."
"Last, in both modes the application can filter matches whose
colocalisation in first image exceed this *precision*."
But we can update the documentation of the parameter if you think this
is not clear enough.
Regards,
Julien
Le 10/06/2015 10:00, Agustin Lobo a écrit :
Doc on Homologous Point Extraction
http://otbcb.readthedocs.org/en/latest/Applications/app_HomologousPointsExtraction.html
is incomplete.
For example, the only information provided on argument mfilter
is that it is a Boolean. No definition, no default value, no example.
Instead, the command line help page is more informative:
"-mfilter <boolean> Filter points according to
geographical or sensor based colocalisation (optional, off by
default)"
although it is not clear if the user has to write "on" or "1" to turn
it on. And it is not clear either what kind of filter (mean filter?)
and which radius
Regarding "precision", there is also no definition in the table (the
information on
Parameter Type is just repeated) but it is later defined as in the
command line help page:
"Estimated precision of the colocalisation function (in pixels).
Estimated precision of the colocalisation function in pixels."
I do not say this definition is wrong, but it is no appropriate. The
definition must
state the role of the argument in the process. In this case, I
understand that the
algorithm searches, for a given point image in1 band1, an homologous point on
image in2 band2 within a radius equal to the value of precision in pixels.
Correct?
Also, what happens if the user sets precision to i.e. 10 and mfilter is off?
Thanks
Agus
--
Julien MICHEL
CNES - DCT/SI/AP - BPI 1219
18, avenue Edouard Belin
31401 Toulouse Cedex 09 - France
Tel: +33 561 282 894 - Fax: +33 561 283 109
--
--
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.
