diff --git a/.gitignore b/.gitignore index a00aff1..8be6b0a 100644 --- a/.gitignore +++ b/.gitignore @@ -6,4 +6,4 @@ src/*.o src/*.so src/*.dll - +junk diff --git a/docs/articles/link2GI1.html b/docs/articles/link2GI1.html index 9990633..f3a91c1 100644 --- a/docs/articles/link2GI1.html +++ b/docs/articles/link2GI1.html @@ -100,7 +100,7 @@
vignettes/link2GI1.Rmd
link2GI1.Rmd
vignettes/link2GI2.Rmd
link2GI2.Rmd
In the past it was quite tedious to link the correct
SAGA GIS
version. Since version 1.x.x of RSAGA
-things are much better. The new RSAGA::rsaga.env()
function
-is to get the first RSAGA
version in the search path. For
-using RSAGA
with link2GI
it is strongly
-recommended to call RSAGA.env()
with the preferred path as
-returned by a findSAGA()
call. It is also possible to pass
-the version number as shown below. Storing the result in appropriate
-variables will even allow you to easily switch between different
-SAGA GIS
installations.
-saga1<-link2GI::linkSAGA(ver_select = 1)
-saga1
-sagaEnv1<- RSAGA::rsaga.env(path = saga1$sagaPath)
RSAGA::rsaga.env()
function
+is to get the first RSAGA
version in the search path. It is
+also possible to pass the version number as shown below. Storing the
+result in appropriate variables will even allow you to easily switch
+between different SAGA GIS
installations.
sf
vector data
objects.
Starting with sp
.
+# get meuse data as sp object and link it temporary to GRASS require(link2GI) require(sp) @@ -218,8 +211,8 @@
Standard full search usage# get data data(meuse) # add georeference -coordinates(meuse) <- ~x+y -proj4string(meuse) <-CRS("+init=epsg:28992") +coordinates(meuse) <- ~x+y +proj4string(meuse) <-CRS("+init=epsg:28992") # Automatic search and find of GRASS binaries # using the meuse sp data object for spatial referencing @@ -228,7 +221,7 @@
Standard full search usage linkGRASS(meuse)
Now do the same with
-sf
based data.diff --git a/docs/reference/loadLibraries.html b/docs/reference/loadLibraries.html index a31a711..e31b557 100644 --- a/docs/reference/loadLibraries.html +++ b/docs/reference/loadLibraries.html @@ -1,5 +1,5 @@ -+require(link2GI) require(sf) @@ -244,7 +237,7 @@
Standard full search usageThe second most common situation is to use an existing
GRASS
site and project, either with existing data sets or manually provided parameters. -diff --git a/docs/reference/loadEnvi.html b/docs/reference/loadEnvi.html index d28b596..06a34e8 100644 --- a/docs/reference/loadEnvi.html +++ b/docs/reference/loadEnvi.html @@ -1,5 +1,5 @@ -+@@ -282,21 +275,21 @@library(link2GI) require(sf) @@ -264,12 +257,12 @@
Standard full search usage # setting up GRASS manually with spatial parameters of the nc data - proj4_string <- as.character(sp::CRS("+init=epsg:28992")) + proj4_string <- as.character(sp::CRS("+init=epsg:28992")) linkGRASS(spatial_params = c(178605,329714,181390,333611,proj4_string)) # creating a GRASS gisdbase manually with spatial parameters of the nc data # additionally using a peramanent directory "root_folder" and the location "nc_spatial_params " - proj4_string <- as.character(sp::CRS("+init=epsg:4267")) + proj4_string <- as.character(sp::CRS("+init=epsg:4267")) linkGRASS(gisdbase = root_folder, location = "nc_spatial_params", spatial_params = c(-84.32385, 33.88199,-75.45698,36.58965,proj4_string))
Typical for specified search path to narrow down the search. To search for
GRASS
installations in the home directory, you can use the following command. -+# Link the GRASS installation and define the search location linkGRASS(nc, search_path = "~")
If you already did a full search and kow your installation fo example using the command
- +findGRASS
you can use the result directly for linking.Manual version selection @@ -305,7 +298,7 @@
Manual version selectionGRASS installation and use the meuse
sf
object for spatial referencing -+linkGRASS(nc, ver_select = TRUE)
@@ -315,7 +308,7 @@@@ -173,7 +173,7 @@Creating a permanent gisdbase fold structure) in “~/temp3” with the default mapset “PERMANENT”” and the location “project1”. Use the
sf
object for all spatial attributes. -diff --git a/docs/reference/linkSAGA.html b/docs/reference/linkSAGA.html index bdc913f..e982e3b 100644 --- a/docs/reference/linkSAGA.html +++ b/docs/reference/linkSAGA.html @@ -1,5 +1,5 @@ -+@@ -327,7 +320,7 @@linkGRASS(x = nc, gisdbase = "~/temp3", location = "project1")
Using a permanent gisdbase foldersf object parameter for all spatial attributes. -
@@ -336,7 +329,7 @@+linkGRASS(gisdbase = "~/temp3", location = "project1", gisdbase_exist = TRUE)
Manual Setup of the spatial attr
Setting up
-GRASS
manually with spatial parameters of the meuse data+diff --git a/docs/pkgdown.yml b/docs/pkgdown.yml index 0d34002..c76a1e1 100644 --- a/docs/pkgdown.yml +++ b/docs/pkgdown.yml @@ -9,7 +9,7 @@ articles: link2GI5: link2GI5.html link2GI6: link2GI6.html link2GI7: link2GI7.html -last_built: 2024-05-06T14:38Z +last_built: 2024-05-07T14:24Z urls: reference: https://r-spatial.github.io/link2GI/reference article: https://r-spatial.github.io/link2GI/articles diff --git a/docs/reference/linkGRASS.html b/docs/reference/linkGRASS.html index 919b9db..97ff670 100644 --- a/docs/reference/linkGRASS.html +++ b/docs/reference/linkGRASS.html @@ -177,7 +177,7 @@linkGRASS(spatial_params = c(178605,329714,181390,333611, "+proj=sterea +lat_0=52.15616055555555 +lon_0=5.38763888888889 +k=0.9999079 @@ -355,7 +348,7 @@
A typical use case for and function syntax dumps and generate a command list that can be easily modified with the necessary arguments.
Usually you have to get the module list first:
-diff --git a/docs/articles/link2GI4.html b/docs/articles/link2GI4.html index a283d49..86e63a4 100644 --- a/docs/articles/link2GI4.html +++ b/docs/articles/link2GI4.html @@ -100,7 +100,7 @@+# link to the installed OTB otblink<-link2GI::linkOTB() @@ -364,7 +357,7 @@
A typical use case for algo<-parseOTBAlgorithms(gili = otblink)
Based on the modules of the current version of `OTB’, you can then select the module(s) you want to use.
-+## for the example we use the edge detection, algoKeyword<- "EdgeExtraction" @@ -377,7 +370,7 @@
A typical use case for Nevertheless, it will give you a valid list of all
OTB
API calls that you can easily manipulate to suit your needs. The following working example will give you an idea of how to use it. -++rgrass::execGRASS('v.info', map = "Zensus_Bevoelkerung_100m_")require(link2GI) require(terra) require(listviewer) @@ -394,7 +387,7 @@
A typical use case for cmd<-parseOTBFunction(algo = algoKeyword, gili = otblink) ## get help using the convenient listviewer -listviewer::jsonedit(cmd$help) +listviewer::jsonedit(cmd$help) ## define the mandantory arguments all other will be default cmd$input <- fn diff --git a/docs/articles/link2GI3.html b/docs/articles/link2GI3.html index d8a8b03..90d2e8c 100644 --- a/docs/articles/link2GI3.html +++ b/docs/articles/link2GI3.html @@ -100,7 +100,7 @@
linkGRASS real world data usecase
Chris Reudenbach
-2024-05-06
+2024-05-07
Source:vignettes/link2GI3.Rmd
@@ -265,7 +265,7 @@link2GI3.Rmd
Setting up a GRASS project ) # check imported data set -rgrass::execGRASS('v.info', map = "Zensus_Bevoelkerung_100m_")
OTB Wrapper
Chris Reudenbach
-2024-05-06
+2024-05-07
Source:vignettes/link2GI4.Rmd
@@ -156,7 +156,7 @@link2GI4.Rmd
A typical use case for cmd<-parseOTBFunction(algo = algoKeyword, gili = otblink) ## get help using the convenient listviewer -listviewer::jsonedit(cmd$help) +listviewer::jsonedit(cmd$help) ## define the mandantory arguments all other will be default cmd$input_in <- fn diff --git a/docs/articles/link2GI5.html b/docs/articles/link2GI5.html index 73d9722..4ebfdb4 100644 --- a/docs/articles/link2GI5.html +++ b/docs/articles/link2GI5.html @@ -100,7 +100,7 @@
GEOSTAT 2018 Examples
Chris Reudenbach
-2024-05-06
+2024-05-07
Source:vignettes/link2GI5.Rmd
diff --git a/docs/articles/link2GI6.html b/docs/articles/link2GI6.html index 74bc71e..99559a9 100644 --- a/docs/articles/link2GI6.html +++ b/docs/articles/link2GI6.html @@ -101,7 +101,7 @@link2GI5.Rmd
Installation guide for link2GI related
Chris Reudenbach
-2024-05-06
+2024-05-07
Source:vignettes/link2GI6.Rmd
diff --git a/docs/articles/link2GI7.html b/docs/articles/link2GI7.html index 1287510..b29a559 100644 --- a/docs/articles/link2GI7.html +++ b/docs/articles/link2GI7.html @@ -100,7 +100,7 @@link2GI6.Rmd
Reproducible projects
Chris Reudenbach
-2024-05-06
+2024-05-07
Source:vignettes/link2GI7.Rmd
diff --git a/docs/authors.html b/docs/authors.html index 8bd2aa5..0ae9421 100644 --- a/docs/authors.html +++ b/docs/authors.html @@ -95,14 +95,13 @@link2GI7.Rmd
Citation
Reudenbach C (2024). link2GI: Linking Geographic Information Systems, Remote Sensing and Other Command Line Tools. -R package version 0.6-1, https://r-spatial.github.io/link2GI/, https://github.com/r-spatial/link2GI/. +https://github.com/r-spatial/link2GI/, https://r-spatial.github.io/link2GI/.
@Manual{, title = {link2GI: Linking Geographic Information Systems, Remote Sensing and Other Command Line Tools}, author = {Chris Reudenbach}, year = {2024}, - note = {R package version 0.6-1, https://r-spatial.github.io/link2GI/}, - url = {https://github.com/r-spatial/link2GI/}, + note = {https://github.com/r-spatial/link2GI/, https://r-spatial.github.io/link2GI/}, }Note
of work space and environment requirements. This becomes even worse on 'Windows' platforms or if several alternative 'GRASS GIS' installations are available. If one knows what to do thergrass
package setup function -rgrass::initGRASS
works fine under Linux. +rgrass::initGRASS
works fine under Linux. This is also valid for well known configurations under the 'Windows' operation system. Nevertheless on university labs or on company computers with restricted privileges and/or using different releases like the 'OSGeo4W' distribution and the @@ -225,12 +225,12 @@Examples
# setting up GRASS manually with spatial parameters of the nc data -proj4_string = as.character(sp::CRS("+init=epsg:28992")) +proj4_string = as.character(sp::CRS("+init=epsg:28992")) linkGRASS(spatial_params = c(178605,329714,181390,333611,proj4_string)) # creating a GRASS gisdbase manually with spatial parameters of the nc data # additionally using a peramanent directory "root_folder" and the location "nc_spatial_params " -proj4_string = as.character(sp::CRS("+init=epsg:4267")) +proj4_string = as.character(sp::CRS("+init=epsg:4267")) linkGRASS(gisdbase = root_folder, location = "nc_spatial_params", spatial_params = c(-84.32385, 33.88199,-75.45698,36.58965,proj4_string)) diff --git a/docs/reference/linkGRASS7.html b/docs/reference/linkGRASS7.html index 98b1610..5499640 100644 --- a/docs/reference/linkGRASS7.html +++ b/docs/reference/linkGRASS7.html @@ -1,5 +1,5 @@ -Deprecated only for backwards compatibility Locate and set up 'GRASS' API bindings — linkGRASS7 • link2GI Deprecated only for backwards compatibility Locate and set up 'GRASS' API bindings — linkGRASS7 • link2GI Locate and set up 'Orfeo ToolBox' API bindings — linkOTB • link2GI Locate and set up 'Orfeo ToolBox' API bindings — linkOTB • link2GI @@ -167,7 +167,7 @@Examples
Identifies SAGA GIS Installations and returns linking Informations — linkSAGA • link2GI Identifies SAGA GIS Installations and returns linking Informations — linkSAGA • link2GI saga<-linkSAGA() if (saga$exist) { require(RSAGA) -RSAGA::rsaga.env(path = saga$installed$binDir[1],modules = saga$installed$moduleDir[1]) +RSAGA::rsaga.env(path = saga$installed$binDir[1],modules = saga$installed$moduleDir[1]) } }Examples
Load data from rds format and associated yaml metadata file. — loadEnvi • link2GI Load data from rds format and associated yaml metadata file. — loadEnvi • link2GI @@ -120,7 +120,7 @@Examples
Load libraries and try to install missing ones — loadLibraries • link2GI Load libraries and try to install missing ones — loadLibraries • link2GI Generates a variable with a certain value in the R environment — makGlobalVar • link2GI Generates a variable with a certain value in the R environment — makGlobalVar • link2GI @@ -118,7 +118,7 @@Examples
R/gdalControls.R
setenvGDAL.Rd
R/otbControls.R
setenvOTB.Rd