Phyto and zooplankton densities in Lake Sulzkar were comparable to eutrophic lowland lakes in 2018. Non-local Elritzen exerted a strong feeding pressure on the zooplankton. Between 2016 and 2018, 45000 Elritzen were fished and relocated. In October 2018, it was possible to pump out the Sulzkar Sea, calcareously and eliminate the fish stock.
After the water level of Lake Sulzkar was lowered by a siphon pipe in August 2018, the residual volume (max. 4 m depth) showed a significant stratification with clinograde profiles of the temperature and pH, as well as a significant increase in the ion content from 2 m depth. The oxygen profile was heterograde with a maximum of 3 m depth. Phyto and zooplankton densities in Lake Sulzkar were also comparable to eutrophic lowland lakes in 2018. Non-location Elritzen (Phoxinus phoxinus) exerted a strong feeding pressure on the zooplankton. The biomass of the phytoplankton (4 mg per litre) was more than thirty times higher than that of the zoo plankton. Between 2016 and 2018, a total of 45000 Elritzes were caught and resettled with raisins. About 20,000 animals were brought to the fish farming of the town of Zell am See for further breeding. The stocking fish in the 1970s had come from Lake Zell, where they disappeared in the 1980s. After installing the suction line, the lake could be lowered by a maximum of 3 m before the physical limit of lifting over a terrain edge was reached and the water column was demolished. In October 2018, the lake was finally drained with three dirty water pumps. After that, the approximately 500 1500 remaining in the remaining volume were killed with a total of 750 kg of burnt lime. Fishing was not possible because of the unstable mud masses.
Build on reliable and scalable technology
Frequently Asked Questions
Some basic informations about API Store ®.
Operation and development of APIs are currently fully funded by company Apitalks and its usage is for free.
Yes, you can.
All important information such as time of last update, license and other information are in response of each API call.
In case of major update that would not be compatible with previous version of API, we keep for 30 days both versions so you will have enough time to transfer to new version. We will inform you about the changes in advance by e-mail.