Fix for issue - https://github.com/Robinlovelace/geocompr/issues/740 #742
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
The 3 functions were not loaded, since raster library was not loaded. Prefixing these with `raster::` tells bookdown to link to the documentation for these funcitons.
|
OK after chatting with @jimr1603 in person going to tweak then merge. |
Robinlovelace
approved these changes
Feb 10, 2022
02-spatial-data.Rmd
Outdated
| @@ -734,7 +734,7 @@ The **terra** package supports raster objects in R. | |||
| Like its predecessor **raster** (created by the same developer, Robert Hijmans), it provides an extensive set of functions to create, read, export, manipulate and process raster datasets. | |||
| **terra**'s functionality is largely the same as the more mature **raster** package, but there are some differences: **terra** functions are usually more computationally efficient than **raster** equivalents. | |||
| <!-- todo: add evidence (RL 2021-11) --> | |||
| On the other hand, the **raster** class system is popular and used by many other packages; as with **sf** and **sp**, the good news is you can seamlessly translate between the two types of object to ensure backwards compatibility with older scripts and packages, for example, with the functions `raster()`, `stack()`, or `brick()` (see the previous chapter for more on the evolution of R packages for working with geographic data). | |||
| On the other hand, the **raster** class system is popular and used by many other packages; as with **sf** and **sp**, the good news is you can seamlessly translate between the two types of object to ensure backwards compatibility with older scripts and packages, for example, with the functions `raster::raster()`, `raster::stack()`, or `raster::brick()` (see the previous chapter for more on the evolution of R packages for working with geographic data). | |||
There was a problem hiding this comment.
I think the following could be better for consistency:
On the other hand, the **raster** class system is popular and used by many other packages; as with **sf** and **sp**, the good news is you can seamlessly translate between the two types of object to ensure backwards compatibility with older scripts and packages, for example, with the functions [`raster()`](link_to_raster_docs) ...
Thoughts @Nowosad ?
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.
The 3 functions were not loaded, since raster library was not loaded. Prefixing these with
raster::tells bookdown to link to the documentation for these functions.If I find more of these I'll flag them as this Issue.