British Geological Survey (BGS) Geophysical Survey 1970/VV/7: South of Mull and Tiree (26/06/1970 to 11/07/1970)

Open data API in a single place

Provided by British Geological Survey (BGS)

Get early access to British Geological Survey (BGS) Geophysical Survey 1970/VV/7: South of Mull and Tiree (26/06/1970 to 11/07/1970) 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 geophysical survey is thought to have been carried out by Institute of Geological Sciences now British Geological Survey (BGS) for BGS, the survey took place in June to July 1970 in the Tiree area and south of Mull on board the RV Vickers Venturer. The purpose is thought to have been to collect data as part of the UK regional mapping programme. Beach sample data were collected for the marine geology unit UK regional mapping programme. No BGS survey report currently available however reference to other RV Vickers Venturer surveys undertaken by IGS can be found in IGS reports 71/16 and 73/14.

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