<div dir="ltr">Hello Paul and Markus,<br><br>at some point would it be useful to get an Import Wizard up and running?<br>It would call the necessary <a href="http://r.in">r.in</a>* or <a href="http://v.in">v.in</a>* according to needed formats...<br>
<br>Michael and I worked on a wxWizard at some point, <br>maybe it could be a good time to resurrect that work?<br><br>Yann<br><br><div class="gmail_quote">2008/10/13 Paul Kelly <span dir="ltr"><<a href="mailto:paul-grass@stjohnspoint.co.uk">paul-grass@stjohnspoint.co.uk</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">On Sun, 12 Oct 2008, Markus Neteler wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Any objections (the motivation is obvious)? I would also update<br>
</blockquote>
<br>
Hi Markus,<br>
Can you elaborate on the motivation? As it is I feel an obvious objection is<br>
that this implies there is no other way to import raster and vector data<br>
than through GDAL and OGR respectively - but I count 8 r.in.*, 14 r.out.*, 4<br>
v.in.* and 6 v.out.* modules in 7.x. So IMHO it is confusing.<br>
</blockquote>
<br>
Well, teaching GRASS over the year almost always brought up the<br>
newcomer question: "Where [censored] is the import module?".<br>
r.in.gdal or v.in.ogr is *not* obvious at all.<br>
</blockquote>
<br></div>
Thanks - surprisingly it wasn't actually obvious to me that the motive was newbie confusion! And yes I agree, good point - I also vaguely remember when starting GRASS being confused as to when r.in.gdal might be useful. And taken alone, r.import and r.export are very good names, easy to remember and also quick to type. I guess it's just the inconsistency that will then exist with r.in.* and r.out.* that I'm concerned about.<br>
<br>
If r.in.gdal was renamed to something like r.in.multi or r.in.various that would be one way of preserving the consistency. Renaming r.in.* to r.import.* and r.out.* to r.export.* at the same time as renaming r.in.gdal to r.import would be another possiblity for preserving consistency. Neither of those are ideal; I'm not seriously suggesting either of them.<br>
<br>
Is the idea of the proposal then to make new users see r.import as the standard import tool they should try first, and that r.in.* are legacy modules to look at if they have difficulty or special requirements? If so, I guess I'm generally in favour of it after all.<br>
<font color="#888888">
<br>
Paul</font><div><div></div><div class="Wj3C7c"><br>
_______________________________________________<br>
grass-dev mailing list<br>
<a href="mailto:grass-dev@lists.osgeo.org" target="_blank">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>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Yann Chemin<br>International Rice Research Institute<br>Office: <a href="http://www.irri.org/gis">http://www.irri.org/gis</a><br>Perso: <a href="http://www.freewebs.com/ychemin">http://www.freewebs.com/ychemin</a><br>
YiKingDo: <a href="http://yikingdo.unblog.fr/">http://yikingdo.unblog.fr/</a><br>
</div>