Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix typos in C5 and C6 #685

Merged
merged 2 commits into from
Nov 29, 2021
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
6 changes: 3 additions & 3 deletions 05-geometry-operations.Rmd
Original file line number Diff line number Diff line change
Expand Up @@ -559,7 +559,7 @@ A variety of georeferencing techniques exist, including:

- Georectification based on known [ground control points](https://www.qgistutorials.com/en/docs/3/georeferencing_basics.html);
- Orthorectification, which also accounts for local topography
- Image [registration](https://en.wikipedia.org/wiki/Image_registration) is used to combine images of the same thing but shot from different sensors the process of aligning one image with another (in terms of coordinate system, and resolution)
- Image [registration](https://en.wikipedia.org/wiki/Image_registration) is used to combine images of the same thing but shot from different sensors by aligning one image with another (in terms of coordinate system and resolution)

R is rather unsuitable for the first two points since these often require manual intervention which is why they are usually done with the help of dedicated GIS software (see also Chapter \@ref(gis)).
On the other hand, aligning several images is possible in R and this section shows among others how to do so.
Expand Down Expand Up @@ -829,7 +829,7 @@ We will use two objects to illustrate raster cropping:
- A vector (`sf`) object `zion` representing Zion National Park.

Both target and cropping objects must have the same projection.
The following code chunk therefore not only reads the datasets from the **spDataLarge** package9 installed in Chapter \@ref(spatial-class)), it also reprojects `zion` (see Section \@ref(reproj-geo-data) for more on reprojection):
The following code chunk therefore not only reads the datasets from the **spDataLarge** package (installed in Chapter \@ref(spatial-class)), it also reprojects `zion` (see Section \@ref(reproj-geo-data) for more on reprojection):
iod-ine marked this conversation as resolved.
Show resolved Hide resolved

```{r 05-geometry-operations-43, results='hide'}
srtm = rast(system.file("raster/srtm.tif", package = "spDataLarge"))
Expand Down Expand Up @@ -1269,4 +1269,4 @@ source("https://github.com/Robinlovelace/geocompr/raw/main/code/05-raster-vector
```{r, echo=FALSE, results='asis'}
res = knitr::knit_child('_05-ex.Rmd', quiet = TRUE, options = list(include = FALSE, eval = FALSE))
cat(res, sep = '\n')
```
```
2 changes: 1 addition & 1 deletion 06-reproj.Rmd
Original file line number Diff line number Diff line change
Expand Up @@ -140,7 +140,7 @@ st_distance(london_geo, london_proj)

To make the `london` and `london_proj` objects geographically comparable one of them must be transformed into the CRS of the other.
But which CRS to use?
The answer is usually 'to the projected CRS', which in this case is the British National Grid (EPSG:27700):
The answer is usually 'the projected CRS', which in this case is the British National Grid (EPSG:27700):
iod-ine marked this conversation as resolved.
Show resolved Hide resolved

```{r 06-reproj-10}
london2 = st_transform(london_geo, 27700)
Expand Down