Same holds true for catch_fl, the cleaned data as output
of challenge 1. Again, notice that it is present in your local
environment, but won’t be during the knitting process.
Read catch_fl containing the cleaned geese catch
-data:
path_catch_file <- here("data", "20231026", "20231026_geese_counts_cleaned.txt")
+Read catch_fl containing the cleaned geese catch data.
+Notice that this file is not provided, but it’s written on disk in the
+last section of 1_geese_read_data.Rmd:
+path_catch_file <- here::here("data", "20231026", "20231026_geese_counts_cleaned.txt")
catch_fl <- read_csv(path_catch_file, na = "")
@@ -9593,9 +9596,9 @@ 3.2.1 Species
"Nijlgans"
)
-
-3.2.2 Catches per per
-year and species
+
+3.2.2 Catches per year
+and species
catch_species <-
catch_fl %>%
dplyr::filter(commonName %in% species) %>%
@@ -9715,8 +9718,8 @@ 4 Dynamic maps
)
)
map_catch_pr
-
-
+
+
4.1 crosstalk
We show also what you can do using the crosstalk package. For
@@ -9751,21 +9754,24 @@
4.1 crosstalk
-
-
+
+
-
-
+
+
-Some limitations: 1. No polygons, only points at the moment 2. the
-interaction doesn’t work with adding the clustering option in the
-leaflet markers, e.g. using
-addCircleMarkers(radius = 1, clusterOptions = markerClusterOptions())
-3. Because all data must be loaded into the browser, Crosstalk is not
-appropriate for large data sets.
+Some limitations:
+
+No polygons, only points at the moment
The interaction doesn’t work with adding the clustering option in
+the leaflet markers, e.g. using
+addCircleMarkers(radius = 1, clusterOptions = markerClusterOptions())
Because all data must be loaded into the browser, crosstalk is
+not appropriate for large data sets.
Do you want more? Go to crosstalk homepage.