<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi,<br>
<br>
I think we need to decide it here, not to create lot of proposals.
The second idea is very interesting. Maybe it worth to create some
common interface (or API) to add new methods BRISK, SURF, SIFT
etc. <br>
You can develop you realisation of BRISK and demonstrate how-to
one can use it via such common interface.<br>
E.g. in GDALComputeMatchingPoints add enum for algorithms or use
exist papszOptions.
<pre class="moz-signature" cols="72">Best regards,
Dmitry</pre>
14.03.2014 17:28, Kshitij Kansal пишет:<br>
</div>
<blockquote
cite="mid:CAKTWcS=9dfhvBv_fQUP+2T3w3jVtxFcjdrKaCY41k3mFzAyTdg@mail.gmail.com"
type="cite">
<div dir="ltr">Hello everyone
<div><br>
</div>
<div>Continuing the previous discussion, I would like to propose
something and the community's suggestions are welcomed/needed.
I can understand that this thread is a little old, so let me
remind you that its regarding the automatic geo-referencer
idea. The idea is also proposed on the GDAL ideas page (<a
moz-do-not-send="true"
href="http://trac.osgeo.org/gdal/wiki/SummerOfCode">http://trac.osgeo.org/gdal/wiki/SummerOfCode</a>). </div>
<div><br>
</div>
<div>Based on the previous discussions, what came out was that
we can improve the current implementation of SIMPLE SURF in
GDAL which was developed as a part of 2012 GSOC GDAL
Correlator project, to support <b>large data</b> and <b>multi
spectral imagery</b>. And then apply this <b>modified</b> algorithm
for the geo-reference purposes. Now I have been in touch with
Chaitanya, who is willing to mentor this project, and there
are some things on which we would like to know community's
suggestions/response.</div>
<div><br>
</div>
<div>There are basically two things that can be done regarding
this project:</div>
<div><br>
</div>
<div>1. As mentioned above, we can modify the SIMPLE SURF
algorithm and make it much better for the geo-reference
purposes. Already, a lot had been discussed on this and we
have a fairly good idea about what is to be done.</div>
<div><br>
</div>
<div>2. One more thing that can be done is that we can implement
BRISK algorithm[1] instead of SURF along with the FLANN
matcher for this purpose. What advantages this thing offers is
that it is fairly fast and gives comparable outputs along with
that it works well with fairly large data sets. So we do not
need to segment the imagery as we would have done in the case
of SURF. Also added to this, this algorithm also has no patent
issues. We had a lot of problem regarding patent issues in
SIFT/SURF and we discussed them at length on the mailing list
as well. </div>
<div><br>
</div>
<div>One thing that I fell can be done is that two proposal can
be written, one for each and then community can decide
accordingly which one is more useful. Or we can decide it here
itself..? </div>
<div><br>
</div>
<div>Kindly provide your valuable comments and suggestion..</div>
<div><br>
</div>
<div>With Regards,</div>
<div class="gmail_extra"><br clear="all">
<div>
<div dir="ltr">
<blockquote style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Kshitij
Kansal</blockquote>
<blockquote style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Lab
For Spatial Informatics,<br>
</blockquote>
<blockquote style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">IIIT
Hyderabad<br>
<br>
</blockquote>
</div>
</div>
1. <a moz-do-not-send="true"
href="http://www.robots.ox.ac.uk/%7Evgg/rg/papers/brisk.pdf">http://www.robots.ox.ac.uk/~vgg/rg/papers/brisk.pdf</a><br>
<br>
<div class="gmail_quote"><br>
</div>
</div>
</div>
</blockquote>
</body>
</html>