The original version of this dataset contained lithologies interpreted as representing a mineral resource for mineral extraction. Collated on a County by County basis as part of the former Office of the Deputy Prime Minister (ODPM) Mineral Resource Information in support of National Regional and Local Planning between 1994 and 2006. A primary objective is to produce baseline data in a consistent format that can be updated, revised and customised to suit planning needs, including Mineral Local Plans and Regional Planning Guidance, as well as those of industry. The BGS Mineral Resource data does not determine mineral reserves and therefore does not denote potential areas of extraction. Only onshore, mainland mineral resources are included in the dataset. This dataset has been produced by the collation and interpretation of mineral resource data principally held by the British Geological Survey. The mineral resource data presented are based on the best available information, but are not comprehensive and their quality is variable. The dataset should only be used to show a broad distribution of those mineral resources which may be of current or potential economic interest. The data should not be used to determine individual planning applications or in taking decisions on the acquisition or use of a particular piece of land, although they may give useful background information which sets a specific proposal in context. During 2011-2012 revisions were made to areas of the resource linework. These changes were made as a result of new research and release of a new version of DiGMap (v5). This work was on an ad hoc basis but affects all resource layers. The paper maps were not re-released with this data update.
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.