This core indicator evaluates the status of abundance of wintering waterbirds in the Baltic Sea region, here visualized for wading feeders. The wintering waterbirds are considered to reflect good status when at least 75% of the considered species deviate less than 30% downwards (species laying more than one egg per year) or 20% downwards (species laying one egg per year) from the baseline condition during the reference period 1991-2000.
This dataset displays the result of the indicator in HELCOM Assessment Scale 3 (Division of the Baltic Sea into 17 sub-basins and further division into coastal and offshore areas).
Attribute information:
"HELCOM_ID" = ID of the HELCOM scale 3 assessment unit
"country" = Country
"Group area" = Name of the group area
"level_2" = Name of scale 2 HELCOM assessment unit (subbasin)
"level_3" = Name of scale 3 HELCOM assessment unit
"Area (km2)" = Area of HELCOM assessment unit
"coastal" = HELCOM ID of the coastal areas
"open_sea" = Open sea assessment unit name
"Abundance" = Assessed parameter
"Threshold" = Threshold value
"Wading feeders" = Results for the category
"Wading feeders status" = Status of the indicator (“Achieve”, “Fail” or “Not assessed”)
"Surface feeders" = Results for the category
"Surface feeders status" = Status of the indicator (“Achieve”, “Fail” or “Not assessed”) "Pelagic feeders" = Results for the category
"Pelagic feeders status" = Status of the indicator (“Achieve”, “Fail” or “Not assessed”)
"Benthic feeders" = Results for the category
"Benthic feeders status" = Status of the indicator (“Achieve”, “Fail” or “Not assessed”)
"Grazing feeders" = Results for the category
"Grazing feeders status" = Status of the indicator (“Achieve”, “Fail” or “Not assessed”)
"AULEVEL" = Assessment unit level used for the indicator
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.