<div dir="ltr">Hello<div><br></div><div>@<span style="font-family:arial,sans-serif;font-size:13px;font-weight:bold;white-space:nowrap">Jukka Rahkonen: </span><span style="font-family:arial,sans-serif;font-size:13px;white-space:nowrap">The OSSIM project (the link you provided) is more of image orthorectification. Although</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px;white-space:nowrap">they are doing image co-registration but its as one of the steps of orthorectification(I could only understand this from the manual).</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px;white-space:nowrap">Also I am not sure of the techniques they are using for this purposes. (Its written corner point detection but How?)</span></div><div><font face="arial, sans-serif"><span style="white-space:nowrap">I am new to OSSIM, so not aware of this thing's functionality and accuracy. I am in the process of estimating it.</span></font></div>
<div><br></div><div>Thank you for pointing this out.</div><div><br></div><div>Coming to the <span style="font-family:arial,sans-serif;font-size:13px">Frank Warmerdam's blog (</span><font face="arial, sans-serif"><a href="http://fwarmerdam.blogspot.fi/">http://fwarmerdam.blogspot.fi/</a></font><span style="font-family:arial,sans-serif;font-size:13px">). Here the author is talking about writing a code for converting the GCP's into RPC's. But the next question comes is where is he getting GCP's from. Now this is the part where I aim to work on and improve. </span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px">Given two images, if we can automatically extract GCP's from them then we are in a way speeding up and automating this whole process. Once we have GCP, there are a lot of things that we can do from them like geo-referencing(which I plan on doing), image stitching etc.</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px"><b>Also you talked about a "more light weighted system". Can you please elaborate on this?</b> I could not understand what you actually meant from that.</span></div>
<div><br></div><div>If we look into the last year idea's page (<a href="http://trac.osgeo.org/gdal/wiki/SummerOfCode">http://trac.osgeo.org/gdal/wiki/SummerOfCode</a>), there is one idea that is proposed regarding the "Raster/Vector geo-referencer on the Web". I want to modify this idea a little bit and want to automate the whole process. As far as the automation is concerned, we can develop GDAL functions for that(which will be completely re-usable) and then developing a Web based geo-referencer would only require calling those functions.</div>
<div><br></div><div>If we do this thing,<b> two objectives will be fulfilled</b>.<b> First</b>, GDAL will get a web based geo-referencer. <b>Secondly</b>, communities that use GDAL and have not developed these kind of geo-referencer(Like QGIS) can directly use the functions developed and then build on that. </div>
<div><br></div><div>Suggestions and comments are welcomed.</div><div><br></div><div>Thank you for your propositions.</div><div><br></div><div>Regards,<br></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 Wed, Jan 29, 2014 at 1:27 PM, Jukka Rahkonen <span dir="ltr"><<a href="mailto:jukka.rahkonen@mmmtike.fi" target="_blank">jukka.rahkonen@mmmtike.fi</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">Kshitij Kansal <kansal.k <at> <a href="http://gmail.com" target="_blank">gmail.com</a>> writes:<br>
<br>
><br>
> Even,<br>
> Thank you for pointing out this issue. I will keep this in mind.<br>
><br>
> I will look into that last year project and try to understand the<br>
implementation. <br>
><br>
<br>
> More suggestions and comments are always welcomed.<br>
<br>
</div>Hi,<br>
<br>
Another OSGeo project OSSIM has implemented an automatic image to image<br>
rectification. Isn't that a bit alike your plan?<br>
<a href="http://download.osgeo.org/ossim/docs/OSSIM_Coregistration_UserManual.pdf" target="_blank">http://download.osgeo.org/ossim/docs/OSSIM_Coregistration_UserManual.pdf</a><br>
<br>
Frank Warmerdam seems to entertain himself with something related<br>
<a href="http://fwarmerdam.blogspot.fi/" target="_blank">http://fwarmerdam.blogspot.fi/</a><br>
<br>
This article from 2013 may also give some inspiration<br>
<a href="http://www.academia.edu/4388853/OrientAL_-_Automatic_geo-referencing_and_ortho-rectification_of_archaeological_aerial_photographs" target="_blank">http://www.academia.edu/4388853/OrientAL_-_Automatic_geo-referencing_and_ortho-rectification_of_archaeological_aerial_photographs</a><br>
<br>
All these three aim to very high quality and I am sure that there is also<br>
need for a more light-weight system.<br>
<span class="HOEnZb"><font color="#888888"><br>
-Jukka Rahkonen-<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
gdal-dev mailing list<br>
<a href="mailto:gdal-dev@lists.osgeo.org">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></div></div></blockquote></div><br></div></div>