z-logo
Premium
Pelagic food web response to whole lake N fertilization
Author(s) -
Deininger A.,
Faithfull C. L.,
Karlsson J.,
Klaus M.,
Bergström A.K.
Publication year - 2017
Publication title -
limnology and oceanography
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 1.7
H-Index - 197
eISSN - 1939-5590
pISSN - 0024-3590
DOI - 10.1002/lno.10513
Subject(s) - zooplankton , phytoplankton , pelagic zone , food web , biomass (ecology) , environmental science , productivity , human fertilization , nutrient , ecosystem , ecology , oceanography , biology , agronomy , macroeconomics , economics , geology
Anthropogenic activities are increasing inorganic nitrogen (N) loadings to unproductive boreal lakes. In many of these lakes phytoplankton are N limited, consequently N fertilization may affect ecosystem productivity and consumer resource use. Here, we conducted whole lake inorganic N fertilization experiments with six small N limited unproductive boreal lakes (three control and three N enriched) in an area receiving low N deposition with one reference and two impact years. Our aim was to assess the effects of N fertilization on pelagic biomass production and consumer resource use. We found that phytoplankton primary production (PP) and biomass, and the PP: bacterioplankton production ratio increased after fertilization. As expected, the relative contribution of phytoplankton derived resources (autochthony) that supported the crustacean zooplankton community increased. Yet, the response in the consumer community was modest with autochthony only increasing in one of the three major zooplankton groups and with no effect on zooplankton biomass. In conclusion, our findings imply that newly available phytoplankton energy derived from N fertilization was not efficiently transferred up to zooplankton, indicating a mismatch between producer energy supply and consumer energy use with potential accumulation of phytoplankton biomass as the result.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here