Hi all,
I have been running the same distance analysis every few years to update density estimates to include the most recent dataset. I have updated the code as things have been deprecated (e.g., convert.units, dht.group, etc). Besides that the structure of my code has not changed. This year when I ran the analysis using my most recent dataset I noticed that the density estimates were really far off from what they should be. I looked into it more and I am pretty sure it is something on the backend of the ds function where sample area is not being calculated like it should be and the Sample.Area and Area are coming out the same (it is a point transect and I put in 0 for Area in a flat file). In prior years the Sample.Area has always been calculate based on the Regions, but now it is the same exact as the Area column. Any insight as to why this is happening would be greatly appreciated.
Thanks!
Maggie