<div dir="ltr">Hello Everyone<div><br></div><div>I have submitted my proposal at the melange website. My proposal is available <a href="https://www.google-melange.com/gsoc/proposal/review/student/google/gsoc2014/kansal/5629499534213120" target="_blank">here</a>.</div>
<div>Please review my proposal and give me some suggestions to make this proposal even more useful to the organization.</div><div><br></div><div>@Dmitriy & Chaitanya - I urge you to please specifically look into the "common interface to various algorithms using some existing API" part apart from the whole proposal, in my timeline. I have devoted 7-8 days for this work. If you people have some comments regarding this, kindly convey it to me.</div>
<div><br></div><div>Thanking You all</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></blockquote></div></div>
<br><br><div class="gmail_quote">On Sun, Mar 16, 2014 at 11:46 AM, Chaitanya kumar CH <span dir="ltr"><<a href="mailto:chaitanya.ch@gmail.com" target="_blank">chaitanya.ch@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p dir="ltr">Kshitij,</p>
<p dir="ltr">As suggested you should plan to allow user to select the algorithm for key point detection and matching.</p>
<p dir="ltr">I'll explain how to do that later. But essentially you may get some input from the user to change the default algorithm to something else. So, all the steps should be done independent of each other.</p><div>
<p dir="ltr">--<br>
Best regards,<br>
Chaitanya Kumar CH</p>
</div><div><div><div class="gmail_quote">On 16-Mar-2014 2:58 am, "Dmitriy Baryshnikov" <<a href="mailto:bishop.dev@gmail.com" target="_blank">bishop.dev@gmail.com</a>> wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div>Hi,<br>
<br>
I only proposed to use the exist API - <span style="font-family:arial,sans-serif;font-size:12.727272033691406px">GDALComputeMatchingPoints,
or modify it to support new method </span><span style="font-family:arial,sans-serif;font-size:12.727272033691406px">BRISK.
You have not to modify </span><span style="font-size:12.727272033691406px;font-family:arial,sans-serif">SimpleSurf,
but only make it still working as now.<br>
GDAL is library, not the "</span><span style="font-size:12.727272033691406px;font-family:arial,sans-serif"><span style="font-size:12.727272033691406px;font-family:arial,sans-serif">Automatic
geo-referencer utility</span>" and some common methods and
functions should be developed. This does not deny that such a
tool can be developed but it must use this </span><br>
<span style="font-size:12.727272033691406px;font-family:arial,sans-serif"><span style="font-size:12.727272033691406px;font-family:arial,sans-serif">common
methods and functions. For example see the console utilities
in apps folder of GDAL source tree. They use GDAL functions
and methods.</span><b><br>
</b></span>
<pre cols="72">Best regards,
Dmitry</pre>
16.03.2014 1:15, Seth Price пишет:<br>
</div>
<blockquote type="cite">
<div>I have done something
like this recently. You would be better off tearing out SURF
& linking to OpenCV for all feature detection and
extraction. Here is a link to the patch that OpenCV needs to
support large & 16 bit imagery.</div>
<div><br>
</div>
<div><span><a href="https://github.com/Itseez/opencv/pull/1932" target="_blank">https://github.com/Itseez/opencv/pull/1932</a></span></div>
<div><span><br>
</span>
<div>~Seth</div>
<div><br>
</div>
<span>via iPhone</span></div>
<div><br>
On Mar 15, 2014, at 12:50 PM, Kshitij Kansal <<a href="mailto:kansal.k@gmail.com" target="_blank">kansal.k@gmail.com</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div dir="ltr">Hello Again,
<div><br>
</div>
<div>@Dimitriy - Currently the <span style="font-family:arial,sans-serif;font-size:12.727272033691406px">GDALComputeMatchingPoints
is using the SimpleSurf algorithm for matching points.
Are you proposing that, I should implement the BRISK and
then provide user the option of using either this or
SimpleSurf(already implemented)? </span></div>
<div><font face="arial, sans-serif">This is indeed a very
interesting thought but the problem in this is that,
the </font><span style="font-size:12.727272033691406px;font-family:arial,sans-serif">GDALComputeMatchingPoints is
developed with respect to the correlator project and I
feel that SimpleSurf algorithm implemented there won't
work on my Automatic geo-referencer as I would be
considering the Multispectral Imagery and Large Datasets
which are not handled in the current implementation.<b>
So this will require modification to SimpleSurf as
well.</b></span><br>
</div>
<div><span style="font-family:arial,sans-serif">I hope I
have made my doubt clear? Please convey your views on
this.</span><br>
</div>
<div><font face="arial, sans-serif"><br>
</font></div>
<div><font face="arial, sans-serif">@Chaitanya - In
comparison to the SURF, BRISK can definitely handle the
large imagery to great extent. But there is going to be
some threshold upto which this algorithm will work
because we must not forget that these algorithms are
developed for Normal RGB images for Computer Vision
related work and there usage to Remote Sensing requires
some modification. I will try to look for this thing in
more detail and then get back to you.</font></div>
<div><font face="arial, sans-serif"><br>
</font></div>
<div><font face="arial, sans-serif"><br>
</font></div>
<div><font face="arial, sans-serif">Also, should I prepare
my initial draft of proposal based this BRISK idea
only? </font></div>
<div><font face="arial, sans-serif">I have already started
work in this direction and will soon post it, for
review.<br>
</font>
<div><br>
</div>
</div>
<div>With Regards,</div>
<div><br>
</div>
<div class="gmail_extra">
<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>
</blockquote>
</div>
</div>
<br>
<br>
<div class="gmail_quote">On Sat, Mar 15, 2014 at 12:29 AM,
Chaitanya kumar CH <span dir="ltr"><<a href="mailto:chaitanya.ch@gmail.com" target="_blank">chaitanya.ch@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p dir="ltr">Kshitij,</p>
<p dir="ltr">What is the performance of the proposed
algorithms for very large rasters? If one of them is
good with large images that's a cleaner choice
without all the workaround with scaling the rasters.</p>
<p dir="ltr">--<br>
Best regards,<br>
Chaitanya Kumar CH</p>
<div class="gmail_quote">
<div>
<div>On 15-Mar-2014 12:22 am, "Dmitriy
Baryshnikov" <<a href="mailto:bishop.dev@gmail.com" target="_blank">bishop.dev@gmail.com</a>>
wrote:<br type="attribution">
</div>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div>
<div text="#000000" bgcolor="#FFFFFF">
<div>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 cols="72">Best regards,
Dmitry</pre>
<br>
</div>
</div>
</div>
</div>
</blockquote>
</div>
_______________________________________________<br>
gdal-dev mailing list<br>
<a href="mailto:gdal-dev@lists.osgeo.org" target="_blank">gdal-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/gdal-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>gdal-dev mailing list</span><br>
<span><a href="mailto:gdal-dev@lists.osgeo.org" target="_blank">gdal-dev@lists.osgeo.org</a></span><br>
<span><a href="http://lists.osgeo.org/mailman/listinfo/gdal-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/gdal-dev</a></span></div>
</blockquote>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
gdal-dev mailing list
<a href="mailto:gdal-dev@lists.osgeo.org" target="_blank">gdal-dev@lists.osgeo.org</a>
<a href="http://lists.osgeo.org/mailman/listinfo/gdal-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/gdal-dev</a></pre>
</blockquote>
<br>
</div>
<br>_______________________________________________<br>
gdal-dev mailing list<br>
<a href="mailto:gdal-dev@lists.osgeo.org" target="_blank">gdal-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/gdal-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br></blockquote></div>
</div></div></blockquote></div><br></div></div>