forked from ebird/ebird-workshop-oca
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathtrends.qmd
195 lines (149 loc) · 10.9 KB
/
trends.qmd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
---
output: html_document
editor:
mode: source
editor_options:
chunk_output_type: console
---
# eBird Trends Data Products {#sec-trends}
The eBird Trends Data Products provide estimates of trends in relative abundance based on eBird data. Trend estimates are made on a 27 km by 27 km grid for a single season per species (breeding, non-breeding, or resident). For further details on the methodology used to estimate these trends consult the associated paper:
<blockquote>
Fink, D., Johnston, A., Strimas-Mackey, M., Auer, T., Hochachka, W. M., Ligocki, S., Oldham Jaromczyk, L., Robinson, O., Wood, C., Kelling, S., & Rodewald, A. D. (2023). A Double machine learning trend model for citizen science data. Methods in Ecology and Evolution, 00, 1–14. https://doi.org/10.1111/2041-210X.14186
</blockquote>
The data frame `ebirdst_runs` indicates which species have trends estimates with the `has_trends` column. We can filter the data frame and only select those columns relevant to trends.
```{r runs}
library(dplyr)
library(ggplot2)
library(rnaturalearth)
library(sf)
library(terra)
library(ebirdst)
trends_runs <- ebirdst_runs %>%
filter(has_trends) %>%
select(species_code, common_name,
trends_season, trends_region,
trends_start_year, trends_end_year,
trends_start_date, trends_end_date,
rsquared, beta0)
glimpse(trends_runs)
```
Information is provided on the trends model for each species, including two predictive performance metrics (`rsquared` and `beta0`) that are based on a comparison of actual and estimated trends for a suite of simulations (see Fink et al. 2023 for further details). The columns in the `trends_runs` data frame are as follows:
- `species_code`: the alphanumeric eBird species code uniquely identifying the species.
- `common_name`: the English common name of the species.
- `trends_season`: season that the trend was estimated for: breeding, nonbreeding, or resident.
- `trends_region`: the geographic region that the trend model was run for. Note that broadly distributed species (e.g. Barn Swallow) will only have trend estimates for a regional subset of their full range.
- `trends_start_year/trends_end_year`: the start and end years of the trend time period.
- `trends_start_date/trends_end_date`: the start and end dates (`MM-DD` format) of the season for which the trend was estimated.
- `rsquared`: R-squared value comparing the actual and estimated trends from the simulations.
- `beta0`: the intercept of a linear model fitting actual vs. estimated trends (`actual ~ estimated`) for the simulations. Positive values of `beta0` indicate that the models are systematically *underestimating* the simulated trend for this species.
Note that some season dates span two calendar years, for example Gray Fantail has 2013-2021 trends estimates for a breeding season defined as November 29 to March 15. In this case, the first season will be November 29, 2013 to March 15, 2012.
```{r crossing}
trends_runs %>%
filter(common_name == "Gray Fantail") %>%
select(trends_start_year, trends_end_year,
trends_start_date, trends_end_date)
```
## Downloading data {#download}
Trends data access is granted through the same process as the eBird Status Data Products. If you haven't already requested an API key, consult the relevant section in the [Introduction to eBird Status Data Products vignette](https://ebird.github.io/ebirdst/articles/status.html#access).
Trends data can be downloaded for one or more species using `ebirdst_download_trends()`, where the first argument is a vector of common names, scientific names, or species codes. As with the Status Data Products, trends data will be downloaded to a centralized directory and file management and access is performed via `ebirdst. For example, let's download the breeding season trends data for Sage Thrasher.
```{r download}
ebirdst_download_trends("Golden Whistler")
```
## Loading data into R {#load}
Once the data are downloaded, the trends data for a set of species, can be loaded into R using the function `load_trends()`. For example, we can load the Sage Thrasher trends estimates we just downloaded with:
```{r load}
trends_golwhi1 <- load_trends("Golden Whistler")
```
Each row corresponds to the trend estimate for a 27 km by 27 km grid cell, identified by the `srd_id` column and with cell center given by the `longitude` and `latitude` coordinates. Columns beginning with `abd_ppy` provide estimates of the percent per year trend in relative abundance and 80% confidence intervals, while those beginning with `abd_trend` provide estimates of the cumulative trend in relative abundance and 80% confidence intervals over the time period. The `abd` column gives the relative abundance estimate for the middle of the trend time period (e.g. 2018 for a 2014-2022 trend). The `start_year/end_year` and `start_date/end_date` columns provide redundant information to that available in `ebirdst_runs`.
```{r dates}
trends_runs %>%
filter(common_name == "Golden Whistler") %>%
select(trends_start_year, trends_end_year,
trends_start_date, trends_end_date)
```
This tells us that the trend estimates are for the breeding season (December 27 to February) for the period 2013-2021.
## Conversion to spatial formats {#spatial}
The eBird trends data are stored in a tabular format, where each row gives the trend estimate for a single cell in a 27 km by 27 km equal area grid. For each grid cell, the coordinates (longitude and latitude) are provided for the center of the grid cell. For many applications, an explicitly spatial format is more useful and these coordinates can be use to convert from the tabular format to either a vector or raster format.
### Vector (points) {#spatial-points}
The tabular trend data can be converted into point vector features for use with the `sf` package using the `sf` function `st_as_sf()`.
```{r spatial-points}
trends_sf <- st_as_sf(trends_golwhi1,
coords = c("longitude", "latitude"),
crs = 4326)
print(trends_sf)
```
### Raster {#spatial-raster}
The tabular trend estimates can most easily be converted to raster format for use with the `terra` package using the function `rasterize_trends()`. Any of the columns in the trends data frame can be selected using the `layers` argument and converted into layers in the resulting raster object.
```{r spatial-raster}
# rasterize the percent per year trend with confidence limits (default)
ppy_raster <- rasterize_trends(trends_golwhi1)
print(ppy_raster)
# rasterize the cumulative trend estimate
trends_raster <- rasterize_trends(trends_golwhi1, layers = "abd_trend")
print(trends_raster)
```
A simple map of these data can be produced from the raster data. For example, we'll make a map of percent per year change in relative abundance. Note that this is slightly different than the trends maps on the Status and Trends website, which show the cumulative trend rather than the annual trend.
```{r spatial-raster-map}
# define breaks and palettes similar to those on status and trends website
breaks <- seq(-4, 4)
breaks[1] <- -Inf
breaks[length(breaks)] <- Inf
pal <- ebirdst_palettes(length(breaks) - 1, type = "trends")
# make a simple map
plot(ppy_raster[["abd_ppy"]],
col = pal, breaks = breaks,
main = "Golden Whistler breeding trend 2013-2021 [% change per year]",
cex.main = 0.75,
axes = FALSE)
```
## Uncertainty {#uncertainty}
The model used to estimate trends produces an ensemble of 100 estimates at each location, each based on a random subsample of eBird data. This ensemble of estimates is used to quantify uncertainty in the trends estimates. The estimated trend is the median across the ensemble, and the 80% confidence intervals are the lower 10th and upper 90th percentiles across the ensemble. Those wishing to access estimates from the individual folds making up the ensemble can use `fold_estimates = TRUE` when loading data. These fold-level estimates can be used to quantify uncertainty, for example, when calculating the trend for a given region. For example, let's load the fold-level estimates:
```{r uncertainty}
trends_golwhi1_folds <- load_trends("golwhi1", fold_estimates = TRUE)
print(trends_golwhi1_folds)
```
This data frame is much more concise, only giving estimates of the mid-point relative abundance and percent per year trend in relative abundance for each of 100 folds for each grid cell.
## Regional trends {#applications-regional}
eBird trend estimates are made on a 27 km by 27 km grid, which allows summarization over broader regions such as states or provinces. Since the relative abundance of a species varies throughout its range, we need to weight the mean trend calculation by relative abundance (`abd` in the trends data frame). To quantify uncertainty in the regional trend, we can use the fold-level data to produce 100 distinct estimates of the regional trend, then calculate the median and 80% confidence intervals. As an example, let's calculate the state-level mean percent per year trends in relative abundance.
```{r applications-regional}
# boundaries of states
states<- read_sf("data/gis-data.gpkg", "regions") %>%
filter(country_code == "AU")
# convert fold-level trends estimates to sf format
trends_golwhi1_sf <- st_as_sf(trends_golwhi1_folds,
coords = c("longitude", "latitude"),
crs = 4326)
# attach state to the fold-level trends data
trends_golwhi1_sf <- st_join(trends_golwhi1_sf, states, left = FALSE)
# abundance-weighted average trend by region and fold
trends_states_folds <- trends_golwhi1_sf %>%
st_drop_geometry() %>%
group_by(state_code, fold) %>%
summarize(abd_ppy = sum(abd * abd_ppy) / sum(abd),
.groups = "drop")
# summarize across folds for each state
trends_states <- trends_states_folds %>%
group_by(state_code) %>%
summarise(abd_ppy_median = median(abd_ppy, na.rm = TRUE),
abd_ppy_lower = quantile(abd_ppy, 0.10, na.rm = TRUE),
abd_ppy_upper = quantile(abd_ppy, 0.90, na.rm = TRUE),
.groups = "drop") %>%
arrange(abd_ppy_median)
knitr::kable(trends_states, format = "html")
```
Note in the table above, many of these regional-level estimates cross zero and are thus not significant. We can then join these state-level trends back to the state boundaries and make a map with `ggplot2`.
```{r}
trends_states_sf <- left_join(states, trends_states, by = "state_code")
ggplot(trends_states_sf) +
geom_sf(aes(fill = abd_ppy_median)) +
scale_fill_distiller(palette = "RdBu",
limits = c(-1.9, 1.9),
na.value = "grey80",
direction = 1) +
guides(fill = guide_colorbar(title.position = "top", barwidth = 15)) +
labs(title = "Golden Whistler state-level breeding trends 2013-2021",
fill = "Relative abundance trend [% change / year]") +
theme_bw() +
theme(legend.position = "bottom")
```
Based on these data, Golden Whistler appears to be doing best in New South Wales.