Data from: Predator-dependent functional response in wolves: from food limitation to surplus killing ...

• Main Authors: Zimmermann, Barbara, Sand, Håkan, Wabakken, Petter, Liberg, Olof, Andreassen, Harry Petter
• Format: Dataset
• Language: English
• Published: Dryad 2015
• Subjects: Alces alces; Moose; Capreolus capreolus; numerical response; Scavenging; faecal pellet group count; hunting success; kill handling time; social organisation; optimal foraging; present; Canis lupus
• Online Access: https://dx.doi.org/10.5061/dryad.9g2p2; https://datadryad.org/stash/dataset/doi:10.5061/dryad.9g2p2

The functional response of a predator describes the change in per capita kill rate to changes in prey density. This response can be influenced by predator densities, giving a predator-dependent functional response. In social carnivores which defend a territory, kill rates also depend on the individual energetic requirements of group members and their contribution to the kill rate. This study aims to provide empirical data for the functional response of wolves Canis lupus to the highly managed moose Alces alces population in Scandinavia. We explored prey and predator dependence, and how the functional response relates to the energetic requirements of wolf packs. Winter kill rates of GPS-collared wolves and densities of cervids were estimated for a total of 22 study periods in 15 wolf territories. The adult wolves were identified as the individuals responsible for providing kills to the wolf pack, while pups could be described as inept hunters. The predator-dependent, asymptotic functional response models ... : Killrate-dataThis file contains for each study period ("pack-winter") data associated to kill rate and prey availabilty. It is the basis for the functional response models in the article. Variables are described in the ReadMe file.weight_puppiesThis file contains data on the time of marking and weight of all wolf pups marked during winters 2000 - 2013 by the Scandinavian Wolf Research Project. Variables are described in the ReadMe file. ...