This dataset represents the underlying data on core indicator Abundance of salmon spawners and smolt. The indicator evaluates the status of the abundance of salmon spawners and smolt in the Baltic Sea based on salmon smolt production in rivers flowing into the sea, also making use of additional supporting data on numbers of adult spawners. Determination of whether the threshold value that determines good status is achieved is based on a comparison of estimated smolt production with an estimated potential smolt production capacity.
River-specific information provided by ICES WGBAST has been joined with river geometry by HELCOM Secretariat.
Attribute information:
"River_name" = Name of the river
"A_unit" = HELCOM scale 2 Assessment unit
"ICES_A_uni" = ICES assessment unit number
"Assessment" = HELCOM scale 2 Assessment unit
"ICES_Asses" = Number of ICES assessment unit
"Estimates_" = Estimates of wild smolt production (*1000) median value
"F90_proba" = 90% probability interval
"Method_of_" = Method of estimation (1. Bayesian linear regression model, i.e. river model, 2. Sampling of smolts and estimate of total smot run size, 3. Estimate of smolt run from parr production by relation developed in the sae iver, 4. Estimate of smolt run from parr production by relation developed in another river, 5. Inference of smolt production from data derived from similar rivers in the region, 6. Count of spawners, 7. Estimate inferred from stocking of reared fish in the river, 8. Salmon catch in river, exploitation and survival estimate)
"Data_sourc" = Data source
"Data_origi" = Data originator (natonal instiute)
"National_m" = National monitoing (YES/NO)
"Use_restri" = Use restrictions (YES/NO)
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.