British Geological Survey (BGS) Sampling Survey 1968/8: Sedimentology investigations: Humber Estuary (01/Oct/1968 to 26/Oct/1968)

Open data API in a single place

Provided by British Geological Survey (BGS)

Get early access to British Geological Survey (BGS) Sampling Survey 1968/8: Sedimentology investigations: Humber Estuary (01/Oct/1968 to 26/Oct/1968) API!

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

Dataset information

Catalog

British Geological Survey (BGS) catalog

Country of origin

United Kingdom

Updated

Created

Available languages

English

Keywords

Datasource

Official portal for European data link

Quality scoring

Dataset description

This marine sampling survey undertaken for research by University of Sheffield and the Institute of Geological Sciences (BGS) took place in October 1968 in the approaches to the Humber Estuary and River Humber on board the MV Moray Firth IV. Surveys associated with this research 1968/2 and 1968/7. The purpose was to collect sedimentological and geological structure data for use in a tidal model. Sediment samples were collected using a shipek grab and vibrocorer. These data archived by BGS. Details of the survey are contained in BGS Technical report WB/MC/69/3.

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