```{r echo=FALSE}
library(knitr)
```
```{r include=FALSE}
knitr::opts_chunk$set(eval=TRUE, echo=TRUE, message=FALSE, warnings=FALSE, progress=FALSE)
```
# Introduction
The analysis is based on a dataset of observations of pantropical dolphins in the Gulf of Mexico (shipped with Distance 6.0 and later). For convenience the data are bundled in an `R`-friendly format, although all of the code necessary for creating the data from the Distance project files is available [on github](http://github.com/dill/mexico-data). The OBIS-SEAMAP page for the data may be found at the [SEFSC GoMex Oceanic 1996](http://seamap.env.duke.edu/dataset/25) survey page.
The intention here is to highlight the features of the `dsm` package, rather than perform a full analysis of the data. For that reason, some important steps are not fully explored. Some familiarity with density surface modelling [@miller_spatial_2013] [@hedley_spatial_2004] is assumed.
# Preamble
Before we start, we load the `dsm` package (and its dependencies) and set some options:
```{r loadlibraries}
library(dsm)
library(ggplot2)
# plotting options
gg.opts <- theme(panel.grid.major=element_blank(),
panel.grid.minor=element_blank(),
panel.background=element_blank())
```
In order to run this vignette, you'll need to install a few R packages. This can be done via the following call to `install.packages`:
```
install.packages(c("dsm", "Distance", "knitr", "distill", "ggplot2", "rgdal",
"maptools", "plyr", "tweedie"))
```
# The data
Most of the data we need is included in the `dsm` package, but two additional objects needed for plotting are required and can be downloaded [here](https://examples.distancesampling.org/dsm-line-dolphins/mexdolphins-extra.rda) and should be put into the same directory as this file. The data can then be loaded into R using the following code:
```{r download-extra-data}
load("mexdolphins-extra.rda")
```
This should add the objects `survey.area` and `pred.polys` to your environment.
## Observation and segment data
All of the data for this analysis has been nicely pre-formatted and is shipped with `dsm`. Loading that data, we can see that we have four `data.frame`s, the first few lines of each are shown:
```{r loaddata}
data(mexdolphins)
```
`segdata` holds the segment data: the transects have already been "chopped" into segments.
```{r head-segdata}
head(segdata)
```
`distdata` holds the distance sampling data that will be used to fit the detection function.
```{r head-distdata}
head(distdata)
```
`obsdata` links the distance data to the segments.
```{r head-obsdata}
head(obsdata)
```
`preddata` holds the prediction grid (which includes all the necessary covariates).
```{r head-preddata}
head(preddata)
```
Typically (i.e. for other datasets) it will be necessary divide the transects into segments, and allocate observations to the correct segments using a GIS or other similar package[^MGET], before starting an analysis using `dsm`.
## Shapefiles and converting units
Often data in a spatial analysis comes from many different sources. It is important to ensure that the measurements to be used in the analysis are in compatible units, otherwise the resulting estimates will be incorrect or hard to interpret. Having all of our measurements in SI units from the outset removes the need for conversion later, making life much easier.
The data are already in the appropriate units (Northings and Eastings: kilometres from a centroid, projected using the [North American Lambert Conformal Conic projection](https://en.wikipedia.org/wiki/Lambert_conformal_conic_projection)).
There is extensive literature about when particular projections of latitude and longitude are appropriate and we highly recommend the reader review this for their particular study area; [@bivand_applied_2008] is a good starting point. The other data frames have already had their measurements appropriately converted. By convention the directions are named `x` and `y`.
Using latitude and longitude when performing spatial smoothing can be problematic when certain smoother bases are used. In particular when bivariate isotropic bases are used the non-isotropic nature of latitude and longitude is inconsistent (moving one degree in one direction is not the same as moving one degree in the other).
We give an example of projecting the polygon that defines the survey area (which as simply been read into R using `readShapeSpatial` from a shapefile produced by GIS).
```{r projectsurvey, results='hide', message=FALSE}
library(rgdal)
library(maptools)
library(plyr)
# tell R that the survey.area object is currently in lat/long
proj4string(survey.area) <- CRS("+proj=longlat +datum=WGS84")
# proj 4 string
# using http://spatialreference.org/ref/esri/north-america-lambert-conformal-conic/
lcc_proj4 <- CRS("+proj=lcc +lat_1=20 +lat_2=60 +lat_0=40 +lon_0=-96 +x_0=0 +y_0=0 +ellps=GRS80 +datum=NAD83 +units=m +no_defs ")
# project using LCC
survey.area <- spTransform(survey.area, CRSobj=lcc_proj4)
# simplify the object
survey.area <- data.frame(survey.area@polygons[[1]]@Polygons[[1]]@coords)
names(survey.area) <- c("x", "y")
```
The below code generates this plot, which shows the survey area with the transect lines overlaid (using data from `segdata`).
```{r areawithtransects, fig.cap="", fig.height=4}
p <- qplot(data=survey.area, x=x, y=y, geom="polygon",fill=I("lightblue"),
ylab="y", xlab="x", alpha=I(0.7))
p <- p + coord_equal()
p <- p + geom_line(aes(x,y,group=Transect.Label),data=segdata)
p <- p + gg.opts
print(p)
```
Also note that since we've projected our prediction grid, the "squares" don't look quite like squares. So for plotting we'll use the polygons that we've saved, these polygons (stored in `pred.polys`) are read from a shapefile created in GIS, the object itself is of class `SpatialPolygons` from the `sp` package. This plotting method makes plotting take a little longer, but avoids gaps and overplotting. The following plot compares using latitude/longitude (left) with a projection (right).
```{r projection-compare, fig.cap="", fig.height=3}
par(mfrow=c(1,2))
# put pred.polys into lat/long
pred_latlong <- spTransform(pred.polys,CRSobj=CRS("+proj=longlat +datum=WGS84"))
# plot latlong
plot(pred_latlong, xlab="Longitude", ylab="Latitude")
axis(1); axis(2); box()
# plot as projected
plot(pred.polys, xlab="Northing", ylab="Easting")
axis(1); axis(2); box()
```
Tips on plotting polygons are available from [the `ggplot2` wiki](https://github.com/hadley/ggplot2/wiki/plotting-polygon-shapefiles).
Here we define a convenience function to generate an appropriate data structure for `ggplot2` to plot:
```{r ggpoly}
# given the argument fill (the covariate vector to use as the fill) and a name,
# return a geom_polygon object
# fill must be in the same order as the polygon data
grid_plot_obj <- function(fill, name, sp){
# what was the data supplied?
names(fill) <- NULL
row.names(fill) <- NULL
data <- data.frame(fill)
names(data) <- name
spdf <- SpatialPolygonsDataFrame(sp, data)
spdf@data$id <- rownames(spdf@data)
spdf.points <- fortify(spdf, region="id")
spdf.df <- join(spdf.points, spdf@data, by="id")
# seems to store the x/y even when projected as labelled as
# "long" and "lat"
spdf.df$x <- spdf.df$long
spdf.df$y <- spdf.df$lat
geom_polygon(aes_string(x="x",y="y",fill=name, group="group"), data=spdf.df)
}
```
# Exploratory data analysis
## Distance data
The top panels of the EDA plots below show histograms of observed distances and cluster size, while the bottom panels show the relationship between observed distance and observed cluster size, and the relationship between observed distance and Beaufort sea state. The plots show that there is some relationship between cluster size and observed distance (fewer smaller clusters seem to be seen at larger distances).
The following code generates the EDA plots:
```{r EDA-plots, fig.height=7, fig.width=7, fig.cap="", results="hide"}
par(mfrow=c(2,2))
# histograms
hist(distdata$distance,main="",xlab="Distance (m)")
hist(distdata$size,main="",xlab="Cluster size")
# plots of distance vs. cluster size
plot(distdata$distance, distdata$size, main="", xlab="Distance (m)",
ylab="Group size", pch=19, cex=0.5, col=gray(0.7))
# lm fit
l.dat <- data.frame(distance=seq(0,8000,len=1000))
lo <- lm(size~distance, data=distdata)
lines(l.dat$distance, as.vector(predict(lo,l.dat)))
plot(distdata$distance,distdata$beaufort, main="", xlab="Distance (m)",
ylab="Beaufort sea state", pch=19, cex=0.5, col=gray(0.7))
```
Top row, left to right: histograms of distance and cluster size; bottom row: plot of distance against cluster size and plot of distances against Beaufort sea state.
## Spatial data
Looking separately at the spatial data without thinking about the distances, we can plot the observed group sizes in space (point size is proportional to the group size for each observation). Circle size indicates the size of the group in the observation. There are rather large areas with no observations, which might cause our variance estimates for abundance to be rather large. We also see the depth data which we will use depth later as an explanatory covariate in our spatial model.
```{r spatialEDA, fig.cap=""}
p <- ggplot() + grid_plot_obj(preddata$depth, "Depth", pred.polys) + coord_equal()
p <- p + labs(fill="Depth",x="x",y="y",size="Group size")
p <- p + geom_line(aes(x, y, group=Transect.Label), data=segdata)
p <- p + geom_point(aes(x, y, size=size), data=distdata, colour="red",alpha=I(0.7))
p <- p + gg.opts
print(p)
```
# Estimating the detection function
We use the `ds` function in the package `Distance` to fit the detection function. (The `Distance` package is intended to make standard distance sampling in `R` relatively straightforward. For a more flexible but more complex alternative, see the function `ddf` in the `mrds` library.)
First, loading the `Distance` library:
```{r loadDistance}
library(Distance)
```
We can then fit a detection function with hazard-rate key with no adjustment terms:
```{r hrmodel}
detfc.hr.null <- ds(distdata, max(distdata$distance), key="hr", adjustment=NULL)
```
Calling `summary` gives us information about parameter estimates, probability of detection, AIC, etc:
```{r hrmodelsummary}
summary(detfc.hr.null)
```
The following code generates a plot of the fitted detection function (left) and quantile-quantile plot (right):
``` {r hr-detfct, fig.cap="", fig.width=9, fig.height=6, results="hide"}
layout(matrix(c(1, 2), 1, 2), width=c(1.5, 1))
plot(detfc.hr.null, showpoints=FALSE, pl.den=0, lwd=2)
gof_ds(detfc.hr.null)
```
The quantile-quantile plot show relatively good goodness of fit for the hazard-rate detection function.
## Adding covariates to the detection function
It is common to include covariates in the detection function (so-called Multiple Covariate Distance Sampling or MCDS). In this dataset there are two covariates that were collected on each individual: Beaufort sea state and size. For brevity we fit only a hazard-rate detection functions with the sea state included as a factor covariate as follows:
```{r hrcovdf, message=FALSE, cache=TRUE, warning=FALSE}
detfc.hr.beau<-ds(distdata, max(distdata$distance), formula=~as.factor(beaufort),
key="hr", adjustment=NULL)
```
Again looking at the `summary`,
```{r hrcovdfsummary, cache=TRUE}
summary(detfc.hr.beau)
```
Here the detection function with covariates does not give a lower AIC than the model without covariates (`r round(detfc.hr.beau$ddf$criterion,2)` vs. `r round(detfc.hr.null$ddf$criterion,2)` for the hazard-rate model without covariates). Looking back to the bottom-right panel of the EDA plots, we can see there is not a discernible pattern in the plot of Beaufort vs distance.
For brevity, detection function model selection has been omitted here. In practise we would fit many different forms for the detection function (and select a model based on goodness of fit testing and AIC).
# Fitting a DSM
Before fitting a `dsm` model, the data must be segmented; this consists of chopping up the transects and attributing counts to each of the segments. As mentioned above, these data have already been segmented.
## A simple model
We begin with a very simple model. We assume that the number of individuals in each segment are quasi-Poisson distributed and that they are a smooth function of their spatial coordinates (note that the formula is exactly as one would specify to `gam` in `mgcv`). By setting `group=TRUE`, the abundance of clusters/groups rather than individuals can be estimated (though we ignore this here). Note we set `method="REML"` to ensure that smooth terms are estimated reliably.
Running the model:
```{r dsm-xy}
dsm.xy <- dsm(count~s(x,y), detfc.hr.null, segdata, obsdata, method="REML")
```
We can then obtain a summary of the fitted model:
```{r dsm-xy-summary}
summary(dsm.xy)
```
The exact interpretation of the model summary results can be found in [@wood_generalized_2017]; here we can see various information about the smooth components fitted and general model statistics.
We can use the deviance explained to compare between models[^rsqoffset].
We can also get a rough idea of what the smooth of space looks like using `vis.gam` (white/yellow indicates high values, red low indicates low values):
```{r visgam1, fig.cap=''}
vis.gam(dsm.xy, plot.type="contour", view=c("x","y"), asp=1, type="response", contour.col="black", n.grid=100)
```
The `type="response"` argument ensures that the plot is on the scale of abundance but the values are relative (as the offsets are set to be their median values). This means that the plot is useful to get an idea of the general shape of the smooth but cannot be interpreted directly.
## Adding another environmental covariate to the spatial model
The data set also contains a `depth` covariate (which we plotted above). We can include in the model very simply:
```{r depthmodel}
dsm.xy.depth <- dsm(count~s(x,y,k=10) + s(depth,k=20), detfc.hr.null, segdata, obsdata, method="REML")
summary(dsm.xy.depth)
```
Here we see a drop in deviance explained, so perhaps this model is not as useful as the first. We discuss setting the `k` parameter in [Model checking], below.
Setting `select=TRUE` here (as an argument to `gam`) would impose extra shrinkage terms on each smooth in the model (allowing smooth terms to be removed from the model during fitting; see `?gam` for more information). This is not particularly useful here, so we do not include it. However when there are many environmental predictors is in the model this can be a good way (along with looking at $p$-values) to perform term selection.
Simply calling `plot` on the model object allows us to look at the relationship between depth and the linear predictor:
```{r dsm-xy-depth-depth, fig.cap=""}
plot(dsm.xy.depth, select=2)
```
Omitting the argument `select` in the call to `plot` will plot each of the smooth terms, one at a time.
## Spatial models when there are covariates in the detection function
The code to fit the DSM when there are covariates in the detection function is similar to the other models, above. However since the detection function has observation-level covariates, we must estimate the abundance per segment using a Horvitz-Thompson-like estimator before modelling, so we change the response to be `abundance.est`:
``` {r dsm-est-xy, cache=TRUE}
dsm.est.xy <- dsm(abundance.est~s(x,y), detfc.hr.beau, segdata, obsdata, method="REML")
```
As we can see, the `summary` results are rather similar:
```{r dsm-est-xy-summary}
summary(dsm.est.xy)
```
As is the resulting spatial smooth (though the resulting surface is somewhat "amplified"):
```{r visgam5, fig.cap=""}
vis.gam(dsm.est.xy, plot.type="contour", view=c("x","y"), asp=1, type="response", zlim=c(0, 300), contour.col="black", n.grid=100)
```
## Other response distributions
Often the quasi-Poisson distribution doesn't give adequate flexibility and doesn't capture the overdispersion in the response data (see [Model checking] and [Model selection] below), so below we illustrate two additional distributions that can be used with count data.
For the models in this section, we'll move back to the `count` response, though the estimated abundance would also work.
### Tweedie
Response distributions other than the quasi-Poisson can be used, for example the Tweedie distribution. The Tweedie distribution is available in `dsm` by setting `family=tw()`.
```{r tweedie-fit}
dsm.xy.tweedie <- dsm(count~s(x,y), detfc.hr.null, segdata, obsdata, family=tw(), method="REML")
summary(dsm.xy.tweedie)
```
### Negative binomial
Though not used here there are, similarly, two options for the negative binomial distribution: `negbin` and `nb`. The former requires the user specification single parameter `theta` or a range of values for the parameter (specified as a vector), the latter estimates the value of `theta` during the model fitting process (and is generally faster). The latter is recommended for most users.
## Other spatial modelling options
There is a large literature on spatial modelling using GAMs, much of which can be harnessed in a DSM context. Here are a few highlights.
### Soap film smoothing
To account for a complex region (e.g., a region that includes peninsulae) we can use the soap film smoother [@wood_soap_2008].
To use a soap film smoother for the spatial part of the model we must create a set of knots for the smoother to use. This is easily done using the `make.soapgrid()` function in `dsm`:
```{r soap-knots}
soap.knots <- make.soapgrid(survey.area,c(15,10))
```
where the second argument specifies the number of points (in each direction) in the grid that will be used to create the knots (knots in the grid outside of `survey.area` are removed).
As we saw in the exploratory analysis, some of the transect lines are outside of the survey area. These will cause the soap film smoother to fail, so we remove them:
```{r soap-setup}
x <- segdata$x; y<-segdata$y
onoff <- inSide(x=x,y=y, bnd=as.list(survey.area))
rm(x,y)
segdata.soap <- segdata[onoff,]
```
Note that the [`soap_checker` script available here](https://github.com/dill/soap_checker) can be useful in ensuring that the boundary, data and knots are in the correct format to use with the soap film smoother.
We can run a model with both the `depth` covariate along with a spatial (soap film) smooth. Note that the `k` argument now refers to the complexity of the boundary smooth in the soap film, and the complexity of the film is controlled by the knots given in the `xt` argument.
``` {r soap-fit, cache=TRUE}
dsm.xy.tweedie.soap<-dsm(count~s(x, y, bs="so", k=15, xt=list(bnd=list(survey.area))) +
s(depth),
family=tw(), method="REML",
detfc.hr.null, segdata.soap, obsdata, knots=soap.knots)
summary(dsm.xy.tweedie.soap)
```
# Model checking
Fitting models is all well and good, but we'd like to confirm that the models we have are reasonable; `dsm` provides some functions for model checking.
We can use `gam.check` to generate diagnostic plots:
```{r dsm.xy-check, fig.cap="", fig.width=6, fig.height=6}
gam.check(dsm.xy)
```
These show that there is some deviation in the Q-Q plot. The "line" of points in the plot of the residuals vs. linear predictor plot corresponds to the zeros in the data.
Note that as well as the plots, `gam.check` also produces information about the model fitting. Of particular interest to us is the last few lines that tell us about the basis size.
The `k` parameter provided to `s` (and `te`) terms in `dsm` controls the complexity of the smooths in the model.
By setting the `k` parameter we specify the largest complexity for that smooth term in the model; as long as this is high enough, we can be sure that there is enough flexibility. In the output from `gam.check` above, we can see that there is a "p-value" calculated for the size of the basis, this can be a good guide as to whether the basis size needs to be increased.
The `?choose.k` manual page from `mgcv` gives further guidance and technical details on this matter.
We can look at the same model form but with a Tweedie distribution specified as the response:
``` {r dsm.xy.tweedie-check, fig.cap="", fig.width=6, fig.height=6}
gam.check(dsm.xy.tweedie)
```
The Q-Q plot now seems much better (closer to the $y=x$ line). In both plots the histogram of residuals is rather hard to interpret due to the large number of zeros in the data.
Further guidance on interpreting `gam.check` output can be found in [@wood_generalized_2017].
### Randomised quantile residuals
In the top right panel of the above `gam.check` plots the residuals vs. linear predictor plot includes a odd line of predictions. These are an artifact of the link function, showing the exact zeros in the data. These can be misleading and distracting, making it difficult to see whether residuals show heteroskedasticity.
Randomised quantile residuals [@dunn_randomized_1996] avoid this issue by transforming the residuals to be exactly normally distributed. This makes the residuals vs. linear predictor plot much easier to interpret as it therefore doesn't include the artifacts generated by the link function. These plots can be produced using `rqgam.check` in `dsm`:
``` {r dsm.xy.tweedie-rqcheck, fig.cap="", fig.width=6, fig.height=6}
rqgam.check(dsm.xy.tweedie)
```
Here we can see that there is no issue with heteroskedasticity (no increase in spread in the residuals vs. linear predictor plot with increasing values of the linear predictor). One can also plot these residuals against covariate values to check for pattern in the residuals.
Note that in general, plots other than "Resids vs. linear pred." should be interpreted with caution in the output of `rqgam.check` as the residuals generated are normal by construction (so for example the Q-Q plot and histogram of residuals will always look fine).
# Model selection
Assuming that models have "passed" the checks in `gam.check`, `rqgam.check` and are sufficiently flexible, we may be left with a choice of which model is "best". There are several methods for choosing the best model -- AIC, REML/GCV scores, deviance explained, full cross-validation with test data and so on.
Though this document doesn't intend to be a full analysis of the pantropical dolphin data, we can create a results table to compare the various models that have been fitted so far in terms of their abundance estimates and associated uncertainties.
```{r modelcomp, cache=TRUE}
# make a data.frame to print out
mod_results <- data.frame("Model name" = c("`dsm.xy`", "`dsm.xy.depth`", "`dsm.xy.tweedie`", "`dsm.xy.tweedie.soap`",
"`dsm.est.xy`"),
"Description" = c("Bivariate smooth of location, quasipoisson",
"Bivariate smooth of location, smooth of depth, quasipoisson",
"Bivariate smooth of location, smooth of depth, Tweedie",
"Soap film smooth of location, smooth of depth, Tweedie",
"Bivariate smooth of location, smooth of depth, Tweedie, Beaufort covariate in detection function"),
"Deviance explained" = c(unlist(lapply(list(dsm.xy,
dsm.xy.depth,
dsm.xy.tweedie,
dsm.xy.tweedie.soap),
function(x){paste0(round(summary(x)$dev.expl*100,2),"%")})),NA))
```
We can then use the resulting `data.frame` to build a table of results using the `kable` function:
```{r results-table, results='asis'}
kable(mod_results, col.names=c("Model name", "Description", "Deviance explained"))
```
# Abundance estimation
Once a model has been checked and selected, we can make predictions over the grid and calculate abundance. The offset is stored in the `area` column[^offsetcorrection].
```{r dsm-xy-pred}
dsm.xy.pred <- predict(dsm.xy, preddata, preddata$area)
```
We use the `grid_plot_obj` helper function to assign the predictions to grid cells (polygons):
```{r dsm.xy-preds, fig.cap=""}
p <- ggplot() + grid_plot_obj(dsm.xy.pred, "Abundance", pred.polys) + coord_equal() +gg.opts
p <- p + geom_path(aes(x=x, y=y),data=survey.area)
p <- p + labs(fill="Abundance")
print(p)
```
We can calculate abundance over the survey area by simply summing these predictions:
``` {r dsm.xy-abund}
sum(dsm.xy.pred)
```
We can compare this with a plot of the predictions from this `dsm.xy.depth`:
```{r dsm.xy.depth-preds, fig.cap=""}
dsm.xy.depth.pred <- predict(dsm.xy.depth, preddata, preddata$area)
p <- ggplot() + grid_plot_obj(dsm.xy.depth.pred, "Abundance", pred.polys) + coord_equal() +gg.opts
p <- p + geom_path(aes(x=x, y=y), data=survey.area)
p <- p + labs(fill="Abundance")
print(p)
```
We can see the inclusion of depth into the model has had a noticeable effect on the distribution (note the difference in legend scale between the two plots). We can again also look at the total abundance:
``` {r dsm.xy.depth-abund}
sum(dsm.xy.depth.pred)
```
Here we see that there is not much of a change in the abundance, so in terms of abundance alone there isn't much between the two models. Next we'll go on to look at variance next where we can see bigger differences between the models.
# Variance estimation
Obviously point estimates of abundance are important, but we should also calculate uncertainty around these abundance estimates. Fortunately `dsm` provides functions to perform these calculations and display the resulting uncertainty estimates.
There are two approaches to estimating the uncertainty of an abundance estimate in `dsm`.
- `dsm.var.gam` which assumes that the spatial model and detection function parts of the model are independent of each other. In this case the squared coefficients of variation for each model component are added.
- `dsm.var.prop` which takes into account the fact that detection probability may be correlated with the spatial part of the model. It uses methods described in [@bravington_reliable_2018].
`dsm.var.prop` can only be applied when there is a covariate in the detection function that varies at the level of the segments, and is recorded at each segment (for example Beaufort). We don't have that situation here, so we opt for `dsm.var.gam`.
Both methods estimate the variance of the abundance for each element in the list provided in `pred.data`. In our case we wish to obtain an abundance for each of the prediction cells, so we use `split` to chop our data set into list elements to give to `dsm.var.gam` (or `dsm.var.prop`).
```{r dsm.xy-var, cache=TRUE}
preddata.var <- split(preddata, 1:nrow(preddata))
dsm.xy.var <- dsm.var.gam(dsm.xy, pred.data=preddata.var,
off.set=preddata$area)
```
Calling `summary` will give some information about uncertainty estimation:
``` {r}
summary(dsm.xy.var)
```
We can also make a plot of the CVs (with transect lines and observations overlaid) using the following code.
```{r dsm.xyvarplot, fig.cap=""}
p <- ggplot() + grid_plot_obj(sqrt(dsm.xy.var$pred.var)/unlist(dsm.xy.var$pred),
"CV", pred.polys) + coord_equal() +gg.opts
p <- p + geom_path(aes(x=x, y=y), data=survey.area)
p <- p + geom_line(aes(x, y, group=Transect.Label), data=segdata)
print(p)
```
Note the increase in CV away from the transect lines.
We can revisit the model that included both depth and location smooths and observe that the coefficient of variation for that model is larger than that of the model with only the location smooth.
```{r dsm.xy.depth-varprop, cache=TRUE}
dsm.xy.depth.var <- dsm.var.gam(dsm.xy.depth, pred.data=preddata.var,
off.set=preddata$area)
summary(dsm.xy.depth.var)
```
# Conclusions
This document has outlined an analysis of spatially-explicit distance sampling data using the `dsm` package. Note that there are many possible models that can be fitted using `dsm` and that the aim here was to show just a few of the options. Results from the models can be rather different, so care must be taken in performing model selection, discrimination and criticism.
# Software
* `Distance` is available at [http://github.com/DistanceDevelopment/Distance](http://github.com/DistanceDevelopment/Distance) as well as on CRAN.
* `dsm` is available at [http://github.com/DistanceDevelopment/dsm](http://github.com/DistanceDevelopment/dsm), as well as on CRAN.
[^offsetcorrection]: An earlier version of this vignette incorrectly stated that the areas of the prediction cells were 444km$^2$. This has been corrected. Thanks to Phil Bouchet for pointing this out.
[^MGET]: These operations can be performed in R using the `sp` and `rgeos` packages. It may, however, be easier to perform these operations in GIS such as ArcGIS -- in which case the MGET Toolbox may be useful.
[^rsqoffset]: Note though that the adjusted $R^2$ for the model is defined as the proportion of variance explained but the "original" variance used for comparison doesn't include the offset (the area (or effective of the segments). It is therefore not recommended for one to directly interpret the $R^2$ value (see the `summary.gam` manual page for further details).