Kent and Essex IFCA whelk pot hole size pilot study 2012

Open data API in a single place

Provided by Marine Environmental Data & Information Network

Get early access to Kent and Essex IFCA whelk pot hole size pilot study 2012 API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
Created
Available languages
English
Keywords
Quality scoring

Dataset description

In response to a dramatic increase in the number of whelk pots being set in the district in 2011, KEIFCA introduced an emergency byelaw limiting the number of pots per vessel to 300. As part of the research into other potential management methods the industry suggested exploring the possibility of the drain hole in a pot being used as an escape hole to reduce the number of undersized whelks caught by the gear. Commercial Whelk pots with varying sizes of drain hole were shot in strings of ten and left to soak for 48 hours, then hauled and redeployed for a second period of 48 hours. The resulting whelks from each pot were measured along their widest and shortest axis', the results were then inputted into a spreadsheet and statistical analyses carried out on the data. The results showed a small positive correlation between hole size and the shell height of the whelks in that pot. This research is currently being expanded via a joint CEFAS/KEIFCA/Sussex IFCA project.
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks