Survey : EHOLT/05/1956 (part of Historic Arctic Survey Series)

Open data API in a single place

Provided by Marine Environmental Data & Information Network

Get early access to Survey : EHOLT/05/1956 (part of Historic Arctic Survey Series) API!

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

Dataset information

Catalog

Marine Environmental Data & Information Network catalog

Country of origin

United Kingdom

Updated

Created

Available languages

English

Keywords

Datasource

Official portal for European data link

Quality scoring

Dataset description

This survey was undertaken by Cefas as part of the Historic Arctic Survey Series; *Gadus morhua* (Atlantic Cod) stocks in the Barents Sea are currently at levels not seen since the 1950s. Causes for the population increase last century, and understanding of whether such large numbers will be maintained in the future, are unclear. To explore this, we digitised and interrogated historical cod catch and diet datasets from the Barents Sea. Data includes temporal and spatial information, cod catch data and length distributions, and hydrographic data. Survey took place between 19/07/1956 and 21/08/1956 on Ernest Holt Equipment used during this survey : - Otter Trawl 78ft Granton with shrimp netting cover Survey operations were undertaken on 27 stations 15 different species were caught on this survey

European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.

190K+

indexed dataset pages

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.

api.store Built by Apitalks

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

About api.storePrivacy Terms of Service