Minor bug fixes:
Minor fix to only pass character vectors to ‘numeric_version’
Support for SpatVector and SpatVectorProxy proxy objects for vector spatial datasets.
tidy methods to summarize information about the SAGA-GIS libraries and tools within any library and return these as a tibble.
Function ‘saga_docs’ to browse the online documentation for each SAGA-GIS tool.
terrapackage as a raster backend.
search_tool function now returns a
tibble containing the tools that contain the matching term
along with additional metadata including the author of the tool, a
description and the tool’s parameters.
tidy S3 method from the
generics package has been extended with a tidy.saga_tool
method that summarizes a SAGA-GIS tool object’s parameters into a
tibble. This is designed for easy viewing of a tools options.
Because ‘Rsagacmd’ now supports multiple raster backends, the
‘raster’ package is no longer automatically attached when using
Rsagacmd. The raster/terra/stars objects resulting from geoprocessing
operations be still be loaded, but to apply additional functions to
these objects (e.g. plot) then the user needs to explicitly load the
desired backend, e.g.
library(stars) in their
The spinner is now turned off for geoprocessing operations because to avoid creating an annoying extra line in Rmarkdown notebooks, jupyter etc.
Rsagacmd now checks the file extensions of tools to ensure that
the correct file extension is used relative to the
vector_format. This ensures
that outputs of SAGA-GIS tools will be correctly loaded by R.
Rsagacmd saga_search should correctly recognize the location of the saga_cmd binary on macOS that is included within the QGIS.app bundle, if installed from official sources.
Rsagacmd 0.1.0 includes many behind-the-scenes changes that organize the the internal representation of SAGA-GIS tools and parameter settings using a similar approach as used by the saga_api.
Most notably, this release provides support for the use of different raster backend, including the existing ‘raster’ package, as well as the newer ‘terra’ package. Configuration options to use different spatial formats as data is passed from R to SAGA (and back) is also provided. For rasters, datasets that are saved from R memory to disk for access by the saga command line (and vice versa) can be in ‘SAGA’ format (the default), ‘SAGA Compressed’, or ‘GeoTIFF’, which can potentially save disk space when transferring large volumes of data. Vector formats now include ‘ESRI Shapefile’ (the default), ‘Geopackage’ and ‘GeoJSON’. The use of the geopackage format eliminates problems when transferring spatial datasets which have attribute names that are >10 characters in length.