Dear Markus,
Good to hear you are well! Great that RC1 is ready!
Yes, I guess it would be sensible to condition on version in these cases,
so first add comments for hard-coded flags and options (there are also
some changes in type, I think). In addition, bin_out_win in parseGRASS()
needs updating and/or conditioning on version, and the logic for handling
where Python scripts are found should be looked at.
You do not (yet) have commit rights on:
https://r-forge.r-project.org/projects/rspatial/ where spgrass6 lives.
Two alignments: should GRASS5 support (GRASS packages) be dropped (yes)?
Should spgrass6 be forked into (new) spgrass which supports >= 7, and
leave spgrass6 for 6.*? If fork, is SVN on R-Forge OK?
Best wishes,
Roger
On Thu, 15 Jan 2015, Markus Neteler wrote:
Dear Roger,
I hope you are well (like me).
To you have any plans to update spgrass6 to spgrass7? While the former
works ok with raster maps, a few minor tweaks are needed to read in
vector maps.
The reason is the parameter standardization effort done in the past
months. We renamed obscure parameters to a set of reasonable standard
names:
http://trac.osgeo.org/grass/wiki/Grass7/NewFeatures#Optionschanges
It is essentially a small search/replace job I can help with.
What do you think?
Best,
Markus
PS: It would also solve http://trac.osgeo.org/osgeo/ticket/1444
--
Roger Bivand
Department of Economics, Norwegian School of Economics,
Helleveien 30, N-5045 Bergen, Norway.
voice: +47 55 95 93 55; fax +47 55 95 91 00
e-mail: roger.biv...@nhh.no
_______________________________________________
grass-stats mailing list
grass-stats@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-stats
