Hi Craig, List,
The pattern you describe (very little data close to the point, a hump at some
distance out and then little data at greater distances) is exactly what one
expects for point transect data -- see, for example Buckland et al 2001 figures
5.1 and 5.2. This is because two things are going on at once: the detection
probability decreases as you move away from the point in a non-linear fashion,
but the area surveyed (see figure 2.3) increases linearly. I put an overhead
from our introductory workshop on the web which will hopefully make this clear -
see
http://www.ruwpa.st-and.ac.uk/distance/points.pdf
It's hard to give specific advice about truncation without seeing the data, and
I'm wary of cookbook recipes -- but truncation of around 10% of point transect
data is a good starting point. The aim is to remove "outliers" -- that is the
odd observation at large distances that can cause Distance to add an extra
adjustment term when it doesn't affect the fit at 0 distance and only decreases
precision. As a rough gude, and assuming "good" data, try fitting any old
detection function and truncating 10%; if there are one or more adjustment terms
fit, try a slightly greater truncation and see if you can get it to drop one of
the adjustment terms, and if it does, see if it makes the estimate of h(0) more
precise. Not something to get hung up about though -- with "good" data it
should make little difference for truncations of about this much -- i.e., the
density estimate should not move much relative to its standard error, and the CV
should not change greatly.
Note that you cannot compare AIC amoung analyses with different truncations (or
cutpoints, when intervals are specified in the Data Filter). AIC is only a
valid comparison when you're comparing analyses using exactly the same input
data, and truncation changes the data.
I would avoid left truncation, especially for point transect data where the
observations made close to the point are especially important in determining the
slope of f(x) at 0 distance -- which is the h(0) in equation 3.14 of the book.
You can use the goodness-of-fit tests to check whether there really is a serious
lack of fit of the data close to the point.
I would also avoid putting the data into intervals for the analysis, especially
since you collected exact distances with a laser rangefinder. When the data are
"good" all you do by putting data into intervals is loose some precision --
although it usually makes little difference in practice when you get about 7 or
more intervals. I *would* recommend specifying your own cutpoints for the
diagnostic goodness-of-fit tests (under Model Definition | Detection function |
Diagnostics) but this is only for the gof tests and not for fitting the
detection function, so makes no difference to the acutal fit (there's lots more
about this point in the online manual).
Hope this helps,
- Len
--
Len Thomas
l...@mcs.st-and.ac.uk http://www.creem.st-and.ac.uk
Centre for Research into Ecological and Environmental Modelling
The Observatory, University of St Andrews, Scotland KY16 9LZ
Tel. (0)1334-461801 Fax. (0)1334-461800 Secretary (0)1334-461829