From c1b57bf49bb0c2e1d2b5440a20853b018d377b88 Mon Sep 17 00:00:00 2001 From: Nowosad Date: Mon, 30 Sep 2024 14:10:57 +0000 Subject: [PATCH] Deploy commit: imrpoves list 6b8fabfe6149e52c2e602cb9cac5dac988bc59c3 --- 02-spatial-data.md | 8 ++--- 13-transport.md | 8 +---- 404.html | 2 +- adv-map.html | 2 +- algorithms.html | 2 +- attr.html | 2 +- conclusion.html | 10 +++---- eco.html | 48 +++++++++++++++--------------- figures/circle-intersection-1.png | Bin 13642 -> 13642 bytes figures/cycleways-1.png | Bin 111102 -> 133779 bytes figures/points-1.png | Bin 15698 -> 15698 bytes figures/rnetvis-1.png | Bin 55412 -> 51780 bytes figures/rnetvis-2.png | Bin 44935 -> 60976 bytes figures/routes-1.png | Bin 135533 -> 163793 bytes figures/wayssln-1.png | Bin 104062 -> 141046 bytes foreword-1st-edition.html | 2 +- foreword-2nd-edition.html | 2 +- geometry-operations.html | 2 +- gis.html | 2 +- index.html | 4 +-- index.md | 4 +-- intro.html | 2 +- location.html | 46 ++++++++++++++-------------- preface.html | 2 +- raster-vector.html | 2 +- read-write.html | 2 +- references.html | 2 +- reproj-geo-data.html | 2 +- search.json | 2 +- spatial-class.html | 10 +++---- spatial-cv.html | 2 +- spatial-operations.html | 2 +- transport.html | 14 ++++----- 33 files changed, 89 insertions(+), 97 deletions(-) diff --git a/02-spatial-data.md b/02-spatial-data.md index d65b99e79..c857efb6e 100644 --- a/02-spatial-data.md +++ b/02-spatial-data.md @@ -1172,11 +1172,11 @@ It is typically used in mapping polar regions. A quick summary of different projections, their types, properties, and suitability can be found at [www.geo-projections.com](https://www.geo-projections.com/). We will expand on CRSs and explain how to project from one CRS to another in Chapter \@ref(reproj-geo-data). -For now, it is sufficient to know that: +For now, it is sufficient to know: -- Coordinate systems are a key component of geographic objects -- Knowing which CRS your data is in, and whether it is in geographic (lon/lat) or projected (typically meters), is important and has consequences for how R handles spatial and geometry operations -- CRSs of `sf` objects can be queried with the function `st_crs()` and CRSs of `terra` objects can be queried with the function `crs()` +- That coordinate systems are a key component of geographic objects +- Which CRS your data is in, and whether it is in geographic (lon/lat) or projected (typically meters), is important and has consequences for how R handles spatial and geometry operations +- That CRSs of `sf` objects can be queried with the function `st_crs()` and CRSs of `terra` objects can be queried with the function `crs()`
Examples of geographic (WGS 84; left) and projected (NAD83 / UTM zone 12N; right) coordinate systems for a vector data type. diff --git a/13-transport.md b/13-transport.md index 26f08fe13..42d6d1fb7 100644 --- a/13-transport.md +++ b/13-transport.md @@ -511,7 +511,6 @@ This is done using the publicly available OSRM service with the **stplanr** func ``` r routes_short = route(l = desire_lines_short, route_fun = route_osrm, osrm.profile = "bike") -#> ``` The output is `routes_short`, an `sf` object representing routes on the transport network\index{network} that are suitable for cycling (according to the OSRM routing engine at least), one for each desire line. @@ -570,7 +569,7 @@ routes_short_scenario = routes_short |> mutate(bicycle = bicycle + car_driver * uptake, car_driver = car_driver * (1 - uptake)) sum(routes_short_scenario$bicycle) - sum(routes_short$bicycle) -#> [1] 1023 +#> [1] 3850 ``` Having created a scenario in which approximately 4000 trips have switched from driving to cycling, we can now model where this updated modeled cycling activity will take place. @@ -643,11 +642,6 @@ ways_centrality = ways_sfn |> mutate(betweenness = tidygraph::centrality_edge_betweenness(lengths)) ``` - -``` -#> [plot mode] legend/component: Some components or legends are too wide and are therefore rescaled. Set the tmap option 'component.autoscale' to FALSE to disable rescaling. -``` -
Illustration of route network datasets. The grey lines represent a simplified road network, with segment thickness proportional to betweenness. The green lines represent potential cycling flows (one way) calculated with the code above.

(\#fig:wayssln)Illustration of route network datasets. The grey lines represent a simplified road network, with segment thickness proportional to betweenness. The green lines represent potential cycling flows (one way) calculated with the code above.

diff --git a/404.html b/404.html index a836329c8..66554bb67 100644 --- a/404.html +++ b/404.html @@ -129,7 +129,7 @@

Second Edition