similar to: R spatial projects mailing list and web site

Release of revised version of R/GRASS GIS raster and sites data interface. The latest version of the R contributed package "GRASS", release 0.1-6, may be downloaded from CRAN (cran.r-project.org) - contributed packaged section, "Devel" directory, file: GRASS_0.1-6.tar.gz. It may also be downloaded from ftp://reclus.nhh.no/pub/R/GRASS_0.1-6.tar.gz. This version is intended for

Thanks to Roger Bivand, my problem was solved. binutils 2.14 was updatet to binutils 2.15, as indicated under. Geir Helge Systad Norwegian Institute for Nature Research Arctic Ecology, Polarmilj??senteret, N-9296 Troms??, Norway Adress aug-04 to feb-05: Albert Pettersonsvei 13, N-5750 Odda fax +47 85 03 82 14 phone +47 53 64 24 94 mobil +47 91 63 70 55 E-mail: geir.systad at nina.no

Howdy All, I am looking for some good tutorials (books, websites, whatever) for calculating/testing for Spatial Autocorrelation using R. Specifically, I am wanting to test for autocorrelation of a number of variables measured at a set of discrete locations. Up to this point I have been exploring the "spdep" package and I can get "moran.test" to work, but I am concerned that

The legacy R spatial infrastructure packages maptools, rgdal and rgeos will be archived by CRAN on Monday, October 16, 2023; rgrass7 has already been replaced by rgrass and will be archived with the retiring packages. The choice of date matches the previously announced archiving during October 2023, and the specific date matches the release schedule of Bioconductor 3.18 (some Bioconductor

The legacy R spatial infrastructure packages maptools, rgdal and rgeos will be archived by CRAN on Monday, October 16, 2023; rgrass7 has already been replaced by rgrass and will be archived with the retiring packages. The choice of date matches the previously announced archiving during October 2023, and the specific date matches the release schedule of Bioconductor 3.18 (some Bioconductor

The third report on the R-spatial evolution project has been published. https://r-spatial.org/r/2023/04/10/evolution3.html It links back to earlier blogs and presentations, and focuses on work that maintainers of R packages and workflows using rgdal, rgeos and maptools need to put in train now before the packages are archived on CRAN. The first changes will occur in June 2023, and the

The third report on the R-spatial evolution project has been published. https://r-spatial.org/r/2023/04/10/evolution3.html It links back to earlier blogs and presentations, and focuses on work that maintainers of R packages and workflows using rgdal, rgeos and maptools need to put in train now before the packages are archived on CRAN. The first changes will occur in June 2023, and the

A new version of the sp package, 2.0-0, has been published on CRAN. This new version defaults to using the sf package rather than the rgdal package, and deprecates use of the rgeos package. These changes are described in https://r-spatial.org/r/2023/05/15/evolution4.html, and lead up to the planned archiving of the retiring packages: maptools, rgdal and rgeos in October 2023. This version issues

A new version of the sp package, 2.0-0, has been published on CRAN. This new version defaults to using the sf package rather than the rgdal package, and deprecates use of the rgeos package. These changes are described in https://r-spatial.org/r/2023/05/15/evolution4.html, and lead up to the planned archiving of the retiring packages: maptools, rgdal and rgeos in October 2023. This version issues

Very helpful. One (possible) correction inline below... On Thu, 30 Mar 2006, Ray Brownrigg wrote: > > From: nhy303 at abdn.ac.uk > > > > I have plotted a map of the Barents Sea and surrounding coastline using: > > > > map('worldHires',ylim=c(50,85),xlim=c(5,65),fill=T,resolution=0) > > map.axes() > > map.scale(x=30,metric=T) > > > >

Revised versions of maptools, a package for reading geographical data from shapefiles, and sp, a package with classes and methods for spatial data handling, have been released on CRAN. They are maptools release 0.5-1 and sp release 0.8-1. The maptools package now depends on sp (>= 0.8), so that users of maptools will need both to update the package itself, and to install the sp package. All

Revised versions of maptools, a package for reading geographical data from shapefiles, and sp, a package with classes and methods for spatial data handling, have been released on CRAN. They are maptools release 0.5-1 and sp release 0.8-1. The maptools package now depends on sp (>= 0.8), so that users of maptools will need both to update the package itself, and to install the sp package. All

This behaviour is confirmed for RH70, RH62, Debian 2.2 on 3 different Pentium-class i386. I've checked back and package ann_0.2-2 works on 1.1.1, but fails with seg. faults on 1.2.0 (ann_0.2-2.pre3.tar.gz to accommodate the change in Makeconf) and subsequent (1.2.0 checked today on RH62 with gcc 2.95.3 19991030 (prerelease)). It is most likely that 1.1.1 was too forgiving, and that better

It looks as though the problem isn't in R - I provoked a SIGSEGV under R 1.1.1 on RH62: > for (i in 1:100) an1 <- ann(cbind(runif(1000), runif(1000)), k = 4) > for (i in 1:100) an1 <- ann(cbind(runif(1001), runif(1001)), k = 4) Program received signal SIGSEGV, Segmentation fault. 0x40111109 in chunk_free (ar_ptr=0x401a5d40, p=0x8849a30) at malloc.c:3111 3111 malloc.c: No such

On Sat, 10 Nov 2018, Andreas Storvik Strauman wrote: > Hello! I'm confused as to what the actual problem with includeRnw is? Is > the problem that it relies on R-knitr? Before it would be withdrawn, may > I be given an opportunity to fix said problem? Yes, the problem is that it expesses an external dependence on anything outside texlive. On packaging systems (for me Fedora),

In revising the splancs package, I use R CMD check. After a number of changes to various files in the directory tree, R CMD check fails at the * checking for undocumented objects ... ERROR stage as shown below. But running undoc() in R (pointed at the Rcheck directory, not on the older version) doesn't show the same error, and grep on the Rcheck R code finds the function. I ran undoc() under

Hello! I'm confused as to what the actual problem with includeRnw is? Is the problem that it relies on R-knitr? Before it would be withdrawn, may I be given an opportunity to fix said problem? includeRnw only invokes the already existing R installation, and should not affect any other global settings or affect the installation in any way. If this is the case, it's a bug and I'd

I contacted John Fox about this first, because parts of the file are attributed to him. He says that he didn't write rstandard.glm(), and suggests asking r-devel. As it stands, rstandard.glm() has summary(model)$dispersion outside the sqrt(), while in rstandard.lm(), the sd is already sqrt()ed. This seems to follow stdres() in VR/MASS/R/stdres.R. Of course for the c("poisson",

I have been running into difficulties with dispatching on an S4 class defined in the SparseM package, when the method calls are inside a function passed as the f= argument to optimize() in functions in the spdep package. The S4 methods are typically defined as: setMethod("det","matrix.csr", function(x, ...) det(chol(x))^2) that is within setMethod() rather than by name before

On Sat, 10 Nov 2018 at 15:17, Roger Bivand <Roger.Bivand at nhh.no> wrote: > > On upgrading my F28 to F29, I've found that R-core and a number of R > packages: > > R-evaluate R-glue R-highr R-knitr R-magrittr R-markdown R-mime R-stringi > R-stringr R-yaml > > are installed, although I only ever install R from source and always keep > my Rs locally. So I