Collection of the eider duck population in the Lower Saxony Wadden Sea in summer (Mauser) 1991. In the Wadden Sea of Lower Saxony, since 1986, the eider duck stocks have been recorded twice a year during a tide from the aircraft. These are the Mauser (July/August) and wintering stocks (January/February). The counts take place in coordination with Schleswig-Holstein. The data is part of the Trilateral Monitoring and Assessment Program (TMAP). Monitoring of migratory birds (Eiders) in the Wadden Sea of Lower Saxony in summer (moulting) 1991. The population of migratory birds (Eiders) in Lower Saxony’s Wadden Sea is biyearly determined by aerial flight since 1986. Counts are carried out in July/August during the moult and in January/February and are coordinated with Schleswig-Holstein. The data are part of the trilateral monitoring and assessment program (TMAP). Collection of the eider duck population in the Lower Saxony Wadden Sea in summer (Mauser) 1991. In the Wadden Sea of Lower Saxony, since 1986, the eider duck stocks have been recorded twice a year during a tide from the aircraft. These are the Mauser (July/August) and wintering stocks (January/February). The counts take place in coordination with Schleswig-Holstein. The data is part of the Trilateral Monitoring and Assessment Program (TMAP). Monitoring of migratory birds (Eiders) in the Wadden Sea of Lower Saxony in summer (moulting) 1991. The population of migratory birds (Eiders) in Lower Saxony’s Wadden Sea is biyearly determined by aerial flight since 1986.
Counts are carried out in July/August during the moult and in January/February and are coordinated with Schleswig-Holstein.
The data are part of the trilateral monitoring and assessment program (TMAP).
Build on reliable and scalable technology
FAQ
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.