However, a RasterStack is more flexible as a single object can refer to layers that have values stored on disk as well as in memory. A RasterBrick should process quicker than a RasterStack (irrespective if values are on disk or in memory). This has implications for processing speed and flexibility. An object of class RasterBrick can refer to only a single (multi-layer) data file, whereas each layer in a RasterStack can refer to another file (or another band in a multi-band file). Organizing RasterLayer objects in a RasterStack can be practical when dealing with multiple layers for example to summarize their values (see calc) or in spatial modeling (see predict).Īn object of class RasterBrick can also contain multiple layers of raster data, but they are more tightly related. Or it can not have any associated values at all.Ī RasterStack represents a collection of RasterLayer objects with the same extent and resolution.
The object can point to a file on disk that holds the values of the raster cells, or hold these values in memory.
They all inherit from BasicRaster and can contain values for the raster cells.Īn object of the RasterLayer class refers to a single layer (variable) of raster data. The main user level classes are RasterLayer, RasterStack and RasterBrick. The 'raster' package defines a number of "S4 classes" to manipulate such data.
Raster-class: Raster* classes DescriptionĪ raster is a database organized as a rectangular grid that is sub-divided into rectangular cells of equal area (in terms of the units of the coordinate reference system).
0 kommentar(er)
