Re: [GRASS-dev] Migration to Discourse

GRASS GIS GRASS GIS developer
1

Moving to discourse replacing digested grass-dev is not a viable option for me. Such platforms raise the noise to signal ratio, so picking out information relevant for the R/GRASS interface will simply become much more time consuming, compared to scanning the daily digest. So I will not be accepting the invitation.

Should anyone involved in the R rgrass package and transitioning to discourse themselves be willing to take over maintaining the package now, I'd be grateful if you could express your willingness now.

Roger

--
Roger Bivand
Emeritus Professor
Norwegian School of Economics
Postboks 3490 Ytre Sandviken, 5045 Bergen, Norway
Roger.Bivand@nhh.no
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

2

Hello,

If you are looking for maintainers, I would be happy to support the R rgrass package. I’m the author of another “bridge” package (Rsagacmd) on CRAN, and I’ve contributed a few add-ons to GRASS, including the scikit-learn / raster add-on r.learn.ml2.

I have also been working on some R-GRASS integration but via reticulate so that the pygrass interface can be used under the hood - with the aim of being able to use common generics (particularly ‘predict’) that can work directly with GRASS RasterRow objects etc.

Steven

Alberta Geological Survey

1 Like
3

Hi @stevenpawley
If you can send your reply thru the mailing list so that Roger can see your reponse.

4

Right, there is a dedicated email thread for this:
https://lists.osgeo.org/pipermail/grass-dev/2024-October/096368.html

5

Right, thanks for that, just replied now.