01-introduction.Rmd: proposed updates wrt rgrass & qgisprocess #979
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Robinlovelace
approved these changes
Aug 27, 2023
| @@ -341,8 +341,8 @@ An important capability of **raster** and **terra** is their ability to work wit | |||
| **raster** and **terra** also supports map algebra, as described in Section \@ref(map-algebra). | |||
|
|
|||
| In parallel with these developments of class systems and methods came the support for R as an interface to dedicated GIS software. | |||
| **GRASS** [@bivand_using_2000] and follow-on packages **spgrass6** and **rgrass7** (for GRASS\index{GRASS} GIS 6 and 7, respectively) were prominent examples in this direction [@bivand_rgrass7_2016;@bivand_spgrass6_2016]. | |||
| Other examples of bridges between R and GIS include **RSAGA** [@R-RSAGA, first published in 2008]\index{RSAGA (package)}, **RPyGeo** [@brenning_arcgis_2012, first published in 2008], **RQGIS** [@muenchow_rqgis:_2017, first published in 2016]\index{RQGIS (package)}, and **rqgisprocess** \index{rqgisprocess (package)} (see Chapter \@ref(gis)). | |||
| **GRASS** [@bivand_using_2000] and follow-on packages **spgrass6**, **rgrass7** and **rgrass** (for GRASS\index{GRASS} GIS 6, 7, 7 + 8 respectively) were prominent examples in this direction [@bivand_rgrass7_2016;@bivand_spgrass6_2016]. | |||
There was a problem hiding this comment.
I suggest only mentioning one of the rgrass interfaces to avoid confusion. Which is most likely to be most appropriate for most people?
There was a problem hiding this comment.
Definitely rgrass then; it is for 'GRASS 7+'. See Readme of https://github.com/rsbivand/rgrass.
There was a problem hiding this comment.
Let's remove the others. Already too many packages mentioned in this book, hard to know which to use just with recommended ones!
There was a problem hiding this comment.
@Robinlovelace on the other hand this section describes history of R-spatial, so that may still be a reason to mention spgrass6, rgrass7 as well as RQGIS in here. Adding more explicitly that these are superseded by rgrass & qgisprocess may be more appropriate?
There was a problem hiding this comment.
@florisvdh yes -- that would be the good approach here
| **GRASS** [@bivand_using_2000] and follow-on packages **spgrass6** and **rgrass7** (for GRASS\index{GRASS} GIS 6 and 7, respectively) were prominent examples in this direction [@bivand_rgrass7_2016;@bivand_spgrass6_2016]. | ||
| Other examples of bridges between R and GIS include **RSAGA** [@R-RSAGA, first published in 2008]\index{RSAGA (package)}, **RPyGeo** [@brenning_arcgis_2012, first published in 2008], **RQGIS** [@muenchow_rqgis:_2017, first published in 2016]\index{RQGIS (package)}, and **rqgisprocess** \index{rqgisprocess (package)} (see Chapter \@ref(gis)). | ||
| **GRASS** [@bivand_using_2000] and follow-on packages **spgrass6**, **rgrass7** and **rgrass** (for GRASS\index{GRASS} GIS 6, 7, 7 + 8 respectively) were prominent examples in this direction [@bivand_rgrass7_2016;@bivand_spgrass6_2016]. | ||
| Other examples of bridges between R and GIS include **RSAGA** [@R-RSAGA, first published in 2008]\index{RSAGA (package)}, **RPyGeo** [@brenning_arcgis_2012, first published in 2008], **RQGIS** [@muenchow_rqgis:_2017, first published in 2016]\index{RQGIS (package)}, and **qgisprocess** \index{qgisprocess (package)} (see Chapter \@ref(gis)). |
github-actions bot
pushed a commit
that referenced
this pull request
Aug 28, 2023
01-introduction.Rmd: proposed updates wrt rgrass & qgisprocess d871ff5
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.