7
Reprojecting rasters is usually a bad thing to do. It involves a non-reversible transformation from one grid system to another grid system that can have a non-linear relationship to the first. Hence the value in a cell of the new system can end up being some average of whichever grid cells in the source raster it overlapped.
If you have a raster and points ...
4
Take a look at some of the identity functions in rgeos such as gTouches, gIntersects, gContains, gRelate, gWithin, ect...
At their most basic, these functions can return a Boolean that will allow you to perform the equivalent of a spatial select. To control output, take a close look at the function(s) arguments and experiment a bit with outputs from ...
2
Lambert equal-area projection
laea_centered <- "+proj=laea +lat_0=-70.30744 +lon_0=43.15268"
call me crazy, but don't you have the lat and long switched around?
2
In the best world the memory allocated to load a las file should be almost equal to the size of the file. But this is not possible especially in R. This is explained in this vignette.
It is important to note that R only enables manipulation of 32-bit integers and 64-bit decimal numbers. But the las specification states, for example, that the intensity is ...
1
R is reporting the size of the object in memory, not the size of the file.
If you run the example from readLAS you'll get las which is:
> las
class : LAS (LASF v1.2)
point format : 1
memory : 5.6 Mb
this size depends on which parts of the file you read in (via the select and other options) and how much the LAS file is compressed.
Most ...
1
This was a bug fixed in version 2.1.4. In short in R when you subset a matrix you get a matrix (that makes sense) but when you subset a single row you get a vector instead of a 1 x n matrix. R's behavior is inconsistent. In rare cases you may have a single remaining triangle in pitfree(). This is why you got an internal error not a matrix. This case is now ...
1
gstat can do spatial-temporal kriging, as explained here: https://www.r-bloggers.com/spatio-temporal-kriging-in-r/ . Time is just a third dimension, and you could use "elevation" data instead of time, in the same algorithms, reaching the desired output.
As an alternative, although not completely native in R, Saga Gis 7.4 just implemented full 3d kriging. ...
Only top voted, non community-wiki answers of a minimum length are eligible
