From f9870d0da3615e68719f420c92f80a536b200564 Mon Sep 17 00:00:00 2001
From: florisvdh
qgis_configure(use_cached_data = TRUE)
-#> Checking configuration in cache file (/home/runner/.cache/R-qgisprocess/cache-0.3.0.9000.rds)
+#> Checking configuration in cache file (/home/runner/.cache/R-qgisprocess/cache-0.3.0.9001.rds)
#> Checking cached QGIS version with version reported by 'qgis_process' ...
#> QGIS versions match! (3.36.3-Maidenhead)
#> Checking cached QGIS plugins (and state) with those reported by 'qgis_process' ...
-#> QGIS plugins match! (1 processing provider plugin(s) enabled)
+#> QGIS plugins match! (0 processing provider plugin(s) enabled)
#>
-#> >>> Run `qgis_enable_plugins()` to enable 2 disabled plugins and access
-#> their algorithms: grassprovider, processing_saga_nextgen
+#> >>> Run `qgis_enable_plugins()` to enable 3 disabled plugins and access
+#> their algorithms: grassprovider, processing,
+#> processing_saga_nextgen
#>
-#> Restoring configuration from '/home/runner/.cache/R-qgisprocess/cache-0.3.0.9000.rds'
+#> Restoring configuration from '/home/runner/.cache/R-qgisprocess/cache-0.3.0.9001.rds'
#> QGIS version: 3.36.3-Maidenhead
#> Using 'qgis_process' in the system PATH.
#> >>> If you need another installed QGIS instance, run `qgis_configure()`;
#> see `?qgis_configure` if you need to preset the path of 'qgis_process'.
#> Using JSON for output serialization.
#> Using JSON for input serialization.
-#> 1 out of 3 available processing provider plugins are enabled.
+#> 0 out of 3 available processing provider plugins are enabled.
#> Having access to 362 algorithms from 4 QGIS processing providers.
#> Use qgis_algorithms(), qgis_providers(), qgis_plugins(), qgis_path() and
#> qgis_version() to inspect the cache environment.
Since we will use GRASS GIS and SAGA later on, you must have GRASS GIS and SAGA version > 7 installed on your system. You also need to @@ -359,7 +361,7 @@
To read in the QGIS output and visualize it, we can run:
library("sf")
@@ -452,15 +454,15 @@ Second exampleinfo
#> <Result of `qgis_run_algorithm("grass:r.slope.aspect", ...)`>
#> List of 9
-#> $ aspect : 'qgis_outputRaster' chr "/tmp/RtmpsZv5Hc/file2eb14c815d2a/file2eb1245e9dd8.tif"
-#> $ dx : 'qgis_outputRaster' chr "/tmp/RtmpsZv5Hc/file2eb14c815d2a/file2eb1566a96b7.tif"
-#> $ dxx : 'qgis_outputRaster' chr "/tmp/RtmpsZv5Hc/file2eb14c815d2a/file2eb1140454fa.tif"
-#> $ dxy : 'qgis_outputRaster' chr "/tmp/RtmpsZv5Hc/file2eb14c815d2a/file2eb11c2e01ca.tif"
-#> $ dy : 'qgis_outputRaster' chr "/tmp/RtmpsZv5Hc/file2eb14c815d2a/file2eb120be0840.tif"
-#> $ dyy : 'qgis_outputRaster' chr "/tmp/RtmpsZv5Hc/file2eb14c815d2a/file2eb14d2531dd.tif"
-#> $ pcurvature: 'qgis_outputRaster' chr "/tmp/RtmpsZv5Hc/file2eb14c815d2a/file2eb17c97489b.tif"
-#> $ slope : 'qgis_outputRaster' chr "/tmp/RtmpsZv5Hc/file2eb14c815d2a/file2eb12051f736.tif"
-#> $ tcurvature: 'qgis_outputRaster' chr "/tmp/RtmpsZv5Hc/file2eb14c815d2a/file2eb171b034b8.tif"
Combine these output rasters as a multi-layered
SpatRaster
object and plot it:
@@ -529,7 +531,7 @@Second example#> z_range: zmin: 0 zmax: 0 #> Projected CRS: WGS 84 / UTM zone 17S #> # A tibble: 100 × 6 -#> id spri file2eb1245e9dd8 file2eb12051f736 file2eb171b034b8 +#> id spri file2ebb6a272366 file2ebb78c91bb7 file2ebb45e24439 #> <int> <int> <dbl> <dbl> <dbl> #> 1 1 4 251. 6.80 0.0000292 #> 2 2 4 79.7 4.60 -0.00206 @@ -567,7 +569,7 @@
Piping #> Using `OUTPUT = qgis_tmp_vector()` #> <Result of `qgis_run_algorithm("native:buffer", ...)`> #> List of 1 -#> $ OUTPUT: 'qgis_outputVector' chr "/tmp/RtmpsZv5Hc/file2eb14c815d2a/file2eb17cd6a796.gpkg"
If .data
is a qgis_result
object,
qgis_run_algorithm_p()
automatically tries to select an
element named OUTPUT
. However, if the output has another
@@ -609,10 +611,10 @@
When piping, CRAN release: 2024-02-06qgis_run_algorithm_p()
automatically cleans
up after you by deleting intermediate results. This avoids cluttering
your system when running geoalgorithms on large spatial data files. To
diff --git a/authors.html b/authors.html
index 25daa7d5..ed263278 100644
--- a/authors.html
+++ b/authors.html
@@ -10,7 +10,7 @@
qgisprocess
- 0.3.0.9000
+ 0.3.0.9001
qgis_process
backend by automatically implementing --skip-loading-plugins
where possible (#201). This benefits package startup time and the timing of qgis_run_algorithm()
, qgis_show_help()
, and several other functions. This feature needs QGIS >= 3.36.qgis_search_algorithms()
.grass
instead of grass7
.qgisprocess 0.3.0
Examples#> If you changed plugin availability or status in the QGIS GUI since you loaded the
#> qgisprocess package, then you must run `qgis_configure()` or reload the package
#> to capture these changes.
-#> 1 out of 3 available processing provider plugins are enabled.
+#> 0 out of 3 available processing provider plugins are enabled.
#> # A tibble: 3 × 2
#> name enabled
#> <chr> <lgl>
#> 1 grassprovider FALSE
-#> 2 processing TRUE
+#> 2 processing FALSE
#> 3 processing_saga_nextgen FALSE
qgis_plugins(which = "disabled")
-#> # A tibble: 2 × 2
+#> # A tibble: 3 × 2
#> name enabled
#> <chr> <lgl>
#> 1 grassprovider FALSE
-#> 2 processing_saga_nextgen FALSE
+#> 2 processing FALSE
+#> 3 processing_saga_nextgen FALSE