[GRASS-dev] Maintainer for rgrass needed by end 2024

[Steven Pawley]

Hi Roger,

Great to hear from you, I’ll take a look at the issue. I’ll also look at roxygen2 in a separate request. We predominantly work with GRASS temporary sessions/projects - especially for processing large grids, because many other GIS software/libraries use in-memory processing.

Kind regards,

Steven




> On Oct 4, 2024, at 5:22 AM, Roger Bivand <Roger.Bivand at nhh.no> wrote:
> 
> Hi Steven,
> 
> Thanks for responding! Could I suggest following up at https://github.com/rsbivand/rgrass/issues/96 ? This also of course is open to any others interested or concerned. rgrass and Rsagacmd overlap a little, but usage of rgrass has the possibility to spin up a temporary location (now project?), and to run GRASS commands constructed through the --interface-description argument, which has now been migrated from XML to xml2. rgrass has also not been roxygenised, as it began well before such tools. All these are things that can be cleared up, probably with the help of others pinged in the github issue I just raised, and others wishing to contribute.
> 
> Best wishes,
> 
> Roger
> 
> --
> Roger Bivand
> Emeritus Professor
> Norwegian School of Economics
> Postboks 3490 Ytre Sandviken, 5045 Bergen, Norway
> Roger.Bivand at nhh.no
> 
> ________________________________________
> From: Steven Pawley <dr.stevenpawley at gmail.com>
> Sent: 04 October 2024 02:11
> To: Roger Bivand
> Cc: grass-dev at lists.osgeo.org; grass-stats at lists.osgeo.org
> Subject: Re: [GRASS-dev] Maintainer for rgrass needed by end 2024
> 
> [You don't often get email from dr.stevenpawley at gmail.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
> 
> Hi Roger,
> 
> 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've also been working on some R-GRASS integration but bringing in reticulate so that the pygrass interface can be used from R, with the aim of being able to use common generics (particularly ‘predict’) that can work directly with GRASS RasterRow objects etc.
> 
> Irrespectively, happy to take a look at some of the open issues over the next few days.
> 
> Kind regards,
> 
> Steven
> 
> Alberta Geological Survey
> 
>> On Oct 3, 2024, at 5:21 AM, Roger Bivand via grass-dev <grass-dev at lists.osgeo.org> wrote:
>> 
>> In connection with the transfer of the grass-dev list to Discourse, which I am not prepared to follow as it will absorb much more time than scanning the digested list headers, I will give up maintaining the R-GRASS interface package at the end of 2024.
>> 
>> The package lives in https://github.com/rsbivand/rgrass and the repo can be moved to the preferred location of the new maintainer, and the maintainer change notified to CRAN without difficulty.
>> 
>> The arrival of Discourse precipitates a change that was started before a workshop at FOSS4G in 2022 https://rsbivand.github.io/foss4g_2022/modernizing_220822.html, and several GRASS users/developers then contributed to the workshop, and have helped improve the package over many years.
>> 
>> Before a hand-over, this group of contributors can go through issues not yet formally closed but mostly settled, to make sure that the new maintainer ramps up smoothly.
>> 
>> Best wishes,
>> 
>> Roger
>> 
>> --
>> Roger Bivand
>> Emeritus Professor
>> Norwegian School of Economics
>> Postboks 3490 Ytre Sandviken, 5045 Bergen, Norway
>> Roger.Bivand at nhh.no
>> _______________________________________________
>> grass-dev mailing list
>> grass-dev at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/grass-dev
>