<br><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Dec 9, 2012 at 1:51 AM, Markus Metz <span dir="ltr"><<a href="mailto:markus.metz.giswork@gmail.com" target="_blank">markus.metz.giswork@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">[answering here because I have worked on some of the affected modules]<br>
<div class="im"><br>
On Wed, Dec 5, 2012 at 6:16 PM, Mohammed Rashad<br>
<<a href="mailto:mohammedrashadkm@gmail.com">mohammedrashadkm@gmail.com</a>> wrote:<br>
><br>
><br>
><br>
> On Fri, Nov 30, 2012 at 7:46 PM, Markus Neteler <<a href="mailto:neteler@osgeo.org">neteler@osgeo.org</a>> wrote:<br>
>><br>
>> On Fri, Nov 30, 2012 at 5:26 AM, Mohammed Rashad<br>
>> <<a href="mailto:mohammedrashadkm@gmail.com">mohammedrashadkm@gmail.com</a>> wrote:<br>
>> ><br>
>> > All,<br>
>> ><br>
>> ><br>
>> > I found these here[1] and says many things which needed help. So I<br>
>> > thought<br>
>> > to give a try in order<br>
>> ><br>
>> ><br>
>> > 1. Imagery Library needs fundamental clean up (the library is not<br>
>> > maintained<br>
>> > from GRASS 5)<br>
>> ><br>
>> > Anyone can elaborate on this line?<br>
>><br>
>> Fully agreed.<br>
>><br>
>> It might be sensible to merge the various image libraries:<br>
>><br>
>> GRASS 6/7:<br>
>> * lib/imagery/: standard lib, in use (i.* except for i.points3,<br>
>> i.rectify3, see below)<br>
>> * imagery/i.ortho.photo/libes/: standard lib, in use (i.ortho.photo,<br>
>> photo.*)<br>
>><br>
><br>
><br>
> i.points3 and i.rectify3 doesnt uses standard lib. So adding API style code<br>
> which can be used by i.point3 and i.rectify3 is what you are saying. Am I<br>
> correct?<br>
<br>
</div>I guess so, but I would suggest to move the libs needed by i.points3<br>
and i.rectify3 to a separate GRASS lib, probably ortholib<br>
><br>
> i.ortho.photo uses i.ortho.photo/libes right?<br>
<br>
No, it uses (will use) ortholib, currently i.ortho.photo/lib, but I am<br>
busy porting it and related modules to trunk.<br></blockquote><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class="im"><br>
><br>
> so merging both libs will provide an API which any grass imagery module can<br>
> share right?<br>
<br>
</div>I would suggest to separate standard imagery lib and<br>
orthorectification, because these two use substantially different<br>
algorithms. The ortholib depends on imager lib.<br></blockquote><div><br></div><div><br></div><div>i.ortho.photo is under progress right? . So moving imager to a lib called ortholib under imagery like imagery/ortholib or as grass_trunk/ortholib is need to be done. right?<br>
</div><div><br></div><div>So If I start moving code around will it affect the current work on i.ortho and friends?</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class="im">><br>
><br>
><br>
>><br>
>> GRASS 5 (! only) image3 lib:<br>
>> * libes/image3/: never finished improvement which integrated the<br>
>> standard lib and the ortho lib. Seems to provide also ortho<br>
>> rectification for satellite data (i.points3, i.rectify3)<br>
>><br>
>> GRASS 5/6 image proc commands:<br>
>> * merge of i.points, i.vpoints, i.points3 (see above)<br>
>> * merge of i.rectify and i.rectify3 (see above)<br>
>><br>
>> Overall<br>
>> * add other warping methods (maybe lanczos or thin splines from GDAL?)<br>
><br>
><br>
> This part is not clear to me at all<br>
<br>
</div>Lanczos is already available.<br>
<br>
What could be gained by adding thin splines to the existing bilinear,<br>
bicubic, bspline, lanczos methods?<br><br></blockquote><div> </div><div>This question is not clear for me</div><div> </div><blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Markus M<br>
<div class="im"><br>
><br>
><br>
>><br>
>><br>
>> However, the library cleanup in GRASS 7 would be essential.<br>
>><br>
>> > 2. Reimplement groups to be generic element (in GIS Library)<br>
>> ><br>
>> > I guess i.group module should be g.group which can groups both<br>
>> > raster/vector<br>
>> > maps<br>
>> ><br>
>> > Is that correct?<br>
>><br>
>> Correct I don't know, maybe subject to discussion.<br>
><br>
><br>
><br>
> Anyone have any comments ?<br>
><br>
>><br>
>><br>
>> Best<br>
>> Markus<br>
><br>
><br>
><br>
><br>
> --<br>
> Regards,<br>
> Rashad<br>
><br>
><br>
</div>> _______________________________________________<br>
> grass-dev mailing list<br>
> <a href="mailto:grass-dev@lists.osgeo.org">grass-dev@lists.osgeo.org</a><br>
> <a href="http://lists.osgeo.org/mailman/listinfo/grass-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/grass-dev</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div><font face="arial, helvetica, sans-serif">Regards,<br> Rashad</font></div><br>
</div>