From f049edf01b3f58eda108d590bfa7e2ed4ebf710c Mon Sep 17 00:00:00 2001 From: rhijmans Date: Sat, 28 Dec 2024 15:38:07 -0800 Subject: [PATCH] r --- man/merge.Rd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/man/merge.Rd b/man/merge.Rd index 1312da5c6..0baff89c3 100644 --- a/man/merge.Rd +++ b/man/merge.Rd @@ -32,7 +32,7 @@ There is also a method for merging SpatVector with a data.frame; that is, to joi \item{...}{if \code{x} is a SpatRaster: additional objects of the same class as \code{x}. If \code{x} is a SpatRasterCollection: options for writing files as in \code{\link{writeRaster}}. If \code{x} is a SpatVector, the same arguments as in \code{\link[base]{merge}}} \item{first}{logical. If \code{TRUE}, in areas where rasters overlap, the first value is used. Otherwise the last value is used} \item{na.rm}{logical. If \code{TRUE} values that are \code{NA} are ignored} - \item{algo}{integer. You can use 1, 2, or 3 to pick a merge algorithm. 1 appears to be fastest but file compression may be poor. 2 and 3 are slower but have better compression. 3 appears to have the best compression} + \item{algo}{integer. You can use 1, 2, or 3 to pick a merge algorithm. 1 is generally faster than 2, but file compression may be poor. 2 is slower but has better compression. In algo 3 a \code{\link{vrt)) is used and returned if no filename is specified; otherwise its performance is like that of algo 2} \item{filename}{character. Output filename} \item{overwrite}{logical. If \code{TRUE}, \code{filename} is overwritten} \item{wopt}{list with named options for writing files as in \code{\link{writeRaster}}}