<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<link href="chrome://translator/skin/floatingPanel.css"
type="text/css" rel="stylesheet">
</head>
<body text="#000099" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi,<br>
<br>
You can find a list of changes in option settings and names here:
<a class="moz-txt-link-freetext" href="http://trac.osgeo.org/grass/wiki/Grass7/NewFeatures#Renamedoptions">http://trac.osgeo.org/grass/wiki/Grass7/NewFeatures#Renamedoptions</a><br>
<br>
Cheers,<br>
<br>
Paulo<br>
<br>
<br>
<br>
On 08/29/2012 02:50 PM, Helmut Kudrnovsky wrote:<br>
</div>
<blockquote
cite="mid:trinity-83a508d3-4217-4c02-bd1b-144c9dbdc6c6-1346244648273@3capp-webde-bs22"
type="cite">
<div style="font-family: Verdana;font-size: 12.0px;">
<div>fyi a question regarding an "translation" (flags,parameter)
table between grass6x and grass7.<br>
<br>
Helmut<br>
<br>
<p>-------- Original-Nachricht --------<br>
Datum: Wed, 29 Aug 2012 14:35:37 +0200 (CEST)<br>
Von: Roger Bivand <br>
An: Helmut Kudrnovsky <br>
Betreff: Re: R + grass7<br>
<br>
</p>
On Wed, 29 Aug 2012, Helmut Kudrnovsky wrote:<br>
<br>
> Dear Roger,<br>
><br>
> I'm trying to improve the GRASS GIS-R-coupling on windows<br>
> (<a moz-do-not-send="true"
href="https://service.gmx.net/de/cgi/derefer?TYPE=3&DEST=http%3A%2F%2Ftrac.osgeo.org%2Fgrass%2Fticket%2F1149%29."
target="_blank">http://trac.osgeo.org/grass/ticket/1149).</a><br>
><br>
> May I ask you if spgrass6<br>
> (<a moz-do-not-send="true"
href="https://service.gmx.net/de/cgi/derefer?TYPE=3&DEST=http%3A%2F%2Fcran.at.r-project.org%2Fweb%2Fpackages%2Fspgrass6%2Findex.html%29"
target="_blank">http://cran.at.r-project.org/web/packages/spgrass6/index.html)</a>
is GRASS<br>
> GIS 7-aware.<br>
<br>
Yes, the description on:<br>
<br>
<a moz-do-not-send="true"
href="https://service.gmx.net/de/cgi/derefer?TYPE=3&DEST=http%3A%2F%2Fcran.r-project.org%2Fweb%2Fpackages%2Fspgrass6%2Findex.html"
target="_blank">http://cran.r-project.org/web/packages/spgrass6/index.html</a><br>
<br>
uses "6+" to signal that subsequent versions are intended to
work. Since <br>
the package only uses system(), it will work as long as <br>
--interface-description returns an XML file. Plenty of
examples and <br>
scripts stop working because GRASS 6 and 7 modules have
different flags <br>
and/or parameter names, but in principle only for that reason.
It's hard <br>
for me to check - it would be useful to have a translation
table for flag <br>
and parameter names by module where changes have occurred.<br>
<br>
Best wishes,<br>
<br>
Roger<br>
<br>
-- <br>
Roger Bivand<br>
Department of Economics, NHH Norwegian School of Economics,<br>
Helleveien 30, N-5045 Bergen, Norway.<br>
<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
grass-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:grass-user@lists.osgeo.org">grass-user@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/grass-user">http://lists.osgeo.org/mailman/listinfo/grass-user</a>
</pre>
</blockquote>
<br>
<div style="bottom: auto; left: 5px; right: auto; top: 66px;
display: none;" class="translator-theme-default"
id="translator-floating-panel">
<div title="Click to translate"
id="translator-floating-panel-button"></div>
</div>
</body>
</html>