Hi,
I think 7-8 days will be enough. According to you plan this issue will
raise on 4-5 week then you'll export BRISK algorithm to GDAL. By now I
don't see any problems - don't worry.
Best regards,
Dmitry
17.03.2014 22:05, Kshitij Kansal пишет:
Hello Everyone
I have submitted my
Hello Dmitry
Thank you.
Is there anything else you can suggest regarding the proposal or Should I
consider the current draft as the final one?
I have planned it to the best way I could think of. I have tried to give
enough time for testing, documentation and code cleaning also as it is a
Hello Everyone
I have submitted my proposal at the melange website. My proposal is
available
herehttps://www.google-melange.com/gsoc/proposal/review/student/google/gsoc2014/kansal/5629499534213120
.
Please review my proposal and give me some suggestions to make this
proposal even more useful to
Kshitij,
As suggested you should plan to allow user to select the algorithm for key
point detection and matching.
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
Hello Again,
@Dimitriy - Currently the 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)?
This is indeed a very interesting
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.
https://github.com/Itseez/opencv/pull/1932
~Seth
via iPhone
On Mar
Also, I wouldn't worry much about the multispectral part of the data. You're
going to have more trouble with reliably finding the correct key point matches.
Use RANSAC, also in OpenCV.
~Seth
via iPhone
On Mar 15, 2014, at 12:50 PM, Kshitij Kansal kansa...@gmail.com wrote:
Hello Again,
Hi,
I only proposed to use the exist API - GDALComputeMatchingPoints, or
modify it to support new method BRISK. You have not to modify
SimpleSurf, but only make it still working as now.
GDAL is library, not the Automatic geo-referencer utility and some
common methods and functions should be
Hello everyone
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
Hi,
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.
You can develop you realisation of BRISK and demonstrate how-to one can
use it via such
Kshitij,
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.
--
Best regards,
Chaitanya Kumar CH
On 15-Mar-2014 12:22 am, Dmitriy Baryshnikov
Hello Everyone
I have updated the Summer Of Code Ideas Page for GDAL. I have Introduced
the above idea in that page also. Mr. Chaitanya Kumar is willing to mentor
the project.
Please look into this.
Suggestions and Comments are welcomed.
Regards,
Kshitij Kansal
Lab For Spatial Informatics,
Hi,
Even note that you cannot get the code from this projects and merge it
to GDAL, but you free to develop you own implementation of this
algorithms as path of GDAL.
This is a same situation with correlator. Andrew cannot get code from
OpenCV and GRASS as incompatible licenses, so the own
Hello
Based on all suggestions and comments above, I have come up with one thing.
The most important thing that could have been a road block for this project
was licence issues which was pointed by Even Rouault.
I am interested in implementing the SIFT or ASIFT algorithms for automatic
On Fri, Feb 7, 2014 at 11:10 AM, Kshitij Kansal kansa...@gmail.com wrote:
This means that the final product as a result of this product will also be
bounded by the above licences. It can not go into GDAL's main distribution
but can be used as a separate utility of GDAL for non-commercial uses
Selon Kshitij Kansal kansa...@gmail.com:
Kshitij,
I'm surprised that you mention licenses
for algorithms. What are your sources for that?
Only *implementations* can be licensed
not algorithms themselves. So if you
develop your own implementation you are free
to select the license you wish. There
Sir
I am providing the links for both the algorithms that I talked. I am new to
this licence issues thing so I would be highly grateful if you can clarify
doubts and if can proceed on working for this idea.
http://www.cs.ubc.ca/~lowe/keypoints/ (SIFT)
http://www.ipol.im/pub/art/2011/my-asift/
Hello
@Jukka Rahkonen: The OSSIM project (the link you provided) is more of image
orthorectification. Although
they are doing image co-registration but its as one of the steps of
orthorectification(I could only understand this from the manual).
Also I am not sure of the techniques they are using
) a lot of
work is already done.
Having this functionality at the core of GDAL would of course target much
more people then only Python users.
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/gdal-dev-RFC-GDAL-Idea-for-GSoC-2014-tp5100128p5100379.html
Sent from the GDAL - Dev
can handle Python) a lot of
work is already done.
Having this functionality at the core of GDAL would of course target much
more people then only Python users.
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/gdal-dev-RFC-GDAL-Idea-for-GSoC-2014-tp5100128p5100379.html
Le mardi 28 janvier 2014 20:41:15, Kshitij Kansal a écrit :
Hello
Thank you for you suggestions.
Joaquim
I looked into the link regarding Affine-SIFT that you provided. Indeed the
results that are shown there are very promising. If we can bring this to
one of the core functionality of
Even,
Thank you for pointing out this issue. I will keep this in mind.
I will look into that last year project and try to understand the
implementation.
More suggestions and comments are always welcomed.
Regards,
Kshitij Kansal
Lab For Spatial Informatics,
IIIT Hyderabad
On Wed, Jan 29,
Kshitij Kansal kansal.k at gmail.com writes:
Even,
Thank you for pointing out this issue. I will keep this in mind.
I will look into that last year project and try to understand the
implementation.
More suggestions and comments are always welcomed.
Hi,
Another OSGeo project OSSIM
Hi all,
I talked with Kshitij about this idea at length. I am sure that he can do a
good job. He has the programming skills and has academic background in
image processing and computer vision.
I am willing to co-mentor him.
Kshitij,
You did not include the extensions we discussed. Estimating the
Well, I actually implemented this idea in Mirone long time ago. First
with SIFT and later with the SURF module in OpenCV, but I really never
tested much from the the point that some cases work well, others not so
much.
Anyway, you might be interested to look also into ASIFT. It looks
Hello Everyone
I am an undergrad student in my Junior year of study. I have been involved
with some research in field of Spatial Temporal Analysis of Images. I have
been using the GDAL for various purposes, for quite some time now. I
thought that now its time to contribute something to Open
26 matches
Mail list logo
