The {camtrapmonitoring} package provides functions for planning and evaluating camera trap surveys. The recommended approach is to first sample a set of candidate camera trap locations larger than the intended number of locations. Next, these candidate locations are evaluated using spatial layers to measure their deployment feasibility (such as distance to road) and to quantify their bias and coverage of project-specific characteristics (such as distribution across specific land cover classes).
{camtrapmonitoring} is designed to work with modern spatial R packages: {sf} and {terra}.
library(camtrapmonitoring)
library(sf)
#> Linking to GEOS 3.12.1, GDAL 3.8.4, PROJ 9.4.0; sf_use_s2() is TRUE
library(terra)
#> terra 1.9.27The sample_ct function returns candidate camera trap
locations using sf::st_sample across the user’s region of
interest. Options include “regular”, “random” or “hexagonal” sampling
across the entire region of interest or stratified by a column in the
provided features.
The example data “clearwater_lake_density” is a simulated species density grid near Clearwater Lake, Manitoba. It is a simple feature collection of polygons with a column named “density” (High, Medium, Low).
We will randomly sample candidate camera trap locations, stratified by the simulated species density.
pts <- sample_ct(
region = clearwater_lake_density,
n = 25,
type = 'random',
strata = 'density'
)
plot(pts)To evaluate candidate camera trap locations, determine each spatial layer required and the criteria associated with it. For example:
Deployment feasibility
Characteristics of candidate locations
First, we will evaluate the deployment feasibility layers. Note the example elevation data is an external TIF file that can be loaded with the {terra} package.
The eval_* family of functions return a vector of values
for each candidate camera trap location. These vectors can be added to
the simple features objects using the base R
df$name <- value syntax (shown here) or with
dplyr::mutate. eval_* functions take
‘features’ (candidate camera trap locations) and a ‘target’ covariate to
evaluate each candidate location with. For eval_pt and
eval_buffer, ‘target’ covariates are expected to be raster
layers while eval_dist expects a ‘target’ vector
object.
# Load data
clearwater_lake_elevation_path <- system.file('extdata', 'clearwater_lake_elevation.tif', package = 'camtrapmonitoring')
clearwater_lake_elevation <- rast(clearwater_lake_elevation_path)
data("clearwater_lake_roads")
# Evaluate elevation using point sample
pts$elev_pt <- eval_pt(features = pts, target = clearwater_lake_elevation)
# Evaluate elevation using buffered point sample
pts$elev_buffer_1e3 <- eval_buffer(
features = pts,
target = clearwater_lake_elevation,
buffer_size = 1e3
)
# Evaluate distance to roads
pts$road_dist <- eval_dist(features = pts, target = clearwater_lake_roads)
# Plot results
plot(pts)Next, we will evaluate the characteristics of candidate locations. Note the example land cover data is an external TIF file that can be loaded with the {terra} package.
# Load data
clearwater_lake_land_cover_path <- system.file('extdata', 'clearwater_lake_land_cover.tif', package = 'camtrapmonitoring')
clearwater_lake_land_cover <- rast(clearwater_lake_land_cover_path)
data("clearwater_lake_hydro")
data("clearwater_lake_wetlands")
# Evaluate land cover using point sample
pts$lc_pt <- eval_pt(features = pts, target = clearwater_lake_land_cover)
# Evaluate distance to hydrology
pts$hydro_dist <- eval_dist(features = pts, target = clearwater_lake_hydro)
# Evaluate distance to wetland
pts$wetland_dist <- eval_dist(features = pts, target = clearwater_lake_wetlands)
# Plot results
plot(pts)To select camera trap locations, define the criteria for selecting and sorting candidate locations.
Criteria for selection:
Criteria for sorting:
# Selection criteria
max_road_dist_m <- 3000
max_elev_m <- 300
ls_lc_classes <- c(1, 2, 5, 6)
# Select out of candidate points
select_pts <- pts[pts$road_dist < max_road_dist_m &
pts$elev_pt < max_elev_m &
pts$lc_pt %in% ls_lc_classes,]
plot(select_pts)# Sorting criteria
ordered <- order(select_pts$wetland_dist, -select_pts$hydro_dist)
order_select_pts <- select_pts[ordered,]
print(order_select_pts)
#> Simple feature collection with 13 features and 8 fields
#> Geometry type: POINT
#> Dimension: XY
#> Bounding box: xmin: 345468.4 ymin: 5976655 xmax: 375165.4 ymax: 5996744
#> Projected CRS: WGS 84 / UTM zone 14N
#> First 10 features:
#> density geometry id_sample_ct elev_pt elev_buffer_1e3
#> 20 High POINT (350173.7 5993152) 20 281 281.3893
#> 14 High POINT (345468.4 5996744) 14 270 268.5888
#> 47 Medium POINT (357108.2 5982014) 47 268 266.8522
#> 42 Medium POINT (375072.8 5985607) 42 270 267.1048
#> 12 High POINT (349337.8 5977391) 12 281 276.5988
#> 53 Low POINT (372128.2 5982421) 53 271 270.7756
#> 30 Medium POINT (364056.9 5982973) 30 272 270.4889
#> 49 Medium POINT (364111.8 5981564) 49 266 266.5990
#> 60 Low POINT (374045.5 5978591) 60 272 265.0008
#> 75 Low POINT (374929.4 5978173) 75 273 264.7587
#> road_dist lc_pt hydro_dist wetland_dist
#> 20 1180.4358 1 5100.2258 1617.831
#> 14 2296.0836 6 852.1648 7211.189
#> 47 427.5417 1 868.3019 7437.169
#> 42 784.4087 6 622.5533 7945.669
#> 12 117.0302 5 5209.7140 11758.741
#> 53 1281.7514 5 1779.5251 11825.739
#> 30 98.4212 1 1066.9049 11911.451
#> 49 724.8008 5 2289.8800 12680.257
#> 60 561.6220 1 5851.1883 15034.212
#> 75 1439.2036 6 6732.7269 15333.493The function grid_ct allows the user to establish
sampling grids around focal locations selected above. The
grid_design function is provided to the user to help
explore grid layout options, using either the ‘case’ argument or the ‘n’
argument.
After the grid design is selected, the grid_ct function
can be used with the selected camera trap locations.
ct_grids <- grid_ct(
features = order_select_pts,
distance = 500,
case = 'queen'
)
plot(ct_grids['id_grid_ct'][1])Example data used in the {camtrapmonitoring} package come from open data sources we gratefully acknowledge in the help page for each data set. Also see the “data-raw” directory in the package source for full data preprocessing steps.
?clearwater_lake_density?clearwater_lake_elevation?clearwater_lake_hydro?clearwater_lake_land_cover?clearwater_lake_roads