2012 - 2012 Centre for Environment, Fisheries & Aquaculture Science (Cefas) English Channel Gillnet Pollack Survey 2011/12 - Fisheries Science Partnership
Open data API in a single place
Provided by Government Digital Service
Get early access to 2012 - 2012 Centre for Environment, Fisheries & Aquaculture Science (Cefas) English Channel Gillnet Pollack Survey 2011/12 - Fisheries Science Partnership API!
This work was carried out as part of the Fisheries Science Partnership (FSP),
a Defra-funded collaborative programme of scientific research between the UK
fishing industry and scientists.
Fishermen that normally switch from netting in the western channel to netting
in the southern north sea in early spring, wanted to explore the viability of
wreck netting for pollack within the channel. The fishermen theorised using a
large mesh net in the channel, would be a feasible alternative to fishing the
North Sea, were the minimising of the bycatch of cod is a problem.
From late February through to mid March 2012, 100 hauls were observed by Cefas
scientists. Catch varied from one wreck to the next. But overall the Jubilee
Pride successfully demonstrated the feasibility of conducting a targeted
fishery for pollack. Catches were dominated by pollack and bib. Pollack
accounted for nearly 90% of the total landed weight of fish. Bib on the other
hand was mostly discarded, accounting for just 0.7% of the total landed weight
of fish. After pollack, the next biggest landing was ling accounting for 6% of
the total landed weight of fish. The contribution of cod to the total landed
weight of fish was just over 1% (just 20 individuals taken throughout the
survey).
The bycatch of sensitive species such as marine mammals and sharks was
minimal, with no mammals caught and just a few tope and spurdog.
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.