I'm getting this error while trying to install spgrass6 on a dual G5/2ghz w
4gb ram, and macos x 10.4.7:
> rS <- "http://r-spatial.sourceforge.net/R";
> install.packages("spgrass6", repos=rS, dependencies=TRUE)
*** caught segfault ***
address 0x5f4d4550, cause 'memory not mapped'
Traceback:
1:
I am going through some similar problems getting rgdal running on macos x:
sudo ./usr/local/bin/R64 CMD INSTALL
--configure-args='--with-proj-include=/usr/local/include
--with-proj-lib=/usr/local/lib' rgdal
...
checking proj_api.h usability... yes
checking proj_api.h presence... yes
checking for
Jonathan,
This is what rgdal was designed to do. Here's an example,
ds1 <- GDAL.open("input.tif")
driver <- new('GDALDriver', 'GTiff')
ds2 <- new('GDALTransientDataset', driver, nrow(ds1), ncol(ds1), type
= "Float64")
for (row in nrow(ds1)) {
x <- getRasterData(ds1, offset = c(row - 1, 0), reg
I was wondering if I could get some brief feedback on exactly what are the
capabilities of the sp and spgrass6 -- say I'd like to use R to calculate
and NDVI image (I know GRASS's mapcalc can do this fine, but I'm thinking of
some more complicated analyses that aren't easily performed in R and I
fi
Thanks Roger, I've been using this to bind rows
together, where I don't necessarily have the exact
same columns in each table. It seems to work fine for
that, so I hadn't noticed that it didn't actually
merge floating points. However, it looks like merging
will work, if you can afford to round off
I found the type size defs in Rinternals.h. They are
R_XDR_INTEGER_SIZE and R_XDR_DOUBLE_SIZE. I've added a check in rgdal
to ensure that type sizes match up.
THK
--
Timothy H. Keitt
http://www.keittlab.org/
___
R-sig-Geo mailing list
R-sig-Geo@stat.m
On Fri, 8 Sep 2006, Mikkel Grum wrote:
> merge(Table1, Table2,
>by = intersect(c("XCOORD", "YCOORD"),
>c("XCOORD", "YCOORD")), all = TRUE)
>
> It might not handle the amount of data you have, but,
> if your tables are normal dataframes, it would do the
> job with a smaller dataset. It d
On Fri, 8 Sep 2006, Scott W Mitchell wrote:
>
> On 8 Sep 2006, at 15:27, Roger Bivand wrote:
>
> > On Fri, 8 Sep 2006, Tim Keitt wrote:
> >
> >> One possibility is that the size of the GDAL data type is not the
> >> same
> >> as the size of the R data type. This will definitely cause
> >> pro
